Skip to content

fix(optimize): separate connector and local MCP guidance - #991

Draft
avs-io wants to merge 5 commits into
getagentseal:mainfrom
avs-io:codex/issue-975-connector-guidance
Draft

fix(optimize): separate connector and local MCP guidance#991
avs-io wants to merge 5 commits into
getagentseal:mainfrom
avs-io:codex/issue-975-connector-guidance

Conversation

@avs-io

@avs-io avs-io commented Aug 13, 2026

Copy link
Copy Markdown
Member

Problem

CodeBurn treated claude_ai_* transcript namespaces like editable local MCP servers. That produced claude mcp remove guidance for claude.ai connectors, which are managed through /mcp or claude.ai Settings and may share a readable name with a separate local server.

Root cause

The low-coverage detector correctly observed loaded connector schemas, but its remediation path did not distinguish server-side connector evidence from local MCP configuration ownership. Savings and action reporting also needed to separate total opportunity from the exact local subset CodeBurn could safely mutate.

Change

  • Keep claude.ai connector namespaces as optimization evidence while rendering them as manual /mcp or Settings follow-up.
  • Build executable plans only for exact local server names found in readable MCP configuration.
  • Preserve connector guidance in mixed findings while applying and journaling only the local mutation.
  • Scope preview, applied, and realized-savings estimates to the exact local targets; suppress claims when attribution is incomplete.
  • Keep internal action-accounting fields out of the public optimize JSON envelope.
  • Mark connector follow-up explicitly as not applied before mutation and still pending afterward.

User impact

Connector-only findings no longer offer a command that cannot work. Mixed and same-name findings cannot remove or imply removal of the connector, and users can see which local server CodeBurn will change and which connector action remains manual.

Preservation and out of scope

  • Connector schema cost remains part of total optimization opportunity.
  • CodeBurn does not attempt to edit claude.ai connector state.
  • This change does not infer per-project connector ownership from aggregate transcript inventory.
  • Existing public optimize JSON structure is preserved.

Testing

  • Focused root tests: 269 passed.
  • Desktop Optimize tests: 9 passed.
  • Full root suite: 2,642 passed, 5 skipped.
  • Serial lock suite: 26 passed.
  • Full desktop suite: 469 passed.
  • Root and desktop TypeScript checks passed.
  • CLI, dashboard, and desktop builds passed.
  • Isolated real-parser QA covered connector-only, local-only, mixed, and same-name collision scenarios.
  • Preview left configuration byte-identical; apply changed only exact local targets; journal/report excluded connectors; undo restored byte-identical configuration.
  • Real TUI and Electron desktop click-through verified connector guidance and local-only removal presentation.

Fixes #975.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

optimize: MCP finding suggests claude mcp remove for claude.ai connectors, which cannot remove them (and collides with same-named local servers)

1 participant