Skip to content
AtoiDocumentation
Use Atoi

Connect

Models, connections, messaging, and plugins: what Atoi can reach and how it reaches you.

Connections, messaging, and MCP clients enter one thread01Connectionlinked service02MessagingTelegram or Slack03MCP clientcoding clientThreadone per workspaceinputs stay visibleoutside inputs arrive without becoming separate homesConnections, messaging, and MCP clients enter one thread01Connectionlinked service02MessagingTelegram or Slack03MCP clientcoding clientThreadone per workspaceinputs stay visibleoutside inputs arrive withoutbecoming separate homes
Connections, messaging, and automations all arrive in the Thread you already use.

Guides

Models and keysConnect a provider with your own key or subscription, enable models, and pick a default.ConnectionsAuthorize services, MCP servers, and browser sessions for Atoi to use.MessagingContinue a thread on Telegram, answer simple asks there, and get updates in Slack.MCP and pluginsInstall the Atoi plugin in Claude Code, Codex, or Cursor, and give that client governed access to your work through the Atoi CLI

Connect is what Atoi can reach and how it reaches you: the models it thinks with, the services it acts in, the messaging links it answers on, and the clients that drive it.

Each connection keeps its own status, errors, and receipts. A green badge or a delivered message proves that one thing and nothing more.

#What Atoi thinks with

Models is where you bring your own provider keys or subscriptions and choose a default. Atoi runs on your keys, never on a shared pool.

#What Atoi reaches

Connections are the services you authorize Atoi to read or act in. Messaging lets a thread continue on Telegram or Slack. MCP and plugins bring Atoi into a coding client, with governed access to your projects.

Recurring work on a schedule lives under Automations.

Read Models first, since nothing runs until a model is connected.