Before submitting
Area
apps/web
Problem or use case
Hey, I think T3 Code is actually a very good UI, except for one thing that is completely missing but very core to development: supporting slash commands in Codex or Claude Code.
Currently, the development process is limited to conversation, but if you want more fine-grained control over slash commands (such as "compact," "goal-setting," and other things that would normally be done in a slash command UI), it's not available yet.
I did a quick inspection of the Codex implementation and found that by using the app server, it is actually possible to have slash commands integrated. The only problem is how we interact with it. I would like to ask whether such a feature could be considered for implementation, as that would be a great enhancement to productivity.
Proposed solution
I think the most native way of implementing this is to parse the incoming prompt when it begins with a forward slash. That slash command, along with the rest of the prompt, will be treated differently by invoking the command internally in the Codex App Server, which enables the usage of slash commands.
It would also be nice if we could parse the available slash commands from the Codex and add a completion, but that is optional.
Why this matters
Because slash command enables many different capabilities, such as compaction, it is very important. Also, Codex recently introduced goal setting with slash command, which is super useful for long-horizon tasks.
If I could not use this capability in the T3 code, I would have to open another terminal to access it instead of using it directly over T3 code. Therefore, it is very important that T3 code includes this capability.
Smallest useful scope
Just allow a custom field or a custom input field for a slash command, so that we could input the slash command alone without any additional prompt.
Alternatives considered
No response
Risks or tradeoffs
No response
Examples or references
No response
Contribution
Before submitting
Area
apps/web
Problem or use case
Hey, I think T3 Code is actually a very good UI, except for one thing that is completely missing but very core to development: supporting slash commands in Codex or Claude Code.
Currently, the development process is limited to conversation, but if you want more fine-grained control over slash commands (such as "compact," "goal-setting," and other things that would normally be done in a slash command UI), it's not available yet.
I did a quick inspection of the Codex implementation and found that by using the app server, it is actually possible to have slash commands integrated. The only problem is how we interact with it. I would like to ask whether such a feature could be considered for implementation, as that would be a great enhancement to productivity.
Proposed solution
I think the most native way of implementing this is to parse the incoming prompt when it begins with a forward slash. That slash command, along with the rest of the prompt, will be treated differently by invoking the command internally in the Codex App Server, which enables the usage of slash commands.
It would also be nice if we could parse the available slash commands from the Codex and add a completion, but that is optional.
Why this matters
Because slash command enables many different capabilities, such as compaction, it is very important. Also, Codex recently introduced goal setting with slash command, which is super useful for long-horizon tasks.
If I could not use this capability in the T3 code, I would have to open another terminal to access it instead of using it directly over T3 code. Therefore, it is very important that T3 code includes this capability.
Smallest useful scope
Just allow a custom field or a custom input field for a slash command, so that we could input the slash command alone without any additional prompt.
Alternatives considered
No response
Risks or tradeoffs
No response
Examples or references
No response
Contribution