docs: clarify #1266's HTTP registration route has no client integration yet (risk of overselling as VS Code support)
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 92/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- vscode
- Domain
- documentation
Research direction
Start in CHANGELOG.md at the release-note entry for #1266. Add the explicit caveat from the issue that the HTTP registration route is backend-only and no current Altimate client, including the VS Code extension, calls it yet. Done means the changelog wording avoids implying VS Code support or client integration.
Written by the indexing model from the issue text.
Description
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
#1266changelog/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.
- Dominant language
- TypeScript
- Stars
- 813
- Forks
- 134
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 65
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from AltimateAI/altimate-code
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
AltimateAI/altimate-code#1359 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
AltimateAI/altimate-code#1323 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
AltimateAI/altimate-code#1288 ·
-
privacy: Altimate Base consent dialog no longer discloses persistent per-installation identifier Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
AltimateAI/altimate-code#1284 ·
-
Difficulty 2/5 Under an hour Newbie friendliness 72/100
AltimateAI/altimate-code#1283 ·
All issues in AltimateAI/altimate-code
Similar issues
-
bug(cli): hapi doctor inline-media prints a fabricated B:\ helper-script path in packaged installs Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Crush Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
catppuccin/catppuccin#3125 ·
-
Add a SECURITY.md Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
ElementsProject/cln-application#167 · 1 comment · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Quantco/pnpm-licenses#17 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100