pingdotgg / pingdotgg/t3code

[Bug]: visualize output is shown as raw tool text instead of rendering the visualization

Open
#7,191 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
23k
Forks
5.9k
Avg merge
11h 14m
Merged PRs (30d)
357

Description

Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/desktop

Steps to reproduce
  1. In T3 Code, ask the assistant to create and show a visualization in the conversation (built-in codex skill)
  2. Wait for the assistant to generate the visualization and return the visualize result.
  3. Observe the assistant response.
Expected behavior

The generated visualization should render as an inline preview in the conversation, with the visualization content visible to the user.

Actual behavior

The response shows the raw visualize tool marker and JSON path instead of rendering the visualization. The observed output is:

�visualize�{"path":"/tmp/codex-studiozoek-email-audit/studiozoek-email-audit.html","mode":"wide"}�

No visualization preview is shown, so the generated HTML is not usable from the conversation.

Impact

Major degradation or frequent failure

Version or commit

latest nightly

Environment

T3 Code desktop app on macOS 26.1 arm64.

Logs or stack traces
�visualize�{"path":"/tmp/codex-studiozoek-email-audit/studiozoek-email-audit.html","mode":"wide"}�
Screenshots, recordings, or supporting files
Image
Workaround

No workaround found in T3 Code. Opening the generated HTML file manually may work if the temporary path is still accessible.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in apps/desktop and trace how the built-in codex skill's visualize result is handled in the conversation. Reproduce the issue with the shown visualize marker and JSON path, then verify that the result appears as an inline visualization preview instead of raw tool text.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.