Skip to content

feat(launch): make Headroom's MCP and RTK opt-in, not the default - #21

Merged
protonspy merged 1 commit into
mainfrom
launch-opt-in-headroom-extras
Aug 8, 2026
Merged

feat(launch): make Headroom's MCP and RTK opt-in, not the default#21
protonspy merged 1 commit into
mainfrom
launch-opt-in-headroom-extras

Conversation

@protonspy

Copy link
Copy Markdown
Owner

Summary

  • scc launch's only reason to reach for Headroom is its compression proxy — registering MCP servers and wiring up RTK on every launch went beyond that.
  • --headroom-mcp now defaults to none instead of retrieve: no MCP server (not even Headroom's own retrieve tool) is registered on a bare launch. Cost: the proxy's compression markers go unactionable until you pass --headroom-mcp retrieve (or all).
  • RTK preflight flips from opt-out (--no-rtk) to opt-in (--rtk): a bare scc launch no longer touches RTK's binary or the entry file's usage block.
  • --headroom-context-tool was already opt-in and unchanged.

Test plan

  • go build ./...
  • gofmt -l . (clean)
  • go vet ./...
  • go test ./...

🤖 Generated with Claude Code

https://claude.ai/code/session_01YGMJjeWYoqTdcgedRLjDJX

scc launch's only reason to reach for Headroom is its compression proxy;
registering MCP servers and wiring up RTK on every launch went beyond
that. --headroom-mcp now defaults to none instead of retrieve, and RTK
preflight moves from an opt-out (--no-rtk) to an opt-in (--rtk) so a bare
`scc launch` starts the agent behind the proxy and nothing else.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YGMJjeWYoqTdcgedRLjDJX
@protonspy
protonspy merged commit 950f8be into main Aug 8, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant