Execution tracking for humans + AI agents

DoneOS

One place to decide, delegate, execute, and prove what got done.

Replace scattered task lists and agent transcripts with a shared execution graph, attributable history, and status that writes itself.

Flutter app MCP server Slack updates
DoneOS Focus Stack showing human and AI agent workDoneOS attributed execution activity Agent running Event recorded
One queueThree-item focus limitHuman + agent attributionOne daily Slack message
A shared operating layer

Task managers track lists. DoneOS tracks execution.

The work has one current state, no matter whether a person or an agent moves it. The event ledger keeps the reason and the actor.

Human work

Decide what matters now

Shape the queue, commit a WIP-limited Focus Stack, and move work with deliberate commands.

Agent work

Delegate without losing control

Give agents scoped MCP access, renewable leases, and the same execution contract as the app.

Shared evidence

Know what actually happened

Every accepted transition records the actor, time, state change, and durable execution event.

One execution loop

From outcome to evidence.

  1. 01Set the outcome
  2. 02Commit the focus
  3. 03Human or agent executes
  4. 04Evidence writes the status
DoneOS shared queue ordered for human and agent work
Queue + Focus

Separate what matters from what is merely available.

Queue holds ready work. Focus is a hard commitment capped at three. Humans and agents see the same priorities without duplicating state.

  • Ranked work linked to goals and key results
  • WIP-limited Focus Stack
  • Human and agent ownership in one view
Explore the execution model
MCP-native execution

Agents get tools, boundaries, and an audit trail.

An agent can inspect goals, claim work, heartbeat a lease, complete or block an item, and summarize status. It never writes directly to the mobile database.

Explore agent execution
doneos / build-agentLIVE
list_work_items3 ready
start_agent_runlease 05:00
send_work_item_to_reviewevent appended
scoped key · attributable writes · idempotent retries
DoneOS daily Slack status generated from execution events
Slack status publishing

The standup is a view of reality, not another writing task.

Done, active, and blocked work roll into one daily message. Agent output stays labeled, and DoneOS updates the same post as execution changes.

  • Select the workspace channel
  • Schedule or publish on demand
  • Update one message from the event ledger
See Slack status automation
Private beta

Stop reconstructing what happened.

Run the work once. Let DoneOS preserve the evidence for people, agents, and the next status update.