State of Modern AI Agent Frameworks, Harnesses, Runtimes, and Decision Models¶
Executive summary¶
As of October 2, 2026, the center of gravity in agent engineering has shifted. The hottest projects are no longer merely libraries that wrap an LLM with tools. The modern stack increasingly separates into a model, an agent harness/loop, a sandbox and policy runtime, a durable context layer, and an operations/orchestration layer. The clearest examples are DeepSeek Harness's everything-is-a-plugin architecture, Pydantic AI's newly integrated Harness, LangChain's Deep Agents, Strands' newly assembled Harness, NVIDIA OpenShell's security runtime, and Paperclip's agent-operations control plane. citeturn20search8turn7search9turn18search15turn18search7turn20search3turn20search10
I interpret the “Jeb” in the question as TypeSafe AI's Jev. Jev is particularly interesting precisely because it is not another general-purpose LLM or agent framework: it is a “System One” decision model that returns typed choices, scores, and calibrated probabilities rather than generated prose. TypeSafe launched it on September 15, 2026, and its emergence alongside Strands' new Decider 2B suggests a new architectural pattern: use expensive generative models for hard cognition, but use fast decision models for routing, permissioning, scoring, escalation, and repetitive agent-loop judgments. citeturn5search0turn5search1turn9search8
My top twelve, ranked for a mixture of current momentum, architectural modernity, recent release activity, production readiness, ecosystem signal, and composability, are:
| Rank | Project | Why it is unusually important right now |
|---|---|---|
| 1 | DeepSeek Harness | The most explosive open-source harness launch in the dataset: roughly 240k stars, 28.8k forks, and +7.1k stars/week; its Cordis-based “everything is a plugin” architecture makes even the agent loop replaceable. It is still explicitly a developer preview, so heat greatly exceeds stability. citeturn21search0turn20search8turn20search12 |
| 2 | Paperclip | The strongest signal that the next layer above frameworks is agent operations: goals, org charts, budgets, governance, schedules, approvals, audit logs and bring-your-own agents. 96.1k stars and +13.1k/week is extraordinary momentum for a project created in 2026. citeturn21search1turn20search10 |
| 3 | Pydantic AI / Harness | Probably the strongest general-purpose Python evaluation candidate today: typed agent APIs plus a newly integrated full Harness with subagents, planning, memory, context management, persistence, coding capabilities, sandboxes and SSH workspaces. v2.53.0 shipped October 1. citeturn24view1turn7search5turn7search9 |
| 4 | Deep Agents | LangChain's modern batteries-included harness above LangGraph: filesystem, planning, context management, skills and subagents out of the box; 29.9k stars and still pre-1.0. This is a substantially more relevant 2026 comparison than treating “LangChain” as one monolithic framework. citeturn19search0turn18search15turn19search7 |
| 5 | Strands Agents / Harness | One of the cleanest harness-first architectures: Python + TypeScript, model/cloud portability, lifecycle limits, sessions, MCP, multi-agent patterns, guardrails, tracing and evals. Its September Harness launch and October 1 Decider 2B release make it one of the freshest ecosystems. citeturn18search7turn9search2turn9search8 |
| 6 | Microsoft Agent Framework | The strongest enterprise-stability candidate: Agent Framework 1.0 reached GA in April, unifying Microsoft's Semantic Kernel and AutoGen direction with Python/.NET, multi-agent orchestration, MCP/A2A and deployment integration. citeturn22search1turn1search1 |
| 7 | NVIDIA OpenShell | Not another agent loop: it is a security/runtime boundary underneath agents. It is the fastest-growing project right now in relative terms—13.8k stars, +4.4k in one week—following NVIDIA's September agent-safety launch. citeturn21search2turn20search3turn31news51 |
| 8 | OpenAI Agents SDK | Still one of the strongest minimal multi-agent SDKs, but the important 2026 change is its evolution toward a more model-native harness spanning files, tools, controlled execution, memory and sandboxes. 29.8k stars with 402 contributors. citeturn24view2turn1search4 |
| 9 | Google ADK | ADK 2.0 is now a serious orchestration/runtime toolkit rather than merely a Gemini helper: explicit graph execution, fan-out, loops, retry/state, human-in-the-loop, A2A, MCP, evals and deployment. 21.7k stars and 527 contributors. citeturn22search2turn6search19 |
| 10 | Mastra | The leading TypeScript-native contender in this group. Mastra 1.0 stabilized APIs in January and added server adapters, composite storage, agent-loop processors, thread cloning and AI SDK v6 integration. It shows exceptional contributor and commit activity. citeturn23search2turn25search2turn25search6 |
| 11 | Claude Agent SDK | Probably the closest programmatic route to Claude Code's increasingly sophisticated harness behavior—hooks, MCP tools, subagents and session management—but it is Claude-specific and governed by Anthropic's commercial terms rather than a conventional permissive OSS license. v0.2.163 shipped October 1. citeturn7search14turn25search3 |
| 12 | TypeSafe AI Jev | The strategically interesting outlier: a hosted decision model rather than an agent framework. Its value is as a low-cost, low-latency decision plane inside another harness. Media and developer attention over the last two weeks has been unusually intense. citeturn5search0turn4search5turn31news46turn31news50 |
This ranking is deliberately not a ranking of “best framework by GitHub stars.” DeepSeek Harness and Paperclip dominate attention metrics but are younger; Microsoft Agent Framework, Mastra and OpenShell have more explicit stability stories; Pydantic AI, Deep Agents and Strands currently look particularly compelling for teams that want to own composition rather than invent an agent runtime from scratch. citeturn20search8turn25search5turn25search2turn19search7
The projects I would evaluate first for a serious upstream-first architecture are Pydantic AI/Harness, Strands, Microsoft Agent Framework, Deep Agents and OpenShell. I would add Jev/Strands Decider as experimental decision-layer components and evaluate Paperclip only if there is a real need for organization-level agent operations. DeepSeek Harness deserves immediate architectural study but not yet an assumption of production stability. citeturn7search5turn18search7turn1search1turn19search5turn25search5turn20search8
Scope and methodology¶
The research cutoff is October 2, 2026. Eligibility required either a launch during roughly October 2025–October 2026 or a material architectural/release milestone during that period. I included four adjacent categories because treating all of them as “agent frameworks” obscures the real market structure: framework/SDK, assembled harness, secure execution/runtime, and agent operations or decision-model infrastructure.
Primary repositories, official documentation and release notes were used for feature, licensing, maturity and roadmap claims. GitHub momentum is normalized primarily through Star History where current data was available. Its “weekly pushes” is used as an activity proxy; it should not be confused with a literal count of commits. The growth rate shown below is:
7-day star velocity = stars added during the most recent week ÷ current stars × 100.
That allows comparison between a 14k-star project and a 240k-star project without pretending that raw star additions mean the same thing. For projects whose repository history has moved or whose product is not centered on a single core GitHub repository, I leave the rate blank rather than manufacture a comparable figure. citeturn21search0turn21search1turn21search2turn24view1turn24view2
The ranking weights momentum heavily but not exclusively: approximately 30% ecosystem/GitHub momentum, 25% architectural differentiation and composability, 20% recent release activity, 15% production maturity/stability, and 10% news/forum signal. That weighting explains why a 13.9k-star GA framework can outrank projects with much larger historical star totals, while a viral new repository does not automatically become the best production choice.
Three important baseline projects did not make the twelve because this report emphasizes the newest architectural wave, not because they are dead. LangGraph remains a major durable-execution substrate and is the foundation beneath Deep Agents; CrewAI 1.15 remains extremely active and had roughly 59k stars; and Agno/AgentOS remains a substantial framework/runtime stack with roughly 42k stars. Deep Agents is the more revealing LangChain comparison for this particular research question, while Microsoft Agent Framework has effectively become Microsoft's successor direction for functionality previously split between AutoGen and Semantic Kernel. citeturn18search15turn6search26turn15search0turn14view3turn1search1
A final caveat matters: GitHub stars measure attention, not deployment quality. DeepSeek Harness's roughly 239.7k stars versus only 55 contributors is perhaps the clearest example. That ratio does not establish anything improper about the growth; it simply means the signal is overwhelmingly awareness/interest rather than direct evidence that hundreds of thousands of teams are deploying it. Paperclip's current launch spike should be interpreted similarly. citeturn21search0turn21search1
Ranked projects and GitHub momentum¶
The quantitative picture is unusually revealing. OpenShell and Paperclip are experiencing launch-stage exponential attention. DeepSeek has the largest absolute new-star count after Paperclip but has already accumulated such a huge denominator that its weekly percentage growth is lower. Among more mature frameworks, Microsoft Agent Framework and Pydantic AI currently have the strongest normalized weekly star velocity of the comparable repositories. citeturn21search0turn21search1turn21search2turn24view1turn22search1
| Project | Stars | Forks | Contributors | New stars, 7d | Star velocity | Activity signal | Interpretation |
|---|---|---|---|---|---|---|---|
| DeepSeek Harness | 239.7k | 28.8k | 55 | +7.1k | 2.96%/wk | Star History reports 0 pushes; GitHub itself shows active RC work and >20k historical commits | Huge attention; developer preview. citeturn21search0turn20search4turn20search12 |
| Paperclip | 96.1k | 16.3k | 218 | +13.1k | 13.63%/wk | 102 pushes/wk | Exceptional viral + development momentum. citeturn21search1 |
| Deep Agents | 29.9k | 4.2k | 160 | +182 | 0.61%/wk | 49 pushes/wk | Strong sustained growth, not just launch hype. citeturn19search0 |
| Pydantic AI | 20.4k | 2.8k | 616 | +190 | 0.93%/wk | 149 pushes/wk | One of the best breadth/activity combinations. citeturn24view1 |
| Microsoft Agent Framework | 13.9k | 2.4k | 278 | +132 | 0.95%/wk | 13 pushes/wk | High normalized growth for a post-GA enterprise project. citeturn22search1 |
| Strands Harness SDK | 8.6k | 1.3k | — | — | — | ~2,845 commits; pushed October 2 | Repository restructuring makes normalized tracker data less clean, but primary-repo activity is very high. citeturn18search7 |
| NVIDIA OpenShell | 13.8k | 1.6k | 126 | +4.4k | 31.88%/wk | 76 pushes/wk | Fastest current relative growth in the comparable set. citeturn21search2 |
| OpenAI Agents SDK | 29.8k | 4.8k | 402 | +128 | 0.43%/wk | 26 pushes/wk | Large, established developer base; growth is now steady rather than launch-like. citeturn24view2 |
| Google ADK | 21.7k | 4.1k | 527 | +84 | 0.39%/wk | 6 pushes/wk | Broad contributor base and strong fork ratio. citeturn22search2 |
| Mastra | 28.4k | 2.9k | 686 | +189 | 0.67%/wk | 276 pushes/wk | Highest development-activity signal in the normalized group. citeturn23search2 |
| Claude Agent SDK Python | 8.2k | 1.3k | — | — | — | v0.2.163 released Oct. 1; near-daily releases recently | Extremely fast release cadence; less open licensing. citeturn25search3 |
| Jev / TypeSafe ecosystem | Core model not OSS | — | — | — | — | Jev 1.13 service plus fast-moving public SDK/skills repos | GitHub metrics are not comparable because Jev itself is a hosted model; TypeSafe's public skills repo was already around 2.5k stars. citeturn4search0turn4search5 |
The most useful “hotness” chart is therefore not raw stars but current relative star velocity:
xychart-beta
title "Current GitHub weekly star velocity"
x-axis ["OpenShell","Paperclip","DeepSeek","MS AF","Pydantic","Mastra","Deep Agents","OpenAI","Google ADK"]
y-axis "New stars / current stars (%)" 0 --> 35
bar [31.88,13.63,2.96,0.95,0.93,0.67,0.61,0.43,0.39]
Two signals stand out. First, OpenShell's 31.9% weekly growth is launch-driven, coinciding with NVIDIA's September 28 Open Agent Safety Platform announcement and substantial mainstream press coverage. Second, Paperclip's +13.1k stars in a week while also recording 102 pushes is a stronger signal than stars alone because development activity is increasing alongside awareness. citeturn21search2turn31news51turn21search1
Among established frameworks, Pydantic's 616 contributors / 149 weekly pushes, Google's 527 contributors, Mastra's 686 contributors / 276 pushes, and OpenAI's 402 contributors are healthier maturity signals than headline star totals by themselves. citeturn24view1turn22search2turn23search2turn24view2
There is also a very early watchlist worth separating from the mature ranking. OpenHarness jumped from roughly 78 stars around September 17 to about 1.1k by October 2, an approximate fourteen-fold increase in about two weeks; it is experimenting with one-worktree-per-harness execution, local models and a store covering dozens of existing harnesses. Context Mode, meanwhile, had reached roughly 24.7k stars as a context-window optimization layer using MCP/hooks across multiple coding-agent environments, and OpenRig was emerging as a persistent-agent-team abstraction over existing harnesses such as Claude Code, Codex and Pi. These are exactly the projects to watch because they compose existing upstream harnesses rather than insisting on yet another universal agent loop. citeturn17search10turn17search2turn19search4
Technical comparison and project notes¶
| Project | Primary role / use case | Models | Orchestration & agent capability | Extensibility | License / maturity |
|---|---|---|---|---|---|
| DeepSeek Harness | Build highly customized coding/general agent harnesses | Model adapters are plugins; designed for provider interchange | Replaceable agent loop, sessions, background work, teams, UI, sandbox and tool layers | Everything-is-a-plugin via Cordis; MCP v2 appearing in current RC | MIT; developer preview; breaking changes explicitly expected. Repo · Docs · Releases citeturn20search8turn20search12 |
| Paperclip | Operate a team/company of agents rather than author an individual agent | Bring-your-own agents/runtimes/providers | Org charts, goals, delegation, routines, budgets, approvals, pause/resume/terminate, audit | Out-of-process plugins, capability-gated services, API/webhooks, portable organizations | MIT; very young but fast-moving date-based releases. Repo · Releases · Roadmap citeturn20search10turn25search0 |
| Pydantic AI / Harness | Production Python agents, structured applications, coding agents | Broad/model-agnostic; typed interfaces around providers | Typed agent loop, Pydantic Graph, memory, planning, subagents, compaction/context management, persistence | MCP, capabilities, custom tools, evals, Logfire; Bubblewrap and SSH workspaces in newest harness releases | MIT; v2.x active. Harness now ships inside main release train. Repo · Docs · Releases citeturn7search9turn7search5 |
| Deep Agents | Long-horizon research/coding/general agents needing a preassembled harness | Any tool-calling LangChain chat model, including major APIs and local/open-weight backends | Planning, filesystem, context management, subagents, skills, persistent backends; async subagents | Middleware/building blocks inherited from LangChain/LangGraph; components individually replaceable | MIT; explicitly pre-1.0, although production deployment is supported. Repo · Docs · Releases citeturn18search15turn19search5turn19search7 |
| Strands | Embedded production agent loop or fully assembled harness | Bedrock, Anthropic, OpenAI, Gemini, Ollama and additional/custom providers | Turn/token limits, cancellation, structured output, sessions, memory, multi-agent patterns, bidirectional streaming | Hooks, MCP, steering, guardrails, tracing, evals; Python + TypeScript | Apache-2.0; core SDK 1.x, newly assembled Harness/CLI younger. Repo · Docs · Releases citeturn18search6turn18search21 |
| Microsoft Agent Framework | Enterprise multi-agent/workflow systems, especially Python/.NET estates | Multi-provider | Agent abstraction plus explicit workflows/orchestration, human approval, state, hosted agents | MCP, A2A, connectors, Foundry, DevUI, local Agent Harness | MIT; 1.0 GA/LTS-grade direction. Repo citeturn1search1turn1search5 |
| NVIDIA OpenShell | Secure execution boundary underneath autonomous agents | Harness/model neutral; run an agent workload inside its sandbox | Not an agent planner; controls filesystem/process/network authority and credential use | Middleware, interceptors, compute drivers, providers; Python/TS/Go/Rust SDKs; Kubernetes | Apache-2.0; 0.1.0 removed alpha designation and introduced weekly stable release qualification. Repo · Docs · Releases citeturn20search3turn25search5 |
| OpenAI Agents SDK | OpenAI-native agent apps, handoffs, realtime/voice and multi-agent workflows | OpenAI first-class | Agents, handoffs, guardrails, sessions, tracing, realtime agents; 2026 harness adds controlled execution/files/memory direction | Tool interfaces, MCP, sandbox clients and model abstraction | MIT; Python SDK mature. Repo · Docs citeturn1search4 |
| Google ADK 2.0 | Code-first multi-agent systems and deployment, particularly around Google ecosystem | Model-agnostic but optimized for Gemini | Graph runtime, branching/fan-out, loops, retry, shared state, nesting, HITL, Task API/A2A | Functions, OpenAPI, MCP, custom agents/tools, Cloud Run and Vertex deployment | Apache-2.0; ADK 2.0, broad contributor base. Repo · Docs citeturn6search19turn22search2 |
| Mastra 1.x | Full-stack TypeScript agent/workflow applications | Broad AI SDK/provider ecosystem | Agents, workflows, memory, RAG, streaming, agent-loop processors, thread cloning | Server adapters for Express/Hono/Fastify/Koa, storage adapters, eval/observability integrations | Core Apache-2.0 with separate enterprise code; 1.0 stable since Jan. 20. Repo · Docs citeturn25search2turn25search6turn7search20 |
| Claude Agent SDK | Programmatic Claude Code-class agents | Claude | Claude Code agent loop, subagents, session resume/forking, hooks, permissions | In-process MCP servers/custom tools and lifecycle hooks | Source visible, but governed by Anthropic commercial terms; v0.2.x and rapidly changing. Repo · Releases citeturn7search14turn25search3 |
| Jev | Fast classification, routing, risk scoring, policy/guardrail decisions inside another system | Jev is the model | No general agent loop; returns typed probabilities/decisions that another harness consumes | Choice, Score and related typed question primitives; SDK/adapters and coding-agent integrations | Hosted service, extremely new; no open-weight core model identified in the official material reviewed. Official site citeturn5search1turn4search5turn4search2 |
Several deserve deeper interpretation.
DeepSeek Harness is the most architecturally radical. Its core idea is that the model adapter, tool registry, session machinery, sandbox, UI and even agent-loop implementation can be swapped as plugins. The current 0.2.0 release-candidate stream is already adding desktop distribution, background task behavior, agent-team UI, MCP v2 protocol support and richer file/document handling. But DeepSeek itself labels the repository a developer preview and warns that compatibility-breaking changes are expected. That combination—radical composability plus explicitly unstable APIs—is exactly why it is an architecture to study immediately but not yet a default foundation. citeturn20search8turn20search12
Pydantic AI made one of the most consequential changes of the past month. Its Harness is no longer a peripheral experiment: by v2.52 it had moved into the monorepo and began shipping on the same release cadence as Pydantic AI itself. The harness includes coding-oriented filesystem and shell capabilities, SSH workspaces, Bubblewrap sandboxing, subagents, memory, guardrails, planning and context management; v2.53 followed on October 1 with further fixes including security-related work. This creates a plausible path to a complete Python agent stack without inventing a new scheduler, loop or framework. citeturn7search5turn7search9turn24view1
Deep Agents represents LangChain's answer to the same harness trend. LangGraph remains the durable execution substrate, LangChain's create_agent is the lighter loop, and Deep Agents deliberately sits above both as an opinionated batteries-included harness with filesystem state, context engineering and delegation. The project explicitly says it can use frontier APIs, open-weight models through hosted providers, and local runtimes such as Ollama, vLLM and llama.cpp. Its production documentation is mature, but LangChain also explicitly classifies Deep Agents as pre-1.0 with potentially changing minor-version APIs. citeturn18search15turn19search5turn19search7
Strands is unusually attractive from a composition standpoint. Its own positioning is essentially “use this instead of hand-writing an agent loop.” It runs in-process without requiring a hosted control plane and already includes budgets, cancellation, sessions, context management, model portability, MCP, multi-agent patterns, guardrails, tracing and evals. The freshly added Strands Harness wraps these primitives into an assembled agent, while the October 1 Decider 2B announcement adds a small open decision model into the same ecosystem. citeturn18search7turn9search8
Microsoft Agent Framework has a different advantage: consolidation and stability. Its 1.0 GA announcement explicitly places it as the unified forward path incorporating lessons from Semantic Kernel and AutoGen, with stable APIs, Python/.NET support, multi-agent orchestration, MCP/A2A and deeper Azure/Foundry integration. Microsoft's stated roadmap continues toward connectors, skills, richer Foundry integration and research-driven capabilities. citeturn1search1
OpenShell is arguably more important than yet another agent framework. Every sandbox starts with constrained access; filesystem, process and network authority is policy controlled; real credentials can be kept away from the agent and bound to approved destinations; policy expansion can be checked before being applied. OpenShell 0.1.0 explicitly removed the alpha designation and established weekly stable releases with conformance, upgrade, breaking-change and security testing. The security model is drawing unusually positive practitioner attention because it addresses the deterministic enforcement layer that LLM guardrails cannot. citeturn20search3turn25search5turn28search0
Jev is the conceptual wild card. Jev 1.13 is advertised with typed probabilistic decisions rather than text generation, a text-only interface, a 64k-token request context, dynamic limits around 100k tokens/second and 40 requests/second, and current pricing around $42 per billion input tokens. Those are vendor-published service characteristics, not independent performance validation. The interesting design implication is much larger than the specific numbers: a harness can ask an inexpensive decision model “is this safe?”, “which tool?”, “should I escalate?”, or “which candidate wins?” without invoking a frontier generative LLM to write a paragraph explaining the answer. citeturn4search5turn5search1
Independent evidence is already making that story more nuanced. One third-party benchmark against Reddit AITA verdicts found Jev close to Sonnet 5 on the task while being materially cheaper and faster, but far below TypeSafe's largest vendor speed claims—a useful reminder to benchmark Jev on the exact decision distribution that matters rather than accept generalized throughput marketing. citeturn31search3
News, forums, and sentiment¶
Developer discussion is currently much more informative on Hacker News than on publicly indexable Reddit. The strongest Reddit quantitative signal I could verify is a dedicated r/PydanticAI community of roughly 5,000 members, reported as growing by about 2,000 members / 100.3% year-over-year, with recurring discussion around deployment, tools, memory, MCP, Gemini and framework interoperability. Comparable fresh numeric Reddit thread data did not surface reliably for most of the other new September launches, so absence from this table should not be interpreted as lack of Reddit interest. citeturn31search0
The recent HN sample is much richer:
| Signal | Engagement | What the discussion says |
|---|---|---|
| “DeepSeek Harness developer preview” | 745 points / 310 comments | By far the strongest developer-forum event in the set. Enthusiasm centers on open infrastructure and plugin architecture; skepticism centers on complexity, security and whether another harness is actually needed. citeturn27search8turn27search4 |
| “DeepSeek Harness Desktop for macOS and Windows” | 206 / 103 | Cordis and long-running composability received praise, alongside concerns about binary trust, permissions and harness proliferation. citeturn27search0 |
| “The agent harness belongs outside the sandbox” | 39 / 29 | Strong architectural debate around keeping the deterministic harness/credentials outside the untrusted execution sandbox. This directly reinforces OpenShell-style separation. citeturn28search1 |
| “An Empirical Study of Harness Design for Coding Agents” | 30 / 2 | Discussion highlighted that planning, tool design and context management interact with model capability; no universal harness configuration wins for every model/task/budget. citeturn28search5 |
| OpenShell formal-methods discussion | 14 / 5 | Directionally positive; interest centers on policy enforcement and formal checks rather than another prompt-level guardrail. citeturn28search12 |
| HarnessRouter | 10 / 14 | Strong support for treating existing harnesses as interchangeable infrastructure rather than rebuilding one, with debate about whether model/harness co-training makes routing valuable. citeturn28search9 |
| Pydantic AI structured-streaming extension | 6 / 3 | Small but strongly practitioner-oriented thread; author reports production usage and identifies lifecycle/streaming glue as the pain point around the core framework. citeturn27search1 |
| Anthropic Agent SDK policy discussion | 5 / 1 | Low engagement but distinctly negative sentiment around subscription/policy predictability, illustrating the lock-in concern around provider-native harnesses. citeturn28search11 |
Those eight selected artifacts total 1,055 HN points and 467 comments. A manual, thread-level—not individual-comment—classification produces three directionally positive items, four mixed/cautious items and one predominantly negative item. This is a directional sample, not a population-level sentiment model:
pie showData
title Sentiment across 8 selected recent HN/forum artifacts
"Positive" : 3
"Mixed / cautious" : 4
"Negative" : 1
The most useful qualitative result is therefore not “developers are 37.5% positive.” It is that technical enthusiasm now comes almost automatically with operational skepticism. Developers like composability, local ownership and better model performance, but the highest-quality discussions repeatedly return to four concerns: what actually executes shell/network actions, where credentials live, whether context can be recovered or inspected, and whether the model/harness combination has been tested rather than merely benchmarked independently. citeturn27search0turn28search1turn28search5turn27search13
The mainstream-news picture is also telling. Jev and OpenShell, rather than traditional framework releases, are getting the strongest recent general-tech coverage. On October 2, the Wall Street Journal reported on Jev's rapid emergence as an alternative decision-model architecture; Business Insider covered a San Francisco Jev hackathon and developer enthusiasm; and Tom's Hardware covered the Jev-powered Pokémon Red experiment while noting that Claude Opus 5 was used as a coach when the decision model got stuck. citeturn31news46turn31news50turn31news47
For OpenShell, both the AP and Guardian covered NVIDIA's September 28 agent-safety announcement. The primary project itself describes policy-bound sandboxes, credential mediation and formally checked access changes; mainstream coverage emphasizes the growing concern that increasingly autonomous agents need a deterministic security boundary underneath the LLM. citeturn31news51turn31news49turn20search3
DeepSeek Harness has generated less traditional mainstream coverage than its GitHub/HN numbers would imply, but developer publications have focused on its record-setting star velocity, Cordis architecture, real OS sandbox mechanisms and explicit developer-preview caveat. That discrepancy reinforces the interpretation that DeepSeek Harness is currently a developer phenomenon first. citeturn31search1turn31search5
Release timeline and what is next¶
The last twelve months show how abruptly the vocabulary moved from “agent framework” toward “harness engineering.” Mastra stabilized a 1.0 application framework in January; Microsoft reached 1.0 GA in April; OpenAI announced a deeper harness architecture later that month; DeepSeek arrived in August; Jev, Strands Harness and OpenShell all made major moves in September; and Pydantic integrated its Harness into its main release train by the end of September. citeturn25search2turn1search1turn1search4turn21search0turn5search0turn9search8turn25search5turn7search5
timeline
title Major modern agent/harness milestones
2025-10-20 : LangGraph 1.0 baseline
2026-01-20 : Mastra 1.0 stable
2026-04-03 : Microsoft Agent Framework 1.0 GA
2026-04-07 : Deep Agents 0.5 adds async subagents
2026-04-15 : OpenAI publishes next-generation Agents SDK harness direction
2026-08-13 : DeepSeek Harness repository / developer preview
2026-09-15 : TypeSafe launches Jev
2026-09-21 : Strands Harness launch
2026-09-25 : OpenShell 0.1.0 stability policy
2026-09-29 : Pydantic AI 2.52 integrates Harness release train
2026-10-01 : Pydantic AI 2.53
: Strands Decider 2B
Next : DeepSeek Harness 0.2.0 after current RC train
: OpenAI TypeScript / code mode / subagent work
: Deep Agents path to 1.0
: OpenShell weekly stable releases
The credible upcoming items should be distinguished from speculation.
DeepSeek Harness 0.2.0 is the most obvious near-term release train because 0.2.0-rc.2 is already published. A final 0.2.0 is therefore the logical next milestone, although the project has not published a date and its README still warns users to expect breaking compatibility. citeturn20search12turn20search8
OpenAI's stated Agents SDK direction includes TypeScript support for the newer harness architecture, code mode, subagents and additional sandbox providers/integrations. Those items are official roadmap direction, but the source does not commit to exact shipment dates, so they should not be represented as dated releases. citeturn1search4
Deep Agents 1.0 has unusually explicit criteria rather than a date: LangChain says it will consider the package ready for 1.0 when core APIs have stabilized through community feedback, production battle-testing has matured, and breaking changes are no longer expected for core functionality. Until then, minor releases can introduce changes that a typical post-1.0 user would expect to be breaking. citeturn19search7
OpenShell has the clearest release-process commitment: beginning with 0.1.0, NVIDIA describes a weekly stable release cadence, automated qualification, upgrade testing, API-change checks and backported security updates for supported prior minor versions. That is more important operationally than guessing an eventual 1.0 date. citeturn25search1turn25search5
TypeSafe's Jev roadmap is directional rather than versioned. TypeSafe says Jev is the first public System One model and indicates additional work/models are in the pipeline, while the service exposes jev-latest and preview aliases. There is not yet enough public roadmap detail to responsibly assign dates to the next architecture or model. citeturn5search0turn4search5
Strands is the ecosystem to watch most closely over the next quarter. Within months it has added TypeScript, context-management work, sandboxing/evals, a Harness Optimizer, a full Harness and then Decider 2B. The public changelog shows Python and TypeScript SDK releases continuing while the new Harness and CLI are only at the beginning of their own version histories. citeturn9search2turn9search8turn18search21
Emerging patterns, gaps, and recommendations¶
The most important pattern is the decomposition of the agent stack. In 2024, “agent framework” often meant a loop that alternated between an LLM and tools. In late 2026, the strongest systems increasingly look like:
model → decision/routing layer → harness → tools/MCP → sandbox/policy runtime → durable context/state → orchestration/operations → eval/observability.
DeepSeek and Strands make the harness explicit; OpenShell isolates execution authority; Paperclip sits above individual harnesses; Jev and Decider 2B suggest a specialized decision layer; Pydantic and Deep Agents combine many of those capabilities but keep them modular. citeturn20search8turn18search7turn20search3turn20search10turn5search1turn9search8
A second major pattern is composition replacing framework absolutism. Strands explicitly supports multiple providers and custom backends; Deep Agents runs over LangGraph and any compatible LangChain chat model; Pydantic exposes capabilities rather than demanding a separate hosted runtime; OpenShell does not care which agent it contains; Paperclip explicitly says it is not an agent framework and expects users to bring their own agents. Even the small HarnessRouter discussion argues that frontier harnesses should increasingly be consumed as infrastructure rather than continually reimplemented. citeturn18search6turn18search15turn7search9turn20search3turn20search10turn28search9
A third pattern is sandboxing becoming a first-class architecture boundary rather than a bash tool option. OpenShell is the strongest expression of this, but Pydantic's Bubblewrap support, OpenAI's sandbox direction and the repeated HN debates about keeping execution and credentials out of the untrusted environment all point the same way. Prompt-level “do not delete production” rules are not a security boundary. citeturn20search3turn7search5turn1search4turn28search1
A fourth is context engineering moving from chat history to a filesystem-like persistent substrate. Deep Agents puts files and context management at the center of the harness; Pydantic Harness supports explicit persistence and compaction; Strands is adding context managers and session support; Context Mode's rapid rise is itself evidence that tool output and context-window pressure have become an infrastructure problem. citeturn18search15turn7search9turn18search7turn19search4
A fifth is that one-model-does-everything is starting to look economically wrong. Jev's entire value proposition is to perform focused probabilistic judgments without generating prose, and Strands Decider 2B independently points toward the same architecture. The likely winning systems will cascade: deterministic code when possible, tiny/decision models for routine judgments, mid-tier generative models for ordinary tasks, and expensive reasoning models only when uncertainty or task complexity warrants escalation. Jev's independent benchmark results are encouraging enough to test this pattern, but also show why vendor-wide speed claims should not substitute for workload-specific measurement. citeturn5search1turn9search8turn31search3
The largest unresolved gaps are consequently no longer “does the framework support tool calling?” Nearly all serious contenders do. The harder gaps are portable session/context formats across harnesses; cross-harness handoff semantics; common permission/policy models; standardized, reproducible harness × model × tool benchmarks; deterministic recovery after partial failure; credential delegation; and genuinely portable eval traces. Recent HN discussion around HarnessRouter and empirical harness design directly reflects the fact that the optimal model/harness combination is conditional rather than universal. citeturn28search9turn28search5
For an upstream-first engineering organization, I would structure evaluation as follows.
The first evaluation lane should be Pydantic AI/Harness versus Strands versus Deep Agents. These three most directly answer, “What can we adopt instead of writing our own agent loop, context manager, subagent runtime, sandbox adapter, skills layer, or planner?” Pydantic is particularly attractive for strongly typed Python systems; Strands is attractive when provider portability and a small in-process harness matter; Deep Agents is attractive when a sophisticated file/context/subagent harness is desired immediately and LangGraph compatibility is useful. citeturn7search9turn18search7turn18search15
Microsoft Agent Framework should be the fourth baseline, especially where .NET interoperability, explicit enterprise workflows, A2A/MCP, managed hosting or long-term API stability matters. It should replace any temptation to construct a bespoke enterprise orchestration engine before the Microsoft upstream has been exhausted. citeturn1search1
OpenShell should be evaluated orthogonally to whichever harness wins. It solves a different problem. A Pydantic, Strands, Deep Agents, Claude or OpenAI agent could still need a deterministic sandbox/network/credential boundary. The fact that OpenShell is harness-neutral is an advantage: adopting it does not force the organization to own another agent framework. citeturn20search3turn25search5
Jev and Strands Decider 2B deserve a focused proof of concept as decision-plane components, not as replacements for a general agent. Good experiments would be tool routing, approval classification, “continue versus escalate,” candidate ranking, memory-write decisions, prompt-injection suspicion scoring and cheap preflight evaluation. Measure calibration, false-negative rates, latency and cost on your actual distributions; the early independent Jev results suggest the concept is real while also demonstrating that performance multipliers vary dramatically with the workload. citeturn5search1turn9search8turn31search3
DeepSeek Harness should be studied now but adopted cautiously. Its plugin architecture could become extremely influential, and the current release train is moving quickly. Yet its own maintainers say to expect rough edges and breaking changes. It is a strong candidate for architectural research, plugin experimentation and competitive benchmarking, not yet the obvious answer for a system where API stability outranks experimentation. citeturn20search8turn27search4
Paperclip should be evaluated only when the problem really is agent operations. If there are many persistent agents with goals, budgets, recurring tasks, approvals and organizational relationships, Paperclip may eliminate an enormous amount of custom operational software. If there are only a few request/response agents, its organization metaphor is unnecessary. Its own documentation explicitly says it is not an agent framework or generic workflow builder. citeturn20search10
Provider-native SDKs should remain optional adapters rather than architectural centers unless the provider-specific capability is the reason for choosing them. OpenAI Agents SDK's sandbox/realtime/handoff stack and Claude Agent SDK's Claude Code-class harness behavior can be excellent when their corresponding ecosystems are desired. But the Claude SDK's commercial licensing and recent HN concern around subscription-policy predictability illustrate why a portable application layer is valuable. citeturn1search4turn7search14turn28search11
The strongest practical shortlist for deeper evaluation is therefore:
Pydantic AI/Harness + OpenShell for a Python-first, typed and security-conscious default; Strands + OpenShell for a leaner model-neutral harness; Deep Agents + OpenShell when rich long-horizon context/subagent behavior is the priority; and Microsoft Agent Framework as the enterprise/control benchmark. Add Jev or Decider 2B above those as an experimental low-cost decision layer rather than building a custom classifier/orchestration model. DeepSeek Harness and Paperclip should remain active evaluations because their momentum and architecture are too significant to ignore, but neither should displace the more mature upstreams merely because its GitHub graph is hotter. citeturn24view1turn18search7turn19search5turn1search1turn25search5turn5search1turn20search8turn20search10