Fix native MCP projection duplicating existing Codex server tables #133

New issue

Closed

opened 2026-07-30 07:49:52 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-30 07:49:52 +00:00

Member

Problem

When Codex already has an MCP server table whose name is present in the canonical mcporter inventory, the first agent-compose projection appends a managed table with the same name. The resulting config contains duplicate TOML tables instead of updating the existing server definition.

Acceptance

Projection absorbs pre-existing Codex MCP tables for inventory-managed server names.
Canonical endpoint, command, arguments, environment, and approval policy replace stale values.
Unrelated Codex settings and unmanaged MCP server tables remain unchanged.
Repeated projection is idempotent.
Focused regression coverage includes quoted and bare server-table names.

## Problem When Codex already has an MCP server table whose name is present in the canonical mcporter inventory, the first agent-compose projection appends a managed table with the same name. The resulting config contains duplicate TOML tables instead of updating the existing server definition. ## Acceptance * Projection absorbs pre-existing Codex MCP tables for inventory-managed server names. * Canonical endpoint, command, arguments, environment, and approval policy replace stale values. * Unrelated Codex settings and unmanaged MCP server tables remain unchanged. * Repeated projection is idempotent. * Focused regression coverage includes quoted and bare server-table names.

coilyco-ops referenced this issue from a commit

2026-07-30 07:52:31 +00:00

fix: update existing Codex MCP tables

coilyco-ops closed this issue

2026-07-30 07:52:31 +00:00

coilyco-ops referenced this issue

2026-07-30 08:13:07 +00:00

interactive: inspect release validation failure for e5766cb #134