Skip to content

Treat a 403 from another server as an unconfirmed removal - #25

Merged
akshitkrnagpal merged 1 commit into
mainfrom
cli-cross-server-revoke
Nov 19, 2026
Merged

akshitkrnagpal merged 1 commit into
mainfrom
cli-cross-server-revoke

Conversation

@akshitkrnagpal

@akshitkrnagpal akshitkrnagpal commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor
  • Turning off an agent linked to another server used that server's saved sign-in, which may be a different account, and accepted a 403 as already revoked. The local link was removed while the authorization could stay active.
  • A 403 from another server now fails the removal: setup reports "Disabled locally, but remote cleanup failed" with the authorization ID and server.
  • A 403 from the server being set up still counts as removed, as before: the account lost access to the workspace, which revokes its agents.

Checks: vp run typecheck, vp run test (171 tests, one new), vp run build.

🤖 Generated with Claude Code


Autofix with [code]smith
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.

Turning off an agent linked to another server used that server's saved
sign-in, which may be a different account, and accepted a 403 as already
revoked. The local link was removed while the authorization could stay
active. A 403 from another server now fails the removal and says where to
remove the authorization. A 403 from the server being set up still means
the account lost access, which revokes its agents.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@akshitkrnagpal
akshitkrnagpal merged commit 6eddd49 into main Nov 19, 2026
1 check passed
@akshitkrnagpal akshitkrnagpal mentioned this pull request Nov 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant