Sim, OpenGeni and smolvm address different parts of AI-agent development: building workflows, keeping a session recoverable when a person must approve an action, and running code in a virtual machine. Their latest releases range from URL-handling safeguards to a change in how a restored machine wakes.
All three repositories list Apache-2.0 licenses for their code. That license does not replace terms for a separate hosted service, model provider or guest software.
Build and monitor workflows with Sim
Sim is a self-hostable workspace for assembling agents visually, conversationally or in code, then deploying them and following run logs, schedules and workflow activity. Its README lists integrations including Slack, Notion, HubSpot, Salesforce and databases.
Version v0.9.13, published October 4, rejects tool URLs with . or .. path segments, including encoded forms, which could send a request to a different endpoint. It also checks a workspace’s usage limit before running a tool that uses a Sim-hosted API key. The self-hosting wizard requires Node.js 20 or later, Docker and a Chat API key; it provisions a database, generates secrets and starts Sim's published images.
Pause a session for human approval with OpenGeni
OpenGeni stores session events in Postgres so a client can replay the history after a reload. For a risky tool call, a person can respond to an approval request and the same call can resume.
The agent-v0.1.47 release on October 4 provides cross-platform binaries with minisign signatures and SHA-256 checksums; its instructions say to verify the signature against a pinned key. The release notes say native macOS and Windows code-signing still requires separate developer credentials. Running the local development stack also requires the exact Bun version in .bun-version, Git, curl, Docker, rustup, a C compiler and an OpenAI or Azure OpenAI key.
The simplest local option runs the agent server directly on the host, where it can access the host filesystem. The README offers a Docker sandbox as a separate option when isolation is needed.
Branch a run inside a microVM with smolvm
smolvm runs each workload in a hardware-virtualized machine with its own guest kernel. A checkpoint saves memory, CPU state and disks; a copy-on-write branch lets a developer try another run from the saved machine state. Version v1.23.2, released October 5, fixes a restore edge case: when exec or a file request wakes a just-restored machine, the runtime now finishes the checkpoint restore without starting a second copy of the workload.
Networking is off by default, and outbound access can be limited to named hosts. The project says safety remains a shared responsibility: mounted folders, open ports, allowed hosts and forwarded credentials determine what crosses the VM boundary. Windows requires Windows Hypervisor Platform, and GPU acceleration is unavailable on Windows.
Sources
- Sim README at commit 36f060b, its Apache-2.0 license and the v0.9.13 release.
- OpenGeni README at commit eeb73ee, its Apache-2.0 license and the agent-v0.1.47 release.
- smolvm README at commit 9770301, its Apache-2.0 license and the v1.23.2 release.
- Illustrative cover image: Data center roof with cooling towers and backup generators, by Rsparks3, CC0 1.0.
