Skip to content

fix(case-studies): correct Pomerado relay numbers - #320

Merged
khaliqgant merged 1 commit into
mainfrom
fix/pomerado-case-study-numbers
Nov 17, 2026
Merged

khaliqgant merged 1 commit into
mainfrom
fix/pomerado-case-study-numbers

Conversation

@khaliqgant

@khaliqgant khaliqgant commented Nov 17, 2026 •

Copy link
Copy Markdown
Member

The Pomerado numbers merged in #123 came from a message store that only goes back to October 14. Pomerado started on September 22, so the page undercounted and called the wrong days the busiest.

This uses PostHog send events (message created, DM, thread reply, group DM) for both Pomerado workspaces, September 22 to November 16, Pacific time:

Was Now
Messages 30,000+ 38,000+ (38,557)
Typical week 5,000-6,500, up to 98 agents 4,000-6,600, up to 97 agents sending
Busiest day 1,313 (Oct 21) 1,753 (Sep 24)
Busiest hour 188 201
Agents connected 86 first week, 650+ by launch 390 since Oct 8; 144 in launch week
Launch-week paragraph 4,893 msgs, then 5,247 / 6,551 / 5,068 4,302 msgs, then 5,611 / 6,601 / 4,803

Agent counts come from presence heartbeats, which only start October 8, so there's no count for their first two weeks. The old "650+" counted agent records rather than connected agents and is dropped.

vitest run lib/test/case-studies.test.ts passes.

🤖 Generated with Claude Code


Autofix with [code]smith
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.


Summary by cubic

Corrects the Pomerado case study numbers, which previously came from a message store that only went back to October 14 and missed Pomerado's first three weeks on the relay.

  • Replaces all figures with PostHog send events from both workspaces, September 22 to November 16 (Pacific time).
  • Updates the total to 38,000+ messages, and corrects the busiest day (September 24), busiest hour, and weekly ranges.
  • Drops the old "650+ agents" figure, which counted agent records rather than connected agents; presence data only begins October 8.

Written for commit db17fc5. Summary will update on new commits.

View guided diff Turn on auto-fix

…st Oct 14 on

The figures came from a store that only keeps messages from October 14,
so they missed Pomerado's first three weeks: the real busiest day, busiest
hour and about 14,600 messages. Use PostHog send events for both workspaces,
September 22 to November 16 (Pacific).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@composalagent

composalagent Bot commented Nov 17, 2026 •

Copy link
Copy Markdown

Composal Verify · PR #320

Skipped Skipped · commit db17fc59b659

Warning

This request is merged; previous verification results remain in the history.

No high-confidence scenario matches were found; no preview or browser run is needed

Diff assessment: Updates browser-rendered Pomerado case-study MDX content, correcting the description, relay statistics table, reporting dates, and launch-week narrative.

Why no scenarios were selected

No saved scenario matched this change.

Recent verification history
Commit Result Started
db17fc59b659 Skipped Skipped 2026-11-17 16:45 UTC

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-17T16:46:19.930394Z db17fc5 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Devin Review

@coderabbitai

coderabbitai Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Explain Change →

No actionable comments were generated in the recent review.

Walkthrough

The Pomerado case study updates its reported Agent Relay message totals, reporting period, weekly activity, peak usage, and connected-agent counts.

Changes: Pomerado statistics

Layer / File(s) Summary
Updated activity figures
web/content/case-studies/pomerado.mdx
The description and statistics table report 38,000+ messages through November 16, with revised weekly, daily, hourly, and agent counts. The launch account reports 144 agents and updated weekly message totals.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Possibly related PRs

Merge Risk: Minimal · up to db17f

This updates published case-study statistics for Pomerado. There is no runtime or product behavior change, and no merge-blocking risk remains.

Pre-merge checks: Passed 4

Check name Status Explanation
Title check Passed The title names the change: correcting the Pomerado relay numbers in the case study. The raw summary confirms the case study file was updated with revised message totals, reporting period, and launch-…
Description check Passed The description explains the change. It says the earlier figures came from a message store starting October 14, while Pomerado started September 22. It gives a before-and-after table for messages, wee…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Title check

Explanation

The title names the change: correcting the Pomerado relay numbers in the case study. The raw summary confirms the case study file was updated with revised message totals, reporting period, and launch-week figures. The title is concise and specific, though it does not mention the root cause (incomplete message store coverage) or the new data source.

Full details: Description check

Explanation

The description explains the change. It says the earlier figures came from a message store starting October 14, while Pomerado started September 22. It gives a before-and-after table for messages, weekly and daily stats, agent counts, and launch-week figures, which matches the case study update in the raw summary. It also notes the agent-count source and that a test command passes.

Finishing Touches

Generate unit tests (beta)

  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

A rabbit counts the messages bright,
Thirty-eight thousand mark the flight.
New weekly figures fill the page,
Agents join across the date and age.
The case study hops along with cheer.

Recent review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 142f845f-95c4-42c7-8e94-70ea4f309753
Commits

Reviewing files that changed from the base of the PR and between 6c71dc3 and db17fc5.

Files selected for processing: 1

  • web/content/case-studies/pomerado.mdx

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

@github-actions

Copy link
Copy Markdown
Contributor

Preview deployed!

Environment URL
Web https://3636b84c-agentrelay-web.agent-workforce.workers.dev

This is a Cloudflare Workers preview version of this PR's build.

@khaliqgant
khaliqgant merged commit 97813c4 into main Nov 17, 2026
7 of 8 checks passed
@khaliqgant
khaliqgant deleted the fix/pomerado-case-study-numbers branch November 17, 2026 16:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant