feat(serve): write pi profile-scoped MCP config #558

Open
opened 2026-09-21 20:46:32 +00:00 by hexajon · 0 comments
Owner

Phase 2 of ADR 0039 (docs/decisions/0039-pi-first-class-harness.md). Refs #546.

WirePi writes the default scope at ~/.omp/agent/mcp.json only. A pi user on a named profile reads ~/.omp/profiles//agent/mcp.json, so that user must copy the block by hand or stay on the default profile. ADR 0039 records this as a known limitation.

Acceptance criteria:

  • install --mcp-client pi can target a named profile.
  • The write keeps the merge-preserve-others, atomic, 0600 contract that the default scope already has.
  • Tests cover a named profile, a missing profile directory, and a second idempotent run.
  • docs/reference is regenerated.
Phase 2 of ADR 0039 (docs/decisions/0039-pi-first-class-harness.md). Refs #546. WirePi writes the default scope at ~/.omp/agent/mcp.json only. A pi user on a named profile reads ~/.omp/profiles/<name>/agent/mcp.json, so that user must copy the block by hand or stay on the default profile. ADR 0039 records this as a known limitation. Acceptance criteria: - install --mcp-client pi can target a named profile. - The write keeps the merge-preserve-others, atomic, 0600 contract that the default scope already has. - Tests cover a named profile, a missing profile directory, and a second idempotent run. - docs/reference is regenerated.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
sixfold-space/madtea#558
No description provided.