Skip to content

Claude integration does not load installed Skills, Slash Commands, or CLAUDE.md memory #1283

Description

@timmske

Summary

The Claude Agent SDK integration in ClaudeAdapter.ts does not pass settingSources to the SDK's query options. As a result, all filesystem-based Claude Code features are silently ignored:

  • Skills (.claude/skills/ and ~/.claude/skills/) — never discovered
  • Slash Commands (.claude/commands/ and ~/.claude/commands/) — never loaded
  • CLAUDE.md memory (CLAUDE.md, .claude/CLAUDE.md) — never read

This means users who have installed Skills (e.g. Impeccable for design review, or any custom Skills) cannot use them through t3code, even though they work perfectly in the Claude Code CLI.

Root Cause

In apps/server/src/provider/Layers/ClaudeAdapter.ts (line ~2561), the queryOptions object is missing the settingSources property:

const queryOptions: ClaudeQueryOptions = {
    ...(input.cwd ? { cwd: input.cwd } : {}),
    ...(input.model ? { model: input.model } : {}),
    pathToClaudeCodeExecutable: providerOptions?.binaryPath ?? "claude",
    // ... other options ...
    includePartialMessages: true,
    canUseTool,
    env: process.env,
    ...(input.cwd ? { additionalDirectories: [input.cwd] } : {}),
    // ⛔ Missing: settingSources
};

Per the official Agent SDK documentation:

"By default, the SDK does not load any filesystem settings. To use Skills, you must explicitly configure settingSources: ['user', 'project']."

Proposed Fix

Add settingSources to the query options:

const queryOptions: ClaudeQueryOptions = {
    // ... existing options ...
    settingSources: ["user", "project"],  // Load Skills, Commands, and CLAUDE.md
};

This could also be made configurable via providerOptions so users can control which sources are loaded (e.g. only "project" for shared team setups, or "user" for personal Skills).

Impact

  • Any user with installed Claude Code Skills (user-level in ~/.claude/skills/ or project-level in .claude/skills/) will find that they are completely ignored in t3code
  • CLAUDE.md project memory files are not loaded, so project-specific instructions don't apply
  • Custom slash commands defined in .claude/commands/ are not available

Steps to Reproduce

  1. Install a Skill in ~/.claude/skills/ (e.g. the Impeccable design review Skill)
  2. Open t3code and start a Claude session
  3. Ask Claude to use the installed Skill (e.g. "use Impeccable to review the design")
  4. Expected: Claude invokes the Skill
  5. Actual: Claude has no knowledge of the Skill and cannot use it

Environment

  • @anthropic-ai/claude-agent-sdk v0.2.77
  • Verified against SDK documentation as of 2026-03-21

Activity

  1. TaylorJonesTRT commented on Mar 22, 2026

    @TaylorJonesTRT

    I believe I've been noticing this too when using the Claude Code adapter when it comes to using CLAUDE.md/AGENTS.md files and it not picking up on that for its context/memory.

  2. JoanLaRosa commented on Mar 23, 2026

    @JoanLaRosa

    agree, this makes t3 code unusable as I rely so heavily on Agents/Skills and Commands

  3. mwolson commented on Mar 24, 2026

    @mwolson
    Contributor

    The fix for this landed in #1334 (merged 2026-03-23), which adds settingSources: ["user", "project", "local"] to the Claude adapter's queryOptions.

  4. drj613 commented on Mar 24, 2026

    @drj613

    I'm not seeing slash commands even with that pulled in

    Image

    vs Claude Code:

    Image

    If I ask the agent what skills it has available it does properly list them all out, but the /commands don't get propagated to the UI when typing my input. Codex is also missing its $skill commands

  5. V4G4X commented on Apr 10, 2026

    @V4G4X

    The ONLY feature I'm waiting for to fully switch to t3code. ❤️

  6. cafreeman commented on Apr 10, 2026

    @cafreeman

    Same, this is the single-biggest blocker for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions