#516 – Meet Beetee
Friday Ship #516 | November 6th, 2026

This week we retired Datadog, built our own error tracking, and put Beetee, an AI agent that fixes bugs, to work.
In Friday Ship #515 we promised better error tracking. We ended up rebuilding it from the ground up, and that set us up for something we’ve wanted for a long time: a teammate whose whole job is fixing bugs.
Goodbye, Datadog
For years, Datadog was how we kept an eye on Parabol. When something broke, its dashboards told us what, where and how often. It did the job, but it was built for people staring at charts, and it meant one more outside company holding records of what happens inside Parabol.
So we built our own. Parabol already runs on Google Cloud, and now our logs and error reports live there too, under our control. Every error is written down with what we need to understand it: what the person was doing, which step failed, and what happened just before. We control every step of the process, and we got rid of dd-trace, which has plagued our app with monkey patches and memory leaks for years. It felt great to clean things up.
Meet Beetee
Better records were only half the solution. The other half is who reads them.
Beetee is an AI agent that fixes bugs in Parabol. Every 15 minutes, he checks our error reports for anything new. When an error is bothering real people, it becomes a ticket with everything we know: how many people hit it, when it started, and what they were doing at the time. Beetee takes the most urgent ticket and investigates. He reads the records and our code, and tries things out on his own private copy of Parabol until he finds the cause. Then he writes a fix and sends it to us, along with a plain-English account of how he got there.
Nothing reaches you until one of us has reviewed and approved it. A deterministic, non-AI piece of the code makes sure none of your data ends up in his code. When he can’t crack a bug, he writes down what he found and hands it to a person. Best yet— we can ask him questions or to rework a solution right there from the fix.
Our old setup couldn’t have fed him. Beetee is only as good as what he can read, and dashboards built for people don’t tell an agent enough. Our new error reports give Beetee everything he needs, all in one place (and for free).
His first three days
We turned Beetee on Wednesday. By Friday he had sent us 16 fixes, and we had approved 11 of them. A few:
- A mystery meeting crash. Some people joining a meeting from an invitation link saw it crash. Beetee noticed that a cluster of them had hit the same meeting within minutes, which pointed at something in that meeting rather than at the people. He traced it to three dashes in a row (—) in the meeting’s text, which tripped up how Parabol loaded it. The fix was one line.
- Integrations stay connected. When Jira or another tool had a brief outage, Parabol could disconnect it, and you had to connect it again. Now an outage on their end won’t sign you out.
- Jira issues with images. If a Jira issue had an image or attachment in its description, Parabol hit an error reading it. Not anymore.
- Sprint Poker. Removing several stories from a Sprint Poker meeting at once no longer trips up the meeting.
The fixes we’ve tallied cost between about 15 cents and $4 each in AI time, and he works within a budget we set. That changes which bugs are worth fixing. Beetee looks at any error that more than one person hits, including the small, annoying ones a team our size rarely gets to.
He doesn’t replace our judgment. Every fix still goes through one of us before it ships. But if a Parabol bug has been bugging you lately, there’s a good chance Beetee is already on it. And if your team has put an AI agent to work on something real, I’d love to compare notes.
Metrics

New signups were 1,089 this week, 9.3% below the four-week average, while teams ran 1,602 meetings, 5.7% below the four-week average and 39.8% below the same week last year. Website sessions jumped to 16,072, 50.8% above their four-week average, and Start, Stop, Continue was once again the most-run retro template: 298 retros by 233 teams.
This week we…
…stopped sending product analytics to Amplitude. Like Datadog, it was one more outside company holding records of how Parabol gets used. What we still need to know, we now measure ourselves.
…kept shaping Reports. When Reports can’t answer a question, it now says so and suggests one it can, instead of quietly answering a different question. You can rate each report with a 🙂 or 🙁. And it can now answer questions about facilitators, stand-ups, invitations, Pages, team leads and spend.
…made Parabol update itself quietly. The “new version available” message is gone. Parabol now picks up a new version the next time you click a link, or while its tab is in the background, but never during a meeting or while you’re typing.
…made Pages more forgiving. Search finds a page even when you misspell a word in its title, finds numbers like #5, and tells you when nothing matches. You can also turn a block into another type, say a paragraph into a heading, from its menu.
…kept patching our walls. Following last week’s security work, we tightened single sign-on, made sure messages that claim to come from Zoom really do, allowed only safe kinds of links in Pages, and updated software with known security issues.
…fixed a stack of smaller things. Signing in from a Page brings you back to that Page. Accepting a team invitation works the first time, and Back takes you out of it. Links to Parabol shared in Slack show a preview image. Zoom summaries and transcripts that arrive before a meeting ends still get attached. The row of avatars in large meetings (50+ people) no longer flickers. Recurring stand-ups keep their template.
Next week we’ll
…begin cool down, following Shape Up Cycle 16.
…put your error reports first. When you hit Parabol’s error screen and tell us what happened, Beetee will work on that error before anything else.
