跳到主要内容
    ↑↓ 选择↵ 打开esc 关闭
    中文English
    canxin121

    Workbench

    v0.3.2Git 与版本控制
    opencode-workbench

    Branch sandboxes for parallel OpenCode development

    GitHub 星标

    1

    月装机量

    58

    近 7 天 10

    综合评分SCORE

    24.0

    生态多维模型

    最近提交

    5 个月前

    2026-02-27

    快速安装与配置

    opencode.json

    写入当前项目的 opencode.json,只对这个仓库生效。

    opencode.json

    {
      "$schema": "https://opencode.ai/config.json",
      "plugin": ["opencode-workbench@0.3.2"]
    }

    opencode 启动时会通过内嵌运行时自动加载 npm 依赖并缓存至本地目录,无需手动在全局环境执行安装。

    Chinese version: README.zh-CN.md

    opencode-workbench is built for concurrent delivery: it maps git worktrees to OpenCode sessions so multiple tasks can run in parallel with clear routing, ownership, and integration flow.

    Why Teams Use Workbench

    • Run many tasks concurrently across isolated branches/worktrees without collisions.
    • Fan out parallel task execution from one supervisor workflow with deterministic routing.
    • Keep per-session execution safe while maintaining high overall concurrency.
    • Track branch/fork/PR metadata per binding to coordinate fast parallel delivery.
    • Enforce supervisor/worker boundaries for reliable, scalable multi-task execution.

    Installation

    Add the plugin to your OpenCode config file opencode.json:

    • Unix/macOS: ~/.config/opencode/opencode.json
    • Windows: %USERPROFILE%\\.config\\opencode\\opencode.json (for example: C:\\Users\\<your-user>\\.config\\opencode\\opencode.json)
    {
      "plugin": ["opencode-workbench"]
    }
    

    Optional version pin:

    {
      "plugin": ["opencode-workbench@0.3.2"]
    }
    

    Quick Start with Natural Language

    Example prompts:

    1. Use workbench for parallel work. Task list: 1. ** 2. **
    2. Use workbench for high-concurrency parallel work, use gh, and take the workflow all the way through PR creation and merge without follow-up confirmation. Task list: 1. ** 2. **
    

    OpenCode Studio Experience

    Workbench includes OpenCode Studio integration so concurrent branch/task orchestration is visible at a glance:

    • Learn more: opencode-studio

    • Session binding overview in Studio (worktree, branch, session linkage).

    • Metadata visibility (fork/upstream/PR) for faster coordination.

    • Better supervisor control when dispatching and reviewing multiple child sessions.

    For teams running multi-branch development daily, OpenCode Studio is the recommended control center to monitor workers, keep routing clean, and reduce context switching.

    Details

    Detailed action contracts, parameter-level behavior, scope/session targeting rules, and governance guidance are documented in DETAIL.md.

    License

    MIT