scale-agentex vs trueforge
Scale AI's open agent platform: scaffold agents with a CLI, run them behind the ACP protocol with a dev UI, and graduate from sync chat to durable Temporal-backed long-running workflows. — versus — TrueFoundry's open agent harness: the runtime loop — model calls, MCP tools, SKILL.md packs, sandboxing, approvals, compaction — behind a chat UI, HTTP API, TypeScript SDK and embeddable UI.
Two open agent platforms with a server, dev UI and SDK. AgentEx graduates you to the ACP protocol and Temporal-backed durable workflows; TrueForge stays a batteries-included harness with sandboxing, approvals and context compaction built in.
| scale-agentex | trueforge | |
|---|---|---|
| Stars | 461 | 3.5k |
| Forks | 53 | 241 |
| Language | Python | TypeScript |
| License | Apache-2.0 | MIT |
| Last activity | 4 days ago | yesterday |
| Topics | agents, orchestration | agents, orchestration |
| Curated connections | 3 | 3 |
scale-agentex — the curator's take
Pick it when agents outgrow request/response: the async tier runs on Temporal, so long-running autonomous work gets durability, retries and resumability without changing your agent code's architecture — that L1→L5 'same framework at every level' pitch is the real differentiator. The local story is genuinely turnkey: ./dev.sh boots Postgres, Redis, Mongo and Temporal plus a dev UI, and `agentex init` scaffolds a working agent. NOT for a simple chatbot — that stack is heavy, and Python 3.12+/Docker are hard requirements. If you want multi-agent conversation patterns rather than deploy-and-scale infrastructure, a framework like CrewAI or AutoGen is the lighter tool. The enterprise 'zero-ops' path funnels into Scale's hosted SGP platform — fine, but know it.
trueforge — the curator's take
Take it when the agent logic is the easy part and you don't want to hand-build streaming, session persistence, tool auth, sandboxing and an approval UI: YAML catalogs configure models, MCP servers, skills and a sandbox once, then agents pick from what you connected. Context engineering is first-class — subagents, deferred tool loading, Code Mode, large-result offloading, compaction — and it scales from `npx` on SQLite to Postgres+Redis via Docker Compose or Helm. Caveats: local mode has no login and is explicitly not for anything internet-facing, sandboxing means Daytona today, and it's a harness rather than a graph framework — if you need bespoke control flow per step, a lower-level runtime fits better.