Opencode Workbench

OpenCode Workbench

A reproducible, self-documenting, and recoverable OpenCode development workstation — configuration, agent skills, MCP stack, and an MCP server that clones the entire setup onto any Linux machine (locally or over SSH).

Homepage & remote MCP: https://opencode-workbench.simonmak.com · POST https://opencode-workbench.simonmak.com/mcp

Overview

This repository is the single source of truth for a complete cloud development workstation. Everything needed to rebuild from scratch is versioned here:

• Workstation configuration and automation
• OpenCode configuration (model, providers, MCP servers)
• Agent skills (76 reusable AI instructions across research, dev, data, science and ops)
• Operational prompts (disaster recovery, backup, security)
• Recovery procedures (playbook, checklist, gap analysis)
• Security governance (secret management, threat model)
• OpenCode sandbox (bubblewrap) — run the agent with a read-only system and no secret mounts
• `opencode-workbench` — an MCP server that installs this profile on any Linux box

No important knowledge exists only in human memory.

Clone This Workbench to Another Linux Machine

Register the MCP server with OpenCode:

{

"mcp": { "opencode-workbench": { "type": "local", "command": ["npx", "-y", "@simonmak-ascent/opencode-workbench"], "enabled": true, "timeout": 600000 } } }

Then ask the agent to run inspect_target → plan_clone → apply_clone { confirm: true } → verify_clone, for { "mode": "local" } or { "mode": "ssh", "host": " ", "user": " " }. apply_clone is consent-gated: without confirm:true it returns a plan (components + privileged-command preview) and changes nothing. Run list_required_credentials to see which keys the box still needs and how to acquire them, and bash scripts/selftest/run-selftest.sh to verify it works. See mcp-server/README.md and docs/architecture/clone-mcp.md.

The clone is key-resilient: with no model key it still boots on the OpenCode Zen free floor, and MCP servers whose credentials are absent are disabled and reported (not left to fail at runtime).

The connector never reads or transmits secret values; it writes an empty ~/.env.workbench template for you to fill in.

Quick Start (≤ 5 minutes)

Fastest path: no box required — register the MCP server with npx -y @simonmak-ascent/opencode-workbench (config in Clone This Workbench); or provision a fresh box:

# Create a new build box

gh SWAS create --repo simonmak-ascent/opencode-workbench --machine basicLinux32gb

Wait for postCreate (3-5 min) — installs everything automatically

Then start coding:

opencode

Architecture

flowchart TB

AGENT["OpenCode agent"] -->|"npx @simonmak-ascent/opencode-workbench"| MCP["opencode-workbench MCP inspect · plan · apply · verify"] REPO[("Git repo — single source of truth")] --> MCP MCP -->|"local or SSH"| BOX["Target Linux box"] BOX --> PROF["Workstation profile OpenCode CLI · 31 MCP servers · 76 skills · Docker infra"]

Clone lifecycle

apply_clone is consent-gated: without confirm: true it returns a plan and changes nothing.

sequenceDiagram

autonumber participant A as OpenCode agent participant M as opencode-workbench MCP participant B as Target box (local or SSH) A->>M: inspect_target M-->>A: OS, toolchain, Docker, existing config A->>M: plan_clone M-->>A: components + privileged-command preview A->>M: apply_clone { confirm: true } M->>B: install components · write ~/.env.workbench template B-->>M: result A->>M: verify_clone M-->>A: pass/fail + missing credentials

MCP tool surface

flowchart LR

A["OpenCode agent"] --> D["Discovery describe_workbench · inspect_target"] A --> C["Clone plan_clone · apply_clone · verify_clone"] A --> K["Components install · remove · update_component"] A --> S["Credentials list_required_credentials · run_auth_flow"]

