Skip to content

Feature Request: Add configuration option to disable automatic Claude Code skills/commands sync #12604

Closed

Description

@yy1588133

Problem Statement

Currently, OpenCode automatically discovers and loads skills and commands from Claude Code compatible directories:

Skills:

  • ~/.claude/skills/<name>/SKILL.md
  • .claude/skills/<name>/SKILL.md
  • ~/.agents/skills/<name>/SKILL.md (agents-compatible)
  • .agents/skills/<name>/SKILL.md (agents-compatible)

Commands:

  • .claude/commands/ (implied from docs)

While this compatibility is convenient for users migrating from Claude Code, there is no way to opt-out of this automatic synchronization for users who want to keep their OpenCode configuration separate.

Use Case

As a user who uses both Claude Code and OpenCode with different workflows, I would like to:

  1. Keep Claude Code's skills/commands separate from OpenCode
  2. Avoid polluting OpenCode's skill list with Claude-specific skills that may not be relevant
  3. Have explicit control over which skills/commands are available in each tool

Proposed Solution

Add a configuration option in opencode.json to disable Claude Code compatibility paths:

{
  "": "https://opencode.ai/config.json",
  "claude_compatibility": {
    "skills": false,
    "commands": false
  }
}

Or alternatively, a simpler boolean toggle:

{
  "sync_claude_config": false
}

Default behavior: true (maintain backward compatibility)

Current Workarounds

The only way to prevent this currently is to rename or remove the .claude/ directory, which is disruptive for users who actively use both tools.

Related Documentation


Would you consider adding this feature? Happy to discuss alternative approaches.

Activity

  1. github-actions commented on Feb 7, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

    Feel free to ignore if none of these address your specific case.

  2. ariane-emory commented on Feb 7, 2026

    @ariane-emory
    Contributor

    Changing the shape of the configuration object is often a tough sell. :/

  3. R44VC0RP commented on Feb 7, 2026

    @R44VC0RP
    Contributor

    There's already an env var for this — set OPENCODE_DISABLE_CLAUDE_CODE_SKILLS=true to skip .claude/skills/ and .agents/skills/ paths (see packages/opencode/src/flag/flag.ts:24-27).

    For commands: .claude/commands/ compatibility doesn't exist yet. PR #6990 is open to add it but hasn't merged. So there's nothing to disable on the commands side.

    If you want this controllable via opencode.json instead of env vars, that's a separate feature request — right now these Claude compatibility toggles are env-only. Would accept a PR to add config schema for it, but env var works today.

  4. junsu-min-ilevit-com commented on Feb 14, 2026

    @junsu-min-ilevit-com

    Checking resolution

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

Metadata

Metadata

Assignees

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