The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
npx ecc-install --profile fullFair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
npx n8nAn open-source AI agent that brings the power of Gemini directly into your terminal.
npx @google/gemini-cliThese intent pages connect this repository to workflow-first and comparison-first discovery routes.
Built around typescript tooling
Supports Claude Code, Cursor, Windsurf, Mcp
Shows active maintenance signals
Carries strong trust indicators from repository metadata
881 GitHub stars recorded
1. Run the Octocode CLI with npx
npx octocode --help
2. Authenticate with GitHub — optional, but unlocks private repositories and higher API rate limits:
npx octocode auth login
npx octocode status # verify the active token source
3. Choose your interface. The same engine and 14 tools run identically either way.
🖥️ CLI — research straight from your terminal:
npx octocode
🤖 MCP — one-click install:
Claude Code:
claude mcp add-json octocode --scope user '{"command":"npx","type":"stdio","args":["@octocodeai/mcp@latest"]}'
Any other client: npx octocode install
➡️ Learn more at octocode.ai.
Everything is optional; Octocode runs on sensible defaults. Settings resolve from three sources, in priority order:
environment variables > <octocode-home>/.octocoderc > built-in defaults
env or your shell.<octocode-home>/.octocoderc, machine-wide defaults read by both the CLI and the MCP server.Octocode home (<octocode-home>) holds the global config, encrypted credentials, sessions, stats, and tmp materialization caches. It defaults by platform and can be overridden with OCTOCODE_HOME:
| Platform | Location |
|---|---|
| macOS | ~/.octocode |
| Linux | ${XDG_CONFIG_HOME:-~/.config}/.octocode |
| Windows | %APPDATA%\.octocode |
Set values as MCP env entries (per client; these win over .octocoderc) or globally in <octocode-home>/.octocoderc (JSON with comments). Tokens never go in .octocoderc — use env or npx octocode auth login.
The Scope column shows where a setting applies: Both, or MCP (the CLI ignores it).
| Env var | .octocoderc key | Default | Scope | What it does |
|---|---|---|---|---|
OCTOCODE_HOME | env only | platform default | Both | Overrides the Octocode data directory for config, credentials, sessions, stats, and caches. |
OCTOCODE_TOKEN / GH_TOKEN / GITHUB_TOKEN | env only | unset | Both | GitHub token, in priority order. Tokens stay in env, never in .octocoderc. |
GITHUB_API_URL | github.apiUrl | https://api.github.com | Both | API endpoint; use /api/v3 for GitHub Enterprise. |
ENABLE_LOCAL | local.enabled | true | Both | Turns local filesystem + LSP tools on/off; set false to disable. |
ENABLE_CLONE | local.enableClone | CLI true, MCP false | Both | ghCloneRepo and directory fetch. Default differs by surface; set false to disable in either. |
WORKSPACE_ROOT | local.workspaceRoot | cwd | Both | Absolute root for resolving relative local paths. |
ALLOWED_PATHS | local.allowedPaths | [] | Both | Extra path allowlist for local access; empty means home directory only after validation. |
TOOLS_TO_RUN / ENABLE_TOOLS / DISABLE_TOOLS | tools.* | unset | MCP | Whitelist, add to, or remove from the registered tool set. The CLI exposes every tool. |
REQUEST_TIMEOUT | network.timeout | 30000 | Both | Request timeout in ms (clamped 5000..300000). |
MAX_RETRIES | network.maxRetries | 3 | Both | Retry attempts (clamped 0..10). |
OCTOCODE_OUTPUT_FORMAT | output.format | yaml | Both | Response format: yaml or json. |
Local defaults on; clone differs by surface. Both CLI and MCP default local tools on; set
ENABLE_LOCAL=falseto disable them. The CLI defaults clone on, while the MCP server requiresENABLE_CLONE=true.
Per-project overrides and custom LSP servers live in a workspace .octocode/ folder. For the full .octocoderc schema, a ready-to-copy example, clone-cache tuning, GitHub Enterprise setup, and precedence details, see the Configuration Reference.