Repository navigation
/resume does not surface Claude CLI sessions despite #6590 #9865
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/web, Claude provider
Problem or use case
#6590 ("First-class interop/sync between T3 threads and local Claude Code CLI sessions") closed as completed on 2026-08-15, citing /resume as the fix for surfacing existing claude CLI sessions (~/.claude/projects/<project>/*.jsonl) inside T3.
On v0.0.39-nightly.20260904.1280, /resume in a Claude-provider thread opens no session list. T3 forwards it as plain text to the model, which asks "What would you like to resume?" — it's reading /resume as a sentence, not a command.
Steps to reproduce
- Open a new thread, Claude provider selected.
- Type
/resume, send. - Expected: a picker listing existing Claude CLI sessions (per [Feature]: First-class interop/sync between T3 threads and local Claude Code CLI sessions #6590).
- Actual: the model replies asking what you want to resume.
Environment
- T3 Code v0.0.39-nightly.20260904.1280, macOS
- Provider: Claude (Claude Sonnet 5)
Suggested fix
Check whether /resume is registered for the Claude driver specifically — it may only be wired for OpenCode/Codex — and route it to the #6590 import flow instead of the chat composer.
Activity
Mnigos commentedon Sep 5, 2026
#6590 was not fixed, it was converted to an Ideas discussion (#6994). GitHub marks converted issues as "closed as completed", which is misleading here.
There is no
/resumehandling in T3 today. The Claude driver does not register that command, so the text goes to the model as a normal prompt./resumeis also an interactive-TUI command in the Claude CLI, and T3 drives Claude in stream mode, so there is nothing to forward it to.The feature request lives in the discussion above. I'd close this one.
shivamhwp commentedon Sep 7, 2026
Note: GPT-6 on behalf of Shivam (@shivamhwp).
Closing as a duplicate of the existing CLI-session import request. #6590 was converted to that discussion; its closed status did not mean the feature shipped. Please keep the session-import request in that discussion.