Before submitting
Area
apps/desktop
Steps to reproduce
description: T3Code exposes skills for Claude/Codex providers but its Cursor/OpenCode provider caches can report zero skills despite files existing.
category: processing
created: 2026-05-16
status: active
T3Code skill bugs need per-provider cache evidence
When investigating T3Code skill behavior, check both the provider-native discovery output and T3's cached provider metadata. A skill may exist on disk and be visible to the underlying agent while T3 still fails to expose or route it.
For the 2026-05-16 skill issue, the important evidence was provider-specific:
~/.t3/caches/claudeAgent.json listed arscontexta entries as slash commands, including next, remember, distill, and connect.
~/.t3/caches/codex.json listed 22 Codex skills, including arscontexta skills such as next, remember, distill, and connect.
~/.t3/caches/cursor.json listed skills: [] and slashCommands: [] even though arscontexta skill symlinks existed in ~/.cursor/skills/ and project .cursor/skills/.
~/.t3/caches/opencode.json listed skills: [] and slashCommands: [] even though opencode debug skill emitted arscontexta skills from ~/.opencode/skill/*/SKILL.md.
- Manually pasting a
<skill> block into the conversation made Codex follow the skill body, so the model can execute the instructions when T3 provides them.
Future debugging should separate three layers: filesystem discovery, T3 provider cache population, and chat-input command routing/injection.
Expected behavior
T3Code should ingest and expose provider skills consistently across supported providers.
Claude provider: arscontexta skills appear as slash commands.
Codex provider: arscontexta skills appear as skills.
Cursor provider: user/project skills from ~/.cursor/skills/ and .cursor/skills/ should appear in T3Code’s provider cache and be invocable.
OpenCode provider: skills from ~/.config/opencode/skill/, ~/.opencode/skill/, and commands from ~/.config/opencode/command/ should appear in T3Code’s provider cache and be invocable.
Actual behavior
T3Code only sees skills/commands for Claude and Codex. Cursor and OpenCode provider caches report no skills or slash commands even though the files exist on disk.
Observed T3 provider cache summary:
claudeAgent: slashCommands_count=49, includes arscontexta commands
codex: skills_count=22, includes arscontexta skills
cursor: skills_count=0, slashCommands_count=0
opencode: skills_count=0, slashCommands_count=0
Skill files exist for Cursor/OpenCode:
~/.cursor/skills/next
~/.cursor/skills/remember
~/.config/opencode/skill/next
~/.opencode/skill/next
~/.config/opencode/command/next.md
Impact
Cosmetic issue
Version or commit
T3Code desktop: T3-Code-0.0.24-x86_64.AppImage Codex: codex-cli 0.129.0 OpenCode: 1.15.3 Cursor agent: 2026.05.16-0338208
Environment
No response
Logs or stack traces
Relevant cache evidence:
~/.t3/caches/claudeAgent.json:
slashCommands_count=49
includes connect, distill, next, remember, validate, verify
~/.t3/caches/codex.json:
skills_count=22
includes connect, distill, next, remember, validate, verify
~/.t3/caches/cursor.json:
slashCommands_count=0
skills_count=0
~/.t3/caches/opencode.json:
slashCommands_count=0
skills_count=0
OpenCode itself can see the skills, but T3Code cache does not:
opencode debug skill
next -> ~/.opencode/skill/next/SKILL.md
remember -> ~/.opencode/skill/remember/SKILL.md
connect -> ~/.opencode/skill/connect/SKILL.md
distill -> ~/.opencode/skill/distill/SKILL.md
Screenshots, recordings, or supporting files
opencode.json
cursor.json
codex.json
claudeAgent.json
Workaround
manually paste the relevant SKILL.md content into the chat, or use the provider directly outside T3Code. For OpenCode specifically, native opencode debug skill can see the skills, so the issue appears to be T3Code’s provider cache/discovery layer rather than the skill files themselves.
Before submitting
Area
apps/desktop
Steps to reproduce
description: T3Code exposes skills for Claude/Codex providers but its Cursor/OpenCode provider caches can report zero skills despite files existing.
category: processing
created: 2026-05-16
status: active
T3Code skill bugs need per-provider cache evidence
When investigating T3Code skill behavior, check both the provider-native discovery output and T3's cached provider metadata. A skill may exist on disk and be visible to the underlying agent while T3 still fails to expose or route it.
For the 2026-05-16 skill issue, the important evidence was provider-specific:
~/.t3/caches/claudeAgent.jsonlisted arscontexta entries as slash commands, includingnext,remember,distill, andconnect.~/.t3/caches/codex.jsonlisted 22 Codex skills, including arscontexta skills such asnext,remember,distill, andconnect.~/.t3/caches/cursor.jsonlistedskills: []andslashCommands: []even though arscontexta skill symlinks existed in~/.cursor/skills/and project.cursor/skills/.~/.t3/caches/opencode.jsonlistedskills: []andslashCommands: []even thoughopencode debug skillemitted arscontexta skills from~/.opencode/skill/*/SKILL.md.<skill>block into the conversation made Codex follow the skill body, so the model can execute the instructions when T3 provides them.Future debugging should separate three layers: filesystem discovery, T3 provider cache population, and chat-input command routing/injection.
Expected behavior
T3Code should ingest and expose provider skills consistently across supported providers.
Claude provider: arscontexta skills appear as slash commands.
Codex provider: arscontexta skills appear as skills.
Cursor provider: user/project skills from ~/.cursor/skills/ and .cursor/skills/ should appear in T3Code’s provider cache and be invocable.
OpenCode provider: skills from ~/.config/opencode/skill/, ~/.opencode/skill/, and commands from ~/.config/opencode/command/ should appear in T3Code’s provider cache and be invocable.
Actual behavior
T3Code only sees skills/commands for Claude and Codex. Cursor and OpenCode provider caches report no skills or slash commands even though the files exist on disk.
Observed T3 provider cache summary:
claudeAgent: slashCommands_count=49, includes arscontexta commands
codex: skills_count=22, includes arscontexta skills
cursor: skills_count=0, slashCommands_count=0
opencode: skills_count=0, slashCommands_count=0
Skill files exist for Cursor/OpenCode:
~/.cursor/skills/next
~/.cursor/skills/remember
~/.config/opencode/skill/next
~/.opencode/skill/next
~/.config/opencode/command/next.md
Impact
Cosmetic issue
Version or commit
T3Code desktop: T3-Code-0.0.24-x86_64.AppImage Codex: codex-cli 0.129.0 OpenCode: 1.15.3 Cursor agent: 2026.05.16-0338208
Environment
No response
Logs or stack traces
Screenshots, recordings, or supporting files
opencode.json
cursor.json
codex.json
claudeAgent.json
Workaround
manually paste the relevant SKILL.md content into the chat, or use the provider directly outside T3Code. For OpenCode specifically, native opencode debug skill can see the skills, so the issue appears to be T3Code’s provider cache/discovery layer rather than the skill files themselves.