This repo contains portable OpenCode configurations. Each subdirectory is a self-contained config — set OPENCODE_CONFIG_DIR to any subdirectory and start opencode to launch with that configuration (e.g., OPENCODE_CONFIG_DIR=~/opencode-config/mcp-synapse opencode). This makes it easy to maintain multiple independent setups (agent councils, MCP servers, specialized toolchains) and swap between them with a shell alias.

Shell Aliases

This repo includes a .aliases file that defines all opencode shell aliases. Run the install script to add them to your shell:

./scripts/install_aliases.sh

This appends a sourcing block to ~/.aliases that sets OPENCODE_CONFIG_REPO to wherever this repo lives on disk. To do it manually instead:

export OPENCODE_CONFIG_REPO="/path/to/opencode-config"
[ -f "$OPENCODE_CONFIG_REPO/.aliases" ] && source "$OPENCODE_CONFIG_REPO/.aliases"

This gives you:

omo-* aliases to swap oh-my-openagent model profiles (Bedrock and personal)
openagent, openagent-latest to launch opencode with a local or npm plugin build
synapse, pdf-reader to launch opencode with MCP server configs
council, council-bio, council-security to launch agent councils

Per-machine setup

The openagent alias requires a one-time setup to generate the opencode.json with your machine's absolute path to the oh-my-openagent clone:

./scripts/setup_omo_plugin.sh

Then use: omo-anthropic (set model profile), then openagent (launch with local plugin) or openagent-latest (launch with npm latest).

Docs

Building a Council of Personas — how to define agents with different expertise areas, assign models, and orchestrate them
MCP Server Configs — how to connect OpenCode to MCP servers like Synapse

Readme.md

opencode-config

Shell Aliases

Per-machine setup

Docs

See Also