@@ -63,12 +63,17 @@ Long-running service changes should be implemented as PR-based workflows rather
6363than direct production mutations. Task reads require an explicit project filter
6464to avoid guild-wide task enumeration.
6565
66- Mention flow is opt-in per message: the bot runs the agent only when directly
67- mentioned in a server channel or thread. Mention-triggered agent results and
68- confirmation buttons are sent by DM to avoid leaking task or plan details into
69- public channels. A follow-up in the same thread should mention the bot again so
70- the bot has an explicit user trigger and fresh Discord role context for that
71- request.
66+ Mention flow is opt-in per message: the bot runs the agent when directly
67+ mentioned in a server channel or thread, or when a user sends the bot a DM.
68+ DM requests are accepted only after resolving the sender as a current member of
69+ the configured 508 Discord server. The ` /agent ` slash command is also registered
70+ for bot DMs and uses the same configured-server membership and role resolution.
71+ Other slash commands default to guild-only registration unless they are
72+ explicitly reviewed and opted in to DM contexts.
73+ Mention-triggered agent results and confirmation buttons are sent by DM to avoid
74+ leaking task or plan details into public channels. A follow-up in the same
75+ thread should mention the bot again so the bot has an explicit user trigger and
76+ fresh Discord role context for that request.
7277
7378Production mention handling depends on Discord gateway and channel access:
7479The bot requests all intents in code, but the production Discord application
0 commit comments