OpenComputer

The word doing the work here is 'managed' — most agent deploys are fine until the agent needs to survive a restart mid-task. What happens to a half-finished job when you redeploy? Does state persist across versions, or is the model that agents should be stateless and anything durable lives outside them?

Durable sessions as the primitive is the right call. The thing teams tend to discover late is that agent state is its own scaling axis, separate from compute, and once it lives outside the process you get retry and resume for free instead of rebuilding them per agent.One question on the managed side: when a session resumes after a long gap, does the agent get the full prior context back or a compacted version? That choice is usually where behavior quietly drifts between a short run and a long one.

Congrats on launching! I have wanted to spin up little agents for small tasks so many times but the setup always killed my motivation before I even started. This looks like it removes exactly that pain. Can two people share the same agent URL and use it together, or is each one tied to a single user?

Paste one prompt, get a live agent URL is a strong pitch. Someone in the comments said you win by deleting setup steps and honestly that matches my experience with most agent platforms being 90 percent config. What happens when an agent session crashes mid task, does the durable sessions API resume from where it stopped?

The paste-to-live-URL flow is exactly the kind of friction reduction that gets developer adoption. The first thing I would test is credential handling: when an agent needs to call an external API, is there a secrets vault per agent where I can store keys separately from the prompt, or does the prompt itself have to carry them? And can the deployed agent expose an inbound webhook endpoint, so external services like Slack or Discord can push events to it — that is what would make this useful for community tooling rather than just scheduled tasks.

Congrats on the launch. Durable sessions is the right primitive to build this on.Adding to the drift point above: what makes a long running agent debuggable is not the sandbox, it is whether each action is replayable after the fact. When something goes wrong on day five you need to answer what the agent believed at that moment and which inputs it saw, not just what it did.That means the session log has to capture the inputs to each decision, not only the tool calls. Tool call history tells you the agent moved the file. It does not tell you why it thought it should.Is the session state inspectable and exportable, or does it stay internal to the platform?

Congrats on the launch. Paste one prompt, get a live agent URL is what got me, that's a genuinely fast path from idea to something live. Curious about that URL itself: does holding the link give you access on its own, or is there a separate auth/token layer in front of it once it's live?

Seems interesting. Looks like the main use case is development but I could see this being useful for trading agents in the future.

The "beyond sandboxes, always on" combination is the interesting bet, and the risky one. Omri's got the security half, so here's the other one.A sandbox was quietly doing two jobs. It contained blast radius, and it gave you a free reset. A durable, always-on agent keeps the first problem and loses the second entirely. The failure I'd watch isn't compromise, it's drift: a long-running agent's picture of the world goes stale and it keeps acting confidently against it. On day one it's right. By day five the thing it "knows" and the thing that's true have quietly diverged, and now every action is real, with no sandbox to throw away.So two questions for a permanent background agent. What does a human see between actions, is there anything that surfaces "still on track" versus just "still running"? And when it does the wrong thing, not malicious, just wrong, what's the undo?The deploy story is genuinely clean. It's the day-five story I'd want to see.

the "durable, always-on" part is the interesting bit to me, more than the deploy step itself. if an agent gets stuck in a loop or just keeps working longer than expected, is there a cost ceiling or a way to pause/kill it from outside the session, or do you find out when the bill shows up?

this is neat. does the agent's URL stay persistent if you update the underlying prompt?

ngl im seeing more and more products win just by deleting setup steps instead of adding features. this kinda fits that pattern.

"managed agent" is doing a lot of work in that tagline - managed by who, exactly? if this is hosting the compute and credentials for an agent that can act on my behalf, what's the blast radius if OpenComputer's own infra gets compromised - does the agent run with scoped, revocable tokens per task, or does it hold onto broad standing access to whatever it's connected to?

Hi PH - today we're launching Agent Deploy, by OpenComputer. It is the easiest way to deploy a fully managed background agent.

It runs on top of our durable agent sessions API, which makes building agents as simple as an API call.

Give it a shot and let us know what you think?