Browse / General-purpose / Opencode-Workspace

Opencode-Workspace

3xOGssavage

Enterprise opencode workspace — 17 agents, 16 MCPs, 117 skills, parallel subagent dispatch

Open 3xOGssavage/Opencode-Workspace → Manually confirmed as a workspace.

Works with any agent

ships AGENTS.md, the cross-tool instruction file.

In its own words

README.md3xOGssavage/Opencode-Workspace

Enterprise opencode workspace backup — 17 agents, 16 MCPs, 117 skills, parallel subagent dispatch. Snapshot dated 2026-08-02. See AGENTS.md for the operating manual.

Onboarding / Quickstart

New team member? See **ONBOARDING.md** for the 9-step happy path (clone → check-prerequisites.ps1 → setup-env-vars.ps1 → install-user-skills.ps1 → clone-vendored-skill-packs.ps1 → set-secrets.ps1 → auth-mcp-servers.ps1 → restore auth.json → verify-setup.ps1). Total time on a fresh machine: ~30 min.

For disaster recovery / backup scenarios, keep reading below.

What's in this repo

Tracked size after cleanup: ~1 MB.

Restore Guide

Scenario A: Same-machine restore

If the workspace was lost but this machine is still in use (same drive letters, same env vars):

  • Extract F:\CD\Backup\opencode-workspace-2026-08-02.zip to F:\CD\Opencode\ (overwrite).
  • Or git clone F:\CD\Opencode
  • The absolute paths in opencode.json already point to F:\CD\Opencode\ — no path normalization needed.
  • Run scripts\setup-env-vars.ps1 to re-set the 4 User env vars (idempotent — safe to re-run).
  • Run npm install in %USERPROFILE%\.config\opencode\ if node_modules\ is missing.
  • Reinstall workspace skills:
  • Restart opencode. Done.
Scenario B: New-machine setup

If migrating to a new machine (different drive letters, no env vars, no auth):

Quoting 9% of the README. Read the rest on GitHub ↗

Read from the repository's git tree on 2026-08-17.