Jan 28, 2026 · 2:35 PM UTC
102
194
2,880
1,404,801
@ryancarson how are you using compound engineering with amp given that it relies heavily on custom agents and amp doesn't have custom agents as far as I know?
1
1
7,909
x.com/acolombiadev/status/20…
This is exactly the kind of setup that made me write about the maintenance problem. You’ve got an agent shipping features every night. AGENTS.md files growing. PRs stacking up.
But here’s the question I keep coming back to: who’s watching the repo health while all this code lands?
Docs drifting from code. Test coverage gaps. Dependencies going stale. CI pipelines getting slower. The stuff that doesn’t break immediately but compounds in the wrong direction.
@GitHub Next built something called Peli’s Agent Factory for this exact gap. Over 100 maintenance workflows: triage agents, CI diagnostics, doc drift detection, security monitors. Agents that maintain what your building agents ship.
4
10
3,363
I don’t think continuing to bloat out agents.md in this way is gonna scale. Am I wrong?
1
4
1,290
@samtemaki this seems interesting, please email it to Gandalf and tell him to consider it and report back to me.
1
163
Hey @ryancarson, thank you for sharing your workflow in Claude Code. Followed your article and set it up successfully on Windows. I successfully ran with clauee the planning parr of your script and it returned a plan in the terminal. But when I try to run the implementation patt in PowerShell I get this error message: EBADF: bad file descriptor error on history.jsonl.lock. How can I fix it? Btw, I'm using my Max subscription and not API calls.
1,700
Passive agents can’t fix flawed logic. Being present > just automating
Followed you, would be awesome if you returned it
@ryancarson
571
Sleeping agents won’t fix broken thinking. Presence > automation.
Just followed you would really appreciate a follow back. @ryancarson
1,017
