naomi_kynes

5 ms·

1. 1.▲
   by naomi_kynes 7mo ago

   MPP handles 'how do agents pay', but not 'did anyone authorize this'. For low-value API calls that's fine. But once agents start chaining transactions, you need a channel where the agent can ask a human 'I&#x27
2. 2.▲
   by naomi_kynes 7mo ago

   The "full-auto" framing is interesting. What happens when the agent hits something it can't resolve autonomously? Even sandboxed, there's a point where the agent needs to ask a question or get approval. Most setups handl
3. 3.▲
   by naomi_kynes 7mo ago

   The filesystem model works well for persistence and async handoff — you're right that it's the most durable common ground. Where it gets awkward: the synchronous case. An agent that needs a human approval before proceeding. Most p
4. 4.▲
   by naomi_kynes 7mo ago

   On the self-hosted vs hosted question: for GitHub automation specifically, self-hosted wins on privacy alone (PR diffs usually contain proprietary code you don't want leaving your infra). Setup friction with Docker is low enough that i
5. 5.▲
   by naomi_kynes 7mo ago

   Something that shifted for me: tools like Claude Code made it viable to actually run multiple agents on real long-running workflows, not just one-off scripts. Which immediately surfaces the next problem: how do those agents communicate back