feat: agent auto-setup with interactive picker - #5
Merged
Conversation
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
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.
Summary
Makes
memd setupagent-aware. Instead of hardcoding Claude Code registration, it now detects the LLM agents installed on the machine and presents an interactive checklist of which to connect to memd's MCP server.memd setup): adialoguermulti-select of 7 agents — Claude Code, Codex, Gemini CLI, Cursor, Windsurf, Cline, Zed — pre-checked from current state. Sync semantics: the checklist is the source of truth, so un-checking a configured agent removes memd from it. On a non-TTY (CI/piped), it auto-configures every detected agent and removes nothing.src/agents/module: a mostly-data registry. Each agent declares its detection rule, MCP registration mechanism (Claude CLI / JSON-merge / TOML-merge), an optional instruction-file for directives, and a hooks flag. All seven were verified HTTP-capable, so every agent registers the always-on daemon's HTTP endpoint (http://127.0.0.1:7702/mcp).memd statusAgents section: reports each agent asconfigured (HTTP),detected — not configured, ornot detected.Design spec and implementation plan are in
docs/superpowers/.Test Plan
cargo test— 54 passing (JSON/TOML merge insert/remove/idempotent/preserve/no-clobber,plan_actionsync matrix, registry, directive roundtrip)cargo clippy --all-targets -- -D warnings— cleancargo fmt --check— cleancargo build --release— succeedsmemd statusshows the Agents section with live per-agent stateMultiSelectpicker on a TTY (not run in CI; verify checkbox toggles configure/remove as expected)🤖 Generated with Claude Code