Introducing V, a personal agent template.
Built on Eve. Works on iMessage, Slack, and web. GitHub and Linear tools with long-term memory.
https://t.co/gy7xKWSrle
In light of what happened, I'm doubling down on skills like /improve.
A frontier model got pulled. If it happened once, it's gonna happen again. Fable today. 4.9 tomorrow or maybe gpt 6 one day.
So, treat intelligence as borrowed. Drain intelligence when it's available. Build a catalog of plans today. Then implement later with a cheaper, open source, or a model you control.
Build the backlog now.
https://t.co/rqHw0fPv4G
We just shipped 𝙷𝚊𝚛𝚗𝚎𝚜𝚜𝙰𝚐𝚎𝚗𝚝, a unified abstraction to orchestrate and integrate any agent’s “brain” into your app.
@aisdk now frees you from both model and agent lock-in. (And it doesn’t just get you portability, it’s also delightful to use ofc!)
This is what the future of design looks like. Not just this specific tool¹, but the fact that every team in the world is now is empowered to build their own 'design factory'.
Shader Lab was built with Claude Code, @threejs, @nextjs, and @vercel. To the exact needs, vision, and specification of @basementstudio.
Every time we work on a project with them, we get a glimpse of an arsenal of internal tools they've deployed. Some built specifically for a project, some more general purpose.
It's now easier to generate software re-assembling powerful building blocks, than searching and procuring the right SaaS for the job.
¹ though it's a banger
The hardest thing about agents and backends is durability. @workflowsdk fixes this.
That LLM you're calling *will* go down. That service *will* rate limit you. That database *will* unexpectedly slow down. You *will* get paged 💀
I've been looking for a unicorn for a decade. I wanted the level of reliability of combining stuff like SQS / Kafka / microservices, and I absolutely did not want *that* at the same time 😂
Truly reliable systems like that are notoriously difficult to reason about, to develop locally, to test, to simulate, to deploy… Workflow SDK solves that without compromises.
We're doing what Next.js did for the frontend, but for one of the most important problems of the new generation of backend applications.
Notably, Workflow SDK has an incredible self-hosting and multi-cloud story from day 0. We've taken amazing lessons from Next.js and poured them into the many Worlds (adapters) you can deploy to.
Congrats to Pranay and the Workflow team on a generational ship: https://t.co/ub7vQ7L6yE
Whether design belongs in Figma or Claude Design is a distraction from a bigger shift.
1️⃣ Design will become autonomous. More helpful to think of it as 𝙳𝙴𝚂𝙸𝙶𝙽.𝚖𝚍, used by your coding agents running your software factory.
2️⃣ Specialized “personal” design tools generated by teams will proliferate. Design is a capability, not a tool. I agree with @rsms that there are many facets of design, and multiple tools are required.
I love prompting in @v0 and it’s become the place where I can channel my inspiration, explore, communicate. But I’m also seeing a new generation of products that use the v0 Platform API or Sandbox and put design on autopilot.
There are next-generation agents like @tryflint and https://t.co/fZ7TO6rczt generating design & brand systems and maintaining them autonomously. Flint can even keep your website and content up to date and its design consistent. No human prompting needed.
From this we will see the emergence of fully autonomous companies with agents like https://t.co/YhOmGYYwgE and https://t.co/v8TuIxujwy, which go a step further and grow and advertise your business.
tl:dr; The future looks very different from the present. AI is a true discontinuity. The “here’s the existing thing but with AI and ${jobTitle} is cooked” is short-sighted.
@ericzakariasson should we provide hints on subagent use of the cli?
like which commands can be run well in parallel with subagents.. or is that useless