Skip to content
LoopCodeDocs

Concepts

Goals, loops and automations

Keep LoopCode working on one objective for hours with /goal, repeat a prompt with /loop, and schedule work with automations.

Goals

A goal is an objective that outlives one turn. LoopCode keeps giving the agent turns toward it — each one checking that the last made real progress — until the agent can prove the goal complete, requirement by requirement. This is how a task runs for hours without anyone typing "continue".

/goal Migrate every API route from Express to Hono, keeping all tests green
/goal --budget 2M Bring test coverage of src/billing above 80%

The goal ends when:

  • the agent marks it complete — only after an audit that checks every requirement against current evidence;
  • a blocker repeats, and the goal is marked blocked with the reason;
  • you pause it;
  • it reaches its token budget, if you set one;
  • your plan's usage runs out — it then waits, and picks up when the window resets.

Steer a goal

CommandDoes
/goalShow where it stands, with pause, resume, edit, budget and clear
/goal pausePause after the current turn
/goal resumeKeep working toward it
/goal edit <objective>Change the objective; the agent hears about it on its next turn
/goal budget 500kSet the token budget (off removes it)
/goal clearDrop the goal; the conversation stays

Pressing esc pauses it too.

Loops

These loops run on your computer while LoopCode is running. They are separate from the upcoming cloud agents called Loops.

/loop repeats a prompt:

/loop 10m check the CI run for this branch and fix anything that fails
/loop keep an eye on the dev server log and fix errors as they appear

With an interval (5m, 1h, …), the prompt runs on that schedule. Without one, the agent paces itself: it ends each turn by choosing when to look again, sooner while things are changing and later when they are quiet.

Automations

Automations are scheduled prompts. Ask in plain words, and LoopCode creates the schedule:

Every weekday at 9:00, summarise yesterday's merged pull requests and the open review requests.
  • Schedules are 5-field cron expressions in your local time, with one-minute granularity.
  • A job runs in its conversation only when that conversation is idle; it never interrupts a turn.
  • Jobs the agent creates for itself expire after a week, so a forgotten loop cannot run forever.
  • The desktop app keeps automations across restarts. They run while LoopCode is running.

Manage them with /automations in the terminal, or the Automations page in the desktop app, which shows each job's schedule and next run.