Skip to content

docs(console): explain why pairing approval can be unavailable - #46

Merged
mrgoonie merged 1 commit into
devfrom
claude/dazzling-archimedes-i7wmw1
Oct 16, 2026
Merged

mrgoonie merged 1 commit into
devfrom
claude/dazzling-archimedes-i7wmw1

Conversation

@mrgoonie

Copy link
Copy Markdown
Contributor

Summary

Companion docs for nextlevelbuilder/dewee#1433. The Pairing inbox page (en + vi) now explains when Approve stays off, what the tooltip means and what to fix:

  • the request's channel is gone, renamed or turned off;
  • the channel has no agent;
  • the code expired;
  • browser sign-ins are approved by the gateway operator only.

It also says that approval checks the channel again at the moment you select Approve, and that Deny is always available.

Verification

  • pnpm test: 33 files, 416 tests passed.
  • pnpm build: completed, 160 pages.

🤖 Generated with Claude Code

https://claude.ai/code/session_01BYfQbHRQu7VC6uwM2JiTKr


Generated by Claude Code

Describe the Pairing inbox states where Approve stays off, what the
operator should fix for each, and that approval rechecks the channel.

Refs nextlevelbuilder/dewee#1433

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BYfQbHRQu7VC6uwM2JiTKr
@mrgoonie
mrgoonie merged commit a9e476f into dev Oct 16, 2026
1 check passed
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.

2 participants