Problem
The Claude Code plugin init flow currently assumes that PowerMem should be installed and managed as a local powermem-server process. That works for a single local setup, but it blocks users who already run PowerMem elsewhere, for example on another host, in a container, or as a shared team service.
Those users should be able to point the plugin at an existing PowerMem server instead of starting a local managed server.
Desired behavior
Add a supported remote-server initialization path for the Claude Code plugin:
- Allow users to provide a custom PowerMem base URL, for example
https://powermem.example.com or http://host:8848.
- Skip local
.env generation, local uvx server launch, and managed PID handling when a remote URL is selected.
- Configure hooks by writing
runtime.env with POWERMEM_BASE_URL=<remote-url>.
- Optionally configure MCP by writing the plugin
.mcp.json with <remote-url>/mcp.
- Support an optional API key without printing it in logs or summaries.
- Keep local mode backward compatible: local init should still default to a loopback local server unless the user explicitly opts into another bind address.
- Make the status command report whether the plugin is configured for local, remote hook, remote MCP, both, or none.
Acceptance criteria
scripts/init.sh supports a remote URL configuration path and does not start a local server in that mode.scripts/status.sh can report remote hook/MCP configuration without requiring a local managed PID.- Hook launchers keep reading
runtime.env and use the configured remote base URL.
- Tests cover local default behavior, remote hook mode, remote MCP mode, remote both mode, and invalid connection mode handling.
- Documentation or skill instructions explain the remote-server setup path.
Related context
A broader draft PR (#1101) explores remote init together with a larger interactive init flow. This issue tracks the focused capability: configuring the Claude Code plugin to use a custom remote PowerMem server address.
Problem
The Claude Code plugin init flow currently assumes that PowerMem should be installed and managed as a local
powermem-serverprocess. That works for a single local setup, but it blocks users who already run PowerMem elsewhere, for example on another host, in a container, or as a shared team service.Those users should be able to point the plugin at an existing PowerMem server instead of starting a local managed server.
Desired behavior
Add a supported remote-server initialization path for the Claude Code plugin:
https://powermem.example.comorhttp://host:8848..envgeneration, localuvxserver launch, and managed PID handling when a remote URL is selected.runtime.envwithPOWERMEM_BASE_URL=<remote-url>..mcp.jsonwith<remote-url>/mcp.Acceptance criteria
scripts/init.shsupports a remote URL configuration path and does not start a local server in that mode.scripts/status.shcan report remote hook/MCP configuration without requiring a local managed PID.runtime.envand use the configured remote base URL.Related context
A broader draft PR (#1101) explores remote init together with a larger interactive init flow. This issue tracks the focused capability: configuring the Claude Code plugin to use a custom remote PowerMem server address.