🤖 This AI assistant went viral on GitHub

Run your own Clawdbot, plus what devs are arguing about in the issues

Hey there.

Welcome to Full Stack Focus. 👋 

Here’s everything you need to know this week in the world of full-stack development.

Programming

🤖 On Programming with Agents
A thoughtful essay from the Zed team on how to work effectively with AI agents without losing engineering rigor. It lays out three practical rules, only use agents for things you already understand, stay actively involved, and review everything, with concrete examples from real development workflows. The core argument is refreshing and grounded, agents automate typing, not thinking, and good software still depends on human judgment, taste, and responsibility.

🤯 Your own personal AI assistant. Any OS. Any Platform.
This GitHub repo for Clawdbot has gone viral in the last few days, it’s a “run it yourself” personal AI assistant that can plug into WhatsApp/Telegram/Slack/Discord/Signal/iMessage (and more) and act like a local, always-on helper across your existing chat apps. It looks genuinely useful if you want an assistant you control on your own devices, with a big feature set (voice, web chat, canvas, skills, routing). That said, there’s also a lot of active chatter in the repo right now, plenty of GitHub issues being debated, plus ongoing discussion around security vulnerabilities / hardening, which is worth skimming before you try deploying it.

↗️ Scaling PostgreSQL to power 800 million ChatGPT users
OpenAI shares a detailed look at how they scaled PostgreSQL to support ~800 million ChatGPT users, handling millions of queries per second on a largely single-primary, read-heavy architecture. The post walks through real production issues, write amplification, cache miss storms, connection limits, and replica lag, and the pragmatic engineering tradeoffs used to survive them. It’s a rare, concrete account of what actually breaks at extreme scale, and how far careful tuning can push “boring” infrastructure like Postgres before sharding becomes unavoidable.

✨ Why $10/Month Apps Are Turning Into Weekend Builds
A fun, personal take on how AI “vibecoding” turns $10–$15/month apps into weekend projects. The author describes replacing tools like dictation, screen recording, and markdown editors with quick, custom-built alternatives that do exactly what he wants — no more, no less. It’s not about shipping products, but about apps on demand for yourself, and why many small SaaS tools may be drifting toward features, not businesses, in an AI-assisted world.

Front-End

👐 Build agents with a modern TypeScript stack
Mastra is an open-source TypeScript framework for building AI agents and agent-powered apps. It positions itself as an end-to-end stack, agents, workflows, RAG, memory, evals, observability, and deployment, aimed at taking ideas from local dev to production. If you’re building agents seriously, it looks polished and developer-friendly, though it’s very much an opinionated “agents as infrastructure” approach rather than a lightweight library.

🌍️ Chrome introduces the <geolocation> HTML element
Chrome is introducing a new <geolocation> HTML element (shipping in Chrome 144) that changes how websites request a user’s location. Instead of triggering permission prompts via JavaScript, this approach makes location access explicitly user-initiated, reduces boilerplate code, and improves success rates by avoiding quiet blocks and accidental denials. It’s a meaningful shift toward declarative, capability-specific browser controls, with early data showing better user trust and smoother recovery when permissions were previously blocked.

🗣️ Building a Hybrid AI Chatbot with Next.js 16
This is a conference talk by Sam Selikoff (Vercel) on building a hybrid AI chatbot with Next.js 16, presented at React Summit US 2025. It walks through how partial prerendering and cache components let you combine static speed with fully dynamic, personalized data, a big shift from the old static vs server-rendered split. If you’re building AI features in Next.js, it’s a clear, practical look at how the new rendering model actually works in a real app, not just in theory.

🫵 React has changed, your Hooks should too
This short piece argues that React Hooks need to evolve now that we’re in the React 18+ / concurrent React era. It breaks down why overusing useEffect causes fragile components, and shows modern patterns built around derived state, custom hooks, concurrency tools, and subscription APIs like useSyncExternalStore. If you’ve been writing Hooks the same way since 2020, this is a clear, practical reset on how React actually wants you to structure logic today.

AI​

More Tools & Stories

Have a great week, see you the same time next week!

- Full Stack Focus team :)