Open Source Agent Frameworks
As of August 2026, AIDiveForge tracks 78 open source agent frameworks. The top three by verified-data score are Open-Kritt, Emem, and Genesys. Curated open source agent frameworks tracked by AIDiveForge. Each project has a verified public source repository. Listings are verified against each tool's live website and re-checked regularly.
Last updated July 29, 2026 · 78 tools
Ranked by AIDiveForge's verified-data score: data completeness, verification recency, community rating, and real visitor engagement. How we rank · No tool can pay for placement.
1. Open-Kritt
The tool runs parallel AI agents across a codebase, so vulnerability discovery that would serialize into hours on a single-context scan distributes across concurrent analysis threads. It targets security researchers and bug bounty teams who need to sweep repositories at scale, not review a function at a time. Self-hosting is supported under AGPL-3.0, which means your code and findings never leave your infrastructure — a requirement for any org with compliance constraints. The open-source core is inspectable and forkable, but managed scans are a paid-only feature, so teams that want the hosted workflow face a significant spend threshold. The page describes GitHub integration as a first-class path, making it a practical fit for teams already running security workflows inside existing CI infrastructure.
PaidOpen SourceSelf-hostedVerified Jul 21, 2026
2. Emem
emem stores facts as short, signed tokens — each one a content-addressed handle that any agent can carry through a summarization pass, hand to another agent on a different model or vendor, and resolve back to the exact signed bytes without trusting whoever sent them. The verify step is offline: recompute the hash and ed25519 signature yourself, no server call required. Cold resolution runs around 180 ms; warm cache hits around 10 ms, with every receipt reporting its own latency stats. The honest caveat from the vendor's own benchmarks: against a bare inline number, a single emem token costs 5.8x more context — the savings only appear when you bundle multiple facts into one round trip.
PaidOpen SourceAPIVerified Jul 23, 2026
3. Genesys
Genesys stores what you share in a causal graph you own, then surfaces that context to any app that speaks MCP — so Claude already knows what you told ChatGPT, without you repeating yourself. The graph explains its own reasoning: ask why it remembers something and you get the actual chain of connections, not a confidence score with nothing behind it. Memories fade by a scoring formula tied to relevance and reactivation, so stale data drops out without silently deleting things that still matter. The free tier caps writes at 300 stores per month — heavy users or teams running MCP agents hit that ceiling, then face a choice.
PaidOpen Source$0-$8/moAPISelf-hostedVerified Jul 22, 2026
4. Jaybase
Jaybase stores every agent-generated fact as an immutable, time-stamped record, which means the full sequence of what an agent wrote, when, and why is always recoverable. The vendor describes it as designed for accounting, compliance, and approval workflows where you cannot afford to lose the paper trail. Because it is append-only, there is no overwrite risk — replaying a sequence from any point is a native operation. The library is self-hostable and open-source under AGPL, so it runs inside your own infrastructure without a call home. The project has a small contributor footprint, which means production teams should expect to own gaps in documentation rather than wait for the maintainer to fill them.
FreeOpen SourceAPISelf-hostedVerified Jul 23, 2026
5. Shepherd
SHEPHERD is a Python substrate from Stanford and Northeastern that turns an agent's execution into a Git-like, reversible trace — so a supervising meta-agent can observe, intercept, fork, and revert any step without rebuilding that capability from scratch each time. The vendor-published benchmark numbers are specific: a supervisor meta-agent lifted pair-coding pass rate from 28.8% to 54.7% on CooperBench; a counterfactual repair meta-agent beat MetaHarness on Terminal-Bench 2.0 by 12.8% while cutting wall-clock time by 58%. The framework is research-grade and open-source, installed via pip. Teams outside the specific use cases the paper targets — runtime intervention, counterfactual optimization, and agentic RL training — will find precious little guidance on how far the substrate stretches.
FreeOpen SourceSelf-hostedVerified Jul 13, 2026
6. firstmate
firstmate puts a single orchestrating agent — the 'first mate' — in front of you, while it spawns a crew of autonomous coding agents behind the scenes, each isolated in its own git worktree. You describe what needs doing; the crew splits the work in parallel and keeps collisions out of your main branch. The visible session backend means you can watch what each agent is doing without switching tabs. The architecture works cleanly for investigation tasks, parallel fixes, or supervised PR generation — the constraint is that there is no API surface, so anything requiring programmatic integration into an existing CI pipeline has to wire around the tool manually.
FreeOpen SourceSelf-hostedVerified Jul 14, 2026
7. AIfunc
The tool treats AI calls the way you already treat HTTP requests: stateless, typed, testable, and wired into your existing code with standard language control flow. No canvas, no orchestration runtime, no new mental model. The vendor states the target is the 80% of real-world AI work that is text-in, structured-data-out — sentiment analysis, summarization, classification. Multi-step workflows are composed with the same if-else and loops you already write. Where this breaks: anything requiring memory across turns, autonomous planning, or tool-use loops is outside the design scope entirely.
FreeOpen SourceAPISelf-hostedVerified Jul 9, 2026
8. Bike4Mind
The workbench routes across 60+ models from OpenAI, Anthropic, Google, and AWS Bedrock through a single interface and API, with a separate lane for open-weight models running on your own hardware via vLLM — the lane no lab can ever sell you or switch off. Sessions, prompts, and artifacts survive mid-conversation model swaps, so when a provider gates its best tier, the switch is a config change, not a rebuild. The agentic layer runs 'Quests' — long-running jobs with a code REPL, search, and MCP access under hard budget caps, so you fire a task and return to results rather than babysitting each step. Where the tool shows its edges: the source-available BSL 1.1 license means self-hosted deployments carry restrictions until the two-year Apache rollover, and teams that need branching multi-agent pipelines beyond single-Quest logic will hit the canvas ceiling fast.
PaidOpen SourceAPISelf-hostedVerified Jul 8, 2026
9. ClawLite
ClawLite extracts the reliability patterns from OpenClaw and strips the rest to roughly 500 lines of logic. You get lane-based serial execution so tool calls don't interleave, automatic context compaction at 80% capacity so small models don't hit the wall mid-task, and provider fallback so a dropped Ollama instance doesn't kill a pipeline. Skill behavior is configured via markdown files, not code. The ceiling appears fast: there is no API, no web UI, no parallel execution path you can opt into for tasks that actually need it, and the project sits at v0.1.0 — which means the surface area is deliberately small and the community footprint is thin.
FreeOpen SourceSelf-hostedVerified Jul 24, 2026
10. Cognee
The core workflow is three lines: install via pip, point Cognee at a data source, and your agents start recalling cited facts instead of hallucinating from scratch each session. Graph-structured memory means relationships between entities survive retrieval — not just keyword matches. First-party integrations cover Claude Code, Cursor, LangGraph, and an MCP server, so compatible agents read and write memory without custom glue code. The ceiling appears when your ontology needs get specific: custom data models and permissions controls are available, but tuning graph structure for a niche domain requires real configuration work. Teams that need a drop-in vector store with zero graph overhead typically reach for a simpler solution.
PaidOpen SourceAPISelf-hostedVerified Jul 13, 2026
11. Cruxible
Cruxible treats agent-written state as something that must be proposed, reviewed, and evidence-linked before it counts — not just logged after the fact. Every claim carries a receipt, every query can be reproduced, and every write goes through a structured proposal workflow rather than landing directly. The model fits audit-heavy domains where 'the agent said so' is not an acceptable answer. The ceiling appears when you need the tool to decide what to do next: Cruxible is a state layer and workflow runtime, not a planner, so you bring the decision logic yourself. Teams with existing data exports can convert them into structured state, but anything requiring dynamic planning or autonomous tool use sits outside this tool's scope.
FreeOpen SourceSelf-hostedVerified Jul 9, 2026
12. eve
The platform gives coding agents a native deployment surface — API, CLI, MCP, and agent-callable Skills — so agents ship and iterate on apps without a human relaying commands. Sandboxed VMs let agents run code they generated without that code touching your production environment. Durable Orchestration means a workflow that pauses for minutes or months resumes from the exact checkpoint, not from scratch. The constraint is architectural: there is no self-hosted path, so teams with strict data-residency requirements or air-gapped environments hit a wall before they write a single agent. At that point, the conversation moves to a competitor with an on-premises option.
PaidOpen Source$20/moAPIVerified Jun 29, 2026
13. Isnad
Isnad attaches provenance metadata to individual claims as they move through agent pipelines, borrowing the narrator-grading logic from classical hadith transmission scholarship to score source reliability at each hop. The vendor describes it as claim-level auditing — you get a trustworthiness grade per claim, not a flat event log. It installs via pip and ships with Docker support and Alembic-managed migrations, which means it slots into existing Python stacks without standing up a separate service. The ceiling appears when your pipeline is not Python-based or when you need a hosted dashboard rather than a library you integrate yourself. Teams outside that boundary are building their own wrapper before they can use the core grading logic.
FreeOpen SourceAPISelf-hostedVerified Jul 11, 2026
14. Kastor
Kastor lets you define agents, tools, prompts, and models in HCL, validate the spec for broken references and unresolved prompt variables, then compile it to a runnable LangGraph project. The plan/apply/destroy loop catches drift between your spec and what's actually deployed — the same mental model as Terraform, applied one layer earlier. The vendor explicitly labels this an early proof of concept with a working local loop; hosted provider integration is on the roadmap but not shipped. Code generation targets LangGraph only. Teams needing a runtime, a UI, or anything beyond a local CLI will be assembling the rest of the stack themselves.
FreeOpen SourceSelf-hostedVerified Jul 9, 2026
15. Kitaru
Kitaru wraps your existing agent SDK — PydanticAI, OpenAI Agents, Claude Agent SDK, or raw Python — and turns every model call, tool call, and intermediate step into a durable checkpoint. When you want to ask what would have happened with a cheaper model or a failed retriever, you replay from a specific checkpoint with one override. Nothing re-executes in production. The vendor's own benchmark shows 200 replayed executions on a cheaper model matching outputs in 192 of 200 cases at 84% lower cost. The ceiling appears when your agent's behavior depends on state that Kitaru's adapter doesn't intercept — external side effects or SDK internals the wrapper never sees won't be faithfully replayed.
FreeOpen SourceAPISelf-hostedVerified Jul 7, 2026
16. MemLedger
The vendor describes MemLedger as a memory framework with an audit trail: every stored fact carries provenance, so when an agent surfaces a stale or wrong preference you can trace the extraction decision that created it. The library includes a policy layer — a `memory.policy.yaml` file — that lets teams quarantine unverified facts before they reach permanent knowledge, which means bad data from one session doesn't silently corrupt the next. An evaluation suite ships alongside the core library, so you can benchmark how well a newer extraction model rebuilds memories from raw history before you migrate. The ceiling appears quickly for teams that need hosted infrastructure, multi-agent coordination, or anything beyond a Python library integration — there is no API, no managed service, and no UI.
FreeOpen SourceSelf-hostedVerified Jul 10, 2026
17. npcpy
npcpy is a MIT-licensed Python library built around three primitives: Context, Agent (NPC), and Tool — which you compose to wire up single agents or multi-agent teams running against local runtimes like Ollama and llama.cpp or cloud providers. The library's knowledge graph support and multimodal LLM integration live in the same package, so a research prototype doesn't require stitching together three separate dependencies. Where it starts to strain is at the integration surface: documentation is sparse for anything beyond the happy path, and production observability — logging, tracing, failure recovery — is not built in. Teams moving from research prototype to a production deployment will find themselves reaching for additional infrastructure the library does not provide.
FreeOpen SourceAPISelf-hostedVerified Jul 14, 2026
18. Provena
Provena wraps around retrieval steps, tools, and context assembly logic to log where every chunk of data came from, hash it for tamper detection, and surface that audit trail when something breaks or an auditor asks. The vendor describes six framework adapters, an MCP server, PostgreSQL storage, and a policy engine — covering most standard Python-based pipelines without requiring a hosted service. Installation is self-hosted and free. The ceiling appears when your compliance requirement goes beyond audit trails: Provena is a passive tracking library, not an enforcement layer, so it records what happened but does not block a bad retrieval from reaching the model. Teams with hard EU AI Act enforcement obligations pair it with a separate policy gate.
FreeOpen SourceAPISelf-hostedVerified Jul 22, 2026
19. Talon
Talon is a self-hosted, MIT-licensed agent harness that runs as a long-lived process with persistent memory, hot-reloadable plugins, and four frontends — Telegram, Discord, Microsoft Teams, and CLI — all sharing one agent core. Swap the backend by changing one line in config.json: Claude SDK, Kilo, OpenCode, Codex, or OpenAI Agents, each implementing the same interface so your plugins and memory survive the switch. Memory is handled through Mempalace — a ChromaDB vector store plus SQLite knowledge graph that retains semantic context across sessions. Background modes (dream and heartbeat) consolidate memory and run proactive maintenance while the agent is idle. There is no hosted API, no paid tier, and no managed runtime — you own the infrastructure entirely, which means you also own the uptime.
FreeOpen SourceSelf-hostedVerified Jul 19, 2026
20. Tessera
Tessera operates as a deterministic evidence layer that sits between your agent and its outputs. Every claim the agent surfaces is linked to a specific source record; claims without that linkage are refused outright, not softened or hedged. Before any action executes, the agent drafts it from verified claims only and surfaces it for your review. The architecture is open-source under MIT and built to integrate with MCP-based agent setups. Where it breaks: teams that need the agent to synthesize across sources where no single record covers the answer will hit refusals that require data-model work to resolve.
FreeOpen SourceAPISelf-hostedVerified Jul 8, 2026
21. Two-tier-memory
The library implements what the repo calls the 'two-tier fix': structured storage in a local SQLite database, with semantic or keyword queries pulling back only the relevant rows instead of the entire memory corpus. The core workflow is a single Python file and a SQL schema — add a memory, query a memory, done. It runs entirely on-device with no external API calls. The wall you hit is expressiveness: the schema is fixed, so teams with complex memory taxonomies end up forking the schema or layering their own abstraction on top. At that point you are maintaining a fork.
FreeOpen SourceSelf-hostedVerified Jul 6, 2026
22. UFO
UFO is an open-source fleet coordinator for local AI coding agents. You enroll machines as rovers, assign work through a hub, and each operation runs in an isolated worktree with its conversation history, telemetry, and artifacts attached — not scattered across tabs. The auto-detection layer reads which AI CLIs are installed on each rover and advertises their capabilities for dispatch, so you are not manually tracking which machine has Claude Code versus Codex. Public beta status means the rough edges are real: APIs shift, documentation trails the code, and production stability is a bet you are making early. Teams with tight reliability requirements will hit that ceiling before teams prototyping fleet patterns.
FreeOpen SourceSelf-hostedVerified Jul 15, 2026
23. Katra
Katra is self-hosted memory infrastructure: drop it on any Docker-capable machine, point your MCP-compatible agent at it, and you get episodic recall, semantic search, knowledge graphs, and temporal analysis without rebuilding your agent. The architecture is a single deployable unit — the vendor describes it as a 'memory appliance' — which means setup friction is low for teams that already run Docker or Helm on AWS. Where it breaks: Katra is memory infrastructure, not an agent runner, so teams expecting built-in task planning or tool execution will need to wire those themselves. The project is early-stage with five stars on GitHub and no reported production deployments in public community channels, which means you are taking on the role of early adopter rather than stepping into a proven stack.
FreeOpen SourceAPISelf-hostedVerified Jul 1, 2026
24. BrAIn
Built on NATS as its messaging backbone, brAIn distributes agent nodes across hardware and wires them together through a reactive event bus — so an agent fires when something happens, not when a scheduler decides it should. Each node can carry its own UI, which means you monitor individual agents in context rather than reading logs and guessing. The architecture is documented (ARCHITECTURE.md, AGENTS.md), MIT-licensed, and ships with Docker and a monorepo package structure, so self-hosting is the intended path. The project is early-stage with 3 stars and 282 commits from a solo maintainer, which means production hardening and community support are things you contribute rather than consume.
FreeOpen SourceSelf-hostedVerified Jul 9, 2026
25. HART OS
HART OS is an open-source, Apache-2.0 multi-agent runtime built on AutoGen that runs autonomous agents across a crowdsourced compute network, routes tasks through gossip-based federation, and keeps humans in the approval chain by design. The Recipe Pattern is the sharpest production differentiator: agents learn a task once in CREATE mode, then replay it in REUSE mode without repeating LLM calls — the vendor states up to 90% faster execution on trained tasks. Budget gating and compute escrow prevent any single node from absorbing costs for others. Where this breaks down is in ecosystem maturity: no comparable alternatives are listed in the market, documentation is structured but thin in places, and teams building beyond the Nunba bundled distribution will be navigating architecture that is still finding its production footing.
FreeOpen SourceAPISelf-hostedVerified Jul 28, 2026
26. Auto Learning Agents
The platform runs anywhere Docker runs: clone, add keys, and agents come online with their own schedules, models, and instructions. Every turn is embedded and topic-classified; agents query that shared memory bank before acting, so behavior improves with use rather than resetting on each session. Approval queues guard any outward-facing work — you review before it ships — and a single toggle pauses all autonomous activity. The Elixir/OTP supervision tree handles restarts without manual intervention, which matters when you need agents running overnight without babysitting. The extension story is custom nodes and tools in code, so teams that need behavior the built-in config cannot express will be writing Elixir or wrapping external services.
FreeOpen SourceSelf-hostedVerified Jul 4, 2026
27. Reference MCP
Reference is a local MCP server that reads session transcripts and memory files — CLAUDE.md, AGENTS.md, and similar — from multiple AI coding tools, then exposes that history to whichever agent is asking. Register it once in each tool's MCP config and any agent can query what any other agent did before. The architecture is passive: Reference does not plan, execute, or chain tasks — it answers lookups. That scope is the point, and also the ceiling. Teams with more than a handful of tools, or who need structured, queryable memory rather than transcript search, will find the file-scanning approach starts to feel fragile as session volume grows.
FreeOpen SourceSelf-hostedVerified Jul 1, 2026
28. Skill Federation
Skill Federation runs locally on your machine and connects to a catalog of over 100,000 vetted skills. When an agent hits a gap, it surfaces matches in milliseconds — each one license-checked, security-scanned, and provenance-tracked — then waits for your approval before installing into .claude/skills/. The benchmark evidence from the vendor is specific: a bare Claude Code agent solves 17.5% of SkillsBench tasks; with Skill Federation retrieving the top match, that climbs to 22.8%, roughly closing 27% of the gap to a hand-crafted ideal skill. The privacy boundary is narrow by design — only an abstract wish crosses the wire, never your code, plan, or outputs. The hard ceiling is integration breadth: Claude Code is supported, with Codex, Cursor, and Gemini listed as coming.
FreeOpen SourceSelf-hostedVerified Jul 3, 2026
29. GOAT 2.0
GOAT2 runs a Telegram-facing multi-agent system on top of async DAG execution, with a three-tier memory stack — Redis for fast session state, ChromaDB for vector retrieval, and Letta for longer-horizon behavioral learning. The DAG runner means agents can execute in parallel where dependencies allow, rather than waiting in a serial queue. The modular layout — separate directories for agents, orchestrator, memory, plugins, registry, and tools — means you can swap a backend without rewriting everything else. The wall appears when you need a non-Telegram interface: the docs describe Telegram as the primary entry point, and rerouting to another frontend requires you to rebuild the interface layer yourself. Teams that need a REST API or web UI will be adding code before they ship anything.
FreeOpen SourceSelf-hostedVerified Jul 4, 2026
30. Jargo
Jargo handles the full audio path: WebRTC in, a streaming transcription-to-reasoning-to-speech pipeline with turn-taking and barge-in, then audio back out — conforming to the RTVI protocol so existing clients drop in without rewrites. Go's goroutine model means hundreds of concurrent audio sessions don't share a global lock, which is the architectural argument for the whole project. The catch is printed in the README itself: this is early-stage, APIs are unstable, and betting a production system on it before the interfaces settle is a real risk. Teams that need a stable, documented voice pipeline today will find more mileage in Python-based alternatives while this matures.
FreeOpen SourceSelf-hostedVerified Jun 28, 2026
31. Agent Governance Toolkit
Policy enforcement, zero-trust identity, execution sandboxing, and reliability engineering for autonomous AI agents.
FreeOpen SourceAPISelf-hostedVerified May 1, 2026
32. AgentArk
The vendor describes AgentArk as a 'secure-first, self-learning' agent runtime written in Rust, deployable via Docker on your own infrastructure. Core capabilities include scheduled automations, conditional watchers, trace logging with drift detection, and guard layers that require your sign-off before an agent acts. Context compaction — distilling what agents have seen from browser data and tool outputs — is built in, which matters when long-running agents start blowing past context limits. The self-evolution component (GEPA) is documented in the roadmap and architecture files, but community adoption is early — the repository shows six stars and zero forks at the time of curation. Teams that need a production-grade, battle-tested multi-agent backbone with existing integrations will hit the ecosystem ceiling fast.
FreeOpen SourceSelf-hostedVerified Jun 22, 2026
33. agentmemory
Orbit is an open-source agent orchestration harness that wraps coding agent runs in bounded, dependency-ordered tasks, then gates task completion on real validation: tests, lint, and type checks must pass before an orbit closes. Every run produces structured JSON artifacts — agent output, rubric scores, accept/iterate/stop recommendations, and a human-readable progress log — so you have a trail to review, not just a diff to guess at. It runs against Claude, Codex, Cursor, or any agent that speaks JSON over CLI. The demo runs without an API key, which matters when you're evaluating whether it even fits your workflow. Where it strains: teams who need a web UI, multi-agent parallelism, or cloud-managed infrastructure will hit the limits of an intentionally small CLI harness fast.
FreeOpen SourceSelf-hostedVerified Jun 7, 2026
34. Agnt
AGNT is a local-first agent operating system built around an AGI loop: the agent executes a step, evaluates the result, and re-plans before moving forward — without you steering each decision. Persistent memory and skill layers mean context survives across sessions, not just within a single run. The visual workflow designer handles repeatable paths; goal-mode hands the agent an objective and lets it figure out the steps. Self-hosted deployment with Docker keeps data on your own infrastructure, which matters when your legal team has opinions about where prompts and outputs live. The custom license — not OSI-standard — is the detail that stops procurement at some organizations before the first demo.
PaidOpen Source$0 or $333/year per additional user for hosted versionAPISelf-hostedVerified Jun 9, 2026
35. Alma
Alma stores facts and preferences — name, role, working style, answer preferences, current context, principles — as a self-model any MCP-compatible agent can read at session start. The data stays on your machine; no hosted account, no vendor lock-in. Access is scoped, so an agent can read the slice it needs without touching the full store. Every durable write goes through an event log, which means changes are auditable and can be reversed. The project is explicitly labeled experimental by the maintainer, so APIs are unstable and behavior can change between commits.
FreeOpen SourceAPISelf-hostedVerified Jun 24, 2026
36. Atizar
Atizar is an open-source, TypeScript-native framework for building agent workflows where humans stay in the loop before consequential actions execute. The core pattern: agents plan and gather, then pause for a sign-off before anything ships — emails send, records update, data moves. That approval gate is architectural, not bolted on after the fact. The self-hosted option means client deliveries stay off third-party infrastructure. Where it gets tight is documentation depth — the README carries most of the guidance, which means teams building complex branching logic are reading source code before long.
FreeOpen SourceAPISelf-hostedVerified Jun 22, 2026
37. AutoGPU
The repo describes autonomous agents writing RTL, running it through real EDA tools, reading timing and layout reports, and revising the design — iterating without a human in the seat for each pass. The documented target is small systolic array architectures, specifically matrix-multiply accelerators; the codebase includes ISA definitions, physical design configs, and golden reference models. At that constrained scope, researchers report the agent loop closes. Scale the design complexity beyond what the existing module hierarchy covers and the agents lose the plot — the feedback loops that work for a mac array do not generalize to a multi-block SoC. Teams pushing past the documented scope end up writing their own agent scaffolding on top, at which point AutoGPU is a reference rather than a runtime.
FreeOpen SourceSelf-hostedVerified Jun 11, 2026
38. AutoLang
Orbit wraps each agent run in a bounded loop: it pulls one task from a dependency-ordered backlog, hands it to whatever agent you've wired up, runs tests, lint, and type checks, and refuses to close the task until validation passes. Every run produces structured JSON — what the agent returned, how it scored against a rubric, whether a human should accept or re-queue. That audit trail is the point. The ceiling appears when your workflow needs anything beyond task-level sequencing: parallel agent execution, real-time dashboards, or integration with existing CI pipelines requires you to build the glue yourself.
FreeOpen SourceSelf-hostedVerified Jun 2, 2026
39. Autonomy
The core loop — AgentLoop — runs up to a configured step ceiling, selects from 15 bundled procedural skills, ranks candidate actions across five weighted dimensions using beam search, executes through ActionGateway with LOW/MEDIUM/HIGH risk labels, then evaluates and learns. Every event in that chain is stored via event sourcing, so the full run is replayable. The learning loop drafts new skills after a successful run and queues them for review rather than auto-applying them. The wall appears when you need agents running in parallel or sharing state across concurrent sessions — the architecture is single-loop, single-goal. Teams that outgrow that model start wiring external orchestration around it.
PaidOpen SourceFree Trial · 7 days$75/moAPISelf-hostedVerified Jun 22, 2026
40. Browser Use
Browser Use is an open-source Python library for autonomous web task automation using LLMs and computer vision. Teams use it to extract competitive data, fill forms at scale, and monitor page changes across hundreds of sites. The tool hits 89.1% success on standard benchmarks and comes with stealth browser support, CAPTCHA solving, and residential proxies across 195+ countries. The vendor also runs a cloud infrastructure option alongside the self-hosted library. Most production teams pair it with managed browser infrastructure and human approval gates for financial or sensitive actions. The sharp edge: LLMs can't reliably distinguish user instructions from webpage content, leaving agents vulnerable to indirect prompt injection attacks that succeed 24% of the time without defenses.
PaidOpen Source$29/moAPISelf-hostedVerified May 8, 2026
41. Build A Harness
The tool is a visual canvas for designing agent harnesses: multi-layer structures that govern what an agent believes, what it can do, and how it recovers when something goes wrong. You draw a graph on the canvas, and FlowSpec compiles it to LangGraph, CrewAI, Mastra, or Microsoft Agent Framework — no rewrite when you switch. The node library covers 27 types across 14 execution and 13 harness categories, from a minimal three-node loop to an 11-layer stack with world model, five-tier control resolution, nine-layer verification, and six recovery strategies. Langfuse tracing is built into the architecture, so every decision is observable. The ceiling appears when your team needs a hosted managed runtime — the vendor states no hosted API exists, so you own the infrastructure from day one.
FreeOpen SourceAPISelf-hostedVerified Jun 25, 2026
42. Conversations in AI Coding Agent
Orbit is an MIT-licensed, self-hosted harness that wraps a coding agent run in a bounded loop: it selects a task from a dependency-ordered backlog, hands off to whatever agent you plug in, runs tests and lint as a hard gate, and writes structured JSON artifacts that record exactly what happened. Every closed orbit leaves four files — agent output, rubric scoring, an accept-or-iterate recommendation, and a human-readable progress log. The demo runs without an API key, which means you can verify the mechanics before committing any credentials. The harness is agent-neutral by design; the vendor page cites Claude, Codex, and Cursor as examples. Where it shows its seams: Orbit is intentionally small, so teams needing a hosted dashboard, team-level access controls, or CI/CD pipeline integration will be writing that glue themselves.
FreeOpen SourceSelf-hostedVerified Jun 4, 2026
43. CopilotKit
The core model is a React and Angular SDK that connects your existing frontend to whatever agent backend you're already running — LangChain, CrewAI, or a custom setup — via the AG-UI protocol, a bi-directional event stream the vendor describes as 'the general-purpose connection between a user-facing application and any agentic backend.' Agents render rich UI cards, forms, and widgets inline as they work, not just text responses. Thread and state persistence is handled automatically across sessions. The friction point arrives when your deployment target isn't a web surface: Slack and Teams connections are flagged as early access, which means you're betting on a roadmap, not a shipping feature. Teams with strict approval gates before agent actions can wire those checkpoints in, but the docs describe this as a configuration responsibility rather than a built-in guardrail system.
PaidOpen Source$39/developer/monthAPISelf-hostedVerified Jun 9, 2026
44. CrewAI
CrewAI helps enterprises operate teams of AI agents that perform complex tasks autonomously, reliably and with full control. The open-source framework (free, self-hosted) defines agents with roles, goals, and backstories, orchestrating them through tasks; the paid AMP adds a visual Studio, deployment infrastructure, tracing, guardrails, and enterprise features. The framework was rebuilt from scratch to remove LangChain dependency; as of v1.14, it's fully standalone and works with any LLM provider. It's used by nearly half of the Fortune 500. But production friction is real: common Reddit advice is to start with CrewAI for speed and migrate to LangGraph when you hit scaling limits—reasonable for most projects. Users report that enthusiasm evaporates when running repeatedly on multiple components, and executing large SELECT queries overflows the LLM context window.
PaidOpen SourceOpen-source free; CrewAI AMP paid tiers start at $99/monthAPISelf-hostedVerified May 6, 2026
45. Eidentic
The SDK centers on a temporal knowledge graph that tracks when facts were true, resolves contradictions, and consolidates between sessions — so the agent sharpens over time rather than accumulating noise. Durable runs, enforced cost ceilings, and CI-gated evals ship as part of the core, not as paid add-ons. The vendor benchmarks report 55.2% on LongMemEval versus 41.0% for full-context stuffing, and claims up to 39× fewer tokens per query. The gap shows up in support and long-running assistant workflows where session history compounds. At v0.1, the ecosystem is early — teams building anything outside the TypeScript path face a hard stop.
FreeOpen SourceAPISelf-hostedVerified Jun 12, 2026
46. Enforra
Orbit is a harness that wraps AI coding agents — Claude, Codex, Cursor, any JSON-speaking CLI — in a bounded task loop: the agent runs, tests and lint decide whether the work passes, and every run leaves inspectable JSON artifacts whether it succeeds or fails. The evidence trail is the product. You get structured output describing what the agent returned, rubric scoring for task focus and diff signal, and a human-readable progress log. Where it breaks: Orbit does not plan, does not write tasks, and does not decide what to build next — it validates and records what other agents attempt. Teams that need autonomous end-to-end execution will hit that ceiling immediately.
FreeOpen SourceSelf-hostedVerified Jun 1, 2026
47. Enju
Orbit structures agent work into discrete, dependency-ordered loops: one task per run, deterministic validation gates, and four output artifacts that record exactly what the agent returned, how the run scored against a rubric, and what should happen next. The demo runs without an API key, which means you can evaluate the harness itself before spending a single token. Where it gets constrained: Orbit is a harness, not a scheduler — it does not autonomously drive through a backlog or retry failed orbits on its own. Teams wiring it into CI pipelines write the outer loop themselves.
FreeOpen SourceSelf-hostedVerified Jun 1, 2026
48. Genomi
The core workflow is four steps: install the agent harness, point it at your raw genome file on disk, build a local SQLite index, then ask questions through whichever AI agent you already run — Claude Code, Cursor, Gemini CLI, Goose, and others are listed as compatible. Pharmacogenomics, carrier status, polygenic risk scores, nutrigenomics, and ancestry PCA projection are all covered through distinct skill modules backed by ClinVar, PharmCAT, PGS Catalog, HPO, GenCC, and 1000 Genomes reference data. The privacy architecture is explicit: raw genome data stays on disk, and only the specific evidence snippets relevant to a query cross the boundary to whatever LLM handles the response. The vendor marks this as experimental and not for clinical use — which means researchers and privacy-conscious individuals exploring personal data are the intended audience, not clinical teams expecting diagnostic-grade output.
FreeOpen SourceSelf-hostedVerified Jun 9, 2026
49. Gorchestra
Gorchestra is a locally-run Go server that wraps multiple Codex and Claude coding sessions into a single interface, streaming every event in real time and persisting the full history to SQLite. You can inspect live file changes and git state mid-run, queue follow-up messages without interrupting the agent, and return to the exact same session state after a disconnect or restart. The tool is MIT-licensed, self-hosted, and carries no hosted backend. The ceiling appears when your workflow demands coordinating agents across machines or teams — everything here is designed around a single developer's local environment, not a shared multi-user setup.
FreeOpen SourceSelf-hostedVerified Jun 22, 2026
50. Halo
HALO is an open-source Hierarchical Agent Loop Optimizer that ingests production execution traces and generates RLM (Reinforcement Learning from Mistakes) reports pointing at the specific harness code responsible for systemic failures. The core loop is: run your agents, collect traces, feed them to HALO, receive a structured critique, patch the harness. It installs as a desktop app via a one-line curl command or as a hosted option through inference.net. The tool is built around planning and execution trace analysis, so it rewards teams who already instrument their agents — if your traces are thin, the reports will be too. Teams with dense trace data get targeted code-level feedback; teams without it get generic signal.
FreeOpen SourceSelf-hostedVerified Jun 25, 2026
51. Hermes Agent
The agent lives on your server — not a vendor's — and connects to Telegram, Discord, Slack, WhatsApp, Signal, and email simultaneously, so the same agent handles a Slack request in the morning and a scheduled backup at night. Persistent memory and auto-generated skills mean it accumulates institutional knowledge over time rather than starting cold on each invocation. Real sandboxing across Docker, SSH, Singularity, Modal, and local backends means you can isolate risky tasks without routing them through a third party. The ceiling appears when you need managed reliability guarantees: at v0.16.0 this is early-stage software, and self-hosted operations teams carry full responsibility for uptime, credential management, and model API costs. Teams that need SLA-backed infrastructure typically wire Hermes into a managed hosting layer — which adds operational overhead the framework itself does not absorb.
PaidOpen SourceAPISelf-hostedVerified Jun 9, 2026
52. Hezo
Hezo runs a hierarchy of agents — CEO, Coach, Captain, workers — each isolated in its own Docker container, with your secrets never passed directly into agent context. Instead, an egress proxy swaps placeholders for real credentials only when the destination host matches an allowed list, and every substitution lands in an append-only audit log. The Coach agent reviews completed work and writes learned rules back onto workers, so repeated mistakes get corrected without you editing prompts by hand. The ceiling appears when you need agents to hit destinations outside the allowed-host list, or when your workflow requires branching logic the org-chart model doesn't express — at that point you're editing configuration that the docs describe but don't walk you through in depth.
FreeOpen SourceAPISelf-hostedVerified Jun 25, 2026
53. Hugging Face Spaces
Orbit acts as a harness around any JSON-speaking coding agent — Claude, Codex, Cursor, or others — running one task per cycle, executing tests and lint checks to decide whether the work advances, and writing structured JSON artifacts for every run. The dependency-aware backlog keeps each task bounded so agents do not drift across scope. Where it breaks: Orbit is intentionally minimal, so teams expecting a hosted dashboard, a GUI, or built-in agent adapters beyond CLI-level integration will build those layers themselves. The artifact trail is machine-readable JSON and a markdown log — useful for audits, not for a non-technical stakeholder who needs a summary.
FreeOpen SourceSelf-hostedVerified Jun 7, 2026
54. Kikubot
Each Kikubot container polls one IMAP mailbox, feeds incoming email into an LLM agentic loop with a configured tool set, and replies over SMTP. Multi-agent workflows emerge naturally: a coordinator agent emails specialists, specialists reply, threads become the audit trail. The architecture requires a running mail server, which adds operational surface area before a single agent does anything useful. Teams with no existing mail infrastructure will spend more time on SMTP/IMAP setup than on agent logic. When the email-as-bus metaphor stops fitting — high-frequency tasks, sub-second latency requirements, or webhooks that can't wait for a polling interval — this architecture forces a full redesign.
FreeOpen SourceSelf-hostedVerified Jun 12, 2026
55. Langflow
Open-source visual builder for constructing AI agents and RAG applications via drag-and-drop interface with Python extensibility.
PaidOpen SourceAPISelf-hostedVerified May 15, 2026
56. llayer
The core idea is radical reduction: state lives in an append-only .jsonl history file, the context window is a jq stream reducer, and the agent loop is a while loop in bash. Because every component is a standard Unix text pipe, you can slice the history file to rewind agent memory and replay any point — a capability most agent frameworks make architecturally impossible. Debugging is grep and pv, not a proprietary trace viewer. The ceiling appears fast: complex tool chaining or parallel agent coordination does not emerge naturally from a bash pipeline, and teams building anything beyond a single-agent REPL will spend more time fighting shell quoting rules than building product.
FreeOpen SourceSelf-hostedVerified Jun 24, 2026
57. Lobu
Lobu connects to over 50 data sources — HubSpot, Stripe, Zendesk, Snowflake, GitHub, and more — and builds a live memory layer that agents query on schedule rather than on demand. A 'watcher' definition tells the agent what to look for and when to pause for a human to sign off before anything ships. That approval-before-action model is what makes the autonomous scanning safe enough to actually run unsupervised. The ceiling shows up when your workflow needs logic that doesn't fit a watcher definition — at that point you're writing connector SDK code and maintaining it yourself. Teams with deeply custom data pipelines will feel that constraint before teams running standard SaaS stacks.
PaidOpen SourceAPISelf-hostedVerified Jun 20, 2026
58. LocalFlow
The core loop is deliberately small: Orbit selects one dependency-ordered task, hands it to whichever coding agent you wire in, runs tests, lint, and type checks, and only closes the task if the agent can prove the work passed. Every run produces four artifact files — structured result JSON, rubric-scored evaluation, a review recommendation, and a human-readable progress log. That paper trail is what lets you compare two agents on the same task by diffing artifacts instead of re-running demos. The harness runs locally with no API key required for the replay demo, so there is nothing to provision before you can see it work. The ceiling appears fast on non-coding tasks — Orbit is built for code-output validation and nothing else.
FreeOpen SourceSelf-hostedVerified Jun 3, 2026
59. LoopTroop
The tool orchestrates a local pipeline — LLM council planning, an iterative execution loop called Ralph, and OpenCode worktree isolation — designed for multi-file feature work where correctness matters more than turnaround time. Every ticket goes through an interview phase before a line is code is written, resolving ambiguities via adaptive question batches that the vendor describes as intentionally taking over an hour. You review diffs and sign off before anything reaches your main branch. The tradeoff is explicit: LoopTroop is slow by design. Teams treating it as a fast pair-programmer will be frustrated inside the first session.
FreeOpen SourceSelf-hostedVerified Jun 24, 2026
60. Memharness
The core premise is storing facts, not strings, with two independent time axes: when something became true in the world and when the agent learned it — so querying past agent states is a real query, not archaeology through logs. Everything lives in a single SQLite file, which means the storage layer makes zero LLM or network calls and stays auditable. Recall combines hybrid vector search and full-text search with a source-staleness signal, so older or superseded sources rank down automatically. Where it breaks: the SQLite backend is a hard ceiling for teams expecting distributed writes or high-concurrency production deployments. Teams hitting that ceiling will need to treat memharness as a pattern to port, not a service to scale horizontally.
FreeOpen SourceAPISelf-hostedVerified Jun 19, 2026
61. MemPalace
Orbit wraps agent runs in bounded loops: it selects one dependency-ordered task, hands it to your agent, runs tests and lint and type checks, and only marks work complete if validation passes. Every run produces structured JSON artifacts and a human-readable progress log, so you are reviewing evidence instead of trusting output. The agent-neutral contract means you can swap Claude, Codex, or Cursor behind the same harness and compare structured artifacts across runs. The tool is intentionally small — it handles the validation harness, not the full development lifecycle. Teams with sparse test coverage will find the validation gates have nothing to enforce.
FreeOpen SourceSelf-hostedVerified Jun 8, 2026
62. Mind-expander
The agent drives the canvas: it can run `npx mind-expander` in the background, load skill integrations, and build guided tours through architecture. You see the same graph the agent is reasoning about, which means review decisions and refactor plans are grounded in actual dependency structure — not the agent's approximation of it. That shared view is the differentiator. The ceiling arrives with language support: Rust and TypeScript are covered, the docs describe more language frontends as planned. Teams whose core services are in Go, Python, or Java will hit that wall on day one.
FreeOpen SourceSelf-hostedVerified Jun 9, 2026
63. Mnemo
Orbit wraps each agent run in a bounded loop: it selects a dependency-ordered task from your backlog, hands it to whichever coding agent you point at it, then runs tests, lint, and type checks before the task is allowed to close. Every run leaves structured JSON artifacts — what the agent returned, how the output scored against a rubric, and a human-readable recommendation to accept, iterate, or stop. The agent-neutral contract means you can swap Claude for Codex behind the same harness and compare artifacts instead of gut feelings. Where Orbit hits its ceiling: it is a harness, not a planner, so teams that need autonomous task decomposition or cross-repo coordination will be adding that layer themselves.
FreeOpen SourceSelf-hostedVerified Jun 6, 2026
64. Multi Agent Protocol for AI Scientist
The protocol pairs a tool-using Scientist agent with a stateful advisor called Socrates that cannot execute code, cannot issue directives, and cannot answer questions — it can only ask them. The advisor must emit [APPROVED] before the Scientist proceeds to the next experiment, which means every plan gets interrogated before compute is spent on it. The vendor reports this lifted test scores on four of five MLE-bench Kaggle tasks, with an average gain of +55.9% over the Scientist running alone. The ceiling appears quickly outside benchmark-style research tasks: there is no API, no UI, and the protocol is designed around a specific two-agent structure that does not generalize to arbitrary pipelines without custom work.
FreeOpen SourceSelf-hostedVerified Jun 25, 2026
65. Myco Brain
The core mechanic is deterministic writes: the application code writes facts to Myco's Postgres store, not the LLM, so every stored fact carries a source document, a confidence score, and a full audit trail queryable via brain_why. One MCP server exposes that memory to Claude Code, Cursor, Codex, Windsurf, and any other MCP-compatible client simultaneously — write from Claude Desktop, retrieve from Cursor, no sync step required. The vendor publishes a 500-question LongMemEval result and a recall@5 figure using a recency reranker, both on the full benchmark set. The hard ceiling appears when your agents need to act on what they remember — Myco stores and retrieves facts; it does not plan, route, or execute tasks, so orchestration logic lives elsewhere.
FreeOpen SourceSelf-hostedVerified Jun 20, 2026
66. OpenAgents
OpenAgents positions itself as the coordination backbone for distributed AI agents. You get a hosted workspace (or self-host) where agents working on separate machines discover each other, share files and browser context, and coordinate via @mentions. Installation is one-liner: install the Launcher desktop app, point agents at a workspace token, and they join. The platform is open-source with an active but modest community. The technical surface is clean—agents register on the network, events flow between them, and context stays shared. The hard part surfaces later: when your agents are actually doing different things (some coding, some reviewing, some managing), orchestrating handoffs stays manual. This is SDK-first, not no-code. If you're building a research team of specialized agents or debugging scenarios where you need human eyes on agent reasoning in real time, the shared workspace genuinely reduces context switching. If you're running a single coding agent that sometimes needs to call another agent, you might be over-engineering it.
FreeOpen SourceAPISelf-hostedVerified May 8, 2026
67. OSymandias
The project ships a self-hosted runtime built on FastAPI, Celery, PostgreSQL, Redis, RabbitMQ, and Qdrant, so you get job scheduling, DAG orchestration, shared memory, tool execution, and a real-time dashboard without stitching services together manually. A Python SDK lets you define agents, attach tools, and wire multi-agent plans through goal decomposition — the runtime handles the queuing and dependency resolution. That stack is genuinely useful for research pipelines or internal analysis workflows where you control the infra. The ceiling appears when you need a managed hosted option: there is none, which means your team owns every database migration, worker restart, and Redis failover.
FreeOpen SourceAPISelf-hostedVerified Jun 19, 2026
68. Patina
Orbit wraps each agent task in a bounded loop: the agent works, validation runs (tests, lint, type checks), and the task only closes when the checks pass. Every loop leaves structured JSON artifacts — what the agent returned, how it scored against a rubric, and a human-readable recommendation to accept, retry, or stop. This makes agent runs auditable after the fact, not just observable in the moment. The ceiling appears when your project needs multi-agent coordination or a hosted execution layer — Orbit is deliberately narrow, self-hosted only, and ships no managed runtime.
FreeOpen SourceSelf-hostedVerified Jun 8, 2026
69. Preseason.ai
Orbit sits between your backlog and your coding agent, selecting one dependency-ordered task at a time, running the agent, then forcing the result through tests, lint, and type checks before marking the task done. Every run writes structured JSON artifacts — what the agent returned, how the output scored against a rubric, whether a human should accept or iterate — so you are reviewing evidence, not trusting a diff. The agent-neutral contract means you can run Claude, Codex, and Cursor against the same task and compare artifacts instead of impressions. The harness is intentionally minimal; it does not schedule, it does not host, and it does not manage secrets — which means the moment your workflow needs cross-repo coordination or cloud execution, you are writing the glue yourself.
FreeOpen SourceSelf-hostedVerified Jun 8, 2026
70. ProData AI
Orbit is an open-source harness that wraps AI coding agent runs in a fixed loop: pick a task from a dependency-ordered backlog, run the agent, validate the output against tests, lint, and type checks, then record structured evidence before the task closes. Nothing advances without proof. Each run produces four artifact files — agent output, rubric scores, a recommendation, and a human-readable log — so you can inspect exactly what happened without replaying the whole session. The harness is agent-neutral; Claude, Codex, Cursor, or any JSON-speaking CLI plugs in behind the same contract. The ceiling appears quickly on teams who need anything beyond the validation-gate model — custom orchestration, parallel agent execution, or UI-driven workflow design are not in scope.
FreeOpen SourceSelf-hostedVerified Jun 6, 2026
71. RoBrain
RoBrain sits between your team's AI coding tools — Claude Code, Cursor, Copilot, Codex CLI — and a shared Postgres instance, capturing not just decisions but the alternatives your team ruled out. An MCP server runs inside the editor and surfaces relevant history before the agent acts; a batch Synthesis scan reads the whole corpus on a schedule to flag contradictions and drift that no single session would catch. That cross-session contradiction detection is where it separates from alternatives that only check at insertion time or silently delete the losing decision. Self-hosted on Apache 2.0 with your own Postgres; cloud extraction and the Planning API are paid-only features.
PaidOpen SourceAPISelf-hostedVerified Jun 1, 2026
72. RunbookHermes
The agent runs multi-signal diagnosis across observability data, builds a root-cause hypothesis, and generates or updates runbooks from what it learns — so the next incident with the same failure pattern starts from a documented baseline instead of a blank slate. The approval-gated remediation workflow means automated action doesn't ship without a reviewer, which matters when the blast radius is a production service. Where it breaks: the repo is five commits deep with zero open issues, which signals early-stage software, not battle-hardened infrastructure. Teams with complex multi-service topologies will hit integration gaps before the agent's reasoning does. Self-hosting is required, so operationalizing this adds a deployment and maintenance surface your platform team owns.
FreeOpen SourceAPISelf-hostedVerified Jun 9, 2026
73. Skawld
The SDK runs on Node.js 18+ and Bun 1.1+ as an ESM-only package, so it fits cleanly into modern TypeScript projects without a build-step fight. The vendor describes a minimal setup as a single `Agent` instantiation with a provider, a tool set, and a session — you are running a streaming agent loop in under a dozen lines. Where it starts to strain is on the documentation side: the README is thin, full docs live off-repo at skawld.com/docs, and community reports are sparse given the early star count. Teams who need battle-tested enterprise support or a large ecosystem of pre-built integrations will hit that ceiling fast.
FreeOpen SourceAPISelf-hostedVerified Jun 9, 2026
74. Strands Shell
The core pattern is tight: decorate a Python or TypeScript function with `@tool`, pass it to an `Agent`, attach hooks that fire before or after each tool call, and the agent runs its loop. The `BeforeToolCallEvent` hook lets you inspect the tool's name and input — and cancel the call with a message if your conditions aren't met. That's not a workaround; it's the documented pattern. Where the framework gets quiet is multi-agent coordination — the docs describe single-agent tool loops clearly, but teams building agents that hand off to other agents will find precious little guidance on failure recovery between hops. When that gap bites, teams layer their own orchestration logic on top, which means maintaining that logic themselves.
FreeOpen SourceAPISelf-hostedVerified Jun 22, 2026
75. Tab Council
Orbit wraps agent coding work in a bounded loop: it selects a dependency-ordered task, hands it to whichever agent you've wired up, then requires passing tests, lint, and type checks before the task closes. Every run produces structured JSON — what the agent returned, how it scored against a rubric, and a human-readable progress log. Nothing advances on the agent's word alone. The ceiling appears when your workflow needs anything beyond single-task validation loops: multi-repo coordination, branching logic between tasks, or a hosted dashboard for non-engineering stakeholders all require you to build on top of Orbit yourself.
FreeOpen SourceAPISelf-hostedVerified Jun 2, 2026
76. Tabbit
Orbit wraps agent execution in bounded, dependency-ordered tasks: one unit of work at a time, with tests, lint, and type checks acting as the gate before progress is recorded. Every run produces four structured artifacts — result JSON, rubric evaluation, a review recommendation, and a human-readable progress log — so code review has evidence instead of vibes. The agent-neutral contract means you can swap Claude, Codex, or Cursor behind the same harness and compare artifacts on identical task sets. The ceiling appears fast: Orbit is deliberately small, so teams that need scheduling across distributed workers or CI/CD pipeline integration will be adding that infrastructure themselves. It is a harness, not a platform.
FreeOpen SourceVerified Jun 1, 2026
77. Vmette
The threat model vmette solves is concrete: prompt injection on a fetched web page, a malicious package in an AI-suggested install, or model output that does something you didn't intend — all of it lands inside the VM, not on your host. The isolation is hardware-level, not a container namespace that a determined process can escape. Because everything runs on-device, no agent output leaves your machine to a third-party cloud sandbox. The ceiling appears at the edges: vmette is macOS-only, and teams whose agents need to run on Linux servers or in CI pipelines will need a different isolation strategy.
FreeOpen SourceSelf-hostedVerified Jun 9, 2026
78. Z3r0
Z3r0 is an open-source, self-hosted workbench where a coordinating agent (Z3r0/CSO) delegates to five specialist agents — code audit, recon, exploitation validation, reverse engineering, and cryptography — each scoped to a defined domain. Sessions run against a PostgreSQL-backed timeline log with replay, so long engagements survive interruptions and context window rollovers. WorkProject records tie every finding to authorized scope, targets, and sandbox bindings, which means the evidence chain stays intact when the model context doesn't. The wall appears when your engagement requires a specialist task not covered by the six fixed roles — there is no agent plugin system described in the docs, so teams extending scope are writing new agents from scratch.
FreeOpen SourceAPISelf-hostedVerified Jun 11, 2026
Listings on this page are sourced and verified by the AIDiveForge data pipeline. AIDiveForge is editorially independent — no money changes hands for inclusion.