Configuration
Environment variables, MCP servers, and memory tier setup.
OrchestKit works out of the box with zero configuration. This page covers optional settings for power users.
Environment Variables
Core (Auto-Detected)
| Variable | Description | Default |
|---|---|---|
CLAUDE_PROJECT_DIR | Your project root | Auto-detected |
CLAUDE_PLUGIN_ROOT | Plugin installation path | Auto-detected |
CLAUDE_SESSION_ID | Current session UUID | Auto-generated |
Web Research (Optional)
| Variable | Description | Effect |
|---|---|---|
TAVILY_API_KEY | Tavily search API | Enables search/extract/map in web research workflow |
Setting Variables
Add to your shell profile (~/.zshrc, ~/.bashrc, or ~/.config/fish/config.fish):
# Web Research
export TAVILY_API_KEY="tvly-your-key-here"Then restart Claude Code or open a new terminal.
Memory Tiers
OrchestKit has 3 memory tiers. All work automatically with zero configuration:
| Tier | Storage | Config Needed | What It Does |
|---|---|---|---|
| 1. Graph | MCP mcp__memory__* | None (zero-config) | Knowledge graph: entities + relations |
| 2. Local | .claude/memory/*.jsonl | None (auto-created) | Session persistence, queue sync |
| 3. CC Native | ~/.claude/projects/*/memory/MEMORY.md | None (auto-sync) | Injected into system prompt |
High-confidence decisions (confidence >= 0.7) automatically promote from Graph to CC Native, ensuring they persist even without OrchestKit installed.
MCP Servers
OrchestKit ships with 4 MCPs enabled by default in .mcp.json:
| MCP | Purpose | Default |
|---|---|---|
context7 | Up-to-date library docs (no key needed) | enabled |
memory | Knowledge graph — persists decisions across sessions | enabled |
tavily | Web search, extract, crawl (requires API key) | enabled |
agentation | UI annotation — browser feedback picked up automatically | enabled |
sequential-thinking | Complex reasoning (optional — Opus 4.6 has native thinking) | disabled |
Tavily Setup
Tavily requires a free API key (app.tavily.com — 1,000 credits/month free).
Option A — 1Password (recommended):
op item create --category "API Credential" --title "Tavily API Key" "API Key=tvly-..."The .mcp.json entry uses op read to fetch it at startup — no key in config files.
Option B — environment variable:
export TAVILY_API_KEY="tvly-your-key-here"Then update .mcp.json to use "${TAVILY_API_KEY}" in the env block.
Option C — Remote MCP (no local process):
"tavily": {
"type": "url",
"url": "https://mcp.tavily.com/mcp/?tavilyApiKey=YOUR_KEY"
}Disabling an MCP
Set "disabled": true for any MCP in .mcp.json:
"sequential-thinking": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-sequential-thinking"],
"disabled": true
}Without MCPs
All skills and agents work without MCPs — they add extra capabilities:
- Without
context7:/implementworks but won't fetch latest library docs - Without
tavily: web research falls back toWebFetch→agent-browser - Without
memory: decisions persist via local files and CC Native memory
Hook Behavior
Hooks fire automatically. If a hook blocks an action unexpectedly:
- Check which hook blocked: the error message includes the hook name
- Hooks you can customize:
- file-guard: Protected file paths and file size limits (override with
ORCHESTKIT_MAX_FILE_LINES/ORCHESTKIT_MAX_TEST_FILE_LINESenv vars) - dangerous-command-blocker: Blocked commands list
- permission auto-approve: Safe command patterns
- file-guard: Protected file paths and file size limits (override with
Most users never need to customize hooks. They're designed to be transparent.
Plugin Settings
Run /ork:configure to adjust:
- Notification preferences (desktop alerts, sounds)
- Memory sync frequency
- Hook toggle system (enable/disable specific hooks)
- Agent model preferences
Next Steps
- The 3 Building Blocks — Understand the architecture
- Memory System — Deep dive into 3-tier memory
Find What You Need
Hub-and-spoke navigation — find the right skills and agents for your role and task.
Cookbook
Step-by-step workflow walkthroughs for common development tasks with OrchestKit.
Last updated on