AgentOS is a free, open source ai development platforms project written in TypeScript and released under Apache-2.0. It has 667 GitHub stars, 97 forks and 10 open issues, and was last pushed 6 days ago. On this registry it ranks #60 of 61 tracked projects in AI Development Platforms, with 5 head-to-head comparisons available. It gained 44 stars over the last 6 tracked days.

What is AgentOS?

AgentOS is an open-source TypeScript framework, published on npm as @framers/agentos, for building autonomous AI agents that remember, adapt, and write their own tools.

What it is

AgentOS is a TypeScript framework for building autonomous AI agents, distributed under the Apache-2.0 licence and maintained in the framerslab/agentos repository. It lives in the JavaScript and TypeScript ecosystem, requires TypeScript 5.4 or newer, and installs as a single npm package. The framework is built around three concerns that its authors treat as one system: persistent cognitive memory, runtime tool creation, and coordination between multiple agents. The project is also an NVIDIA Inception member and publishes benchmark results through a separate repository, framerslab/agentos-bench.

The concrete problem it addresses is session amnesia in long-running agent deployments. Most agent libraries hand a model a conversation history and lose everything when the process ends, and most require the developer to pre-declare every tool an agent may call. AgentOS replaces both patterns. It provides a persistent memory layer modelled on eight neuroscience-backed mechanisms, including Ebbinghaus decay, retrieval-induced forgetting, reconsolidation, and source-confidence decay, so that what an agent retains degrades and reconsolidates rather than accumulating forever. Alongside that, it replaces the static tool registry with a forge: an agent writes a TypeScript function with a Zod schema, an LLM judge approves it, and the function runs in a hardened node:vm sandbox before joining the catalog for the remainder of the session.

Key capabilities

  • Persistent cognitive memory driven by eight neuroscience-backed mechanisms, including Ebbinghaus decay, retrieval-induced forgetting, reconsolidation, and source-confidence decay.
  • Runtime tool forging, where an agent writes a TypeScript function with a Zod schema, an LLM judge approves it, and the function executes in a hardened node:vm sandbox before joining the session catalog.
  • One dispatch interface across 11 LLM providers, with the provider auto-detected from the environment when the provider option is omitted.
  • Optional HEXACO personality traits, configured as numeric dimensions such as openness and conscientiousness in the agent definition.
  • Six orchestration strategies for multi-agent collaboration, exercised in the repository by examples/emergent-hierarchical-spawning.mjs.
  • Guardrails and a voice pipeline, listed among the framework's documented feature areas.
  • Startup auto-loading of 100 or more extensions and 88 skills.
  • Published memory benchmarks of 85.6% on LongMemEval-S at $0.0090 per correct answer with gpt-4o, and 70.2% on LongMemEval-M.

Who uses it and how

  • Teams building long-running assistants that must retain context across sessions rather than resetting to a blank history at each invocation.
  • Developers working in TypeScript who want agent definitions expressed as typed code, with a Zod schema gating any function an agent writes for itself.
  • Projects that need to switch or spread load across model providers, since a single dispatch interface covers 11 providers and resolves a default model per provider, such as claude-sonnet-4-6 for Anthropic unless a specific model is pinned.
  • Builders of multi-agent systems, who can apply one of six orchestration strategies and reproduce hierarchical spawning from the bundled example.
  • Applications that want configurable agent temperament, expressed through optional HEXACO personality dimensions.

Getting started

Install the package with npm install @framers/agentos, then import the agent function and construct an agent with a provider, instructions, optional personality traits, and a memory configuration. The provider can be supplied explicitly or detected from the environment, and the framework auto-loads its extensions and skills at startup.

How it compares

The facts provided for this page do not name any other tool, paid or otherwise, that AgentOS is positioned against, so no product-by-product contrast can be drawn. It stands alone in this registry on the basis of the material available.

When to use it — and when not to

Choose AgentOS when an agent needs durable memory across sessions or needs to extend its own toolset without a developer writing each function in advance, and when the application is Node-based, since runtime tool forging depends on node:vm. Skip it if the target runtime is a browser or an edge environment where node:vm is unavailable, or if the project requires documentation of self-hosting infrastructure, because the material provided does not identify any backing database, object storage, or mail service that a self-hoster would have to operate. The README also does not describe a hosted option, so adopting AgentOS means running it inside an application the adopter already controls.

project readme (upstream, from github) — read inline
AgentOS: TypeScript AI Agent Framework with Cognitive Memory

AgentOS · TypeScript AI Agent Framework

Agents that remember, forge their own tools, and survive long-running sessions. Persistent cognitive memory, optional HEXACO personality, multi-agent orchestration, and one dispatch interface across 11 LLM providers. Apache-2.0.

npm CI tests codecov TypeScript License NVIDIA Inception LongMemEval-S LongMemEval-M agentos-bench Discord

Benchmarks * Website * Docs * npm * Discord * Blog


