/goal

Type it and what “done” means, in plain language.

/goal every test in ~/budget passes

the checkable end state

Give it a condition the checker can see in the chat (“pytest reports 0 failed”, “the build prints no errors”). “Make it better” never becomes true.

The loop

  1. Answers your message
  2. A small model reads the transcript since the goal was set
  3. Judges: met, not met, or impossible

stops on its own when

  • met
  • impossible
  • stalled
  • capped

The checker sees up to 400 messages since the goal was set, limited to the last 16,000 characters.

It reports impossible only when the model cannot remove the obstacle itself, such as an access right you need to grant. Slow progress does not count.

What does not interrupt it

the run

What you see

Every round shows up as a line in the chat.

Ceilings

Rounds default 25

Stalls after four rounds naming the same missing piece. Otherwise capped at 25 rounds; the operator can change that number.

Need the older, unattended kind instead? /jobgoal (/jg, /job) starts a background job with its own log under Jobs.

Condition

Up to 4000 characters. Chats without an account cannot set a goal.

Something missing or wrong here? Say so. The documentation is part of the product, not an afterthought. All topics · Security · Status · X · Legal & privacy · Home