Skip to content

docs: drop applications.commands scope from Discord setup #39

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Aaronontheweb merged 1 commit into from
May 21, 2026
+2 −5
Merged

docs: drop applications.commands scope from Discord setup #39

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 1 addition & 4 deletions src/content/docs/channels/discord.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,10 +39,7 @@ Scroll down on the Bot page to **Privileged Gateway Intents** and enable **Messa

### 4. Set up OAuth2 scopes and permissions

Go to **OAuth2 > URL Generator**. Check these scopes:

- `bot`
- `applications.commands`
Go to **OAuth2 > URL Generator**. Check the `bot` scope.

![OAuth2 scopes selection](/screenshots/output/discord-setup-oauth-scopes.png)

Expand Down
2 changes: 1 addition & 1 deletion src/content/docs/channels/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@ netclaw daemon stop && netclaw daemon start

Daemon start hangs, then Discord shows `disconnected`. Logs show a 30-second timeout waiting for the gateway READY event.

The bot token may be valid but the bot hasn't been invited to any server, so Discord has nothing to initialize. Verify the bot has been added to your server with the correct OAuth2 scopes. Use Discord's [URL Generator](https://discord.com/developers/docs/topics/oauth2#bot-authorization-flow) to create an invite link with `bot` and `applications.commands` scopes.
The bot token may be valid but the bot hasn't been invited to any server, so Discord has nothing to initialize. Verify the bot has been added to your server. Use Discord's [URL Generator](https://discord.com/developers/docs/topics/oauth2#bot-authorization-flow) to create an invite link with the `bot` scope.

## ACL and Permissions

Expand Down
Loading