Section 01
What this guide is
This guide explains what the Agent Bus is today from the human operator's point of view.
Section 02
The plain truth first
Agent Bus is not yet a finished user-facing app.
Section 03
What Agent Bus is meant to become
Agent Bus is the local-first coordination layer for human and AI work.
Section 04
What exists today
The MVP currently includes these implemented pieces:
Section 05
What does not exist yet
These pieces are not live yet:
Section 06
What the current CLI can do
The current CLI is mostly for inspection and export.
Section 07
What Redis means right now
Redis Streams are the intended local broker shape.
Section 08
What using Agent Bus looks like today
Today, the practical path still goes through LifeHub Command Interface.
Section 09
Where Codex and Hermes fit today
Codex and Hermes currently attach through controlled local dispatch, not through live queue daemons.
Section 10
Current task lifecycle model
The implemented lifecycle is:
Section 11
What delegation means
Delegation is not free-form agent chat.
Section 12
What deadletters mean
A deadletter is a safe failure record.
Section 13
What you can ask ChatGPT to do right now
Useful current commands are conversational:
Section 14
The missing first user experience
The next thing you likely need is not browser wake yet.
Option A: Demo seed script
A script that creates sample agents, tasks, delegation, results, and deadletters in memory so you can run inspection commands and see the model.
Option B: Real task-submit CLI
A command like:
Option C: Redis-backed persistence adapter
A real Redis store behind the coordinator, so state survives process boundaries.
Option D: Tiny local dashboard
A simple HTML/local web view showing agents, queues, tasks, results, and deadletters.
Section 15
Recommended next practical sequence
Before browser wake, the recommended user-facing sequence is:
Section 16
What to remember
Agent Bus is real, but not yet user-friendly.