The Agent OS for TypeScript
Operate agents like production systems.
Frameworks help you build agents. HazelJS helps you run them — durable, governed, local-first.
Get started
Local Agent OS in minutes
Install CLI
$ npm install -g @hazeljs/cli- 1
Create an agent
$ hazel new agent support-agent - 2
Install deps
$ cd support-agent && npm install - 3
Apply (starts hazeld)
$ hazel apply
Install → Apply → Running · survives closing the terminal
Why an Agent OS?
Frameworks get you to a demo. An Agent OS keeps agents alive in production — durable runs, governance, and local apply in TypeScript.
01
Frameworks help you build
Prompt loops and tools get you to a demo.
02
Agent OS helps you operate
Durable runs, Gatekeeper, DNA, and HITL keep agents running for real.
03
Local-first TypeScript
hazel apply on your laptop. Cloud and Kubernetes are optional.
Five layers. One Agent OS.
Define → Run → Decide → Govern → Survive — inside your TypeScript backend.
Architecture
Inside HazelJS Agent OS
Define & Deploy
Version identity, prompt, skills, and policies as DNA. Declare desired state with Store/Apply — tools stay in TypeScript.
Run
Agent Runtime executes the loop. Agent VM classifies effects and enables speculation/undo. Organism self-organizes specialists from a mission and environment signals.
Decide
Bounded closed-set judgment before side effects. Evidence, judge, critic, and confidence inform policy — never authorize. Default provider is native hazel-agent, not an external-model wrapper.
Govern
Skillgate curates which APIs become capabilities. Gatekeeper authorizes each tool call — default deny, approvals, rewrite.
Survive
Durable runs, crash-safe HITL, leases, state, and recovery — so agents outlive process restarts.
TypeScript / Node.js Backend
Runs beside your APIs — local-first, no separate runtime plane required.
Define → Run → Decide → Govern → Survive
Explore
Build your first agent
Five minutes on your laptop. Apache 2.0. No cloud required.