rivet-dev/agentos

Give agents an operating system as a library. Runs in your existing backend – no sandboxes, VMs, or SaaS. Powered by WebAssembly & V8 isolates.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 15 minutes ago
Added to GitGenius on September 14th, 2026
Created on February 7th, 2024
Open Issues & Pull Requests: 153 (+0)
GitHub issues: Enabled
Number of forks: 251
Total Stargazers: 4,626 (+0)
Total Subscribers: 12 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.7 days
Mean response time: 19.6 days
90th percentile: 56.4 days
Tracked items: 25

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 60% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. 16% of tracked open issues have had no activity in three months. Only 10% of issues opened in the past year have been closed. Three people close 93% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 63
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 64 days
Stale 30+ days: 51
Stale 90+ days: 10

Recent activity

Opened in 7 days: 1
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Detailed Description

agentOS is a library that gives agents an operating system runtime embedded directly in your backend process, powered by WebAssembly and V8 isolates.

The tool solves the problem of running untrusted agent code safely without the overhead of sandboxes, containers, or microVMs. It achieves this by executing guest JavaScript in V8 isolates and compiled tools as WebAssembly, all within a single compact runtime that lives inside your application process. Agents can call your backend functions directly through bindings, keeping credentials on the host while exposing only inputs and outputs. Security is enforced through granular permissions that gate filesystem, network, process, and environment access, with outbound capabilities denied by default.

Adoption makes sense for teams building agent-powered applications that need low latency and minimal resource overhead. The tool suits backends where agents need tight integration with your existing functions rather than operating as separate services. It works best when you want to avoid the complexity of managing sandboxes or containers. The README distinguishes agentOS from traditional sandboxes by noting that sandboxes provide full Linux environments suitable for browsers, native binaries, and dev servers, whereas agentOS is a lightweight VM optimized for agent integration. The tool can work alongside sandboxes through sandbox mounting, spinning up a full sandbox on demand when a workload requires it. Deployment is straightforward—it ships as an npm package that runs locally during development and deploys to managed infrastructure or self-hosted environments.

The project maintains active engagement with its community through a public Discord channel. Development appears focused on stabilizing the API, as the README explicitly notes the tool is in preview with an API subject to change. The codebase includes built-in support for multiple agent implementations and ships with common POSIX utilities out of the box, suggesting a mature approach to practical usability.