Before submitting
Area
Provider integrations / chat attachments
Problem or use case
When using the Codex provider, Codex can generate images, but t3code does not appear to surface the generated image in the chat UI. In my case, I asked Codex to create a tabby cat image. The generation completed, but the app did not show the image, so I had to ask for the raw file path instead.
That makes image generation hard to use from t3code because the successful output is hidden from the normal conversation flow.
Proposed solution
Support Codex image generation results as first-class chat outputs. When Codex returns or writes a generated image, t3code should display an image preview in the thread and expose the local file location or an action to open the file.
A good UX would be:
- Show generated images inline in the assistant message.
- Provide an affordance to open the image file locally.
- Preserve the generated image reference when the thread is reloaded.
Why this matters
This would make Codex image generation usable inside t3code instead of requiring users to manually inspect filesystem paths. It also keeps multimodal work visible in the same thread where the request was made.
Smallest useful scope
A first pass only needs to detect generated image file outputs from Codex and render them inline in the current thread with the file path available.
Alternatives considered
The current workaround is to ask Codex for the file location and open the image manually outside t3code. That works, but it is easy to miss the result and breaks the chat-based workflow.
Risks or tradeoffs
The implementation may need to handle provider-specific result metadata and local file access carefully. It should also avoid assuming every generated file is safe or renderable as an image.
Examples or references
Example interaction:
- Ask Codex:
create an image of a tabby cat
- Codex generates the image successfully.
- t3code does not display the image preview, so the user asks for the saved file path.
Contribution
I would be open to helping implement this.
Before submitting
Area
Provider integrations / chat attachments
Problem or use case
When using the Codex provider, Codex can generate images, but t3code does not appear to surface the generated image in the chat UI. In my case, I asked Codex to create a tabby cat image. The generation completed, but the app did not show the image, so I had to ask for the raw file path instead.
That makes image generation hard to use from t3code because the successful output is hidden from the normal conversation flow.
Proposed solution
Support Codex image generation results as first-class chat outputs. When Codex returns or writes a generated image, t3code should display an image preview in the thread and expose the local file location or an action to open the file.
A good UX would be:
Why this matters
This would make Codex image generation usable inside t3code instead of requiring users to manually inspect filesystem paths. It also keeps multimodal work visible in the same thread where the request was made.
Smallest useful scope
A first pass only needs to detect generated image file outputs from Codex and render them inline in the current thread with the file path available.
Alternatives considered
The current workaround is to ask Codex for the file location and open the image manually outside t3code. That works, but it is easy to miss the result and breaks the chat-based workflow.
Risks or tradeoffs
The implementation may need to handle provider-specific result metadata and local file access carefully. It should also avoid assuming every generated file is safe or renderable as an image.
Examples or references
Example interaction:
create an image of a tabby catContribution
I would be open to helping implement this.