- Move programs.mcp.servers out of agents.nix into mcp.nix so hosts that
do not load the whole coding set (T3 Code servers) can import it alone
- Add claude-code.nix: programs.claude-code with enableMcpIntegration,
replacing the bare llm-agents.claude-code package (would collide on
bin/claude). home-manager delivers the catalogue as a generated plugin,
~/.claude/settings.json and ~/.claude.json stay writable
- ai-memory: register the session-aware Claude bridge via
programs.claude-code.mcpServers instead of `ai-memory install-mcp`;
activation only removes the stale user-scope entry now
- Adjust ai-memory.test.sh accordingly
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
A plain HTTP entry carries no bearer; Claude Code then attempts OAuth
dynamic client registration against ai-memory and fails. The stdio
bridge reads [auth].bearer_token_file from the client config.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
coding.aiMemory wires Claude Code and OpenCode2 to the central ai-memory
server: Nix owns the client config (server URL + bearer token file), the
OpenCode MCP entry, and the scope markers (home workspace plus one marker
per workspaceDirs entry); activation runs ai-memory's own installers for
hooks, the Claude MCP bridge and the skills. The token never lands in a
generated file: hooks and the bridge read [auth].bearer_token_file, the
OpenCode plugin reads the data-dir auth-token symlink.
Pi (and its babysitter profile) are no longer used; LifeOS is being
removed from the hosts as well.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>