Repository navigation
Description
Summary
When using Claude as the model provider, slash commands (/) supported by Claude Code but not recognised by T3 Code (including built-in and user-defined commands) are treated as unknown skills, and submitting them causes the UI to freeze and become unresponsive
Additionally:
- Built-in Claude Code slash commands like
/renameare not recognized (shows "Unknown skill: rename") - Custom user slash commands (e.g.
/suggest-renamedefined in~/.claude/commands/suggest-rename.md) are not discovered or loaded - The UI freezes after typing `enter' — the spinner appears and the input becomes unresponsive, requiring the session to be abandoned
Only a limited set of T3 Code-native commands (/model, /plan, /default) appear in the autocomplete dropdown — none of the Claude Code built-in or user-defined commands are available.
Steps to Reproduce
- Open T3 Code with Claude as the provider (Claude Sonnet 4.6)
- Have a custom command defined at
~/.claude/commands/suggest-rename.md - Start a conversation
- Type
/suggest-rename— returns "Unknown skill: suggest-rename" - Type
/rename— returns "Unknown skill: rename" - Type
/rename claude-code-rename-and-custom-slash-commandsubmit and wait. - The UI freezes with a loading spinner and the thread becomes unresponsive
Expected Behavior
- Built-in Claude Code slash commands (
/rename,/help, etc.) should work - Custom slash commands from
~/.claude/commands/and~/.claude/skills/should be discovered and available - Nothing should not freeze the UI
Actual Behavior
- Only T3 Code-native commands (
/model,/plan,/default) are available - Built-in Claude Code commands return "Unknown skill"
- Custom user commands are not discovered
- UI freezes after interacting with the
/command palette
Screenshot
Screenshot shows the frozen state — Claude correctly identified the custom command exists at ~/.claude/commands/suggest-rename.md, but invoking it via /suggest-rename failed. The /rename built-in also failed. The input is frozen with a loading spinner.
Related
This is likely related to #1283 which identifies that settingSources is not being passed to the Claude Agent SDK, meaning all filesystem-based Claude Code features (skills, slash commands, CLAUDE.md memory) are silently ignored. The freeze behavior may be an additional issue where an unrecognized command causes the session to hang rather than failing gracefully.
Environment
- T3 Code version: 0.0.13 (2a237c2)
- Platform: Mac Mini M1
- macOS version: 26.3.1 (a) (25D771280a)
- Model provider: Claude (Claude Sonnet 4.6)
- Mode: Chat, Full access, Low reasoning
- Branch context: master (local project: rds-version-check)
Activity
solrevdev commentedon Mar 30, 2026
Update: I upgraded to 0.0.15 (f82bae1).
The app looked like it found and used my custom
suggest-renameskill to suggest a better thread name, but/renamestill hangs while thinking for 0s.I opened Claude Code in the same folder as the T3 Code project and the project name matched the original thread name in the project window.
I also tried renaming the thread in the T3 UI to see whether that would rename the underlying Claude Code thread/prompt, but it did not.
When I deleted the thread to remove the project (which you have to), the thread name in Claude Code changed to Unknown skill: rename via
claude --resume.Not sure whether this is useful, but hopefully the screenshots help explain this update:
If this update is not useful then I am happy to delete to keep the issue simpler.
pjmuller commentedon Mar 31, 2026
Upvote, I have exactly the same issue
in the t3 code
when looking up this conversation via claude code in the terminal
[-]Slash commands freeze UI when using Claude provider — built-in and custom commands not recognized[/-][+][Bug]: Claude provider slash commands not discovered; unrecognized command freezes UI[/+]usamakamran1 commentedon Apr 15, 2026
I have the same issue. Can not run even basic claude commands such as
/usage. This makes my usage of Claude Code limited even though I like the GUI from T3Code. Hoping this gets resolved soon.Andrew-Forster commentedon Apr 15, 2026
Should be fixed in #1905