Claude365 sub next?
.@AnthropicAI is building every SaaS product into @claudeai -- and making them free for life.
@Office365, @google, @canva, @figma.... right down the line.
and this can't be antitrust if the products are FREE FOR LIFE -- right?! docket @DavidSacks!
5
288
13 years ago, Apple asked a question that hits me harder today than ever:
If everyone is busy making everything, how can anyone perfect anything?
Every day, I see a world flooded with effortless AI slops. I’m realizing that to build something truly great today, you need a level of focus the world has never demanded before.
It feels like trying to write a quiet, beautiful song in a room full of loud noise.
Agent-desktop is truly a gamechanger
What shipped at Vercel Labs in October
95 releases
730 issues closed
3,500+ PRs merged
New: agent-desktop
→ Computer use for any coding agent
→ macOS, Windows + Linux
New: tsc-ts
→ The TypeScript 7 compiler, written in TypeScript
→ Compiled to native with scriptc
agent-browser
→ Safer MCP
→ 42 browser tools for eve agents
skills
→ Sync skills across a monorepo
→ Sync reads optional + peer deps
→ Faster updates
json-render
→ Streaming fixes
→ Form + PDF fixes
→ json-render-shadcn skill
portless
→ No more sudo
→ portless mcp
deepsec
→ Kimi K3.1 Pro + DeepSeek V4.1 Flash benchmarks
native
→ native test for TS apps
→ Reusable markup components
→ Virtual lists
scriptc
→ Fully native, no JS engine
→ WebAssembly compiles to native
→ Profile-guided optimization
just-bash
→ mktemp + yes
→ Closer to real bash + jq
fx
→ Launches 23× faster
→ 41% fewer tokens
→ Agents that survive redeploys
wterm
→ Faster color rendering
→ Emoji + flags in one cell
→ Vim matches your page theme
vgpu
→ Build-time WGSL shaders
→ Turbopack support
→ Depth + MSAA on canvas
lat․md
→ lat ui to browse your knowledge graph
→ Graph view + static export
emulate
→ npx emulate mcp
→ AWS Cognito
→ Slack interactivity
ai-cli
→ ai mcp
→ ai decide can judge images
mcp-handler
→ MCP Events
run
→ CPU time limits for agent code
5
226
Ux should now be default liquid - except all the backend “core” system like DB, auth, model, gateway, payments
I'm now building an "improvements" feature into all of my personal vibecoded applications: a freeform text input that's hooked up to an agent that yolo implements whatever is submitted.
It's an interesting experience -- the activation energy barrier to sanding any rough edge or implementing any new feature becomes extremely low. Someone else who uses one of the applications I created has already implemented 150 improvements over the course of a few days. This pattern feels like a new kind of tool -- liquid software? -- and every application that doesn't have this feature now has a slightly rigid and anachronistic flavor. Why can't I just tell it how I want it to be different?
Now, it's not obvious to me how this pattern can or should scale. Does it become unmaintainable after a while? (Maybe model intelligence improvement outstrips my feature appetite such that it's fine?) How does collaborative software work in this model? Can software designed this way be secure and reliable?
Whatever the larger questions about broader deployment, it definitely works great in a personal context. It reminds me a little of the visions of Lisp/Lisp machines, Smalltalk, and HyperCard -- systems that the user can take control of and modify. Those visions never quite worked, though: the vast majority of software today is not end-user modifiable in any useful way. So, while this "liquid" affordance is a very small touch, the way it changes one's relation to the software feels a bit transgressive and empowering in a Lickliderian and Engelbartian way.
1
2
159

























