OmO 5.1.33 Keeps Daemon-Hosted Agents Running After You Exit

Background work can outlive its parent session

OmO 5.1.33 says daemon-hosted background agents now keep running when their parent exits or starts a new session. The parent detaches without aborting their turns, according to the October 13 release notes. That makes the practical change about continuing delegated work, rather than launching another model or adding a new chat interface.

The scope matters: this behavior is for daemon-hosted tasks. Local in-process and stdio children retain their existing shutdown behavior. On exit or /new, OmO displays the old session and an omo --resume command for collecting results; children remain owned by that session. Session detachment is not a promise that work survives a daemon shutdown or computer restart.

What OmO is, and what changed this week

OmO’s tagged English README describes a standalone omo application running on senpi, the maintainer’s fork of Pi. Its multi-agent workflows, memory and bundled skills are existing product context, not features first introduced by 5.1.33. The older OpenCode plugin edition and this standalone application are different installation targets.

This release also says unresponsive process children receive heartbeat checks and RPC deadlines rather than hanging a task indefinitely. Three missed ten-second probes mark a running child as unresponsive, preserve its transcript and expose inspection and rerun guidance. Resuming a finished task with a full concurrency group now queues the follow-up instead of blocking the call, the notes say.

DeepSeek is the provider, not the harness

The bundled senpi update fixes a reported DeepSeek API failure where a tool schema’s root type was null. The release says schemas now declare a root object type for DeepSeek’s official API and gateways forwarding to it. This is an interoperability fix inside the agent stack, not a new DeepSeek model or a claim that every provider configuration has been tested.

Installation, credentials and limits

For the npm route, the package is omo-ai: npm install -g omo-ai@5.1.33, followed by omo. The package requires Node 24 or newer. The README also provides native binary installation instructions, including Windows. Do not substitute the unrelated npm package named omo.

For existing OpenCode users, the migration guide says omo setup can import API keys, custom providers, MCP definitions and skills after confirmation. OAuth logins must be performed again. Tool permissions and plugin hooks are not transferred, so users should review execution settings rather than assume the old host’s controls carried over. The cited sources do not establish a universal model-usage price; provider access and terms remain separate.

OmO’s source is covered by a Sustainable Use License, not an unrestricted permissive license. Its terms allow internal business purposes and non-commercial or personal use, with distribution restricted to free, non-commercial purposes. AITrending checked the English release, tagged documentation and package metadata, but has not independently exercised these runtime changes across operating systems or providers.