Thread goals
Give a thread a durable objective, control automatic continuation, and understand when Tejus pauses or completes the goal.
A thread goal is an explicit, persistent objective attached to one thread. It stays visible above the composer, carries across turns and restarts, and gives the agent a durable definition of what it is trying to finish.
Use a goal when the work genuinely spans several turns and you want Tejus to keep pursuing the same outcome. Do not use one for every ordinary prompt: a goal starts follow-up turns automatically, so it should reflect deliberate intent.
Set a goal
Enter the objective after /goal:
/goal Finish the release notes, verify the site build, and report the deployed pages.You can also choose Goal ("Set a goal to keep pursuing") in the composer + panel, which turns your current draft into the goal. Setting or resuming a goal starts work on it right away when the thread is idle.
Write the goal as an observable outcome. Include the important scope and completion boundary, but keep turn-specific instructions in normal messages.
Use the goal controls
The goal panel above the composer shows the objective, the elapsed time, and its state: Pursuing goal or Goal paused. Its buttons are Edit goal, Pause goal / Resume goal, Expand goal / Collapse goal, and Delete goal.
The same actions are available from the composer:
| Command | Result |
|---|---|
/goal | Show the current goal |
/goal <objective> | Set or replace the goal |
/goal edit | Put the current goal back into the composer for editing |
/goal pause | Pause continuation and stop the elapsed timer |
/goal resume | Resume pursuit and timing |
/goal clear | Remove the active goal without recording it as achieved |
Use /goal -- <objective> when the objective itself is a control word such as pause. See the slash-commands reference.
How continuation works
After a turn completes cleanly, Tejus starts another turn to continue an active goal, asking the agent to make concrete progress on the full objective and to verify it before claiming completion.
Automatic continuation waits for higher-priority work. Messages you have queued run first. A pending approval or question, or a turn that is still running, defers continuation until it is resolved. Continuation does not run in plan mode, in subagent threads, or in archived threads. A failed, cancelled, or interrupted turn, a timed-out continuation, or an explicit stop pauses the goal instead of immediately starting it again.
A queued message from you takes priority over an automatic goal continuation. Goals preserve the objective; they do not take control away from you.
Achievement and blocked goals
When the agent has completed the objective, it reports that to Tejus. The goal is cleared and the completing turn shows a Goal achieved in … badge with the elapsed time (paused time is not counted).
The agent is told that if the same external blocker prevents meaningful progress for three consecutive goal turns, it should report the goal as blocked. Tejus then pauses the goal (Goal paused) instead of looping. Difficulty, incomplete work, or a useful clarifying question are not reasons to mark a goal blocked. Resume the goal after the blocker changes.
Goals can be set for every provider, but reporting achievement or a blocker uses Tejus's agent tools, which the built-in Tejus agent does not have. With the Tejus provider a goal keeps continuing until you pause, stop, or clear it, or a turn fails.
Goals, forks, and handoffs
A goal belongs to its thread. A provider handoff continues the same thread, while a fork creates another thread with its own future lifecycle. Check the destination after either operation and set or revise its goal explicitly when the new thread should pursue a different outcome.
Goal checklist
- The objective was explicitly requested
- Completion is observable
- The goal belongs to one thread and environment
- Turn-specific instructions remain in normal messages
- Pending approvals and questions are answered
- Failed or interrupted work is inspected before resuming
- A paused (blocked) goal is resumed only after its blocker changes
- Achievement is verified from the actual result, not only the badge