mcp: headersCommand missing from V2 ConfigMCP.Remote schema (merge drift risk)

Open Beginner friendly
#996 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
backend, tooling

Research direction

Compare packages/core/src/v1/config/mcp.ts ConfigMCPV1.Remote with packages/core/src/config/mcp.ts ConfigMCP.Remote, focusing on the headersCommand field. Start by finding how the V2 schema is defined and whether nearby tests cover MCP config parsing. Done means V2 either preserves headersCommand consistently or the maintainers explicitly decide that V2 ConfigMCP should be removed.

Written by the indexing model from the issue text.

Description

Found during v0.9.1 release review (Tech-Lead). packages/core/src/v1/config/mcp.ts ConfigMCPV1.Remote has headersCommand (bearer-auth, #793). The newer Effect-Schema ConfigMCP.Remote in packages/core/src/config/mcp.ts does NOT. Not a live bug today (MCP load goes through V1), but V2 Config.Service is already wired into other subsystems. If MCP config loading migrates to V2, headersCommand will silently vanish via onExcessProperty: "ignore" — dropped auth headers, no error. Add headersCommand to V2, or decide V2 ConfigMCP is dead and remove it.

Dominant language
TypeScript
Stars
813
Forks
134
Avg merge
2d 5h
Merged PRs (30d)
62

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AltimateAI/altimate-code

All issues in AltimateAI/altimate-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.