Skip to content

task: Editor / agent / MCP-client integration (6 issues) #395

@DeusData

Description

@DeusData

Scope

Umbrella tracker for editor / agent / MCP-client integration bugs that aren't covered by an existing per-agent install. Includes install-target compatibility (AlmaLinux), process lifecycle, MCP handshake edge cases, and requests for new agent targets.

Sub-issues

Status (2026-05-31)

4 of 6 resolved (#182, #222, #253 fixed; #366 already shipped). Remaining: #185 (awaiting reporter retest on v0.7.0) and #330 (accepted enhancement, tracked separately). The bug surface of this group is closed; the two open items are a reporter-dependent retest and a feature request.

Acceptance

  1. AlmaLinux / RHEL-family install path verified — static binaries remove the glibc dependency. ✅
  2. Process lifecycle: server exits cleanly when parent terminates — open (codebase-memory-mcp.exe running after quitting VS Code. #185, pending retest).
  3. JSON-RPC id accepts string and integer values per the spec. ✅
  4. New agent targets (Codex hook, antigravity) decided in/out of scope — antigravity in (done); Codex hook accepted as tracked enhancement (feat: add Codex SessionStart reminder hook for codebase-memory tool discovery #330).

Why one task

These are all "the integration surface broke for X agent / X distro". The fixes touch cli.c install paths + the MCP server handshake — same surface area.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingeditor/integrationEditor compatibility and CLI integrationtaskUmbrella task grouping multiple related issues

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions