feat(plugin): /rune:configure rewrite for v0.4 Go binary#115
Merged
couragehong merged 1 commit intoMay 7, 2026
Conversation
The v0.3 configure flow assumed a Python plugin: detect plugin root, run scripts/install.sh to create a venv + pip install, run scripts/configure-claude-mcp.sh to register the MCP server, validate by importing the mcp Python package, etc. None of that applies in v0.4 — the Go binary auto-spawns from the plugin manifest's mcpServers entry, so /rune:configure only needs to: collect Vault credentials, write ~/.rune/config.json, and trigger reload_pipelines. Notable changes: - Drop venv install + install.sh / configure-claude-mcp.sh dispatch. - Drop the Python-import infrastructure check. - Mark TLS option 1 (Self-signed certificate) as Recommended; the install-dev.sh default leaves Vault TLS-on, so option 3 (No TLS) only works when the user has explicitly turned TLS off on the Vault side. - Add a sudo-cp fallback hint for /opt/runevault/certs/ca.pem (root:0640 by default, unreadable to the user before group membership applies). - Add a known-issue note pointing at the ReloadPipelines re-spawn bug (separate fix); first-time configure on a freshly-spawned MCP server needs a Claude Code restart until that fix lands. - Set state to "active" directly (was "dormant" + a separate /rune:activate step in v0.3 to gate model download — Go boot loop doesn't download anything, so the activate dance isn't needed). status.md / activate.md / etc are still on v0.3 logic and will follow in later commits. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The v0.3 configure flow assumed a Python plugin: detect plugin root, run scripts/install.sh to create a venv + pip install, run scripts/configure-claude-mcp.sh to register the MCP server, validate by importing the mcp Python package, etc. None of that applies in v0.4 — the Go binary auto-spawns from the plugin manifest's mcpServers entry, so /rune:configure only needs to: collect Vault credentials, write ~/.rune/config.json, and trigger reload_pipelines.
Notable changes:
status.md / activate.md / etc are still on v0.3 logic and will follow in later commits.