Shiploop：把多仓库开发编排成单终端工作流的 Claude Code 插件
原文标题：claude became my team and cut my burn rate by 3x
一位 GPU 云平台创始人把团队从 5 人缩到 2 人后，围绕 Claude 自建了一套多仓库开发编排工具 Shiploop，并已开源。它用一个 advisor 会话负责思考和规划，worker 各自在独立 git worktree 中写代码以避免并行冲突，同时跨会话管理上下文、保留失败经验，并把每个任务先写入队列文件防止会话中断丢工作。
当前语言的正文正在等待翻译，暂时显示原文。
hi, i’m the founder of a gpu cloud platform.
we used to be a team of 5. in may, we transitioned to working duo.
we started relying heavily on claude to keep shipping across the stack.
our codebase spans 4 core repos:
- distributed daemon agent
- cloud aggregation layer
- orchestrator
- platform console
across typescript, go, shell, postgresql, python, javascript, css, dockerfiles, and makefiles.
when i need to fix something, ship a feature, or even ideate, i need context across all 4 repos, sometimes plus the admin panel and website.
for every change, claude can spin up the complete stack locally, make the changes, test them, and validate the results with screenshots through a headless browser while making sure it doesn't break anything that already works while staying within secure boundaries.
that's where things started becoming painful.
- long sessions fill up with code, logs, and retries. compaction quietly drops decisions made earlier.
- two sessions working on the same repo step on each other, so most tasks end up running sequentially.local runs can fail because of the stack, dependencies, or third-party APIs. a fresh session often retries the same task without knowing what already failed.
so i started building a harness around how i actually worked.
over the following months, i kept tuning it to help me keep shipping continuously.
shiploop is that harness, extracted into a tool i can use across projects.
i've spent the past 4 months tuning it around how i actually work.
once installed, shiploop learns how your project runs and adapts over time.
it decides:
- which model should handle each task
- what context that task needs
- how much work can safely run in parallel
the core idea:
- multiple repos can be driven as one workspace from a single terminal.
- one advisor session thinks and plans. workers do the coding, each in its own git worktree, so parallel work doesn't collide.
- manages context across sessions, preserving learnings from failures
- identifies what can be handled deterministically
- every task is written to a queue file first, so work isn't lost if a session dies.
- shares codebase knowledge across workers, keeps workers lean, and filters out noise from successful runs.
install:
/plugin marketplace add anshss/shiploop
/plugin install shiploop@shiploop
then run `/shiploop:setup` once in a project.
this is something i've been using myself for the past few months.
blunt feedback is welcome.
来源：Reddit · ClaudeCode / Codex / VibeCoding · reddit.com