More PRs than anyone can read
When coding agents write the code, a small team can merge more PRs in a day than anyone can read. The decisions behind that work happen in Slack threads, and the PRs rarely say which decision they follow. Context grows faster than one person can absorb it, whatever the size of the team.
A digest of every merge adds to the pile, and search only answers the questions you already thought to ask. What helps is something that remembers what the team decided in a thread and notices when a PR goes another way.
How it works
- It reads. We’ll set it up with you: GitHub and Slack for now. Biddle reads PRs, commits, reviews, CI, and issues, plus the product channels where decisions get made. A PR description written by a coding agent counts as a statement of intent.
- It keeps the record. Workstreams and decisions go into one running record, each entry tied to the PR, commit, or message it came from. Anything it can’t tie to evidence stays out of the record, and the briefing says how many items it left out.
- It tells you. One briefing DM each weekday morning, per product. In between, a nudge only when merged code drifts from a decision, or when a question has gone unanswered for days while a PR waits on it.
It connects to GitHub and Slack. Linear and Notion aren’t supported yet.
Ground rules
- Every claim has a receipt.
- If Biddle can’t point to the PR, commit, or Slack message behind a sentence, the sentence doesn’t go in.
- Read-only on GitHub.
- Biddle doesn’t comment on PRs or write code, and it doesn’t post in your team’s channels. It talks to you, in a DM.
- Quiet unless it matters.
- A wrong nudge costs more than a missed one. When Biddle isn’t sure, it holds the item for the morning briefing and says so.
- It picks.
- Of the day’s merges and threads, you see the few that changed a plan, need your call, or have quietly stalled.
Where it stands
Biddle is in early access, and it isn’t sending briefings to anyone yet. We’re building it on our own repos first: Liouville Labs runs a dozen products with agents writing most of the code, and one of them shipped more than 200 PRs in two weeks. Early-access teams come next, and we’ll set it up with you.