So I don’t think issue tracking is actually dead. It's very much alive and well. Bloated, human-era ticketing probably is dead though. Coding agents don't kill the need for structure; they actually demand more of it. The faster the agent, the faster context rots and work sprawls. Scaffolding isn't optional anymore; it's the only thing keeping the wheels on this thing, and why we created fp.dev

Claude sure likes “the gap”.

This Tuesday we hosted our monthly @daytonaio AI Builders Meetup in San Francisco in partnership with @WorkOS & @coderhq. We had an incredible lineup of speakers covering topics from forkable sandboxes for long-running AI agents and self-driving codebases to scaling AI workflows in production, building reliable code review agents, generative UI patterns, and the infrastructure powering agentic software systems. Thanks to our speakers 🎤 @muhashmii × @daytonaio @matt_md5 × @WorkOS Jullian Pepito × @coderhq @HKrackDev × @coderabbitai @tyler_cpk × @CopilotKit @mies × @fiberplane Thank you to everyone who joined us. See you tonight at UC Berkeley for the AI Researchers Meetup!

Turns out codex doesn't care about getting a sandwich.

Otter: an opinionated monorepo template for autonomous agent workflows. Ships with: - @EffectTS_ conventions ast-grep enforcement - fp issue tracking with lifecycle hooks - Drift documentation anchoring - Agent skills pre-configured Everything we learned building with agents in production, packaged as a starter template: 🔗github.com/fiberplane/otter

No Mac Minis were hurt during the creation of this process.

We are happy to announce our monthly @daytonaio AI Builders Meetup in partnership with @WorkOS & @coderhq at the WorkOS SF office on May 5! Join us for insightful talks, practical lessons from production AI systems, and great conversations with an amazing lineup of speakers: 🎤 @muhashmii, @Daytona 🎤 @matt_md5, @WorkOS 🎤 Jullian Pepito, @coderhq 🎤 @HKrackDev, @coderabbitai 🎤 @tyler_cpk, @CopilotKit 🎤 @mies, @fiberplane 📍 Full agenda and RSVP on this link: luma.com/e1d5eql5

Introducing <snappy-cli-name> One command to stop <mild-painpoint> npx <snappy-cli-name> init npx skills add @<weird-org-name>/<snappy-cli-name> <mermaid-diagram-or-fancy-gradient/> *2k likes | 270 retweets | 9million bookmarks*

drift is cool, check it out

Big Things have Small Beginnings.

We're sooo back

We've been building with @Claude Code at @fiberplane since early days. Biggest takeaway: agents don't get better because you prompt them better. They get better when the codebase is explicit enough to constrain them. @EffectTS_ for typed errors dependencies. Team favorite ast-grep to enforce patterns at commit time. Our own Drift to catch stale docs. We wrote up our entire setup, learnings and shares our rules here: fiberplane.com/blog/2026-04-…

AI agents don’t get better when you prompt them better. They get better when the codebase is explicit enough to constrain them. Learn how we build with Claude Code at Fiberplane - @EffectTS_ , ast-grep, Drift. Read more on our blog in the comments section.