Tweet by FredKSchott

May 18, 2026

hitting this interesting cross-roads with flue: 1) repo automation, workflows 2) hosted agents as the framework matures, the differences between them are becoming more obvious and more frustrating to design around (and by extension, for users). for example: in astro, it was a specific design goal that our repo automation and human maintainers would reuse 90% of the same content. Shared skills, tools, configuration, etc. etc. running "flue run triage" in a GitHub Action should be as close to a core maintainer opening up claude code in the repo and asking "triage this issue: URL" but if you're building and deploying a hosted agent, you want your skills and tools and subagents to live alongside the agent code, not the sandbox file-system. splitting your agent logic across "this logic (agent code, tools) lives in the codebase" vs. "this logic (skills, roles) lives in the sandbox" is a maintenance nightmare. i'm not sure what the answer is, but I see projects like Sandcastle by @mattpocockuk laser-focused on repo automation. I trust Matt to build something great here that will be hard for us to compete with. We are trying to do too much for too many people. meanwhile, I'm now talking with so many devs building agents (not just oss devs with oss repos) and there is no one doing what flue is doing today. A part of me really just wants to explore and optimize for this, and build the best framework for agents. idk, talking out loud a bit. will spend more time exploring this this week. curious if anyone who's tried flue (or considered it) has thoughts!

Author
FredKSchott
Date
May 18, 2026
Open on X