Changelog
What changed for someone who uses Loopcaptain. This file holds the first version; every later version has its notes on the releases page, written from the commits.
0.1.0 (2026-11-15)
The first public version.
Security
- Start passes a started loop only
PATH,HOME,LANG,TERMandLOOPCAPTAIN_INBOX_KEY, not the board's whole environment, and asks for a tick the first time a given command of a given repository is run. - The board signs every inbox line (
sig, an optional field of protocol 1) with a key outside every repository; the helper and the MCP toolinbox_readsay whether an entry issigned, so a loop can refuse a forged stop or reply. Each line names its loop, and the board's own status ignores a line whose signature fails. - The file viewer refuses credential files (
.netrc,*.pem,id_rsa*and more) and shows content only for known text files. - The board follows no symbolic link in a loop's folder, and the MCP
tools write only under their working folder or
LOOPCAPTAIN_MCP_ROOTS.
Changed
- The demo is one example loop that builds a dashboard on loop
engineering: it asks once with buttons, converges over four rounds,
and honours only a signed stop.
loopcaptain demowrites it from an installed package; its history is the loop itself run with past times. loopcaptain validatealso checks that artifact paths exist, that time does not run backwards and that a round has one outcome; it warns of rounds written after the fact and of loops that never read their inbox. Problems and warnings are printed apart;--strictfails on warnings too.loopcaptain doctor <repository> <loop-id>sends a running loop a signed stop and passes once the loop took it and ended: the one way to know a loop listens.loopcaptain watch <folder>andunwatch <folder>edit the board's config, so the board needs no checkout.
Added
- A documentation site (Zensical): get started, connect or build a loop,
every agent, the board, the protocol, a reference written from the
code, security, architecture.
make docsbuilds it and joinsmake check;llms.txtpoints agents at the standard. - The README opens with two prompts to copy into any coding agent (build
a loop, watch the loops on this machine), kept once in
standard/prompts/;AGENTS.mdsection A is the runbook the second one points at, andstandard/AGENTS.mda guide to building a loop. loopcaptain mcp-config <agent>anddocs/agents.md: how each coding agent adds the MCP server and runs a loop unattended.- Protocol 1 grows, every field optional:
atfor the real time of an event, a round's wholecost, cache tokens and turns,metrics,attempt,error(needs_personwaits for you),session,outcome(kept or discarded),next_at, questionidandoptions,workspaceandstateinloop.json, and the eventsquestion_closed,loop_stoppedandheartbeat. - A loop that said when it is back shows as
sleeping, not stalled. - The board flags "no progress?" before the loop does: the same material findings open two rounds running, a measure flat for three rounds, open findings that do not fall.
- The overview groups loops by repository, with a "Waiting" tab for questions; worktrees of one repository show once, from the one written last.
- The loops protocol, version 1: a loop writes
loop.jsonand appends toevents.jsonlin.loops/<loop-id>/; the board appends toinbox.jsonl. Eight events:round_started,step_started,step_finished,finding_closed,round_finished,question,check,inbox_read. standard/: the text, a helper of 50 lines to paste, threeloop.jsontemplates, the JSON Schema, and anAGENTS.mdfor the agent that connects a loop.- The board: all loops with what waits for you on top; one loop with its brief, the graph of a round, every round against every step, a round in detail, the items it evaluates; a page to copy the standard from.
- Steering from the board: answer a question, send a note, stop after the current round, start the command a loop declares.
- The
loopcaptaincommand:serve,validate,emit,schema,spec,mcp. - An MCP server with the protocol as five tools (
protocol,loop_register,emit,inbox_read,loop_status), for loops an agent session drives. make demo: three invented loops, one of them startable, that cost nothing.- The overview draws each loop's latest twelve rounds beside its round count: a square per round, darker for more findings left open, a green dot for none, a ring while it runs. A loop that converges is seen without opening it.
- The documentation has an Installation page (one command from the repository, with uv, pipx or pip), a five-minute Get started with the example loop, and a Setup page: what the board watches, how to check a loop, and what to look at when a loop does not show.
- The overview shows where to look first: the tiles for what runs and for what stalled or failed take colour when their count is not zero, every row carries a stripe in its status colour, and a row with a question or a failure is tinted.
- The README and the documentation show the board with an invented set
of eight loops in every status: the front page large, four more views
in a grid.
make shotsretakes them.