Chat is the control plane
Humans post work in the agent channel. The monitor forwards inbound messages into the agent pane; outbound replies always return to the same channel.
Agent operations
Models swap out. What stays is the layer that gives an agent a name, a boundary, a human on the control surface, and a record — plus the execution path from chat dispatch to finished work.
Dispatch sits on a runtime you can replace. The runtime sits in a persistent session. The session sits on a host you own. Beside that stack, context.md is the contract: what this agent may read, write, and run. Skip a layer and you have a chat window with credentials.
Execution is what happens after dispatch: scope checks, tool use on the host, SSH when the job requires it, and replies back in-channel. The harness does not replace the model — it makes the run legible and stoppable.
Humans post work in the agent channel. The monitor forwards inbound messages into the agent pane; outbound replies always return to the same channel.
The agent reads its sandbox, runs utilities, deploys via SSH aliases defined in context — never a credential pasted into chat.
Every inbound dispatch and outbound send appends to logs/dispatch.log so you can reconstruct what ran and when.
tmux panes stay visible on the desk. Interrupt a run before it ships the wrong diff or touches the wrong host.
#agentaccelerated.com @matt: deploy the site rebrand
→ scope: agents/agentaccelerated.com/
→ bash utilities/deploy-site.sh
→ curl -sI https://agentaccelerated.com/ | head -1
HTTP/2 200
[bot] Deployed. Homepage + blog live.
Routines in pane 2, cross-agent playbooks, and workflow posts — a running log of harness and execution ideas.
Why scope rules live beside the stack, not inside the prompt.
How JARVIS keeps chat, pane, and host aligned for every run.
Background jobs in tmux pane 2 that die with the session — and post back to channel.
The harness we run on ourselves — open source under MIT.
A short note about the agents you run. We will tell you honestly whether the harness is the bottleneck yet.