Repository navigation
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
brsbl
added this pull request to stack #5478
October 14, 2026 04:58
This was referenced Oct 14, 2026
… an off-by-default flag Adds work_origin (person, agent, automation, plugin, system) to thread_created and user_message_sent when BB_FF_WORK_ORIGIN_TELEMETRY is on, so retention reads can separate person-started work from scheduled automation runs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… flag in parsed configs Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Follows PostHog and Segment naming guidance and bb's snake_case event fields: the property says who started the work. The internal initiator system maps to the value bb. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Matches bb's domain initiator (user | agent | system) and avoids PostHog's reserved person term, per the shared analytics schema vocabulary. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…or telemetry Plugin SDK sends now carry originPluginId, so automation runs into an existing thread report automation. bb thread spawn sends BB_THREAD_ID as senderThreadId, and the new thread reports agent when that sender has a turn running. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Without it the plugin SDK's attribution was dropped before the request left, so automation runs into an existing thread still reported initiator user. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
brsbl
force-pushed
the
bb/work-analytics-migration-thr_ch8epzf42x
branch
from
October 21, 2026 04:38
ee08e78 to
870bf85
Compare
brsbl
removed this pull request from stack #5478
October 21, 2026 04:40
brsbl
added this pull request to stack #5984
October 21, 2026 04:40
brsbl
force-pushed
the
bb/work-analytics-migration-thr_ch8epzf42x
branch
from
October 21, 2026 04:48
870bf85 to
156aa54
Compare
brsbl
force-pushed
the
bb/work-analytics-migration-thr_ch8epzf42x
branch
from
October 21, 2026 05:06
156aa54 to
8e0eec1
Compare
This was referenced Oct 21, 2026
This branch has not been deployed
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.
Human comments
What was wrong
Anonymous work records needed persistent tables. The migration also conflicted with newer migrations.
What changed
Stack order: #5947 → #5437 → #5477 → #5469 → #5470 → #5471 → #5472 → #5473 → #5439.
How you verified
BB-Thread-ID: thr_ch8epzf42x
BB-Thread-ID: thr_nq42ntdw95
BB-Thread-ID: thr_k4ic49de34