Store / Coding agent control / Harness

Coding agent control for Codex and Claude Code

See what your coding agent is doing. Stop it when you need to.

Harness puts the plan, questions, time limit, alerts, and stop control outside the terminal. You can let an agent work without losing sight of the run or the ability to end it cleanly.

  • Coding agent control
  • Stop a runaway agent
  • Codex and Claude companion
Backlog project board app icon
Harness Suite7 controls · macOS and Linux

Agent work should not disappear into a terminal scrollback.

A long run is hard to trust when you cannot see the current plan, know whether a question is waiting, or stop the right process without collateral damage.

01 / PLAN

See what it thinks it is doing.

Todo gives the run an explicit plan, including a human-controlled list of work the agent must not do.

02 / ATTENTION

Let questions wait without stalling everything.

Mail holds non-blocking questions. Help reserves visible and audible alerts for the issues that genuinely need attention.

03 / CONTROL

Put a real end on the session.

Timer makes the limit visible. Stop! gives you one clear control for ending Claude, Codex, or both.

Seven controls for the moments where agent work gets slippery.

Each control has one job. Use the whole suite or buy only the individual instrument you need.

TODO + MAIL

Plan and questions

Make the intended work visible, preserve hard guardrails, and answer questions when you are ready.

TIMER + STOP!

Time and interruption

Set the duration before the run starts and keep a decisive brake pedal within reach.

HELP + THOUGHT + BREATH

Alerts, notes, and pacing

Separate real alerts from noise, capture thoughts in Markdown, and add a quiet pause to long hands-off sessions.

Add a project board when one run becomes a body of work.

Backlog turns tasks, dependencies, and status changes into a shared operating picture for you and the agent.

STEP 1

Plan on the board.

Define the work, order dependencies, and make blocked tasks obvious before execution begins.

STEP 2

Run through Harness.

Let the agent read the plan, leave questions, respect the timer, and surface important alerts.

STEP 3

Review the trail.

See what moved, what remains, and where the work stopped without reconstructing the run from chat history.

Backlog + Harness SuiteProject board plus all 7 controls · macOS and Linux

The controls stay beside the agent, not behind another dashboard.

The boundary supports the control model. A remote service is not required to tell a local agent what to do or when to stop.

Data boundary
Plans, questions, timers, alerts, and control commands stay on your computer and are exposed to the agent over localhost.

Questions about controlling coding agents

Direct answers for developers looking for a Codex companion, a Claude Code control panel, or a safer way to run agents unattended.

How do I stop a runaway Codex or Claude Code agent?

Harness includes Stop!, a direct local control that can end Claude, Codex, or both without hunting through terminal windows. Timer also gives each work session an explicit limit before it starts.

What can I see while a coding agent is working?

Todo exposes the plan, Mail collects questions, Timer shows the remaining work session, and Help surfaces alerts. Add Backlog when you also want a board for tasks, dependencies, and status.

Does Harness work with both Claude Code and Codex?

Yes. The store includes instruction files for Claude Code and for Codex, Cursor, and other agents that can call localhost APIs.

Other ordinary jobs, handled directly.

Choose one tool for the task in front of you.