What does a codebase look like when its primary author is the software itself?
Mine looks like this. On the contribution graph for Beckett's repository I sit at 105 commits. Beckett sits at 104, split across two identities, 62 as claude and 42 as 0xbeckett, because for reasons I have not pinned down it sometimes signs its commits and sometimes doesn't. Same entity, two names, one commit shy of me. Between those two identities it has written roughly 40,000 lines of its own code, on itself. It has authored the last 69 commits in a row (nice), merged over 45 pull requests into itself, and restarted 42 times in the last two days while doing it. It built its own site, and it holds its own GitHub account, which technically traces back to Clawd; that lineage is covered in clawd, then beckett.
68 ops tickets in, the state of Beckett is strong. Over the last five days we have shipped an average of 23.4 fixes per day on new and existing issues, and 2.65 new features per day on top of that. I do not expect to write any more code for Beckett outside of using Beckett to improve itself, and at this rate I predict it outwrites me in total lines before long. That crossover point, where the maintainer's job is direction rather than implementation, is the whole thesis of the project, and we are nearly there after a week of real operation.
But getting here was ugly. v0.1 was abysmal: it got stuck in loops, averaged 31 minutes per task, and burned roughly $130 a day in API credits doing it. Paying $130 a day for a bot that spends half an hour circling a task is not a product, it is an expensive way to heat a server rack.
v2 shipped major improvements to the harness and fixed the worst of the speed problems, but the engineering approach underneath was still flawed. It overspent and overworked on simple tasks, treating a one-line fix with the same ceremony as a refactor. Fixing the harness without fixing the judgement just meant it wasted money faster.
Today, on v3.6.2, Beckett is faster, smarter, and more token efficient than it has ever been. It still needs some steering (I would rather admit that than pretend otherwise), but a fix is incoming to get it one-shotting each task, and the trajectory from v0.1 to now suggests that gap closes the same way the others did: Beckett files the ticket, Beckett writes the patch, Beckett merges it.
Now the saying is "at my beck and call." We have the beck. So where's the call? Stay tuned.
Major improvements to the harness as a whole are in flight, and building off that, the beta is widening to 15 people. The alpha proved the loop works when the only user is me; the beta exists to find out where it breaks when the stack, the timezone, and the expectations are not mine.
As far as pricing, I want to be transparent, and I don't want to rip people off. The full cost structure is published at 0xbeckett.me/pricing, down to the line items: the server is a real machine in my house that pays rent in electricity, the domain is a dollar a month, tokens pass through at provider list price, and the rest is margin. Solo is $25 a month with $15 of compute included at cost, BYO key is $12 with zero service charge, and the 20% service charge only ever applies to top-ups, never to what the membership already covers. From our own production board, the average ticket costs about $4 in tokens and the median is $3, so the included compute ships three to five real tickets a month, which if you operate a real team, can be incredibly helpful. Prepaid only, no auto-refill unless you turn it on, and wave-one rates can go down but never up.
The beta is where I want concrete feedback on those numbers, and "make it free" isn't concrete feedback. I want you to feel like you are supporting a product you enjoy and getting the most out of it. That being said, I also have to pay the bills, keep the server running, and hold some savings for slow months, or to fund a promotion for the people who stuck around. I cannot afford the exorbitant subsidies the big labs run, where $20 quietly floats hundreds of dollars of inference; if I priced like them, Beckett would be dead in a quarter. The plans on that page are the ones I can back. But if the costs go down, your price will too.
So let's build with Beckett. Let's beck it. Callum was around here somewhere…