Run autonomous task daemon with guardrails
Claim tasks from a shared kanban queue and execute them with cost caps, retries, and peer recovery until the backlog clears.
/goal "<objective " + /subgoal (numbered criteria), or headless buddy goal . buddy --yolo grants 400 tool rounds under a $100 cap with guardrails, and the 24/7 autonomous daemon ( buddy autonomy install ) claims tasks from a shared queue and runs them free-first (local → Tailscale → paid). That queue is a unified kanban board : the agent's kanban tools and the daemon drive one shared board with a claim lease + heartbeat , zombie reclaim of a crashed peer's work, a retry budget that dead-letters a hopeless task to a review column, and a dependency DAG — view it as Hermes-style columns with buddy autonomy tasks board
claude-code
More automation loops
Run workflows with dynamic sub-agents
Split a task into packets, run sub-agents in parallel, synthesize results, and verify completion.
/goal loop and verify until complete
automationlow risk
Run agent turns until goal met
Agent executes repeated turns toward a condition, with a lightweight evaluator checking progress after each turn until the goal is reached.
/goal <condition turns a prompt into a durable objective. Thanos immediately starts a turn toward the condition, and after each turn a fresh, tool-less side-channel evaluator (a one-shot completeSimple call, not a subagent — so no extra agent turn and no re-entrancy) reads the last turn's evidence and returns MET / NOT MET . NOT MET auto-continues another turn with the reason as guidance; MET clears the goal and records the achievement. Unparseable evaluator output is treated as NOT MET (fail-safe: it never declares a false "done
automationmedium risk
Run agent until goal met
Queue agent turns with goal context until your objective is achieved, treating the goal as untrusted data.
/goal <objective , after /goal resume , and after every agent turn that leaves the goal active , the extension queues Codex's goal continuation prompt as hidden model-visible context. The objective is XML-escaped and wrapped as untrusted user data so it does not become higher-priority instructions
automationlow risk