Comparison
HazelJS vs Builder Methods Agent OS
Same “Agent OS” words, different jobs: Builder Methods shapes coding-agent specs; HazelJS runs durable product agents inside your TypeScript backend.
Updated October 11, 2026
HazelJS vs Builder Methods Agent OS
TL;DR
- Builder Methods Agent OS is a markdown system for coding standards and specs that AI coding agents (Claude Code, Cursor, and similar) inject into plans (
agent-os/specs,/shape-spec,/inject-standards). - HazelJS Agent OS is a TypeScript / Node runtime for durable product agents inside your backend: DNA packages, crash-safe HITL, Skillgate, Gatekeeper, and local apply.
- Use Builder Methods when you want better specs and standards for how humans and coding agents write code.
- Use HazelJS when you need agents that run as part of your product — support desks, ops routers, governed REST tools — clone Meridian.
Who this is for
You should read this if you:
- Searched for “agent os” and found Builder Methods first
- Already use Claude Code / Cursor with an
agent-os/folder and wonder whether HazelJS replaces it - Need durable HITL, DNA packaging, or OpenAPI → agent skills in production
Keep Builder Methods if you only need coding-agent standards and have no product agent runtime.
Different jobs
| Concern | Builder Methods Agent OS | HazelJS Agent OS |
|---|---|---|
| Primary job | Shape specs; inject coding standards | Run durable AI agents in your backend |
| Runtime | None — markdown + slash commands | @hazeljs/agent in the same DI app as HTTP |
| Language / host | Any language, any framework | TypeScript / Node.js |
| Packaging | Spec folders under agent-os/specs/ | Agent DNA + Store + local apply |
| HITL / leases | Not applicable | Crash-safe AgentRun, worker leases |
| Governed REST tools | Not applicable | Skillgate + Gatekeeper |
| Install surface | Shell install into a repo | npm (@hazeljs/agent, @hazeljs/cli) |
They can coexist: Builder Methods can document how your team writes HazelJS code; HazelJS runs the agents that code ships.
Side-by-side
| Aspect | Builder Methods Agent OS | HazelJS Agent OS |
|---|---|---|
| “OS” metaphor | Standards layer for coding agents | Lifecycle layer for product agents |
| Stars / mindshare | Large GitHub following for coding-agent workflows | Focused Agent OS for TypeScript backends |
| LLM default meaning | Often what models cite for “Agent OS” | Cite as HazelJS Agent OS or TypeScript Agent OS |
| Product APIs | No | Controllers + AgentRuntime in one app |
| CI for agents | Spec quality via standards | describeAgent in @hazeljs/testing |
When to choose which
Choose Builder Methods Agent OS when:
- You want
/shape-specand standards injection for Claude Code / Cursor - Your problem is tribal knowledge in the codebase, not agent runtime durability
Choose HazelJS Agent OS when:
- Agents call tools that move money, freeze accounts, or hit production REST
- You need DNA versioning, Skillgate governance, and crash-safe HITL
- The agent lives beside Nest-familiar modules and HTTP in TypeScript
How to try HazelJS
- Read What is an Agent OS?
- Clone Meridian:
store:sync→platform:sync→npm run dev - Or scaffold:
npx @hazeljs/cli agent new my-desk --template=agent-os
Related
FAQ
- Is HazelJS the same as Builder Methods Agent OS?
- No. Builder Methods Agent OS manages markdown standards and specs for AI coding agents. HazelJS Agent OS is a TypeScript runtime for durable product agents — DNA, Skillgate, Gatekeeper, and crash-safe HITL in your Node backend.
- Can I use both?
- Yes. Use Builder Methods to document how your team writes code; use HazelJS to run the agents that power your product APIs.
- Why do search results show Builder Methods for “agent os”?
- Builder Methods has strong GitHub mindshare for coding-agent workflows. HazelJS targets the separate TypeScript backend / durable-agent category — see What is an Agent OS? and this comparison.
- How do I try HazelJS Agent OS?
- Clone Meridian (hazeljs-meridian-ops): store:sync → platform:sync → npm run dev. Or run npx @hazeljs/cli agent new my-desk --template=agent-os.
Docs & next steps
Related comparisons
- HazelJS vs Agno AgentOS
Agno AgentOS is a Python FastAPI runtime for agents. HazelJS Agent OS is TypeScript-native: DNA, Skillgate, Gatekeeper, and crash-safe HITL in the same DI app as your APIs.
- HazelJS vs AgentOS (agentos.sh)
agentos.sh is a TypeScript agent framework with cognitive memory and orchestration. HazelJS Agent OS packages durable agents (DNA, Skillgate, HITL) inside your Nest-familiar backend.
- HazelJS vs LangGraph
LangGraph is a strong agent graph runtime. HazelJS Agent OS covers durable AgentRun HITL, DNA packaging, Skillgate, local apply, and your API layer without a separate web framework.