opencode-workbench/ ├── mcp-server/ # opencode-workbench: clone this profile onto Linux │ ├── src/ # inspect / plan / apply / verify, local + SSH │ ├── test/ # unit tests (vitest) │ └── README.md ├── connector.json # MCP connector manifest / registration snippet ├── plugins/ # memory.ts + doc-tools.ts OpenCode plugins ├── package.json # thin launcher for opencode-workbench (bin + prepare) ├── .devcontainer/ # build box definition & bootstrap │ ├── devcontainer.json # Container image, features, ports, remoteEnv │ ├── setup.sh # Post-create: installs opencode, MCPs, Docker infra │ └── aliases.sh # Shell aliases sourced at runtime ├── .opencode/ │ └── skills/ # 76 agent skills, one directory per SKILL.md ├── vendor/ # Vendored MCP source code │ ├── perplexity-agent-mcp/ │ └── browserless-mcp/ ├── configs/ # Reference configurations │ ├── mcp/ # MCP server inventory & architecture │ ├── opencode/ # OpenCode settings documentation │ ├── shell/ # Shell configuration │ ├── git/ # Git configuration & hooks │ └── providers/ # AI provider configuration ├── docs/ # Complete documentation system │ ├── WORKBENCH_CHARTER.md # Governance: mission, principles, requirements │ ├── security-model.md # Security architecture & threat model │ ├── IMPROVEMENT_BACKLOG.md # Tracked improvements and fixes │ ├── CHANGELOG_WORKBENCH.md # Append-only change history │ ├── architecture/ # System documentation (incl. clone-mcp.md) │ ├── recovery/ # Recovery procedures (4 docs) │ ├── prompts/ # Operational prompt library (9 prompts) │ └── backup-reports/ # Dated backup snapshots ├── scripts/ # Automation scripts │ ├── backup/ # Master backup script │ ├── inventory/ # Auto-generate inventories (software, env, MCP, OpenCode) │ ├── security/ # Secret pattern scanner │ ├── recovery/ # Recovery validation │ └── maintenance/ # Config sync, routine tasks ├── .github/workflows/ # CI (docs, inventory, gitleaks, mcp-server) ├── opencode.json # OpenCode configuration (MCP servers) ├── AGENTS.md # OpenCode agent instructions └── README.md # This file

What's Inside

Workstation Governance

This workstation operates under a formal charter. Key principles:

• Single Source of Truth: Runtime must match repository. Drift is a bug.
• Secrets Never Touch Disk: All secrets flow through the build box Secrets.
• Immutable History: Changelog is append-only. Every change is traceable.
• Documentation Lives With Code: Docs describe the system as it is, not as imagined.

Read the full charter: docs/WORKBENCH_CHARTER.md

Backup Workflow

# Master backup — full inventory, security scan, commit prep

bash scripts/backup/run-master-backup.sh

Quick backup — save state before risky operations

bash scripts/maintenance/sync-runtime-config.sh && \ git diff > /tmp/quick-backup-$(date +%Y%m%d).diff

Or use OpenCode prompts:

• docs/prompts/RUN_MASTER_BACKUP.md — execute backup via AI
• docs/prompts/QUICK_BACKUP.md — rapid state preservation

Recovery Workflow

Assume the build box is deleted. Only Git repo + build box Secrets survive.

# 1. Create new build box

gh SWAS create --repo simonmak-ascent/opencode-workbench --machine basicLinux32gb

2. Wait for automation (3-5 min)

3. If needed (usually done by setup.sh):

npx playwright install chromium

Vercel MCP uses VERCEL_ACCESS_TOKEN (token auth — no OAuth step)

4. Validate recovery

bash scripts/recovery/validate-recovery.sh

Full details: docs/recovery/RECOVERY_PLAYBOOK.md

MCP Architecture

Totals: 31 configured (29 enabled, 2 disabled: google-search, google-workspace).

See: docs/architecture/mcp-inventory.md

Secrets Management

All secrets stored in the build box Secrets. Never in repository files.

Additional keys for opt-in servers (EXA_API_KEY, CLOUDFLARE_API_TOKEN, STRIPE_SECRET_KEY, SURREAL_*, ALIBABA_CLOUD_*, AZURE_*, FIRECRAWL_API_KEY, FRED_API_KEY, COMPANIES_HOUSE_API_KEY) are catalogued in docs/architecture/secrets.md — never by value.

See: docs/architecture/secrets.md

Documentation Index

| `docs/WORKB