make:
Agent-web, serve agent-browser
Agent-browser uses agent-api to get info about agents
Agent api connects to a streaming http socket to agent-controller for events from agent
Agent-controller is responsible for making sure the tmux session exists and that the agent is running. It's the agent's interface into the system via the agent-mcp-service and using that mcp server as a channel. Agent-controller tails the conversation transcripts and uses that as one event stream, and then also uses agent-mcp-service as another evnt stream. Additionally, the agent-cli can record an agent event by directly hitting the agent-controller. The agent-controller batches these all up and emits them. The browser can consume them and then show the agent transcript live in the browser, also using a websocket or streaming http, and displaying it like claude-stream would show
make:
Agent-web, serve agent-browser
Agent-browser uses agent-api to get info about agents
Agent api connects to a streaming http socket to agent-controller for events from agent
Agent-controller is responsible for making sure the tmux session exists and that the agent is running. It's the agent's interface into the system via the agent-mcp-service and using that mcp server as a channel. Agent-controller tails the conversation transcripts and uses that as one event stream, and then also uses agent-mcp-service as another evnt stream. Additionally, the agent-cli can record an agent event by directly hitting the agent-controller. The agent-controller batches these all up and emits them. The browser can consume them and then show the agent transcript live in the browser, also using a websocket or streaming http, and displaying it like claude-stream would show