indifferentketchup/boocode
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: remove Go codecontext sidecar, wire all boocontext MCP tools

Browse Source 
Deletes all 17 native codecontext tool wrappers (~2,400 lines). Code analysis now provided entirely by boocontext MCP server (discovered at startup via appendMcpTools()). Adds 9 previously missing MCP tools (get_summary, scan, get_coverage, get_schema, get_env, get_events, get_knowledge, get_wiki_index, lint_wiki) to all relevant agent tool lists. Updates AGENTS.md, guidance files.
This commit is contained in:
indifferentketchup
2026-06-08 04:18:04 +00:00
parent 6fde7002aa
commit 7096ae4ddc
33 changed files with 50 additions and 2412 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
CLAUDE.md
View File

@@ -113,10 +113,10 @@ BooCoder at port 9502: `curl http://100.114.205.53:9502/api/health`. Runs as `bo
- A local PreToolUse hook (`security_reminder_hook.py`) regex-flags Node's older `child_process` spawn helpers as unsafe (false positive even on the File-suffixed variant). Use `spawn` — it's accepted.
- `/opt/boolab` hosts a sibling BooCode at `boocode.indifferentketchup.com` — useful for side-by-side iPhone comparison when debugging booterm rendering. It uses Tailwind v3, boocode uses v4 — don't assume build parity.
- booterm SSHs to the host as `samkintop@100.114.205.53` (the Tailscale IP). The hostname `ubuntu-homelab` (in the bash prompt) does NOT resolve inside the container. Override via `BOOTERM_SSH_HOST` / `BOOTERM_SSH_USER` env vars in docker-compose if the shell moves to a different machine.
- codecontext sidecar lives at `/opt/boocode/codecontext/`. HTTP API at `http://codecontext:8080/v1/<tool_name>` over the `boocode_net` bridge (no host port). BooCode wrappers in `apps/server/src/services/tools/codecontext/`. The `.codecontextignore` at project root is honored when `--respect-gitignore` is passed (enabled in the shim).
- codecontext fork at `/opt/forks/codecontext/` — separate git repo (branch `boocode-ts`), pushed via the boocode_gitea SSH key to `indifferentketchup/codecontext`. Build `go build ./...`; test `go test ./...`. Docker rebuild requires staging the fork first: `tar -czf codecontext/fork.tar.gz -C /opt/forks/codecontext --exclude=.git --exclude=bin .` then `docker compose build --no-cache codecontext` (the Dockerfile COPYs `fork.tar.gz` into the builder stage; Gitea is behind Authelia, no HTTP clone). `fork.tar.gz` is gitignored.
- Go binary: `/snap/go/current/bin/go` (not on PATH). Use `export PATH=$PATH:/snap/go/current/bin` or the full path.
- `os/exec` child supervisors must call `child.Wait()` in a goroutine and `os.Exit` on child death. `Signal(0)` returns nil on zombies and is NOT a liveness check. Without `Wait()`, docker's `restart: unless-stopped` never fires because the parent stays alive. `codecontext/shim.go` is the reference.
- Boocontext MCP server integrates tree-sitter code analysis tools (callgraph, health, impact, symbols, types, wiki). Wrappers in `apps/server/src/services/tools/codecontext/` (directory name retained for import compat). Invoke boocontext tools through the tool registry — MCP tools are appended at startup via `appendMcpTools`.
- The old Go codecontext sidecar has been removed from the Docker deployment (v2.8.20). The TypeScript boocontext fork at `/opt/forks/codecontext/` (branch `boocode-ts`) still exists for reference but is no longer deployed. Build: `go build ./...` from within that directory if needed for local testing.
- Go binary (only if working with the fork): `/snap/go/current/bin/go` (not on PATH). Use `export PATH=$PATH:/snap/go/current/bin` or the full path.
- `os/exec` child supervisors must call `child.Wait()` in a goroutine and `os.Exit` on child death. `Signal(0)` returns nil on zombies and is NOT a liveness check. Without `Wait()`, docker's `restart: unless-stopped` never fires because the parent stays alive.
## Conventions