opencode-add-dir
v1.7.2
Published
Add working directories to your OpenCode session with auto-approved permissions
Maintainers
Readme
opencode-add-dir
Add working directories to your OpenCode session — inspired by Claude Code's /add-dir command.
When you need an agent to read, edit, or search files outside the current project, this plugin grants access without permission popups.
Quick Start
opencode plugin opencode-add-dir -gRestart OpenCode. The plugin auto-registers itself in your tui.json — no manual config needed.
git clone https://github.com/kuzeofficial/add-dir-opencode.git
cd add-dir-opencode
bun install && bun run deployAdd the local path to both configs:
// ~/.config/opencode/opencode.json
{ "plugin": ["/path/to/add-dir-opencode"] }
// ~/.config/opencode/tui.json
{ "plugin": ["/path/to/add-dir-opencode"] }Commands
All commands are interactive TUI dialogs — type the command and select from autocomplete.
| Command | Dialog | Description |
|---------|--------|-------------|
| /add-dir | Text input + remember checkbox | Add a working directory. Toggle [x] Remember with tab to persist across sessions. |
| /list-dir | Alert | Shows all added directories. |
| /remove-dir | Select list + confirm | Pick a directory to remove, then confirm. |
How It Works
The plugin has two parts: a TUI plugin for the interactive dialogs and a server plugin for silent permission handling.
TUI Plugin
Handles all three slash commands via dialogs. Directories are stored in two files under ~/.local/share/opencode/add-dir/:
directories.json— Persisted dirs, survive restarts.session-dirs.json— Session-only dirs, cleared automatically on startup.
Which file gets written depends on the "Remember across sessions" toggle in /add-dir.
Respects
XDG_DATA_HOMEif set.
Server Plugin
Runs in the background — no commands, only hooks:
| Hook | What it does |
|------|-------------|
| config | Injects external_directory: "allow" permission rules for all added dirs at startup |
| tool.execute.before | Pre-authorizes sessions when file tools (read, write, edit, bash, glob, grep, list, apply_patch, multiedit) target an added directory |
| event | Listens for permission.asked events and auto-approves when the path matches an added directory |
| experimental.chat.system.transform | Injects added directory paths into the system prompt so the LLM knows about them |
These three permission layers work together: config handles startup rules, tool.execute.before handles proactive grants during tool calls, and event catches any runtime permission requests that still come through.
Context Injection
By default the system prompt only gets the list of added directories. If you set:
export OPENCODE_ADDDIR_INJECT_CONTEXT=1The plugin will also read and inject AGENTS.md, CLAUDE.md, and .agents/AGENTS.md from each added directory into the system prompt — useful when working across projects that have their own agent instructions.
Development
bun install
bun test # Run tests
bun run typecheck # Type check
bun run build # Build npm package
bun run deploy # Build server + TUI locallyProject Structure
src/
├── index.ts # Server plugin entry
├── plugin.ts # Server hooks (permissions, context injection)
├── tui-plugin.tsx # TUI plugin (dialogs for add/list/remove)
├── state.ts # Persistence, caching, path utils, tui.json auto-config
├── permissions.ts # Session grants + auto-approve
├── context.ts # System prompt injection
└── types.ts # Shared type definitions