Cursor

@creatine_cycleSep 26

i don't think that now is the best time to be in SF. i think that time was 2022 after covid where SF felt like gotham city and the real sickos had weathered the storm while starting the juggernauts of today. 2026 SF feels reminiscent of the 2010s when it was consensus to be here and the striver could chase 200k-300k at big tech. the conversations and discourse in SF reflect this now. AI is priced in and we have ended up in a 2 week news cycle where there is a sequence of new benchmark breaking releases, a scandal with political fallout and weird little bits of cringe striver slop in between. it's not all bad and the pace of progress on the frontier is staggering and interesting. but i have a hard time believing that this amount of capital and comfort surrounding AI is creating the environment that will breed many more cursors or midjourneys like that of 2022. i love it here and always have but it is consensus to be here now. it's always less interesting when that's the case

@rauchgSep 25

We're helping world-class organizations like @klaviyo build agentic deployment platforms. ① Connect every agent (claude, codex, cursor…) ② Configure SSO via their IDP (Okta, Entra) ③ Now everyone can cook, securely® What happens to SaaS once every company sets this up? I get this question a lot 😁 First, the data must come from somewhere. These apps only work if they can be infused with business data. This is why we see the big enterprise SaaS players suddenly prioritize shipping CLIs and MCPs. Or dust off APIs they were neglecting for years. The new 'procurement bar' will be how ergonomic your product is for *agents*, rather than humans. How easily they can navigate your ontology and work with your data. Once that's in place, there's a long tail of SaaS applications that I suspect will never be bought again. They'll be generated. They'll be more secure, more performant, more modern, and tailored to each company's and employee's needs.

@mattypSep 25

I'm building a video editor by making Cursor edit my video This is a Cloud Agent with the editor loaded Cursor is using Grok 4.7 to edit the video via MCP, then testing the UI At each failure, the agent reflects then fixes the product. The goal is a clean end-to-end edit With the right feedback loops, you can autonomously build software

@mattpocockukSep 25

This is an extremely good watch. The things that felt novel/interesting to me: 1. Lock down your agents Humans tend to like 'sharp knife' abstractions - that are powerful, but you can cut yourself if your use them wrong. Lauren says agents perform much better in extremely locked-down environments. Abstractions are designed so they can't screw up, and lint rules enforce it. They built a whole internal framework (Dune) to keep the agent on track. That helps optimise agents that don't have a large context window to work productively in your codebase. 2. Create verification infrastructure To trust the results of any agent, you either need to sit and watch it OR have it provide evidence of its improvement. This has always made sense to me, but Lauren really pushes it hard here: - Invest in custom CLI's that let the agent drive the app and measure its performance - Make the app "factory ready" from the get-go - i.e. deployable to an environment where the agent can mess about with it 3. Feature Maps Lauren's software factory (what she calls an 'outer loop') often requires the agent to break down vague bug reports from users and to turn those into potential fixes. To aid that, they built a 'feature map' of all the main features in their application, which describe exactly how the app is supposed to function. This has become essential for helping the agent navigate the codebase, and figure out quickly how things are supposed to work. It's maintained along with the codebase, and kept in sync via automations. This is the kind of documentation I usually warn against. It goes stale quickly and can confuse agents if it's not kept up to date. But Lauren's team are using it as critical navigation infrastructure, and it makes it possible for agents to explore faster and better - even on a large codebase. So it sounds like navigation docs like this are worth it if they enable new behavior. Banger talk - watch the whole thing on 2x.