The core ways Atoi helps beyond plain chat while staying inside the thread.
Planning, search, code work, file handling, memory, and previews are the main capability lanes people feel first.
Capability map
| Capability | What it helps with | Notes |
|---|---|---|
| Planning | Turning rough work into an executable thread | Best before handing work to a durable agent lane |
| Search | Fresh facts, citations, live comparisons | Best when the thread depends on current information |
| Code | Reading, editing, patching, debugging | Use when structure, proof, and reviewability matter |
| Previews | Inspecting the result of agent work | Useful before deciding whether a run is done |
| Create | Drafts, transforms, polished outputs | Best when the final artifact matters as much as the reasoning |
| Files | Grounding a conversation in uploaded material | Useful for documents, code, project context, and image-aware work |
| Memory | Reducing repeated setup over time | Most helpful when preferences stay stable |
What this is not
Capabilities are meant to stay close to the work. Atoi tries to avoid turning every helpful action into a separate noisy control panel.
Use the lightest capable path first, then reach for more structure only when the task actually asks for it.