~/reading

17

Issue 17/September 19, 2026/8 tools · 2 headlines

In-process WASM OSes and K8s sandboxes that keep agents off the host

Power users are wiring lightweight isolation layers: WASM and V8 agent operating systems, Kubernetes sandbox CRDs, Rust harnesses, and capability firewalls that drop into custom loops without closed IDEs or heavyweight microVMs.

01 — Power tools

The stack

  1. 01toolGitHub
    wasmagent-js↗

    WasmAgent

    Embedded compliance layer with WASM kernels, MCP firewall, capability manifests, signed AEP rollouts, and trace-to-training export.

    Use caseUse it to wrap tool calls with policy vetting, emit signed evidence records, and feed verified trajectories into DPO or PPO pipelines.

    mcpfirewallcompliancewasm
  2. 02repoGitHub
    wasmsh↗

    Mayflower

    Bash-compatible WASM shell runtime with VFS, Pyodide Python, 88 utilities, and K8s-scalable dispatcher for dense agent sessions.

    Use caseUse it to back Deep Agents or custom loops with an in-process or remote bash-plus-Python sandbox that cannot touch the host.

    wasmbashpyodidelangchain
  3. 03repoGitHub
    Ephemora Cell↗

    MichaelS1011

    Capability-based Wasmtime sandbox for MCP tools and untrusted code with fuel, memory, time, and I/O caps plus signed execution records.

    Use caseUse it to run agent-generated or MCP tool code under hard resource budgets and produce auditable signed results.

    wasmtimemcpcapabilitiesaudit
  4. 04toolGitHub
    AgentOS (Opyt)↗

    NarendraPatwardhan / OpytAI

    WebAssembly VM giving agents a full Unix computer with shell, files, processes, snapshots, host tools, and capability boundaries.

    Use caseUse it to replace bag-of-tools agents with a programmable guest computer that can pipeline shell work and call host-bound tools safely.

    wasmvmposixsnapshots
  5. 05harnessGitHub
    agentos (iii)↗

    iii-experimental / iii-hq

    Self-evolving agent OS of narrow Rust workers registering functions and triggers on a shared engine with wasm and microVM sandboxes.

    Use caseUse it to compose domain workers for reasoning, memory, security, and execution that evolve under governed self-modification.

    rustworkersself-evolvingengine
  6. 06toolGitHub
    tasking-agent↗

    FeynmanZhou

    Web console workbench for Deep Agents Code with pluggable sandboxes (local, Cube MicroVM, Tencent) and normalized event tracing.

    Use caseUse it to drive and audit a headless coding agent through a three-pane UI with session history, artifacts, and sandbox swaps.

    consoledeep-agentscubetracing
  7. 07toolGitHub
    agentbox (julianthome)↗

    julianthome

    Minimal Docker Compose sandbox that launches pi or opencode with Ollama, tmux, and git session branching for reviewable runs.

    Use caseUse it to spin a polished local terminal agent environment that auto-wires host Ollama models and keeps changes on a review branch.

    dockerpiopencodeollama
  8. 08toolGitHub / crates
    Harn↗

    Harn project

    Language and runtime for defining agent tasks, prompts, tools, and rules with enforced permissions and saved work history.

    Use caseUse it to author reusable agent workflows as Harn programs that the runtime executes with sandbox boundaries and session logs.

    languageruntimepermissionsworkflows

02 — In the wild

Articles and releases

  1. releaseGitHub Releases
    agentOS v0.2.20 release↗

    rivet-dev

    Rivet shipped agentOS v0.2.20 with runtime fixes for WASM pipe reads and native sidecar packaging. The release keeps the in-process V8 plus WASM model with optional external sandbox mounts for heavy workloads.

    releasewasmruntime

    Shipped

  2. articleGIGAZINE
    How important is a harness for an AI coding agent?↗

    GIGAZINE

    Coverage of the HarnessTax study comparing seven models across three harnesses on SWE-bench Lite and Terminal-Bench. Success rates stayed close while cost varied up to five times, showing harness choice can dominate spend.

    articlebenchmarkcost

    Read

Get the daily tools digest

RSS