Behavioural Process Intelligence · Public Mirror
OpenAI
What we read from 300 public GitHub events across the last 3 hours. Real attribution preserved — these events are already public.
FIG 1 · Lede
Mirror · OpenAI · May 9, 2026
12 PRs merged with no independent review.
12 PRs merged with no independent review. Spans 3 repos. Either reviewers were anonymous to the events feed, or the PRs went in without a non-author approval.
openai/openai-agents-python#3296·openai/openai-agents-python#3295·openai/openai-agents-python#3294·openai/codex#21778·openai/openai-agents-js#1275
12 issues opened, only 3 closed. Net +9 this window. Triage backlog is growing — maintainer queue lengthening.
openai/codex#21886·openai/codex#21885·openai/openai-cookbook#2677·openai/codex#21884·openai/codex#21883
1 release shipped without release notes. Examples: openai/codex rust-v0.131.0-alpha.2. Short or empty release bodies — what did this ship and why?
13 PRs merged between 22:00 and 06:00 UTC. Spans 3 repos. Either an always-on global org or a deploy-late-night habit.
openai/openai-agents-python#3296·openai/openai-agents-python#3295·openai/openai-agents-python#3294·openai/openai-agents-python#3216
13 PRs merged on a weekend. Across 3 repos. Could be on-call work, could be habit drift.
openai/openai-agents-python#3296·openai/openai-agents-python#3295·openai/openai-agents-python#3294·openai/openai-agents-python#3216
openai/codex shipped 1 release. Tagged release activity is the cleanest public signal of shipping rhythm.
openai/codex carried 52% of activity. 156 of 300 events in the last 3 hours. Next: openai/openai-agents-python (34).
FIG 2 · Activity stats
FIG 3 · Repos by activity
- openai/codex156 events · 0 commits · 3/0 PRs
- openai/openai-agents-python34 events · 0 commits · 9/3 PRs
- openai/symphony28 events · 0 commits · 0/0 PRs
- openai/codex-plugin-cc13 events · 0 commits · 0/0 PRs
- openai/openai-cli13 events · 0 commits · 0/0 PRs
- openai/whisper8 events · 0 commits · 0/0 PRs
FIG 4 · Contributors by activity
- @seratch16 events · 7% share
- @spacexchateslai12 events · 5% share
- @HomeHeartTherapy6 events · 2% share
- @adityasingh24006 events · 2% share
- @soulhash-labs5 events · 2% share
- @rodrigoantonioli5 events · 2% share
FIG 5 · Rituals we can't see from GitHub alone
Public-GitHub data shows code behaviour. The rituals below need the rest of the toolchain. With Slack, Linear, Notion and Google connected, Assemblr would also surface:
Silent merge · PR merged with no Slack/release-notes followup within 30 min.
Needs: Slack #releases channel
Orphan ticket · Linear issue closed without a corresponding code merge in 7 days.
Needs: Linear (or Jira) to see ticket transitions
Ladder break · Cross-toolkit ritual fires N-1 of N expected steps for ≥3 occurrences.
Needs: Linear + Slack to stitch the cross-tool ladder
Stale-design code · Code shipped where the linked design doc hasn't been touched in 30+ days.
Needs: Notion or Google Docs for design-doc edit history
Postmortem skip · Incident channel created, no postmortem doc within 7 days of resolution.
Needs: Slack incident channels + Notion postmortem template
Phantom standup · Standup channel post pattern that ran ≥4 weeks then stopped ≥7 days ago.
Needs: Slack standup-channel message stream
This is what we'd see for your team.
Connect GitHub, Slack, Linear, Notion, and Google. We mine the actual behavioural patterns and ship a weekly briefing your VPE will actually read.
Book a demo →FIG 6 · Embed in your README
Paste this in your README. The badge updates daily and links back to this Mirror.
[](https://www.assemblr.net/mirror/openai)