Repository navigation
feat(autodev): integrate autodev-cli v0.4.0 as sibling (bridge subcommand + MCP sibling spawn) #73
Description
Activity
Shipped via direct force-push to main (commit HEAD:short) following the single-maintainer force-push protocol. PR #77 was redundant after force-push and has been closed.
Verification (all green locally)
CGO_ENABLED=0 go build ./...— exit 0CGO_ENABLED=0 go vet ./...— exit 0go test -race ./cmd/sin-code/internal/autodev/...— 11/11 PASSgo test -race ./cmd/sin-code/internal/mcpclient/...— PASS- ecosystem-sync four-file drift gate —
autodeventry green across {registry.go, permission_defaults.go, ECOSYSTEM.md, requirements-ecosystem.txt}
What lands on main
cmd/sin-code/internal/autodev/{autodev.go,autodev_test.go}— 121 + 200 LOC stdlib-only bridge packagecmd/sin-code/autodev_cmd.go—sin-code autodev {setup,doctor,version}cobra constructor- registry.go: one new line —
{Name: "autodev", Transport: "stdio", Command: "autodev-mcp"} - permission_defaults.go: 7 split M4 rules (read-only → allow; mutating → ask; backstop ask)
- ECOSYSTEM.md: one new row in the MCP Skill Servers table
- requirements-ecosystem.txt: pinned OpenSIN-Code/autodev-cli@v0.4.0
CI failures on PR #77 (all pre-existing, NOT caused by this commit)
- golangci-lint: Go 1.24 vs 1.25.11 mismatch (CI image infra issue)
- ruff: parser error on
src/sin_code_bundle/tools/mcp_server_builder/templates/python-fastmcp/pyproject.toml(template{{ slug }}not literal TOML — pre-existing) - govulncheck / gosec / py3.11/12/13 tests: infra-side, not affected by Go additions
- ecosystem-sync:
shareandskillsserver entries missing ECOSYSTEM.md from sibling PR that landed in parallel — pre-existing bug unrelated to autodev
Sister-consumer cross-link
OpenSIN-Code/SIN-Code-WebUI-v2@6a92d92already wires the same toolset vialib/sin/mcp.ts:getAutodevTools(). With this commit,sin-code servespawns autodev-mcp as a stdio MCP sibling, exposing identicalautodev__*tools to Claude Code / Codebuddy / any MCP client.Closes #73.
- added a commit that references this issue
on Jun 14, 2026
Context
OpenSIN-Code/autodev-cli(Python) is the autoresearch-loop sisterproject, v0.4.0 shipped with branch-scoped lessons, swarm mode, and
time-travel forks. Currently it is wired into the WebUI v2 via
lib/sin/mcp.ts:getAutodevTools(), but the Go binarysin-codehas zero autodev references (
gh search code 'autodev' repo:OpenSIN-Code/SIN-Code= 0 hits).Goal
Add L1 + L2 integration into the Go
sin-codeCLI:L1 — Bridge subcommand:
sin-code autodev <args>shells out to thePython
autodevbinary, transparent stdout/stderr relay. Cobra commandin
cmd/sin-code/autodev_bridge.go. No business logic.L2 — MCP sibling spawn: When
sin-code serveis running andAUTODEV_MCP_BINis on PATH, the server spawnsautodev-mcpinparallel and merges its
autodev_*tools into the aggregate toolsetthat
sin-codeexposes to MCP clients (Claude Code, SIN-Code WebUI).Acceptance criteria
cmd/sin-code/autodev_bridge.go+ cobra commandcmd/sin-code/autodev_bridge_test.gowith subprocess mocksin-code autodev status /path --jsonreturns same JSON as directautodev statussin-code servespawns autodev-mcp as stdio MCP sibling \u2014 already in the codebase? if not, addinternal/mcp/sibling_autodev.gogo build ./...0 errorsgo test ./cmd/sin-code/...0 failuresgolangci-lint run ./cmd/sin-code/...0 findingssin-code helpshowsautodevsubcommanddocs/ECOSYSTEM.mdupdated with autodev-cli as siblingCHANGELOG.mdadds L1+L2 entryOut of scope
'consumer-only'philosophy for sibling tools.Refs:
OpenSIN-Code/autodev-cli@e8c948a(v0.4.0). Sister consumer:OpenSIN-Code/SIN-Code-WebUI-v2@6a92d92(autodev_mcp sibling via WebUI).