Micha "mies" Hernandez van Leuffen

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

@lucasmeijer @f_ili_p_ziva @fiberplane Thanks for the shoutout: fp.dev is indeed issues as MD, local first, sync optional

@f_ili_p_ziva I don't know, but I'm going to try to put them one layer higher: in the orchestration / task management layer. the @fiberplane guys are doing some interesting work in this space

I'm slowly migrating from "its a good idea to have lots of .md files for plans/bugs/tasks in the repo" to "yeah lets not do that at all".

Check out our reference implementation called 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 Open Source repo here: github.com/fiberplane/ott…

Shoutout to @daytonaio for organizing and @WorkOS for hosting a great night where builders gathered and of course giving us the opportunity to talk about how we're thinking about Autonomous Software Factories @fiberplane. Excellent conversations and new friends were made!

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/ott…

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

@RhysSullivan Biased but check out fp.dev A CLI that agents like, brainstorms and issues as markdown, sync optional

Where I’d love to see linear pivot to is helping me break down huge tasks / engineering efforts into manageable chunks Make a great chat at that with a good interface, let me pull in tons of reference repos & do deep research Leverage their huge dataset of completed projects

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 One command to stop npx init npx skills add @/ *2k likes | 270 retweets | 9million bookmarks*

drift is cool, check it out

The overview is flagged because the anchored section drifted; not because someone fixed a typo in auth.md's unrelated "Rate Limits" section. The anchor is section-precise. Drift is open source: github.com/fiberplane/dri…

My favorite new drift feature is anchoring markdown to markdown. So say you have a high-level docs/api-overview.md that tells developers "see the Authentication section for details." You don't want to duplicate the auth flow, but you do want to know when the auth docs change so you can update the overview.

Turns out the dark software factory runs on markdown. CLAUDE.md, specs, plans, REFACTOR-V2-BRAINSTORM.md. Agents read them as context and write more of them as output. When those docs drift from code, agents propagate the rot. Drift is the integrity layer.

@mitryc0 Linear is great for coordinating people. We’re building for a different loop: not team handoff tracking, but agent execution inside the repo. If the work is happening in Claude Code/Codex and the repo, the issue tracker should live there too.

@mies why not just use linear?

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

@omererdgan us!

@mies who is the designer of this beauty ?

Big Things have Small Beginnings.

@MattEvantic @alanchanguk Agreed and check out @harveyhodd and Rivan.com

As an immigrant, I am struggling to understand why there is so much focus on sovereign AI and not on sovereign energy. Energy independence and cheaper energy would benefit all of UK and Europe. This would have a far greater impact than any sovereign AI funds. @alanchanguk

We're sooo back

Issues and brainstorms as markdown. Local first, sync optional. Our bet is simple: in an agent-native workflow, the issue stops being paperwork and actually becomes the control plane. Plan the work. Bound the task. Keep the memory. Check out fp.dev