Use Goal Mode

Goal Mode lets one session continue working after a normal turn when the requested outcome is not complete yet. Kora evaluates the completed turn without tools, using the same provider and model, and either marks the Goal as achieved or starts a bounded continuation.

Start a Goal

Enter a slash command in the composer:

/goal all tests pass and the build succeeds

The condition is saved on the current session and the first normal provider turn starts immediately. A session can contain only one Goal; setting another condition replaces the existing terminal Goal.

When you type /goal at the start of the composer, Kora replaces the text command with a removable Goal chip. Type the condition in the composer as usual. Removing the chip cancels the pending Goal command; submitting reconstructs /goal <condition> for the existing Goal workflow.

Switch execution mode inline

The same composer accepts these mode commands at the start of the input:

Command	Result
/ask	Switch to Ask mode
/plan	Switch to Plan mode
/debug	Switch to Debug mode
/build	Switch to Build mode

The command is consumed immediately and any following text remains in the composer as the prompt. For example, /plan inspect the release flow switches to Plan mode and leaves inspect the release flow ready to send.

Follow progress

The Goal appears in the composer addendum and in the session sidebar. Its state can be:

State	Meaning
active	The session can continue toward the condition
evaluating	Kora is checking the latest completed turn
achieved	The evaluator confirmed the condition
failed	A turn, evaluator, or run limit stopped the Goal
cancelled	You stopped or cleared the Goal

The evaluator returns a decision and a reason. If the condition is not met, Kora starts a normal continuation message and includes the reason as guidance. Continuations are queued behind an already queued user message.

Stop or inspect a Goal

Use these commands locally from the composer:

/goal       # show the current Goal status
/goal clear # clear the Goal and stop evaluation

/goal stop, /goal off, /goal reset, /goal none, and /goal cancel are equivalent clear aliases. /clear also clears the current Goal.

The normal Stop action aborts the active model stream, evaluator, and future continuations. An intentional stop never restarts the session automatically. A new direct user message supersedes an evaluator without incorrectly failing the Goal.

Limits and failure behavior

• A Goal stops after 50 completed turns or two hours, whichever comes first.
• The evaluator has no tool access and receives bounded transcript evidence.
• Evaluator failures retry at most twice before the Goal becomes failed.
• Provider, workflow, and non-abort evaluator errors produce an explicit failed state.
• Goal evaluation uses normal usage metering and is attributed separately to the active Goal.

Goal Mode follows the provider’s normal availability and authentication rules; it does not add a separate Premium gate.

Troubleshooting

• The Goal does not continue → check whether the session is already queued, stopped, achieved, failed, or at one of the run limits.
• The Goal is evaluating → wait for the evaluator to finish, or send a direct message to supersede that evaluation.
• The Goal failed → read the diagnostic reason in the composer addendum, correct the underlying issue, and set a new Goal condition.
• You want to stop all autonomous work → use the normal Stop action or /goal clear.