Aius can work with the services and data you already use: GitHub, Linear, Notion, Slack, a database, a calendar and many more. It reaches them through connections (MCP servers). You don’t install or configure anything yourself: tell the agent what you want to connect.

Connect something

Ask in plain words, for example:
  • “Connect GitHub so you can read the issues for this project.”
  • “Connect our Postgres database at localhost so you can query the orders table.”
  • “I’d like you to read my Notion notes.”
The agent then:
  1. Looks for a connection in the public MCP registry, and on the web when the registry has nothing suitable.
  2. Tells you what it found, who runs it and what it can read or change, and what you need for it, such as an access key and where to get one. It asks in the conversation only for things that are not secret, such as the name of your workspace.
  3. Asks your approval before it connects, showing exactly what will run on your computer or which address it will connect to.
  4. Asks you to paste each key or password into a hidden field in the terminal (see Keys and passwords).
  5. Connects it, checks it with one call that only reads, and uses it straight away, in the same conversation.
You don’t have to ask first. When your question needs data from a service or database you mention or plainly use, such as a CRM, analytics, ads, Postgres, Notion, Google Sheets, Stripe, HubSpot or Slack, the agent proposes connecting it and leads you through it: what the connection can read or change, numbered steps to create the access key with read-only permissions in that service, and the hidden field to paste it in. It checks the connection with one read-only call and then answers your question with it. If something fails, such as a rejected key or missing permissions, it says what went wrong and how to fix it. It connects nothing until you approve the connection. The agent prefers the service’s own connection, where you sign in with the service and nothing runs on your computer. When only someone else’s connection is available, it tells you who runs it, because that server sees everything that passes through it, and it gives it no key without your yes. Some connections are small programs that run on your computer instead; the approval prompt shows the exact program before anything starts. For a database on your computer or your network, the agent picks one of those, since a hosted connection could not reach it. Each service gets a connection of its own, named after it. The agent replaces an existing connection only when you ask, and the approval prompt then says which one it replaces. Once connected, tools the service marks as read-only run freely. Any other tool may change data in the service or send data out, so it asks for your approval first; see Approvals.

Google Drive, Sheets and Docs

Google lets only registered apps sign in to Drive, Sheets and Docs. So the agent first offers the simple ways: download the files into your project folder (File > Download for a Sheet or Doc), or read files such as CSV and Excel from the Google Drive for desktop folder on your computer. Sheets and Docs appear in that folder only as links, so download those first. If you want a live connection, it walks you through registering an app in Google Cloud and connecting it.

Signing in

Many services ask you to sign in and approve access. Aius opens the sign-in page in your browser and finishes connecting as soon as you approve. When no browser can open, for example on a remote computer, the sign-in link appears in the conversation and in a notice, and is copied for you. Open it in a browser on the computer that runs the TUI within five minutes. If the link runs out, ask the agent to connect the service again.

Keys and passwords

Once you approve a connection, Aius asks for each key or password it needs in a hidden field in the terminal: the name of the key, where to get it, and a field that shows a dot for each character and how many there are, never the key itself. What you paste goes straight to a private file on your computer that only your user can read. It is never written into your AIUS settings, and it never goes into the conversation: the agent, the model, AIUS Light and the logs never see it. Don’t paste a key into the conversation itself; everything you type there is sent to the model. When you follow the conversation in the browser, AIUS Light says which key to paste in the TUI on which computer. There is no field for it in the browser. Keys given to a connection are also left out of the copy of the conversation that AIUS Light keeps and your other computers receive.

Connections (/mcps)

Connections shows every connection, in the same order and with the same states in the terminal and in AIUS Light: connected, waiting for you to sign in (Needs sign-in), turned off (Off) or failing. There are three places to see them: In an AIUS Light conversation, /mcps lists the connections of the computer the conversation runs on.

In the terminal

Type /mcps to open the list. Add a connection… at the end of the list asks what you want to connect and hands the request to the agent. AIUS Light, the connection to the web platform, comes with your AIUS sign-in. It is always on and can’t be removed. AIUS Connect brings in what you connected on aius.co, such as your Gmail. Select it and press Enter, then sign in with your aius.co account in the browser. Aius keeps it on from then on. You can also manage connections in the conversation: “What’s connected?”, “Turn off the Slack connection”, “Remove Notion”.

Connections in AIUS Light

Connections in the left rail of AIUS Light, under Projects and Conversations, lists the connections of your computers that are on now, with how many there are. A connection on two computers shows once, with the better of its two states. Each one has the same name, order and state as in /mcps and the terminal’s sidebar. A computer that is off shows none of its connections until it is on again. The Connections page lets you search them by name, address or computer, and show only those that are connected, need attention (waiting for sign-in, or failing) or are turned off. Select a connection to see what it is (an online service and its address, or a program on your computer), its state on each computer and in which folders, and the requests that change it, such as signing in again or removing it, ready to copy into the TUI on that computer. AIUS Light shows only the address’s host or the program’s name, never a key or the rest of the address. A connection to a service Aius knows, such as slack_personal or google_ads, shows that service’s logo, and its page names the service, who makes it and a link to its site. Any other connection shows its initials on a colour of its own. The page has a tab for each kind of connection, sorted by what Aius reaches rather than how:
  • Computers: every computer, server or cloud instance Aius runs on, on or off, with its system, AIUS version, folders and how many connections it has. A computer that is off shows when it was last seen.
  • Apps & services, Databases (Postgres, Snowflake, BigQuery…), Files (Google Drive, Dropbox, Box, OneDrive) and AI models: the connections of that kind.
  • Sign-ins: how each connection signs in and where that is kept, on which computer: a browser sign-in in AIUS’s sign-in store, a key, token or credentials file given in the connection’s settings (from AIUS’s private secret files when you pasted it into the TUI), a program that keeps its own sign-in (such as a browser session or its own token files), or nothing. Light shows which kind of credential a connection uses, never the key or token itself.
  • Data map: each computer that is on, with what it reaches, grouped by kind.
One service can have several connections, such as Apollo online (apollo) and a program on your computer that uses Apollo’s API (apollo_local). They show together under the service, each as its own row with its own state and sign-in, and each connection’s page lists the others. A connection named the same on two computers but set up differently shows each computer’s way on its row. One connection can also hold several accounts, such as a Google connection that reaches a personal and a work account and picks one for each request. Light doesn’t know which accounts a connection holds, so a connection’s page says the account is not reported rather than guessing one from its name. A connection’s page also names its kind, how it signs in and its account. Terminals older than 2026-11-21 don’t say how a connection signs in; their connections show “Not reported by this computer’s TUI yet” until they update. Add connection lists the services Aius knows, with their logos, and you can search them by name, maker or kind (CRM, finance, data…), or take any other name. Aius sets a connection up on your computer, so Light gives you the request to paste into the TUI there; the agent then does the rest as described in Connect something.

Change how Aius works

Your preferences are changed the same way, by asking:
  • “Always ask before running shell commands.”
  • “Use Claude Opus 5.5 as the default model.”
  • “Read notes.md as instructions in every conversation.”
  • “Don’t share conversations automatically.”
The agent shows the change for your approval and saves it for every folder. Changes to a connection apply immediately; other settings apply the next time you start the TUI. To switch the model for the conversation you are in, ask the agent or use /models. Models always come from the AIUS catalog; see Models.