AgentAccelerated Talk to us

Agent operations

The harness is the work.

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.

One stack between the model and production.

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.

DispatchJARVIS v4 · Rocket.Chat
Agent runtimeCursor, Claude Code, Codex, OpenCode
tmux sessionOne persistent session per agent
OS · SSHHost you control
  • 01Name and boundaryDirectory, channel, session, host — one name, readable blast radius.
  • 02Human on the surfaceAgents live in team channels. Approve from a phone, not only a terminal.
  • 03Keys on your hardwareCredentials stay on the host that holds the work.
  • 04Supervision and stopWatch live panes. One word halts a run mid-task.
  • 05RecordEvery dispatch and reply logged per agent — operations, not rumours.

From message to merge-ready work.

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.

Dispatch

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.

Runtime

Tools on the host

The agent reads its sandbox, runs utilities, deploys via SSH aliases defined in context — never a credential pasted into chat.

Audit

JSONL dispatch log

Every inbound dispatch and outbound send appends to logs/dispatch.log so you can reconstruct what ran and when.

Stop

Operator override

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.

Talk to us about your harness.

A short note about the agents you run. We will tell you honestly whether the harness is the bottleneck yet.