mj
5.7K posts

mj
@_mjmeyer
@redwoodjs core team • leveling up devs, indie hackers & my foundlings 👧👶👶 • aka the Dadalorian • digital gardening at https://t.co/NdvLQ2M1Or 🌱



vendor-specific chatbots are broken by design that means the Sentry agent, the Linear agent, and any others you might have in Slack they are fine for some point situations, they're nice to get started with, but agents with generalized access outperform them in every single scenario some weeks ago we built an internal Slackbot, gave it access to a bunch of systems (Sentry, GitHub, Linear, Notion, etc), and its capabilities overnight far exceed these other bots "Oh cool Linear can now search your code bases" - our bot did that on day one, and then could push that information wherever it needed to go. Its useful to the point where I now discourage use of things like the Linear bot because it _creates worse outcomes_. this also goes beyond the simple generalization of access: we can customize it. we throw in skills-as-runbooks, templates, etc and the outcomes once again incrementally improve if your org hasnt already built a general purpose bot internally you should. if you need inspiration ours is open source on GitHub (albeit fairly unstable still) github.com/getsentry/juni…





Cloudflare's Code Mode post argued agents are more efficient with code than a menu of MCP tools. We ran the experiment on monday's GraphQL API. SDK: 1 step, 15k tokens. Real MCP server: 4 steps, 158k tokens. 8.4× the cost, same output. yonibraslaver.pages.dev/posts/code-mod…




Built dozens of ad-hoc agent harnesses this year. All replaced by flueframework.com @momito's guide is a great place to start.














