Overview

Atoi is one thread for coding agents, projects, and the work between them. It is a product shell for planning in chat, handing implementation to durable execution, reviewing changes and previews, and keeping project state visible when the terminal disappears.

One product loop

Most work begins as a conversation. Name the outcome, supply the source material that matters, and make the next decision legible. A thread can remain a plain conversation, become a group thread, collect project context, or produce durable tasks. Those are properties of the work around the thread, not different kinds of chat.

When a request requires repository inspection, file changes, tests, builds, or another lasting implementation result, Atoi uses a separate product-owned runtime. Chat remains Convex-native and streaming; durable implementation runs through the in-repository runtime under packages/mono. The result returns to the product as task state, approvals, artifacts, changes, checks, and proof. There is no top-level Code page to manage.

Projects hold continuity

Projects are workspaces rather than alternate chat modes. Each project brings together its instructions, files, documents, runtime binding, associated threads, and task ledger. The main project lenses are Home, Threads, Tasks, and Views.

• Home gives the project identity, shared resources, recent threads, and routes to the rest of the workspace.
• Threads lists every conversation associated with the project.
• Tasks keeps durable work and its receipts addressable after the conversation moves on.
• Views applies saved lenses to project material so recurring review shapes do not require manual reconstruction.

Tagging a project in the composer associates the current thread through the thread–project join. A thread can be associated with more than one project, and removing an association does not convert it into a different object.

Surfaces at a glance

The web app is the broadest product surface. It includes the home orchestration thread, project workspaces, inbox, search, global views, For you, automations, channels, skills, customization, and provider settings.

The iOS and macOS apps are native Apple clients backed by the shared Atoi product state. The iOS release lane ships through TestFlight. The Android app is a native Compose client with chat, projects, groups, inbox, search, task detail, channels, memory, and settings surfaces.

The terminal has two related entry points. The Atoi TUI is a keyboard-first product cockpit over the operator read model. The atoi CLI exposes explicit commands for account connection, projects, workspaces, threads, tasks, search, inbox, automations, MCP, and diagnostics. Runtime sessions remain part of Atoi’s execution substrate rather than a separate end-user product.

The common rule is durable identity: continue the same thread, inspect the same task, and preserve the same receipt regardless of where you return.