anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Feature Request: Configurable skills search paths & TUI settings management #7978

New Issue
Open
opened 2026-02-16 18:08:50 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 18:08:50 -05:00
Owner
Copy Link
Copy Source

Originally created by @AllyourBaseBelongToUs on GitHub (Jan 29, 2026).

Originally assigned to: @thdxr on GitHub.

Feature Request

Summary: Add JSON config and TUI-based management for skills search directories

Current Situation

Version: 1.1.42

The symlink workaround works:

New-Item -ItemType SymbolicLink -Path ~/.config/opencode/skills -Target ~/.claude/skills

After which opencode debug skill shows skills from both locations. However, this is not well-documented and requires manual CLI setup.

Problem

  1. No JSON configuration - Skills search paths are hardcoded in source, not configurable via opencode.json
  2. No TUI settings management - Cannot toggle directories or change search priority through the interface
  3. Documentation gap - Not clear how to share skills between Claude Code and OpenCode

Proposed Solution

Part 1: JSON Configuration

Add skills section to opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "skills": {
    "search_paths": [
      "C:\Users\<user>\.claude\skills",
      "C:\Users\<user>\.config\opencode\skills",
      ".opencode/skills/"
    ],
    "enabled": true
  }
}

Part 2: TUI Settings Management

Add a settings UI (maybe accessible via Ctrl+S or a settings command) that allows:

  • Toggle directories on/off for skill searching
  • Reorder search priority via drag-and-drop or arrow keys
  • Add custom paths through the UI
  • Visual indicator of which directory each skill loaded from

Example TUI flow:

┌─ OpenCode Settings ─────────────────┐
│ Skills Search Paths:                │
│ ☑ C:\Users\...\.claude\skills      │
│ ☑ C:\Users\...\.config\opencode\   │
│ ☑ .opencode/skills/                │
│                                    │
│ [↑↓] Reorder  [Enter] Toggle       │
│ [+ ] Add custom path               │
│ [Esc] Save & Exit                  │
└────────────────────────────────────┘

Use Cases

  1. Share skills between Claude Code and OpenCode without symlinks
  2. Disable project-specific skills temporarily when working on shared projects
  3. Prioritize global skills over local ones (or vice versa)
  4. Add team skill libraries from network shares or cloud storage

Alternatives Considered

  • Symlink workaround - Works but not discoverable, requires CLI
  • Environment variables - Already supported via OPENCODE_CONFIG_DIR, but single path only and no UI

References

  • Claude Code has configurable search_paths for skills
  • Users increasingly use multiple AI CLI tools and want to share configuration
Originally created by @AllyourBaseBelongToUs on GitHub (Jan 29, 2026). Originally assigned to: @thdxr on GitHub. ## Feature Request **Summary:** Add JSON config and TUI-based management for skills search directories ## Current Situation **Version:** 1.1.42 The symlink workaround works: ```bash New-Item -ItemType SymbolicLink -Path ~/.config/opencode/skills -Target ~/.claude/skills ``` After which `opencode debug skill` shows skills from both locations. However, this is not well-documented and requires manual CLI setup. ## Problem 1. **No JSON configuration** - Skills search paths are hardcoded in source, not configurable via `opencode.json` 2. **No TUI settings management** - Cannot toggle directories or change search priority through the interface 3. **Documentation gap** - Not clear how to share skills between Claude Code and OpenCode ## Proposed Solution ### Part 1: JSON Configuration Add `skills` section to `opencode.json`: ```json { "$schema": "https://opencode.ai/config.json", "skills": { "search_paths": [ "C:\Users\<user>\.claude\skills", "C:\Users\<user>\.config\opencode\skills", ".opencode/skills/" ], "enabled": true } } ``` ### Part 2: TUI Settings Management Add a settings UI (maybe accessible via `Ctrl+S` or a settings command) that allows: - **Toggle directories** on/off for skill searching - **Reorder search priority** via drag-and-drop or arrow keys - **Add custom paths** through the UI - **Visual indicator** of which directory each skill loaded from Example TUI flow: ``` ┌─ OpenCode Settings ─────────────────┐ │ Skills Search Paths: │ │ ☑ C:\Users\...\.claude\skills │ │ ☑ C:\Users\...\.config\opencode\ │ │ ☑ .opencode/skills/ │ │ │ │ [↑↓] Reorder [Enter] Toggle │ │ [+ ] Add custom path │ │ [Esc] Save & Exit │ └────────────────────────────────────┘ ``` ## Use Cases 1. **Share skills between Claude Code and OpenCode** without symlinks 2. **Disable project-specific skills** temporarily when working on shared projects 3. **Prioritize global skills** over local ones (or vice versa) 4. **Add team skill libraries** from network shares or cloud storage ## Alternatives Considered - **Symlink workaround** - Works but not discoverable, requires CLI - **Environment variables** - Already supported via `OPENCODE_CONFIG_DIR`, but single path only and no UI ## References - Claude Code has configurable `search_paths` for skills - Users increasingly use multiple AI CLI tools and want to share configuration
yindo commented 2026-02-16 18:08:50 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Jan 29, 2026):

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

  • #10976: [FEATURE]: Support Multi-level Nested Skill Directory Structure

While #10976 focuses on nested directory organization for skills, this request (#11189) extends that concept with JSON configuration and TUI management of search paths. Feel free to ignore if these address different aspects of your needs.

@github-actions[bot] commented on GitHub (Jan 29, 2026): This issue might be a duplicate of existing issues. Please check: - #10976: [FEATURE]: Support Multi-level Nested Skill Directory Structure While #10976 focuses on nested directory organization for skills, this request (#11189) extends that concept with JSON configuration and TUI management of search paths. Feel free to ignore if these address different aspects of your needs.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#7978
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?