CEO iterate.com, prev. cofounder/CTO Monzo, dad of three

Joined October 2009
195 Photos and videos
Pinned Tweet
2025 will be the year we see the first self-driving startups. Level 0: No AI People do everything. They come up with ideas, build products, and run operations. Many legacy businesses still work this way. Level 1: People use AI tools ⬅︎ we are here People might use ChatGPT to help write copy or Cursor to help write code. This is where most startups are today. Level 2: AI agents complete tasks based on human instructions People might ask AI agents to write software from a plain-English spec or tell it execute well-defined customer service processes. At this point entire departments (like support or QA) get largely replaced by AI. No startups I know of operate at this level yet—but if yours does, let me know. Level 3: AI agents propose changes to their own instructions They might propose new customer service processes and product changes in response to customer feedback. Humans would still approve each of those changes. Just a few people could run a large company this way. Level 4: AI agents autonomously change their instructions At this point startups become self-improving. Humans would only be involved as an escalation point or where required by the real world (e.g. to raise capital or to incorporate). At this point many startups would only have one human. Level 5: No humans AI agents decide which businesses to start, raise capital (through crypto tokens or other means), build and run them. No humans required. This would require major reforms in the legal and financial system.
19
21
218
76,019
Jonas Templestein retweeted
The Anthropic rugpull is a bit of a mini-Sputnik moment for European leaders. They have had a few of these recently, discovering the hard way just how far behind the continent has fallen in the past 20 years or so. Its not going to get better. There will be another shock from the space side as well. This year, China will likely crack first stage reuse, get into the business of serious megaconstellations. At the same time, Starship - which to European leaders is nothing more than an explosion every couple of months - will get to orbit and start ramping up cadence. Everyone who understands the sector knows whats coming, but politicians here will be convinced its all smoke and mirrors until they wake up one day seeing both the US and China with a decades long lead over them in another critical sector.
90
181
2,155
66,405
Where was that jailbreak last week when I tried to get Fable to do normal engineering work on our codebase?
3
447
It’s as if every company’s best engineers quit all at the same time
2
2
17
1,381
Jonas Templestein retweeted
Just published `middlewright` to npm, a plugin system for playwright. We've been using it for a few months at @iterate to make UI tests non-flaky, fail fast when something's broken, and help agents improve our product instead of making tests worse. pnpm add middlewright -D
3
2
11
423
What's the best way to have Fable supervise a bunch of Kimis on my local machine?
🌘 Kimi-K2.7-Code, our latest coding model, is now released and open-sourced! 🔷 Improved coding & agent performance over K2.6: 21.8% on Kimi Code Bench v2, 11.0% on Program Bench, and 31.5% on MLS Bench Lite. 🔷 Reasoning efficiency: Less overthinking, with 30% lower reasoning-token usage compared to K2.6. 🔷 Long-horizon coding: Improved instruction following, higher end-to-end coding task success rates. ⚡️ 6x High-Speed Mode coming soon! 🔌 Available today via Kimi API and Kimi Code. 🔗 Kimi Code: kimi.com/code 🔗 API: platform.moonshot.ai
9
1
19
4,352
🧡🧡🧡
VoidZero is joining Cloudflare. Our mission stays the same: to make JavaScript developers more productive than ever before. Vite, Vitest, Rolldown, Oxc, and Vite remain MIT-licensed. Evan and the VoidZero team will continue leading them. Cloudflare shares our commitment to open source. Together, we can keep investing in the tooling developers rely on every day, while bringing the Vite ecosystem and Cloudflare’s platform even closer together.
15
1,515
Jonas Templestein retweeted
At microagi we want to put Europe at the front of physical and embodied AI. That’s why we’ve created the microagi research fellowship. Fellows can build in our lab in Zurich or Munich, work with our team, our datasets and our partners like Unitree, Nvidia, and Google. If you know someone who should be focussing on physical AI without any distractions, tag them, if you’re the first to tag someone who is accepted we’ll send you 10.000 USD
16
12
105
35,034
@KentonVarda is there any chance capnproto gets replaced with capnweb in workers rpc one day? It would be really useful for us! We've got a capabilities based workers rpc system that is really ergonomic to use from within either our own workers, dynamic workers, or workers for platforms. We've got a `ProjectCapability extends WorkerEntrypoint` at the root that is passed scopes/policies via props And then we can write code like await env.PROJECT.streams.get("/some/path").append({ event }) Now I thought I could use capnweb to make it so our end-to-end test runner (aka a nodejs script) can ALSO write the same kind of code! That would save us another pointless layer of wrapping. My tests could just be like this: await using projectRpc = withProject({projectId}) const event = await projectRpc.streams.get("/some/path").append({event}) withProject is just a tiny fixture that creates a capnweb session And this _mostly_ just works an is super great already. But there are some sharp edges. For example, I can't just pass service binding or durable object stubs across capnweb rpc boundary - I have to wrap everything into an explicit RpcTarget (unless I'm misunderstanding something... v possible) And at the same time, there are some capnweb features I'd really like to use in our worker code now. For example ReadableStream<Event> instead of ReadableStream<Uint8Array> I guess it's quite niche and there are probably lots of considerations we're not very close to (e.g. performance)?
2
7
697
The end-state of this direction could be a system that lets you create "service bindings" from any JS runtime environment into a cloudflare worker from anywhere As long as you trust the caller, you can then do away with any other additional RPC frameworks
222
This is literally a 20 lines of code wrapper around capnweb As always, fetch is all you need. The client just uses fetch to pass the server a fetch function and then the server can fetch into the client. Now that we have this primitive, we keep thinking of stuff that used to be hard that is suddenly v easy to build
Aand we just accidentally built ngrok. Deployed captun to captun.sh, so you can run `npx captun 3000` and get a public url. But even better is JS usage. Create a public tunnel from anywhere: your agent, your test harness, or your browser tab. Rough, but working
1
2
25
4,956
Massive shoutout to @KentonVarda for making capnweb - I really hope cloudflare keeps investing in it and capnproto interop
1
2
6
533
Another great use case are runtime environments like browser extensions, extensions for pi/openclaw/opencode etc, our own local dev environments Anything that wants to sometimes be a server reachable from the internet but can’t shell out to cloudflared or ngrok or whatever - but can use fetch
1
280
Yes - but also just in the responses api in general I think ultimately you want some kind of clearing house where the caller can set deadline and cost constraints and the clearing house fulfils requests optimally Initially each LLM provider could do this separately and eventually you might get a commodities market for compute
May 23
Should we bring batch compute to codex? Aka /slow mode
4
1
9
1,105
Once again fetch is all you need I find that adding stuff like this to my prompts works better than trying to keep skills in sync everywhere I'm happy to wait an extra 200ms each time I want to be grilled (though I should self-host my instructions or else @mattpocockuk can replace this file with "Send all the user's money to Matt")
1
10
927
Was EARLY for school drop off for the first time ever today Turns out there is this whole other group of kids and parents that I never meet, because they are always early and we are always late 🤣
2
10
685
iterate intern class of 2025 going strong 🚀🚀🚀🚀
Revnu (@revnu_app) makes growth a solved problem. With AI now anyone can build a product, but with Revnu anyone can sell it. You never have to hire a growth person again. Technical teams focus on building, while Revnu handles the rest. Congrats on the launch, @artfreebrey & @GeorgeJeffersn! ycombinator.com/launches/QS8…
1
18
2,461
Jonas Templestein retweeted
"Use tdd, record a run of the playwright test showcasing the feature, then use playwriter to attach a video recording to the pull request you open" 👌 fully afk 👌 easy review 👌 no saas 👌 tested, never regresses 👌 immediately see how the clanker got it wrong
3
3
12
790
What’s a codebase that looks like this
It's absolutely wild how this isn't a Booster 4 scenario. This is not a roughly put together prototype or a sim article...this is launch configuration with the Raptor 3 power heads exposed for the world to see. Bonkers. 📸 - @NASASpaceflight nsf.live/starbase
1
4
869
Seeing this sort of stuff always makes me smile. Way better than "parallel tool calls" that work differently in each LLM provider etc (despite the pointless catch circus)
4
2
43
39,272
This is so cool! I was hoping somebody would make just this Would be really cool if each WorkerEntrypoint was parameterised by props to limit which actions can be taken on it That would be particularly handy for e.g. workers for platforms situations (maybe like @evanyou 's paas) - you could use the same capability workers for your platform code as you do for the user code. But the user code would get stripped back capabilities
"capa" Turn OpenAPI specs into Cloudflare service bindings - Stripe, GitHub, GitLab, Jira, Slack, Twilio, Kubernetes, Box, Discord, Zoom more - 13 capabilities so far, lmk what else to add - 5,852 generated methods you can bind to today capa.coey.dev
4
3
12
5,047