agentloop

Give your coding agent a harness.

Conductor plans, native memory, hard budgets, and external ship gates — in the agent you already use.

In practice

Plan. Approve. Verify. Stop.

Multi-step work goes through Conductor first. Execute waits for your yes. Done means the outside world agrees.

agentloop · bash
you
refactor the auth module. keep the public API
/plan conductor
scaffold · budgets · parallel map · awaiting approval
approved · pev · swarm none
exec jwt.ts · session.ts
verify 12/12 tests · lint clean

Works where you already code

01 · /plan

Conductor plans. Approval before expensive Execute.

Multi-step work gets a structured scaffold: consumption estimates, parallelization map, agent picks, risks, and hard stop budgets. Execute waits until you approve.

Open conductor-plan →
conductor = {
  scaffold:  "slices + verify",
  estimate:  "turns · context · cost",
  parallel:  "map · swarm verdict",
  gate:      "await approval",
  stop:      ".agentloop/stop.yaml"
}
02 · /memory

Local-first memory. Cold sessions that still know the repo.

Native store at .agentloop/memory/. Upsert, supersede, contradict, digest. Handoffs carry the next action and memory keys so another chat continues without re-explanation.

Open persistent-memory →
scripts/memory.sh session-brief
scripts/memory.sh upsert --key …
scripts/memory.sh supersede old --key new
.agentloop/handoff.md  → next action
context-surgeon        → continuous
03 · /swarm

Parallel when it helps. Caps when it would hurt.

Spawn workers only for large, independent tracks — and only when Conductor’s swarm verdict is surgical and approved. One strong composed pass beats five shallow ones.

Open the swarm skill →
verdict     surgical | none
workers     3 / 3 cap
depth       ≤ 2
compose     preferred for craft
quality     over noisy parallel
04 · /ship

Done means the outside world agrees.

Tests, lint, types, diff budget, scope check. Hard budgets in stop.yaml. The model does not grade its own homework.

Open the ship-gate skill →
tests         12/12
lint          0 warnings
types         clean
max_turns     honored
─────────────────
status        ready to merge
Install

Pick your agent.
Copy. Paste. Run.

Plugin install, or install.sh to seed Conductor-ready .agentloop/ templates. Use --full for commands, hooks, and helper scripts. Then /doctor/plan → approve → execute.

Cursor

Local plugin from this repo, or project bootstrap via install.sh.

Full guide →
Paste into Cursor chat
Install agentloop as my coding harness.

1. Clone https://github.com/edenbuilds/agentloop if it is not already local.
2. In Cursor: Customize → Plugins → add this directory as a local plugin
   (it ships `.cursor-plugin/plugin.json`).
3. Or bootstrap:
   ./scripts/install.sh /path/to/this/project
   # optional full surface:
   ./scripts/install.sh --full /path/to/this/project
4. Run /doctor. Init memory: scripts/memory.sh init
5. For multi-step work: /plan → wait for my approval → then /agentloop or /pev.
   External ship gate. Quality over swarm. Council only on consequential calls.
   Keep .agentloop/handoff.md current.

Follow AGENTS.md. Method lenses only. Never celebrity cosplay.
Shell bootstrap
git clone https://github.com/edenbuilds/agentloop.git
cd agentloop
./scripts/install.sh /path/to/your/project
./scripts/install.sh --full /path/to/your/project   # optional
./scripts/doctor.sh
./scripts/memory.sh init

After install: /doctor/plan (approve) → /agentloop or /pev. Craft: /polish.

Craft pack

Quality gates for work humans will actually trust.

When output starts to sound like every other AI page, run craft. Strip the sludge. Check contrast. Optional voice stays off unless you turn it on.

Mission control without changing how your team works.

Same chat. Stronger loop. Clearer stops.

Fig. · harness console (conceptual)

PEV loops

+ New mission
MissionModeStepVerifyState
auth-refactorPEV + council4 / 612/12Shipping
api-migrationSwarm ×32 / 58/8Running
landing-polishCraft compose3 / 3PassDone
onboarding-flowPEV1 / 4-Queued
ship-gate · auth-refactor verified
Doctrine

The model is not the product. The harness is.

Code owns the loop. The LLM reasons inside nodes. It does not invent control flow. Write stop conditions. Prefer quality over swarm. Verify outside the model.

Read the doctrine

Click the cube