You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Star4 (4)You must be signed in to star a repository
About
Curated infrastructure resources for building production AI agents: runtimes, sandboxes, workspaces, tool protocols, security, observability, and evaluation.
A curated collection of infrastructure resources for building production AI agents: runtimes, workspaces, sandboxes, tool protocols, context systems, security, observability, and evaluation.
Last reviewed: 2026-07
This list focuses on the systems layer below agent products and above foundation models.
It is not a general "awesome AI agents" list. It is focused on the infrastructure needed to run agents safely and reliably in production.
Organized around one question, asked of every component: what state is this, and where does it belong?
Common validation stage for agent-produced changes.
Sandbox and Execution
The useful first question is not "which provider?", but "what boundary protects the host?". Agent sandboxes also need a state model, because long-running agents often need files, snapshots, or branches to survive beyond one process.
Isolation model
Boundary
Typical fit
Process policy sandbox
Host process plus OS policy
Local tools or helper processes with filesystem and network limits.
Shared-kernel container
Namespaces, cgroups, capabilities, seccomp
Dense Linux workloads where compatibility matters more than kernel separation.
Userspace-kernel container
Container API with syscall mediation
Stronger isolation than ordinary containers while preserving OCI-style workflows.
Language or WebAssembly runtime
Engine-level isolate or capability grants
Controlled plugins, edge functions, and short-lived extension code.
MicroVM
Separate guest kernel per workload
Untrusted Linux code, generated code, package installs, and agent execution.
VM-backed container runtime
Container UX backed by lightweight VMs
Kubernetes or OCI workflows that need a stronger tenant boundary.
Full VM or enclave
Hypervisor VM or confidential-computing TEE
Broad OS compatibility or highly sensitive secret-handling paths.
State model
What persists or branches
Why it matters for agents
Ephemeral runtime
Nothing durable by default
Good for one-shot code execution and tests.
Durable volume
Files survive sandbox stop/start
Useful for package caches, generated artifacts, and long tasks.
Filesystem snapshot
Filesystem state can be cloned or restored
Enables branch-mutate-evaluate workflows without rebuilding environments.
Memory/process snapshot
Running state can resume from a checkpoint
Useful for fast warm starts and long-lived interactive sessions.
Branchable backing services
Databases or object state can fork cheaply
Keeps agent experiments isolated beyond the filesystem.
Gives a broad sandbox taxonomy and measurement framework for fidelity, controllability, observability, containment, reproducibility, and governance artifacts.
Large-scale empirical study of real coding-agent PRs.
Observability Checklist
A production agent run should record:
Run ID
Workspace ID
Model and harness
Tool calls
File changes
Command execution
Cost and latency
Policy decisions
Publish attempts
External references such as PR URLs
Error and retry history
Final outcome
Harness Self-Improvement
Self-improving harnesses use execution evidence to propose, evaluate, and
promote changes to prompts, skills, tools, memory, settings, or other harness
surfaces without changing model weights.
Structured LLM programs with optimizers; useful reference for eval-driven prompt and module compilation.
Checklist
If an agent can propose changes to its own harness, the improvement loop needs
production controls, not just a prompt-optimization script:
Keep raw traces, normalized events, verifier evidence, candidate patches,
comparisons, approvals, promotions, and rollbacks linked by stable IDs.
Version harness configuration and eval suites immutably, with content hashes
at every comparison and promotion boundary.
Run each eval attempt in a fresh workspace with deterministic verifiers,
explicit wall-clock, turn, cost, and latency budgets, and idempotent recovery.
Classify failures from recorded evidence, with event IDs and lower confidence
for partial traces or ambiguous patterns.
Restrict candidates to explicit editable surfaces, and fail closed on path
traversal, escaping symlinks, stale base hashes, protected policy/eval files,
hidden state, oversized content, or executable changes.
Separate candidate configuration deltas from agent task output deltas, so
baseline and candidate runs remain comparable.
Compare baseline and candidate by task and repetition, with held-in and
held-out sets frozen before evaluation and hidden from proposal context.
Treat protected-surface violations, held-out regressions, missing required
metrics, incomplete traces, cost increases, latency regressions, and
non-activation as hard gates when configured.
Promote accepted candidates through the normal workspace, approval, and
publish lifecycle; record the actor, patch, previous version, promoted
version, and rollback path.
Implement rollback as an isolated reverse promotion that detects file
divergence instead of overwriting user changes.
Keep optional extension telemetry authenticated, bounded, idempotent, and
non-blocking so observability failures do not break productive runs.
Useful view into mainstream coding-agent workflows.
Data Layer and Storage
Agent infrastructure usually combines several storage concerns: control-plane records, conversation and run history, workspace state, artifacts, memory, and observability data. This section focuses on reusable storage ideas rather than generic application frameworks.
Note: no purpose-built session-store engine exists yet. The session log's contract - idempotent append, read-your-own-tail at low latency, per-session ordered replay, and fork - fits neither OLTP nor plain append logs. Pointers welcome.
Control-Plane Metadata
Agent definitions, identity, permissions, config, source references, and low-volume control-plane state usually fit normal OLTP systems well.
Practical primitive for workspace locks, publish locks, and idempotent control-plane operations.
Conversation and Run History
Agent runs are easiest to debug and replay when prompts, model calls, tool calls, decisions, file changes, and checkpoints are recorded as ordered history. Some frameworks implement replay and branching at the framework layer; storage choices need to preserve the semantics those features depend on.
Product example where branching a conversation/session is exposed as a native workflow.
Workspace and Artifact State
Coding agents and computer-use agents often need durable files, snapshots, forked workspaces, generated artifacts, and discardable candidate output. This is where storage design meets sandbox lifecycle.
S3-compatible object storage reference for artifacts, logs, and workspace-adjacent binary state.
Memory
Long-running agents may need memory beyond a single run. The important infrastructure questions are provenance, branching, compaction, retention, and whether memory is editable or only append-derived.
Shows why analytics-shaped engines can fail the session-store contract: async insert defers visibility and deduplication happens later, the opposite of read-your-writes.
Contributions are welcome. Please read CONTRIBUTING.md before opening a pull request.
A resource belongs here if it helps answer at least one of these questions:
How should an agent runtime manage state?
How should tools be exposed safely?
How should workspace changes be isolated and published?
How should sandboxes execute untrusted or semi-trusted actions?
How should agent runs be traced, evaluated, and replayed?
How should secrets, permissions, and policy be enforced?
How should coding agents integrate with repos, issues, PRs, and CI?
A resource does not belong here if it is only:
A generic prompt engineering article
An end-user chatbot product
A generic AI app directory
A model leaderboard with no infrastructure implications
A shallow tutorial with no reusable systems insight
About
Curated infrastructure resources for building production AI agents: runtimes, sandboxes, workspaces, tool protocols, security, observability, and evaluation.