#Agent

New on our Engineering blog: Creating in-house source control. In May, we merged around 2,500 code changes per day. In September, we merged more than 30,000 per day. As a result, we became bottlenecked by developer infrastructure built for human (rather than agent) scale. Here, we share how we built a new version control system—and fully migrated our monorepo from git—in five months: https://www.anthropic.com/engineering/redesigning-source-control

New on our Engineering blog: Creating in-house source control. In May, we merged around 2,500 code changes per day. In September, we merged more than 30,000 per day. As a result, we became bottlenecked by developer infrastructure built for human (rather than agent) scale. Here, we share how we built a new version control system—and fully migrated our monorepo from git—in five months: https://www.anthropic.com/engineering/redesigning-source-control

I just gave my a Grokbot four years of past tax returns and financial files. Just a dump of folders and unlabled files. K-1s, 1099s, mortgage statements, HSA records, and every email with our CPA. 266 files. I just said, please double check my CPA's work. A few minutes later, it had found a lot of mistakes. Mortgage interest left off our 2022 return entirely. HSA payroll contributions counted twice, four years in a row, which created a penalty tax that never should have existed. A missing IRA form for Jen that would have cost us. On this year's return: home office errors, two K-1s missing, an outdated 1099, and startup losses we never claimed. And a retirement contribution the return already deducted...that we hadn't actually deposited. I sent it all to our CPA. They sent back an amended return. The bot reviewed that too. One fix went the wrong direction. The explanation had typos. Three versions later, all in one afternoon, it said ready to sign. Just a few hours start to finish. With about 90 seconds of my time and attention required. I was just the meat proxy hitting send as Grokbot watched the replies in my email. Our CPA is great and turned every fix around the same day. We chatted afterwards. He wanted to know what I was using - just normal ole' grokbot. I asked him what he was using? No AI tools. I set him up with @magnetictax for next season (we're an investor). All CPAs should be using Magnetic Tax or something like it. Every single one. All individuals should be double checking the work and past work with Grokbot or something like that. Want to copy the exact the prompt I used? it was just this: "Please do a thorough review of my taxes and help me understand if my CPA made any mistakes" "Think deeply" Or just tag your bot into this thread.

grok @bot 0.70.2 is rolling out! - each bot can claim its own email address at @mail.grokbot.com and draft emails for you to send - apps like Figma, Notion and Canva show up as live cards right in the chat - bots can search X and read public posts and profiles without connecting an X account - describe what you want and your bot suggests a matching template - shared pages can be downloaded as a pdf - an approval check before anything irreversible and much more! https://x.ai/changelog/bot

I gave Grok Bot its own button → Press the Action Button → Open Grok in voice mode → Give it tasks and deadlines → Grok delegates them to Bots I feel like James Bond.

Meet Pancake, the Vercel for GTM. Try it at http://pancake.ai Your agent ships your product. Now it ships your go-to-market. How? A GTM brain that knows your business, 50+ data providers to find the right customers and tools to reach them. Your next customers are one prompt away. (did I really have to jump off a plane to say that? questionable, but I survived and now you're reading my tweet)

Today we release 𝙻𝙵𝙼𝟸.𝟻-𝟸𝟺𝙱-𝙰𝟸𝙱, the largest 𝙻𝙵𝙼𝟸.𝟻 family member. It is an efficient local model for laptops and PCs to work through multi-step tasks inside popular agent harnesses. > 24B total parameters, 2B active per token > Context expanded to 131K tokens > A 128K-token vocabulary > 33T pretraining tokens > It is a reasoning model > Very easy to fine-tune and customize > Performs competitively with Qwen3.6-35B-A3B, a model with ~50% more total and active parameters, on agentic and tool-use tasks. > Open base and post-trained weights on @huggingface 🤗 1/

A year ago I started Agor to keep track of my own agent sessions across a pile of terminals. Today @agorcloud Open Beta is out: the hosted version, where your team and your agents share and work together on live boards. Tell me what you build. https://na2.hubs.ly/H08kZv70

Today, we're launching Sazabi version 1.0. The reality of shipping software as a team in the age of AI is actually crazy. Agents merging their own PRs. Hundreds of deployments per day. A codebase that is constantly changing. Junior developers with 10x or 100x leverage. 😵‍💫 I spent the last year building a safety harness for teams that ship with AI. It's called @sazabi. The premise is simple: 1. You send us logs. 2. We detect anomalies, investigate them, and send you back rich, actionable alerts about real problems in your app. Sazabi helps you find issues before your users notice. No monitors or noisy alerts. Just pure signal. And today we're making it available for anyone to use.

New on our Engineering blog: Creating in-house source control. In May, we merged around 2,500 code changes per day. In September, we merged more than 30,000 per day. As a result, we became bottlenecked by developer infrastructure built for human (rather than agent) scale. Here, we share how we built a new version control system—and fully migrated our monorepo from git—in five months: https://www.anthropic.com/engineering/redesigning-source-control