v1 shipped · v2 next · see the roadmap
SpecStrand

Control the agents you do not fully trust

SpecStrand puts your own agent on a plan it drains task by task over MCP or the spec CLI, holds it at the gates until you approve, carries messages to and from the run, and keeps a record of every step it took.

The loop

One loop, until the work is done

Every task runs the same cycle. Your agent repeats it on its own, draining the queue and waiting for whatever you add next.

  1. Claim

    Your agent pulls the next ready task off the queue, over MCP or the spec CLI.

  2. Work

    It does the work against your plan and repo.

  3. Report

    It reports progress, findings, and a pass/fail verdict.

  4. Complete

    It closes the task out, then reaches for the next one.

repeat until the queue is empty

In practice

Watch a plan drain.

Agents claim what is ready, work it, report, and complete. When a gate needs you, they wait; the moment you approve, they fan out.

open an agent is on it done gate: needs you

What you get

Plans that drain themselves

Your agent claims the next ready task, works it, reports, completes, and reaches for the next. No babysitting, no copy-paste between tabs.

On the roadmap: your model, your rules

Bring-your-own-model (Anthropic, OpenAI, Google, or a local server) is planned for v2, not shipped today. Right now you point your own agent at SpecStrand.

Gates, messages, and the record

A gate holds the run until you say go. Messages reach the agent while it works. The run timeline keeps every step it took. All of it in the Studio, one workbench.

Ready to put an agent under control?

Spin up a project, queue the work, gate what matters, and point your agent at it.

Log in