Goals
Messages and context
With Codex, Claude, and OpenCode 2.2.5+, /goal sets what "done" means and the agent keeps working across turns until it judges the goal met.
T3 Code docs: composer
What it’s for
Long tasks with a clear finish line, such as getting all tests in a package to pass.
T3 Code docs: composer
How to use it
Theo’s tips
Theo warns that putting /goal at the front of a prompt is the quickest way to burn tokens for little gain. He says a well-written prompt without it should do the same thing.
5:54
…probably heard me say in other videos, the quickest way to burn a bunch of tokens and get nothing out of it is to add /goal to the front of your prompt. I do still mostly believe that as a piece of advice, but mostly because if you remove the slash goal and you write the right prompt, it should do the same thing.
For long autonomous tasks, Theo stays out of the loop. He sets a goal, gives the agent many sub-agents (40 in his TypeScript-to-Rust test), and lets it work on its own.
26:33
I just set a goal and gave it 40 sub agents and said, ‘Do as you…
What’s changed
- Adds support for native goals.Updated Nov 12
- Native goals now work in supported Antigravity threads.Updated Nov 12
- OpenCode goals stay in sync across clients.Updated Nov 10
1 earlier change
- Native /goal for Codex and Claude, with goal status shown in the UI.Added Oct 5
Unofficial notes. Not affiliated with Theo or t3.gg.