FIX: Attribute automation-triggered AI usage to system user #36622
+8
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When automations triggered AI API calls, the usage was incorrectly attributed to the post author who triggered the automation, rather than to the system. This caused users to see AI usage in their Rewind reports for AI features they never intentionally invoked. Added an `attributed_user` parameter to `Playground.reply_to_post()` and `Playground.reply_to()` that flows through to `BotContext`. When set, this user is recorded in `AiApiAuditLog` instead of defaulting to the post author. The automation handlers (`LlmPersonaTriage` and `LlmTriage`) now pass `Discourse.system_user` as the `attributed_user`, ensuring automation-triggered AI calls are properly attributed to system rather than the triggering user. Direct user-initiated AI interactions (mentioning bots, using AI features) continue to be attributed to the actual user since `attributed_user` is nil in those cases. Internal ref - t/170333
janzenisaac
approved these changes
Dec 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When automations triggered AI API calls, the usage was incorrectly attributed to the post author who triggered the automation, rather than to the system. This caused users to see AI usage in their Rewind reports for AI features they never intentionally invoked.
Added an
attributed_userparameter toPlayground.reply_to_post()andPlayground.reply_to()that flows through toBotContext. When set, this user is recorded inAiApiAuditLoginstead of defaulting to the post author.The automation handlers (
LlmPersonaTriageandLlmTriage) now passDiscourse.system_useras theattributed_user, ensuring automation-triggered AI calls are properly attributed to system rather than the triggering user.Direct user-initiated AI interactions (mentioning bots, using AI features) continue to be attributed to the actual user since
attributed_useris nil in those cases.Internal ref - t/170333