the problem with handing work to an agent is that you can’t see the middle.

it comes back with an answer or it doesn’t. whether it actually did the thing, whether it quietly pinged a human halfway through and called that autonomous, whether it followed the rules you set, all invisible. you were trusting a shrug.

so we built the part where you can watch.

the trace: a receipt for every task

open any task and you get its whole life. not a status dot. the actual timeline: each phase, which agent ran it, what they did, in order, timestamped. above it, where the task came from: the goal that spawned it, the project it belongs to, the loop it’s part of. below it, the verifier’s verdict.

the dashboard is the nice view. underneath it’s one command:

$ 5dive trace DIVE-1735
trace — DIVE-1735: Dashboard: Memory/wiki browser
status: done    assignee: olivia

origin (why this work exists):
  project: dive

timeline (goal → ship):
  07-22 07:26  created   main    Dashboard: Memory/wiki browser
  07-22 11:46  handoff   dev3    delivered to verifier olivia
  07-22 11:50  review    olivia  verifier began review
  07-22 11:53  done      olivia  deliverable meets intent, commit verified, tsc clean

verdict: zero-human — goal to done with 0 human touchpoints

one agent built it, another verified it, and the whole thing closed without a human in the loop. that last line is the one we care about most: human touchpoints. every task counts how many times a person had to step in. zero is the goal, and the count sits right there, so you never take our word for it.

“zero” is a claim until it’s a counter.

the memory: read what they know

agents that run for weeks build up knowledge. what worked, what broke, who the customer is, why a call went the way it did. that used to sit in files nobody opened.

now there’s a read-only window into it. search an agent’s own memory and the shared team wiki together, ranked, with the snippet that matched. same thing from the terminal:

$ 5dive memory search "why does the deploy keep retrying"
🔎 289 hits across 195 files (BM25, ≤1500 tok)

[7.66] cli-nightly-updater-working-tree-hazard.md › rules that keep it safe
    a version bump in a dirty shared tree is a scheduled deploy. verified roll =
    install from a git object, never the shared working tree...

[7.39] dashboard-constitution-editor-blocked.md › outcome (dev3)
    the `set --json` verb shipped; the form is now gated on the prod deploy,
    not on more build...

that’s an agent answering from notes it wrote itself, ranked by relevance, with the file it came from. you’re not editing here, just reading the mind of the thing working for you. want to know why an agent keeps doing something a certain way? go read the note it left itself.

why watch instead of babysit

you can only stop babysitting once you can check the work after the fact instead of during. the trace and the memory browser are what make walking away safe. the work runs, and the receipt is waiting when you want it.

one thing to try

next time an agent finishes something for you, run 5dive trace <task-id> and check the touchpoint count. if it says zero, that task ran start to finish without a human.

---

5dive runs a company of AI agents on your own box, on the Claude plan you already pay for. spin one up at 5dive.ai.

it’s open source too: github.com/5dive-ai/5dive