When Junior needs OAuth authorization from a user, the runtime sends an ephemeral Slack message containing the auth link. Ephemeral messages posted in a thread are only visible to the target user and do not appear as a thread reply to anyone else — they don't increment the reply count or show in the thread view.
Current behavior
- User mentions Junior in a thread
- Junior needs auth, sends an ephemeral message with the auth link
- From the user's perspective (and all other thread participants), Junior appears to silently ignore the request — no visible reply, no indication anything happened
- The ephemeral auth link is easy to miss, especially in a busy thread
Reaction emoji is lost across auth pauses
Separately but related: the acknowledgement reaction emoji (added to the user's message when processing starts) is removed when the auth pause kicks in, and is never re-added after auth completes and the request resumes. The expected behavior is that the reaction reappears on the original message once processing continues, since that's the message being acted on. Currently the user loses both visible signals — the reaction disappears and no reply appears.
Gap
There is no visible feedback that Junior received the request and is waiting on authorization. This makes it look broken or unresponsive. Combined with the lost reaction, the entire interaction feels like Junior ghosted the request.
Suggested approach
Post a visible (non-ephemeral) thread reply when an auth pause occurs, something like:
I need authorization to continue — I've sent you a private link to connect.
This gives the requesting user and thread participants visible confirmation that Junior is active and waiting. The actual auth URL stays ephemeral/private.
Additionally, re-add the acknowledgement reaction to the original message after auth completes and processing resumes.
Considerations:
- Keep the visible message brief and actionable
- Don't expose the auth URL in the visible message
- If auth completes and the request resumes, the visible message still makes sense as context
- If auth is never completed, the message explains the stall
- The reaction should be restored on the original triggering message, not on the auth reply
Action taken on behalf of David Cramer.
When Junior needs OAuth authorization from a user, the runtime sends an ephemeral Slack message containing the auth link. Ephemeral messages posted in a thread are only visible to the target user and do not appear as a thread reply to anyone else — they don't increment the reply count or show in the thread view.
Current behavior
Reaction emoji is lost across auth pauses
Separately but related: the acknowledgement reaction emoji (added to the user's message when processing starts) is removed when the auth pause kicks in, and is never re-added after auth completes and the request resumes. The expected behavior is that the reaction reappears on the original message once processing continues, since that's the message being acted on. Currently the user loses both visible signals — the reaction disappears and no reply appears.
Gap
There is no visible feedback that Junior received the request and is waiting on authorization. This makes it look broken or unresponsive. Combined with the lost reaction, the entire interaction feels like Junior ghosted the request.
Suggested approach
Post a visible (non-ephemeral) thread reply when an auth pause occurs, something like:
This gives the requesting user and thread participants visible confirmation that Junior is active and waiting. The actual auth URL stays ephemeral/private.
Additionally, re-add the acknowledgement reaction to the original message after auth completes and processing resumes.
Considerations:
Action taken on behalf of David Cramer.