AgentOS is an open-source TypeScript framework for AI agents that remember, adapt, and write their own tools.

  • Top open-source memory benchmarks: 85.6% on LongMemEval-S at $0.0090/correct (gpt-4o), and 70.2% on LongMemEval-M, the only open-source library above 65% on M with reproducible methodology.
  • Runtime tool forging. An agent writes a TypeScript function with a Zod schema, an LLM judge approves it, and it runs in a hardened node:vm sandbox before joining the catalog for the rest of the session.
  • Persistent cognitive memory with 8 neuroscience-backed mechanisms: Ebbinghaus decay, retrieval-induced forgetting, reconsolidation, source-confidence decay.
  • Optional HEXACO personality, 6 orchestration strategies, guardrails, and voice across 11 LLM providers; 100+ extensions and 88 skills auto-load at startup.

Three AgentOS agents with distinct HEXACO personalities collaborate on a code review, forge a new tool at runtime once they hit a gap their static toolkit can't cover, the LLM judge approves the spec, and all three invoke it on the next turn.

Runtime tool forging + multi-agent collaboration. Reproduce with node examples/emergent-hierarchical-spawning.mjs.


Install

npm install @framers/agentos
import { agent } from '@framers/agentos';

const tutor = agent({
  provider: 'anthropic',                          // resolves to claude-sonnet-4-6 (provider default)
  // model: 'claude-opus-4-8',                    // pin a specific model to override the default
  instructions: 'You are a patient CS tutor.',
  personality: { openness: 0.9, conscientiousness: 0.95 },
  memory: { types: ['episodic', 'semantic'], working: { enabled: true } },
});

// Provider auto-detected from env when `provider` is omitted.

const session = tutor.session('student-1');
await session.send('Explain recursion with an analogy.');
await session.send('Can you expand on that?'); // remembers context

Full quickstart * Examples cookbook * API reference

Sessions in 0.10. Sessions carry a lossless conversation transcript — assistant tool calls, tool results, thinking blocks — independent of the memory subsystem, bounded by default (whole-block eviction past a ~120K-token estimate). memory: false no longer makes a session stateless; pass history: false for that. Long tool-driving loops get session.reseed(snapshot) (atomic history replacement with in-flight epoch guarding), session.messages() as checkpoint material, and per-send generation overrides (toolChoice, requestTimeout, cache, cacheDiagnostics, blockLabel):

// Before 0.10 — stateless unless memory was on:
const s = agent({ model, memory: false }).session('job-1'); // kept no history

// 0.10 — sessions remember by default; opt out explicitly:
const stateless = agent({ model, memory: false, history: false }).session('job-1');
const bounded = agent({ model, history: { maxTokens: 60_000 } }).session('job-2');
bounded.reseed([{ role: 'user', content: 'compact resume snapshot' }]);

Cache note: history byte-stability holds for the stored transcript between eviction events; the wire request can still legitimately differ when dynamic memory context or message-mutating hooks inject per-call content.


Emergent Design

Three things accumulate across a session and compose into behavior: memory (what was said, decided, retrieved), the tool surface (which grows when an agent forges a tool the judge approves), and an optional HEXACO personality vector that biases retrieval, routing, and decisions. Each is configurable and observable.

Runtime tool forging. When no tool covers a sub-task, the agent writes a TypeScript function with a Zod schema; a separate LLM judge approves it; it runs in a hardened node:vm sandbox (5s wall clock, no eval/require/process), then joins a discoverable index for the rest of the session. First forge costs full tokens; reuse costs tens. Promoted tools export as SKILL.md skills. Emergent capabilities ->

HEXACO personality (optional). Off by default; the runtime behaves identically without it. When supplied, the kernel weights retrieval, specialist routing, and tool selection by trait values, so the same prompt and tools yield measurably different decision sequences. It lives in the kernel, not the prompt, so it persists under context pressure. HEXACO docs ->

Soul files. Identity, voice, hard limits, and HEXACO scores can live in a SOUL.md workspace. Its memory/ directory is a markdown wiki (an index.md catalog plus entities/, concepts/, log/ pages with [[wikilinks]]) that is the agent's long-term memory: markdown is the source of truth, the vector/graph index is rebuilt from it, and souledAgent() wires it end to end. Soul Files ->

import { souledAgent } from '@framers/agentos';

const aria = await souledAgent({ provider: 'anthropic', soul: '~/.agentos/agents/aria' });

Memory Benchmarks

gpt-4o reader, gpt-4o-2024-08-06 judge, full N=500, single-CLI reproduction with bootstrap 95% CIs and per-benchmark judge-FPR probes.

  • LongMemEval-S: 85.6% at $0.0090/correct, 3,558 ms p50: +1.4 points over

readme truncated — read the full docs on github

Frequently asked questions

Is AgentOS free to use?

AgentOS is open source under the Apache-2.0 licence. There is no licence fee and no seat count — you can self-host it or, where the project offers one, pay a vendor for a managed version instead.

What does AgentOS do?

TypeScript framework for building autonomous AI agents

What is AgentOS written in?

AgentOS is primarily written in TypeScript. Its source is publicly available at https://github.com/framersai/agentos, and it has 667 GitHub stars.