Akili OS documentation
One engine with three faces — Build for software, Motion for video, Work for documents and data. Everything runs on your machine; only model calls leave it.
What you get
| Face | What it does |
|---|---|
| Build | Writes, runs, tests and ships software. It reads before it writes, verifies before it claims, and takes a checkpoint you can undo. |
| Motion | Video as structured, editable scene data — authored, verified and exported to MP4. A scene is revised by id, not regenerated. |
| Work | Real .docx, .xlsx, .pdf and .csv, research with citations, and email triage. Office is not required. |
All three share one provider list, one budget, one policy engine, one plan view and one audit log. Learn a control once and it applies everywhere.
The models
Akili Fundi (Code) is the build model: long agent runs, refactors and migrations. Akili Core is the everyday model: chat, search and quick edits. Both carry a 1,000,000-token context window and you can switch between them mid-conversation.
If you would rather use your own provider account, you can — see Bring your own.
Staying in control
- Budgets — per-conversation and per-day caps that stop a run mid-flight rather than reporting the spend afterwards.
- Policy — disable whole tools or block command patterns; a team policy in the repo can only tighten a person's own, never loosen it.
- Audit — every tool call, timestamped, in
.akili-code/audit.log.