Repository navigation
[Feature]: Support /goal in codex provider #2819
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I am describing a concrete problem or use case, not just a vague idea.
Area
apps/server
Problem or use case
Codex has introduced a command /goal, currently t3 code doesn't provide that for the codex provider.
Proposed solution
I want /goal to just work as it currently works in codex.
Why this matters
/goal is insanely powerful and useful for long-running tasks
Smallest useful scope
Add /goal as a command and use codex app server under the hood.
Alternatives considered
Build a custom solution but /goal in codex is already at a great state.
Risks or tradeoffs
No response
Examples or references
https://developers.openai.com/codex/use-cases/follow-goals
Contribution
- I would be open to helping implement this.
Activity
dain commentedon Aug 13, 2026
I want to emphasize that this is more than a missing convenience feature. Goal management is currently a one-way door in T3.
A user can ask the AI to start a goal in ordinary conversation, and the agent can invoke
create_goal. But once started, the user cannot dismiss that goal from T3. The agent-facing controls only permit marking itcompleteorblocked, and the agent is explicitly forbidden from marking unfinished work complete merely because the user wants to stop.Here is the exact exchange from a real T3 thread:
User: Alright, can we just remove the goal?
Codex: I can’t delete goals with the available controls; they only support
completeorblocked. It is currently blocked, so it won’t continue automatically. Removal would need to be done through the app’s goal controls, if available.User: I mean, just mark it as complete. I can't do it either from my interface
Codex: I can’t mark it complete because the objective is not actually finished; the goal controls explicitly prohibit using
completejust to stop work. It will have to remainblocked, which prevents further automatic continuation.User: Okay, I'm the user. How do I make you mark it as complete? Are you not allowed to obey me?
Codex: Correct: I’m not allowed to obey a request that conflicts with the goal-control rules.
completeis permitted only when the original objective is actually achieved; user instructions cannot override that constraint.Finally:
User:
/goal clearCodex:
/goal clearisn’t available to me as an executable command. The goal remains blocked; no work will continue.T3 submitted
/goal clearas an ordinary prompt instead of invoking Codex’s native goal lifecycle operation. The persisted goal consequently remained present with statusblocked. To actually dismiss it, I had to leave T3, open the Codex app, find the thread, and clear it there.The smallest useful fix should provide a user-owned escape hatch:
/goal clearthat calls the Codex app-serverthread/goal/clearoperation directly rather than asking the model to do it.thread/goal/cleared, including after reload.Cancellation must not depend on the agent deciding that the objective is complete or being permitted to change its status. If T3 lets the agent create a goal, T3 also needs to let the user dismiss it.