Baari walkthrough: daily work, dashboard and threads
The approved revised walkthrough introduces Baari, shows its read-only local
operator dashboard and repository threads, then follows an invoice CSV task
through architecture, bounded work, checks, reconciliation and a shared worklog.
It closes with the product URL, installation and baari explain.
The isolated Python service, thread actors and dashboard registry are fictional demo fixtures using released Baari v0.27.1 commands. This is an explanatory demo, not a production billing integration. The video combines captured command output with explanatory title cards; it does not claim to record Claude, Codex or Gemini executing autonomously.
The narration source is narration.json. Voice: AI-generated Aiden, using the approved relaxed conversational instruction from the existing Kuickr voice-production guide. Captions follow the same script.
The work item references governing architecture, one authorization boundary and
CSV-export acceptance. The demonstrated sequence is work start, work check,
work reconcile, work finish, and work log. Wave membership is explicit.
A workflow finish is not a commit or release.
105.44 seconds · 1920 × 1080 · AI-generated Aiden voice. Sentence captions use proportional timing, not forced alignment.
Approved by Nauman on 17 November 2026.
Transcript
Meet Baari
Baari is a local first tool for developers and coding agents. It connects bounded work, architecture and handoffs, so the next session knows where to begin.
See the coordination
The local dashboard shows replies and repository checks in one read only view. It reads the same records as the CLI, so you can see what needs attention without giving it control of your agents.
Keep the conversation
Threads name the next owner and the next action. Revision checked replies preserve the conversation. Claude, Codex and Gemini can follow the same repository contract.
Architecture sets the boundary
Here is a small example: download an invoice as a CSV. The architecture keeps authorization in the service and formatting in the exporter. The work item names that boundary and its acceptance checks.
Start bounded work
Start the item and Baari returns the handoff. The wave groups the delivery. It does not create another ticket. Missing architecture or acceptance is a blocker, not an invitation to keep building.
Check the actual behaviour
Now run the declared checks. This demo verifies the CSV and rejects access to another customer’s invoice. The receipt belongs to the current inputs, so changing those inputs can make the proof stale.
Reconcile the facts
Reconcile joins the available facts and reports gaps. It reads by default. Finish records the verified outcome, but it does not commit, release or turn local success into a shipped claim.
Leave a useful handoff
The worklog brings the activity and evidence together. Claude, Codex or Gemini can pick up from the same repository records. Less ceremony, with the architecture and proof still underneath.
Start with one repository
That is Baari: bounded work, visible coordination and a shared history. Visit baari.kuickr.co, install with Homebrew, and start with baari explain.