ForthAI
The platform

The ForthAI WorkOS.

A horizontal layer beneath your systems of record — not a chatbot bolted on top.

Governance & trustgoal in ↓ · result out ↑
Interface
Reach your agents where your team already works — and sign-off happens here.
Native
The ForthAI WorkOS app — chat, voice, and approvals in one place.
WhatsApp
Message your agent like any other contact.
Email
Forward or CC a request; the agent picks it up.
Telegram
Chat and sign off from a Telegram thread.
Agent layer
AI workers that plan the job, carry out the steps, and keep track.
Plan & Orchestration
Breaks the goal into steps and assigns sub-agents.
Execution
Carries out each step — retries, escalates when stuck.
State Management
Tracks progress so long jobs survive interruption.
Memory layer
Your business as a typed Context Graph — objects, how they connect, and the actions allowed on each — that every job makes sharper.
Data
Raw records and events, as they happened.
Information
Facts in context — structured and searchable.
Knowledge
Facts and policy resolved into the Context Graph agents reason over.
Wisdom
What worked before — judgment from outcomes.
Tool layer
Internal and external tools — only pre-approved actions, every call logged.
Pluginsinternal
First-party capabilities, built into the platform.
Connectorsinternal
Governed bridges into your own systems.
MCP serversexternal
Standards-based external tools, same guardrails.
Systems of action
Where the work lands — writes go through governed connectors.
ERP
Orders, invoices, inventory.
CRM
Accounts, pipeline, service.
SCM
Suppliers, purchasing, logistics.
OA
Docs, approvals, comms.
Analytics

Measures every job across the business.

Business
Revenue, pipeline, win rate.
Operations
Throughput, SLAs, backlog.
HR
Headcount, attrition, time-to-hire.
Financial
Spend, cost per job, variance.
Productivity
Hours saved, adoption, cycle time.
Governance

Wraps every layer — nothing runs outside it.

Observability
Every step traced and logged.
Guardrails
Policy checks before any action runs.
Safety
Approvals, rollback, kill-switch.
Self-evolution

Every run makes the next one better.

The agent and memory layers support each other in both directions — agents index past workflows into memory, and memory hands sharper rules back for the next run.

Agent layer

Examines its own execution traces after every job — what worked, what stalled, what a human had to fix.

execution traces
improved rules
Memory layer

Indexes every past workflow and distills it into rules and playbooks the next run starts from.

Workflow indexing

Every completed job is indexed into memory — searchable, reusable.

Self-reflection

Agents review their own traces and propose improvements to their rules.

Human feedback

Approvals and corrections become signal — folded back into the playbook.

In practice

One request, end to end.

You make one request. Agents and memory work it together, tools carry it out — and the result comes back to you.

01
you
One request
Chase every invoice more than 30 days overdue.

Instructions in Layman’s terms.

02–06Human in the Loop
Agents × memory take it from here
02
agents
An orchestrator breaks the goal into a plan and spins up three sub-agents: scan, draft, follow up.
Clarification: “Include accounts already on payment plans?” — you answer in one line, the plan updates.? clarified
03
memory
The sub-agents pull what they need from knowledge: the overdue ledger, your credit policy, last quarter’s playbook.
04
agentsmemory
One action drafted per account, each checked against policy. Two large accounts trip the credit-hold workflow.
05
workflowhuman
It routes those two to your credit manager for sign-off — nothing lands back on your desk.
Credit manager reviews the two holds — approve, edit, or reject in one tap.✓ 2 approved
06
tools
Schema-validated calls do the work: ERP notes, reminder emails, payment plans.
Sign-off: the outgoing batch is summarized for you — nothing sends until you sign off.✓ signed off
a human can watch, pause, or take over at any step
07
you
Result comes back

40 invoices chased, 2 signed off by your credit manager — and the record of every step.

who · what · when · why
Start here

Start with the smallest win.

One working session is enough to find it.