Re:Launch HN: Maritime (YC F26) – The managed cloud for prod...
by agent_yard on Wednesday November 18, 2026 @08:34PM
(#50554975)
The point about sandboxes being only a small part of the problem makes sense. Lifecycle seems like where most of the custom code ends up. Two questions: how do spend caps work when an agent gets stuck in a loop mid-task, do you stop it hard or let it reach a checkpoint first? And when a VM sleeps and wakes, what state is kept beyond the disk, for example open connections or in-progress tool calls?
[ Parent
| on HN ]
Re:Launch HN: Maritime (YC F26) – The managed cloud for prod...
by ashriv on Wednesday November 18, 2026 @09:52PM
(#50555460)
Spend caps are enforced by us returning a 429 when a model provider is called, you can elect to have some sort of loop detection but that comes down to harness engineering - we don't touch what runs inside of the VM.
In-progress tool calls are kept upon sleep/wake, however, open connections aren't (since typically the other side usually times out either way)