Skip to content

Installer/updater scope and safety: no per-client selector, destructive update step before an interactive prompt, hidden ui_enabled, brittle legacy-marker cleanup #1558

Description

@PsyTech-Rob

Environment: v0.10.2, Windows 11. Four related findings from one install/update cycle.

1. install has no per-client selector

install writes MCP config, agents, skills, instructions and hooks for every detected client (Claude Code, Codex, OpenCode, Cursor). We only wanted Claude + Codex; the OpenCode/Cursor integrations had to be reverted by hand — and the next install/update silently recreates them. A --clients=claude,codex style selector (or per-client confirmation in interactive mode) would fix this.

2. update -y ran a destructive step before a blocking interactive prompt

On 0.9.0 → 0.10.2, update -y auto-confirmed deletion of other projects' index files (two .db indexes, ~59 MB, lost) and then aborted on the interactive standard/ui variant chooser ("failed to read input" under a non-interactive shell). Destructive cleanup should be sequenced after the last prompt that can abort the run. #1538 removes the chooser, which fixes this particular abort but not the ordering principle; #1544 is adjacent.

3. ui_enabled is invisible to config list / config set

The only way to disable the UI HTTP listener (default 127.0.0.1:9749) is editing config.json ("ui_enabled": false) by hand — the key is not shown by config list, not settable by config set, and the server binary accepts --ui=false without effect. It took two debugging sessions to find the knob; meanwhile the daemon exposes a loopback HTTP surface that looked impossible to turn off.

4. Legacy hook cleanup aborts on an orphan marker

An earlier duplicated install left a Codex config.toml with a # <<< codebase-memory-mcp SessionStart <<< closing marker without its # >>> opener. install then fails that client with error: agent_config ... op=legacy_hook_cleanup and stops the activation ("one or more agent configurations failed"). Since the malformed state was produced by a previous installer run, cleanup could tolerate/strip orphan markers instead of aborting (self-heal).

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingeditor/integrationEditor compatibility and CLI integrationenhancementNew feature or requestpriority/highNeeds near-term maintainer attention; high-impact bug, regression, safety issue, or release blocker.ux/behaviorDisplay bugs, docs, adoption UXwindowsWindows-specific issues

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions