Why AGBoss?
AGBoss makes building LangGraph agents in TypeScript faster, easier to read and safer to change. You declare what each component is; the framework wires them into a graph and gives every run tests, traces and a price tag.
AGBoss is declarative
Agents, tools, routers and workflows are classes with a decorator. Dependencies arrive through the constructor, the workflow wires them into a graph.
The code reads like the diagram you would have drawn, so it’s quick to write and quick to review.
AGBoss is testable
Every component can be unit-tested with the model and tools stubbed out. Configurations can be compared side by side, so a prompt change is an A/B test, not a guess.
AGBoss is observable
Each run is traced end to end, and the trace link sits right under the answer. You see which agent ran, what it called and why it routed where it did.
AGBoss is cost-aware
Token spend is part of the result of every turn. Budgets are reserved before a run starts, so one runaway conversation can’t drain the account.
AGBoss is lock-in free
It embeds into the Node.js backend you already have. Bring your own HTTP server, database and model provider; nothing has to move to a new platform.
AGBoss is LangGraph
Under the decorators it’s a regular LangGraph graph. Everything LangGraph can run, AGBoss can run; it just takes the wiring off your hands.
What you can build
Routing & multi-agent
Send each request to the agent that should handle it.
Guide comingTool-using agents
Typed tools and MCP servers, called from configuration.
Guide comingKnowledge bases
Ground answers in your own documents, with a store you choose.
Guide comingHuman approval
Pause before a risky step and resume once a person says yes.
Guide comingReady to get started?
Build and run your first agent in a few minutes.