Skip to content
Atoi
Open Atoi

Connect

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

Connections, Channels, and MCP clients enter one Thread01Connectionlinked service02Channeloutside conduit03MCP clientcoding clientThreadone conversationinputs stay visibleoutside inputs arrive without becoming separate homesConnections, Channels, and MCP clients enter one Thread01Connectionlinked service02Channeloutside conduit03MCP clientcoding clientThreadone conversationinputs stay visibleoutside inputs arrive withoutbecoming separate homes
Connections, channels, 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.ChannelsContinue a thread on Telegram, answer simple asks there, and get updates in Slack.MCP and pluginsGive Codex, Claude Code, Cursor, or Pi governed access to your projects and tasks, and install the Atoi plugin.

Connect is what Atoi can reach and how it reaches you: the models it thinks with, the services it acts in, the channels 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. Channels let a thread continue on Telegram or Slack. MCP and plugins give a coding client governed access to your projects and add tools to Atoi.

Recurring work on a schedule lives under Automations.

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