All Modules
Install personaforge once and import the module you need from that package.
bash
npm install personaforgeHeadline API
ts
import { agent, defineAgent, compose, pipe, tool } from 'personaforge';Public module map
| Import path | What it exposes |
|---|---|
personaforge | Headline agent APIs, SDK helpers, custom tool helpers |
personaforge/tools | Integrations and toolkits |
personaforge/session | Session stores |
personaforge/knowledge | Knowledge engine, loaders, retrieval |
personaforge/memory | Memory stores and embedding-backed recall |
personaforge/guardrails | Safety validators and built-in rules |
personaforge/production | Production wrappers such as withResilience() |
personaforge/guard | Circuit breaker, rate limiter, health checks |
personaforge/runtime | HTTP runtime, auth, WebSocket transport |
personaforge/orchestration | Supervisor, routing, consensus, A2A |
personaforge/workflow | Workflow control-flow helpers |
personaforge/graph | Durable DAG execution |
personaforge/scheduler | Cron scheduling |
personaforge/reasoning | Reasoning engines |
personaforge/db | Framework-managed persistence backends |
personaforge/observability | Logging, tracing, metrics, eval helpers |
personaforge/llm | Provider classes and routing helpers |
personaforge/model | openai(), anthropic(), ollama() shorthand factories |
personaforge/skills | Pre-built skill bundles |
personaforge/processors | Mastra-style input/output/error processor pipeline |
personaforge/durable | Long-running, resumable agent execution with replay |
personaforge/goals | Durable, thread-scoped judge-scored objectives |
personaforge/code-mode | Sandboxed multi-tool computation |
personaforge/approval | Human-in-the-loop approval + suspended runs |
personaforge/gateway | createEnterpriseGateway() — multi-tenant, policy-enforced HTTP gateway with compliance dashboard |
personaforge/events | Typed event bus + core event vocabulary |
personaforge/registry | Agent registration, discovery, delegation toolkit |
personaforge/harness | evaluate() — A/B harness over agents/tasks/workflows |
Example imports
ts
import { agent } from 'personaforge';
import { TavilySearchTool } from 'personaforge/tools/search';
import { createSqliteStore } from 'personaforge/session';
import { GuardrailValidator } from 'personaforge/guardrails';
import { withResilience } from 'personaforge/production';
import { CircuitBreaker } from 'personaforge/guard';
import { createHttpService } from 'personaforge/runtime';
import { createGraph } from 'personaforge/graph';
import { ScheduleManager } from 'personaforge/scheduler';
import { ReasoningManager } from 'personaforge/reasoning';
import { createAgentDb } from 'personaforge/db';
import { ConsoleLogger } from 'personaforge/observability';
import { openai } from 'personaforge/model';
import { webResearchSkill } from 'personaforge/skills';Guidance
Use root imports for the common getting-started flow.
Use personaforge/<module> when you want a narrower import surface or a clearer ownership boundary in app code.
The repository is still implemented as a monorepo, so contributor docs and migration notes may refer to @personaforge/* workspace package names. Those internal names are not the public install story.