AltimateAI / AltimateAI/altimate-code

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

Open
#996 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
811
Forks
134
Avg merge
3d 2h
Merged PRs (30d)
50

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.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.