fix: properly track user_id in ai_usages for Telegram and web#162
Merged
tuvshinjargal merged 1 commit intomainfrom Feb 24, 2026
Merged
fix: properly track user_id in ai_usages for Telegram and web#162tuvshinjargal merged 1 commit intomainfrom
tuvshinjargal merged 1 commit intomainfrom
Conversation
- Check for conversationUser property first in TrackAiUsage (set by continue() method) - Add explicit listener for AgentStreamed event in addition to AgentPrompted - Update tests to use create() instead of make() to persist user to database
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
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.
Summary
user_idas null inai_usagestable by checking forconversationUserproperty first (set by thecontinue()method) before falling back touserpropertyAgentStreamedevent in addition toAgentPromptedcreate()instead ofmake()to properly persist user to database for foreign key constraint