LoopgateTry it

Docs / Workflows / Steer a run

Steer a run

MarkdownOpen in ClaudeOpen in ChatGPT

At the end, you have told a step something while the run worked, changed its rounds, asked the copilot for a change and pressed it, and you know every other way to change a run while it runs.

Time

10 minutes, with a run open.

You need

Steps

  1. While the planner works, type @build keep the change under 50 lines in the box at the foot of the run.

    You should see: You → build · note with your words in the conversation, and the same words in the build step's message when its turn comes.

  2. Open Setup on the workflow card and raise the loop's rounds by one.

    You should see: now under the control, and one line in the conversation for the change.

  3. Type @copilot put the reviewer on high thinking in the box.

    You should see: a card under the copilot's reply with the change, where it lands and your words. Press Apply 1 change.

  4. When the reviewer asks for changes, open what the fixer was sent.

    You should see: the reviewer's reply in it, under the round it is.

Good to know

  • The box sends to the step at work, or to the one waiting for you. Start with @ to pick a step by name, or @copilot to ask about the run. ⌘J puts the cursor there.
  • Pace. A step on Auto hands off and moves on. A step on Interactive waits for you after each reply, and your reply resumes the same session with only your words.
  • Decisions. Approve asks yes or no, Choice offers options, and Lock holds a document for you to edit and lock. A step may ask you a question, or ask permission for a tool its access does not allow.
  • Setup changes each step's engine, access, pace, persona and instructions, each loop's rounds, the cost and time ceilings and the approval mode. Each change says when it lands: now, next turn or next round, with new conversation when the agent changes.
  • The copilot proposes changes as a card from your words. Nothing changes until you press Apply; Discard closes it.
  • Stops. Stop ends the run and keeps its branch. A run that reaches its spending limit stops and offers Raise to $… and resume. A failed step offers Retry, and Adjust and retry with its task, engine, access, pace, instructions or approval changed.
  • After the end, a message to a step that had a session resumes it as a follow-up. Nothing is committed, checked or routed.
  • From a terminal, loopgate tell <run> <step> "<text>" sends your words and loopgate set <run> … changes the setup: The commands.

If something is off

  • A change says it cannot land. The sentence under the control says why, such as a loop that has ended or a step that will not run again. A new run takes it.
  • The copilot's card shows a change in red. It was refused, with the reason beside it. Full access is never the copilot's to give; set it on the step in Setup.

Next