You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Show the provider session ID in thread details, so a thread can be resumed in the CLI
#37501
Each Claude and Codex thread in T3 Code is a normal provider session (Claude threads live in ~/.claude/projects like any CLI session), but the UI never shows the session ID. In the Claude Code CLI I keep the session ID in my status line and use it to resume a session in another terminal (claude --resume <id>), refer to it from other tools, or find its transcript file. In T3 Code there's no way to get it without reading the database.
Proposal
Add a Session item to the thread details panel showing the provider and the session ID, with a copy button.
Include the same ID in t3 thread show --json and t3 thread list --json, so scripts can get it.
Optional: a "Copy resume command" action that copies cd <worktree> && claude --resume <id> (or codex resume <id>).
Why
It's the bridge for people who use both T3 Code and a terminal: start in T3, continue a thread in tmux on the same machine when needed, or point another agent at it. Related: #32997 (letting Codex Desktop/CLI resume a T3 thread).
For now I'm using a small script that reads statev2.sqlite read-only to map threads to session IDs, which works but depends on internal tables that can change.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Problem
Each Claude and Codex thread in T3 Code is a normal provider session (Claude threads live in
~/.claude/projectslike any CLI session), but the UI never shows the session ID. In the Claude Code CLI I keep the session ID in my status line and use it to resume a session in another terminal (claude --resume <id>), refer to it from other tools, or find its transcript file. In T3 Code there's no way to get it without reading the database.Proposal
t3 thread show --jsonandt3 thread list --json, so scripts can get it.Optional: a "Copy resume command" action that copies
cd <worktree> && claude --resume <id>(orcodex resume <id>).Why
It's the bridge for people who use both T3 Code and a terminal: start in T3, continue a thread in tmux on the same machine when needed, or point another agent at it. Related: #32997 (letting Codex Desktop/CLI resume a T3 thread).
For now I'm using a small script that reads
statev2.sqliteread-only to map threads to session IDs, which works but depends on internal tables that can change.All reactions