Summary
#1266 ("expose Altimate Base registration over HTTP for non-TUI hosts") is backend plumbing only — as of v0.11.0, no Altimate client actually calls the new routes. A grep of sdks/vscode turns up zero references to Altimate Base, the disclosure route, or the register route.
The CHANGELOG.md entry itself is careful ("a host that talks HTTP to altimate serve (e.g. the VS Code extension)... Two new routes...") but that phrasing is one careless rewrite away from becoming "Altimate Base now works in the VS Code extension" in a release announcement or blog post — which would not be true today.
This connects to a real, separate gap already under investigation: the VS Code extension's model picker (ModelPicker.tsx in vscode-altimate-mcp-server) only shows providers where connected === true, and nothing in that extension currently drives the consent/registration flow — so even with #1266's HTTP route available, there is no UI path yet for an extension user to reach it.
Proposed fix
- Add an explicit caveat to the
#1266 changelog/release-note entry: "This is a backend capability only — no current Altimate client (including the VS Code extension) calls it yet."
- Track the actual extension-side integration (consent UI + model-picker wiring) as separate follow-up work — this issue is scoped to the messaging/oversell risk only, not the integration itself.
Provenance
Found during the v0.11.0 stable release's Product Manager persona review.
Summary
#1266("expose Altimate Base registration over HTTP for non-TUI hosts") is backend plumbing only — as of v0.11.0, no Altimate client actually calls the new routes. A grep ofsdks/vscodeturns up zero references to Altimate Base, the disclosure route, or the register route.The CHANGELOG.md entry itself is careful ("a host that talks HTTP to
altimate serve(e.g. the VS Code extension)... Two new routes...") but that phrasing is one careless rewrite away from becoming "Altimate Base now works in the VS Code extension" in a release announcement or blog post — which would not be true today.This connects to a real, separate gap already under investigation: the VS Code extension's model picker (
ModelPicker.tsxinvscode-altimate-mcp-server) only shows providers whereconnected === true, and nothing in that extension currently drives the consent/registration flow — so even with #1266's HTTP route available, there is no UI path yet for an extension user to reach it.Proposed fix
#1266changelog/release-note entry: "This is a backend capability only — no current Altimate client (including the VS Code extension) calls it yet."Provenance
Found during the v0.11.0 stable release's Product Manager persona review.