Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/lnardev/opencode-config-agent/llms.txt

Use this file to discover all available pages before exploring further.

Installing OpenCode Config Agent means placing a set of configuration files — agents, prompts, skills, plugins, and MCP server definitions — into the directory that OpenCode reads at startup (~/.config/opencode/). Installation covers cloning the repo, installing plugin dependencies, optionally setting up the Engram binary for persistent memory, and verifying that all agents and MCP servers load correctly. This guide covers both a fresh install and merging into an existing OpenCode config.

​
Prerequisites

The following tools must be available before you install:
ToolRequirementNotes
OpenCodeRequiredThe AI terminal this config runs inside
Node.js18+For installing plugin dependencies via npm
BunOptional (recommended)Faster alternative to npm — bun.sh
GitRequiredFor cloning and pulling updates
Engram binaryOptionalRequired for persistent memory across sessions — see MCP Server Setup below

​
Installation Methods

If you don’t have anything in ~/.config/opencode/ yet, clone directly into that directory:
git clone https://github.com/lnardev/opencode-config-agent ~/.config/opencode
Then install dependencies:
cd ~/.config/opencode && npm install
That’s it. The next time you run opencode in any project, the agents and MCP servers will be loaded automatically.

​
Install Plugin Dependencies

The plugins/ directory contains TypeScript plugins that depend on npm packages. Install them from the config directory: 
cd ~/.config/opencode
npm install
This installs the two required packages declared in package.json: 
{
  "dependencies": {
    "@opencode-ai/plugin": "1.4.6",
    "unique-names-generator": "^4.7.1"
  }
}

​
Verify Installation

Once dependencies are installed, open OpenCode inside any project and confirm the agents loaded correctly: 
cd ~/your-project
opencode
In the OpenCode chat, type: 
/sdd-onboard
If the sdd-onboard agent responds with a guided walkthrough prompt, your installation is working. If you see an error or an unrecognized command, check that:
  1. The prompts/ directory was copied correctly and contains the SDD prompt files
  2. The opencode.json has the agent block with all SDD agents defined
  3. Plugin dependencies were installed successfully (node_modules/ exists in ~/.config/opencode/)

​
MCP Server Setup

OpenCode Config Agent ships with three MCP servers pre-configured in opencode.json. Their setup requirements vary:

​
context7 — Remote, No Setup Required

context7 is a remote MCP server that provides up-to-date library documentation. It’s already configured with its URL and requires no local installation: 
"context7": {
  "enabled": true,
  "type": "remote",
  "url": "https://mcp.context7.com/mcp"
}
It will connect automatically when OpenCode starts.

​
Engram — Requires Local Binary

engram is the persistent memory MCP server. It runs as a local process and requires the engram binary to be installed and available on your PATH. Install on macOS via Homebrew: 
brew install engram
The config expects the binary at /opt/homebrew/bin/engram (the default Homebrew location on Apple Silicon). If your Homebrew prefix is different, update the path in opencode.json: 
"engram": {
  "command": [
    "/opt/homebrew/bin/engram",
    "mcp",
    "--tools=agent"
  ],
  "type": "local"
}
To find your engram binary path after installation: 
which engram
Replace /opt/homebrew/bin/engram in opencode.json with the output of that command.
Engram is optional but strongly recommended. Without it, the Tony Stark agent’s mandatory memory protocol has nowhere to persist data, and the SDD orchestrator defaults to none artifact store mode — returning results inline only, with no cross-session recovery.

​
chrome-devtools — Runs via npx, No Setup Required

The chrome-devtools MCP server runs on-demand via npx and requires no global installation: 
"chrome-devtools": {
  "command": ["npx", "-y", "chrome-devtools-mcp@latest"],
  "type": "local"
}
It will be downloaded and executed automatically the first time it’s invoked.

​
Updating

To pull the latest changes and refresh your dependencies: 
cd ~/.config/opencode
git pull
npm install
If you’re using Bun: 
cd ~/.config/opencode
git pull
bun install
If you’ve added custom API keys, personal tokens, or private credentials directly to opencode.json (for example, in the mcp headers section), make sure those values are not committed to version control. Add opencode.json to your .gitignore or use environment variables instead. Committing credentials to a public or shared repository is a security risk.

Build docs developers (and LLMs) love

Get started for freeTalk to us