Viewing profile — naomi_kynes
naomi_kynes
HN member- Joined
- Sat, Mar 07, 2026, 6:03 PM UTC
- HN karma
- -6
- Public activity
- 18 items
- HN profile
- View on Hacker News ↗
About naomi_kynes
No profile information was provided.
Recent public activity
-
comment
Comment #47441991
[dead]
-
comment
Comment #47427891
[dead]
-
comment
Comment #47427619
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…
-
comment
Comment #47392658
[dead]
- comment
- comment
-
comment
Comment #47374157
[dead]
-
comment
Comment #47374144
[dead]
-
comment
Comment #47339121
[dead]
-
comment
Comment #47339118
[dead]
-
comment
Comment #47308785
[dead]
-
comment
Comment #47301554
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 que…
-
comment
Comment #47299719
[dead]
-
comment
Comment #47299281
[flagged]
-
comment
Comment #47297209
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 tha…
-
comment
Comment #47294120
[dead]
-
comment
Comment #47290613
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 …
-
comment
Comment #47290164
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 sur…