In 2026, agent infrastructure is going to explode. It began months ago, and will only strengthen into this winter. Vercel, Cloudflare, Daytona, are examples of companies racing to build all sorts of products, like agent frameworks and sandboxes. This indicates a future where coding agents, among other types, will NOT live locally.
More and more, coding agents will be autonomous and in the background. This has always been the mission for Replicas, and we are doubling down on it. Over the last month, we incorrectly positioned Replicas as something that clears “small tickets”. Tasks you want to get done while you focus on something more important. That framing was wrong.
We have a lot to show over the next few weeks, but here is our starting point.
What We’ve Learned
Over the last few months, we've used Replicas agents to build Replicas itself. We did not fill the commit sheet with meaningless tickets like changing the copyright footer to show impact. We used it on medium tickets and large tickets. Features that required larger scale architecture work and multiple rounds of testing. Bodies of work that months ago, we would not have had the confidence to leave in the background.But thanks to a lot of internal work, Replicas is feeling more like a real SWE everyday. They read Linear tickets and understand intent. They hit CI failures and debug them. They iterate on pull request reviews. And soon, they'll sit with company documentation (e.g Notion) and your comms (Slack).
The dogfooding has been intense, and is proof that Replicas works best when treated as a team member, and not a ticket clearing utility.
Our January Directive
Later this month, we’re overhauling the harness. Moving to faster VMs, revamping our dashboard, and integrating Replicas into more platforms and trigger points. We’re breaking down the SWE agent to first principles, and amicably calling this the SWE Agent Directive.This is a lot of buzzwords, and it’s best to take it seriously when we show results in a couple weeks.
Stay tuned :)