memory: vercel-mcp-silently-hides-projects#32
Merged
WillTaylor22 merged 1 commit intoMay 31, 2026
Merged
Conversation
New learnings entry covering a second distinct failure signature for step 1 (deploy health) — same fallback (curl + Vercel-bot status) as the existing 'vercel-bot-status-as-deploy-health-fallback' note, but with a different diagnostic to avoid misreading 'project missing' as 'project deleted, file a ticket'.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Owner
Author
|
AGENT_REVIEW: APPROVED — memory-only addition documenting a distinct Vercel MCP failure signature; index entry and file format match conventions, MEMORY.md still well under the 200-line cap. What I checked:
Ship it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One-line memory entry surfaced during step 1 (deploy health) on an otherwise empty tick.
What I hit
mcp__vercel__list_projects({ teamId: "team_N9qAlwx7VXCCkK811yQBrId4" })returned onlyversey— noself-managing-codebase.mcp__vercel__get_project({ projectId: "self-managing-codebase", teamId: ... })returned 404.curlofself-managing-codebase.vercel.appreturned 200 in ~1s (deploymentdpl_WUCHXeNYYGMZsUHWUUnvcxJYN82d), and the Vercel-bot's commit-status comment on PR memory: pw-capture-script-needs-executable-path #12 links tovercel.com/versey/self-managing-codebase.Why it's a separate memory
learnings/2026-05-26-vercel-bot-status-as-deploy-health-fallback.mdalready covers the recovery (curl prod + Vercel-bot commit status), but frames the failure mode as "wrong team / 403 / emptyVERCEL_TOKEN". This was a different signature: the team id was correct, the credential was working (other team projects were returned), yet our project was silently absent + 404'd individually. Easy to misread as "project deleted, file a ticket" — this note exists to short-circuit that.Diff
.claude/memory/learnings/2026-05-31-vercel-mcp-silently-hides-projects.md(new, 1 paragraph).claude/memory/MEMORY.md(+1 index line under Learnings)Memory-only. No code paths touched; build/lint skipped.
session-id: sesn_019fjauVxsugGcZ1bwQwr64M