FAQ and glossary
Resolve common product questions and use Atoi's canonical nouns consistently.
#Frequently asked questions
#Is Atoi a collection of agents?
No. Atoi presents one accountable product voice. It can use models, skills, connections, computers, and durable execution without asking you to manage an internal roster.
#Do I need a project before I can ask something?
No. Start from Library and use Ask Atoi. Add a Project when shared context or continuity improves the work.
#Is a task another conversation?
No. A conversation carries intent and decisions. A Task carries durable execution state and proof. The task should remain reachable from the conversation that caused it.
#Does connecting a service let Atoi do everything in it?
No. A Connection represents an authorized integration with explicit provider scope. Individual actions can still require an ask or approval.
#Is a Computer my current device?
Not necessarily. A Computer is an execution target: local, paired, hosted, or otherwise connected. Read its current status before assigning work.
#Does Publish invite a collaborator?
No. Publish creates a public share. Invite grants a person access to private shared context. See Sharing, invitations, and publishing.
#Canonical glossary
| Term | Meaning |
|---|---|
| Atoi | The single accountable product voice |
| Library | The generated signed-in root for orientation and return |
| Conversation | The transcript and narrative record of intent, asks, decisions, and results |
| Project | Durable shared context: source, instructions, documents, conversations, and accountable work |
| Task | Durable work with explicit state and a receipt |
| Ask | A focused question that requests missing human judgment |
| Approval | Authorization for a known consequential action |
| Receipt | Inspectable result evidence such as changes, checks, artifacts, and proof |
| Connection | An authorized external integration or capability source |
| Computer | An execution target Atoi can use when connected and allowed |
| Skill | Reusable instructions for how Atoi should perform a class of work |
| Channel | An outside communication conduit such as Telegram; not a new workspace |
| Publish | Create an explicitly public representation of selected content |
| Invite | Grant a person access to private collaborative context |
Use the human-facing singular Connection, even where a machine-facing CLI command remains atoi connector for compatibility.
Verification sources
- docs/decisions/2026-08-20-atoi-glossary.md
- docs/decisions/2026-08-23-organizing-model.md
- docs/decisions/2026-08-23-settings-grammar.md
Was this useful?