Agent 01device sync
runningGive it the vision.
Keep the outcome.
Kogni turns a human goal into a durable mission, coordinates agents against explicit acceptance criteria, and keeps executing, verifying, and repairing until the result is met—or an honest stop condition needs you.
Ship the account-linked KogniOS experience and prove every acceptance criterion.
5 / 7 verified
ManagerPlan · delegate · verify · repair
Agent 02repository checks
verifyAgent 03web acceptance
readyDescribe the result. Review what “done” means.
No work starts during the briefing. The human sees the exact scope, authority, assumptions, non-goals, budget, deadline, and stopping rules before authorizing execution.
- 1
“Here is the vision…”The Manager reads project context and resolves only consequential ambiguity with focused questions and forms.
- 2
vision.readyYou review measurable criteria, constraints, decisions, authority grants, and the evidence each result must produce.
- 3
mission.runningKogni plans, delegates, checks, repairs, and resumes after interruption without asking you to reconstruct the work.
More than a long-running chat.
Model context is temporary. Mission state, repository truth, authority, and evidence are not. Kogni keeps those layers separate so agents can be replaced without losing the work.
Vision briefing
The Manager asks only the questions that materially change the result, then turns your answers into a reviewable contract: outcome, acceptance criteria, constraints, authority, budget, deadline, and stop conditions.
Durable missions
Execution survives process restarts and disconnected browsers. Tasks, leases, evidence, blockers, amendments, and verification history live in durable state—not in one model context window.
Concurrent agents
The Manager decomposes criteria into bounded assignments. Agents work in isolated snapshots and exchange scoped checkpoints, claims, events, and handoffs without sharing one undifferentiated prompt.
Kogni-native repositories
Git-compatible object storage gives the control plane exact commits, task branches, compare-and-set publication, and deterministic server-side checks. GitHub can remain an optional edge rather than the system of record.
Account-to-OS sync
A signed, monotonic account manifest tells each authenticated KogniOS image which project and exact revision it may hydrate. Interrupted sync, rollback, equivocation, and cross-account paths fail closed.
Governed execution
Shell, files, browser, network, publication, deployment, spend, and destructive actions are separate authorities. The Manager can continue autonomously without silently inheriting permission to do everything.
The control plane remembers. KogniOS does the work.
Identity and orchestration live with the account. Files, tools, and execution remain inside permission-scoped KogniOS workers connected outbound.
Kogni control plane
Owns durable intent and coordination without becoming a shared root shell.
- Vision contracts and mission state
- Manager planning, leases, events, and evidence
- Native repository metadata and verified publication
- Scoped collaboration and optional elastic admission
KogniOS workers
Authenticate to the account, hydrate exact project state, and execute with bounded authority.
- TUI QR or manual-code device activation
- Signed account manifest and atomic workspace sync
- Sandboxed shell, files, browser, and local context
- Outbound encrypted sessions with revocation