Head to head · Agent frameworks · October 2026 research run

BoxLang AI vs Terse Durable Actors

Terse Durable Actors and BoxLang AI score within a point of each other on agent readiness, 69.6 (B) and 69 (B). BoxLang AI leads on reliability, security & auth and transparency & trust. Both do agent frameworks.

Best agent frameworks and SDKs · All 190 frameworks comparisons

Which one, for what

BoxLang AI B

Best for Teams already running BoxLang or modernising CFML on the JVM who want agents, RAG and MCP with approval and guardrails in the same language

Ahead on

  • Reliability, 66 against 51
  • Security & auth, 71 against 49
  • Transparency & trust, 70 against 53

Also in its favour

  • No key needed to call it

Watch for

Runs only on BoxLang, a JVM language, so it suits teams already on BoxLang or CFML rather than Python or TypeScript stacks

Terse Durable Actors B

Best for Stateful actors for chat, collaboration and multi-agent coordination, as an open-source alternative to Cloudflare Durable Objects per its README.

Ahead on

  • Schema & documentation, 81 against 71
  • Agent ergonomics, 89 against 74
  • Payments & pricing, 90 against 75

Also in its favour

  • Free to start without a card
  • No incidents deducted, where BoxLang AI loses 3 points for them

Watch for

Version 0.18.7, with no stable release and no changelog file in the repository

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Security & auth BoxLang AI +22

BoxLang AI 71

Framework reading. 30 for what leaves the machine and credentials, 20 for approvals and sandboxing, 15 for prompt injection, 15 for audit and 20 for the security programme. No telemetry in the module's source, requests go only to configured providers, keys come from settings or environment variables, and request logging is off by default. 3.4.0 fixed a Gemini key leaking into logs through the request URL (27 of 30). Approval is enforced in code by HumanInTheLoopMiddleware with five policies, GuardrailMiddleware blocks tools by name and argument pattern, and stdio commands never use a shell. All of it is opt-in. allowedCommands allows any executable by default, FileSystemTools allows any path without allowedPaths, and the MCP server has no authentication unless configured (12 of 20). Unicode hygiene and fencing of ${context} are on by default, with opt-in input sanitiser, LLM judge and output guard. Streaming guards detect after the fact, which the changelog says (14 of 15). About 70 interception points, LoggingMiddleware, FlightRecorderMiddleware and MCP server statistics, with no OpenTelemetry export (11 of 15). CONTRIBUTING.md asks for reports to security@ortussolutions.com and the Slack #security channel. No security.txt (410), no bounty, and no published advisory found, while 3.6.0 lists a SQL injection fix in MySQL vector memory under Fixed (7 of 20). 71 in all.

Terse Durable Actors 49

One server secret, DURABLE_ACTORS_SECRET, as a bearer token for the API and MCP, plus an optional invoke-only key limited to public actor methods. With the secret unset the API is unauthenticated, which SECURITY.md warns about (15 of 30). The invoke-only key and the MCP read-only hints give some least privilege, with no confirmation step before invoke_actor (10 of 20). The OpenAPI file marks actor output as untrusted and to be rendered as plain text, with no guidance for agents on injected instructions (6 of 15). Request history, actor logs, WebSocket sessions and state versions tied to the request that saved them (12 of 15). SECURITY.md gives a private reporting address, security@useterse.ai. No bug bounty, certification or published advisories found (6 of 20). On GKE the self-hosting guide runs actors in gVisor sandbox pods with per-actor storage credentials. Total 49.

Transparency & trust BoxLang AI +17

BoxLang AI 70

Apache-2.0, OSI approved, though the licence file sits in src/main/resources rather than the repository root (30). The FAQ says prompts and history go to the chosen cloud provider and that Ollama keeps data local, and we found no telemetry in the source, but there's no statement for the module of what, if anything, Ortus receives. Ortus's privacy policy covers its website and customers and says data is collected when you use its products without naming which (15 of 30). Migration notes are dated in the changelog, and default models were moved off a Groq model on its removal date, but there's no written deprecation policy or support window (10 of 20). No telemetry statement either way in the docs (10 of 20). 65 in all.

Terse Durable Actors 53

MIT, copyright 2026 Terse (30). Self-hosted state stays in your PostgreSQL database and GCS bucket per the self-hosting guide. Terse's terms and privacy policy, both dated 14 May 2026, describe an earlier product of flows and workspaces, give no retention periods and don't mention Terse Cloud (10 of 30). No deprecation policy found, and SECURITY.md says older releases get no backports (0 of 20). SDK invocation telemetry is off by default and writes to standard error when enabled, and request spans and platform events are exported only to a collector the operator configures. No call to Terse's own hosts was found in the runtime or SDK source (18 of 20). Total 58.

Reliability BoxLang AI +15

BoxLang AI 66

Read with the local-software lines. Official package on ForgeBox, installed with install-bx-module bx-ai or box install bx-ai, with BoxLang 1.14.0 or later in box.json and JDK 21 in CONTRIBUTING.md, but the 3.6 announcement says BoxLang 1.18 or later (18 of 20). tests.yml runs about 140 test classes against Ollama and the vector stores in Docker Compose, and against paid providers on development and releases, on pull requests and pushes to development. Whether runs pass wasn't read, since WebFetch refused github.com (15 of 25). Open issues and replies weren't read for the same reason. The changelog closes issues #182 to #259 in 3.3.1 to 3.4.0, and bugs also go to Ortus's Jira (10 of 25). Keep a Changelog with semantic versioning stated and Migration sections, but breaking changes ship in minor releases (8 of 15). 3.6.0, past 1.0 (15). 66 in all.

Terse Durable Actors 51

Graded as local software, the runtime and SDKs you run yourself. The README and the Python SDK README install with bunx durable-actors or uvx --from 'durable-actors[cli]' and state Bun 1.4.2+ and Python 3.11+, and the release workflow publishes to npm. The registry pages were not read (15 of 20). A public CI workflow runs Rust, Python, TypeScript and example builds on every push and pull request. Whether it passes on main was not checked (15 of 25). 23 issues were open on 18 November 2026, mostly improvements and feature requests, with a few bug reports such as a constructor that keeps its SQLite writes after throwing (17 November) and alarms that run more than once (11 November) (18 of 25). Release notes are generated from pull-request labels on GitHub Releases, which were not read, and no changelog file or breaking-change notes were found in the repository (3 of 15). Version 0.18.7, not 1.0 or declared stable (0). Total 51.

Agent ergonomics Terse Durable Actors +15

BoxLang AI 74

Framework reading, scored on what a tool-calling agent with MCP takes. An agent with an MCP server is one aiAgent() call with mcpServers, and toolFilter and prefix limit what each server adds. Skills can load lazily, but autoLoadSkills is on by default and injects every SKILL.md under /.agents/skills into every agent (20 of 25). MaxToolCallsMiddleware caps tool calls, window and summary memory bound history by messages or tokens, withMaxResponseBytes caps MCP answers and listTools( cursor ) pages tools (17 of 20). Named exceptions (ProviderError, UnsupportedCapability, InvalidArgument, MCPCommandRefused, BXAI.SecurityViolation) but no reference page, and the changelog says a timed-out call still surfaces as a JSON parse error (12 of 20). RetryMiddleware with exponential backoff, approval resumes that don't replay the model call or rerun executed tools, and a stdio client that never repeats an in-flight call. MCP tool annotations such as readOnlyHint aren't read (15 of 20). An agent needs a name and works with defaults, and a mock provider runs with no key, but it is one language (10 of 15). 74 in all.

Terse Durable Actors 89

Ten MCP tools with one-line descriptions (25). Cursor paging with stated limits (1 to 100, or 1 to 500 for requests) and filters by actor, outcome, log level, text and time window (20). Errors carry a code and a message, start limits return named codes with Retry-After, and invalid MCP input says which characters are allowed (14 of 20). Nine tools carry readOnlyHint and invoke_actor carries destructiveHint, but invocations have no idempotency key (15 of 20). Local development needs one command and no credential, with official TypeScript and Python SDKs and generated typed clients (15). Total 89.

Payments & pricing Terse Durable Actors +15

BoxLang AI 75

Self-hosted rule, scored on the paid option. No payment protocol (0). BoxLang runtime plans are public without a login, Starter $749 a year and BoxLang+ and BoxLang++ from $1,999 to $4,999 a server or node a year, plan pricing rather than per unit (10). The Apache-2.0 module installs with no card (20) and no account or sign-up (20). 50 in all. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.

Terse Durable Actors 90

Read with the self-hosted rule, with the price line for Terse Cloud. No x402, MPP or L402 in the repository (0). Terse Cloud publishes per-second prices without a login, US$0.00001971 per CPU and US$0.00000667 per GiB of memory requested (30). The MIT runtime is free to run with no card (30). An agent can start the runtime locally with no signup (30). Total 90.

Schema & documentation Terse Durable Actors +10

BoxLang AI 71

Framework reading. A reference page for each built-in function with its arguments, and tool schemas generated from typed function arguments with required fields since 3.3.1. BoxLang is dynamically typed and no published API reference was found, though the repository builds DocBox API docs (15 of 25). llms.txt with about 150 entries and a Markdown copy of every page (10). The FAQ says when to use aiChat() or aiAgent() and the security guide says which guards to use when, though some FAQ links still say coming soon for pages that exist (14 of 20). Tool arguments are typed with required lists, and stdio options a server doesn't have throw InvalidArgument (11 of 15). About 100 example scripts in the repository and a gallery on ai.boxlang.io, but the production guide catches RateLimitException, TimeoutException and AuthenticationException, which the module's source never throws, and there is no exception reference (9 of 15). Keep a Changelog and a release-history page per version, but the 3.6.0 page still read unreleased on 1 November and two old versions appear twice in the changelog (12 of 15). 71 in all.

Terse Durable Actors 81

OpenAPI 3.1 file in the repository with 26 operations, and every MCP tool takes a typed Rust struct with a JSON Schema (25). Markdown docs in the repository, an AGENTS.md and an agent skill for setting up projects (10). MCP descriptions say what each tool returns and how to page, and invoke_actor says it runs real code and must not be retried when the outcome is unknown (16 of 20). Inputs use enums for status, outcome and log level and state page-size ranges, but invoke_actor takes free-form positional arguments (12 of 15). Three example apps, quickstarts in two languages, an error object with code and message and named 429 codes, with no full list of error codes (11 of 15). Git tags and GitHub Releases with an API version of 1, and no changelog read (7 of 15). Total 81.

Score by category

CategoryWeightBoxLang AITerse Durable ActorsEdge
Reliability16%6651BoxLang AI +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7181Terse Durable Actors +10
Agent ergonomics13%7489Terse Durable Actors +15
Security & auth14%7149BoxLang AI +22
Payments & pricing10%7590Terse Durable Actors +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8383even
Transparency & trust7%7053BoxLang AI +17
Negative events≤15-30
TotalB 69/100B 69.6/100

Facts side by side

FactBoxLang AITerse Durable Actors
KindAgent frameworkAgent framework
VendorOrtus SolutionsTerse
Hosted endpointno (local only)no (local only)
TransportsStreamable HTTP
AuthNoneAPI key
PricingFreeFreemium
x402nono
LicenceApache-2.0MIT
Tools exposednone10
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-202026-11-18
Terms last updatedno date given2026-05-14
Privacy policy last updatedno date given2026-05-14
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularitynone368 stars

How the scores have moved

Verdicts

BoxLang AI

A JVM agent framework with human approval, guardrail middleware and an MCP client over HTTP and stdio, all enforced in code, with three releases in the 90 days to 1 November 2026. It runs only on BoxLang, the stronger guards are opt-in, and minor releases have renamed public classes without a deprecation period.

Terse Durable Actors

Durable Actors gives coding agents ten compact MCP tools with read-only and destructive hints, a public OpenAPI 3.1 file and typed TypeScript and Python clients, under MIT with near-daily releases. It is pre-1.0 at 0.18.7, one server secret controls everything unless an invoke-only key is added, and Terse's policies predate Terse Cloud.

Before you call either

BoxLang AI

  1. Set mcp.stdio.allowedCommands to the executables you need. The default empty list lets any command start as a stdio MCP server.
  2. Pass allowedPaths when you create FileSystemTools. With none, its tools can read, write and delete anywhere the JVM user can.
  3. Attach HumanInTheLoopMiddleware with a checkpointer for tools that write or spend. Approval is opt-in.
  4. Create MCP clients with MCP() rather than the class, since 3.6.0 renamed MCPClient to MCPHttpClient without an alias.
  5. Use the mock provider to test agent wiring and guardrails with no API key or network.

Terse Durable Actors

  1. Call list_projects first and pass its projectId to every other tool
  2. Never retry invoke_actor when the outcome is unknown, because calls are not deduplicated and run real code
  3. Set DURABLE_ACTORS_SECRET before exposing a server beyond localhost, and send it as a bearer token
  4. Give backends that only call actors the invoke-only key, not the server secret
  5. On 429 actor_start_rate_limited, wait for the Retry-After seconds before starting another actor

Questions

Which is better for AI agents, BoxLang AI or Terse Durable Actors?

Terse Durable Actors and BoxLang AI score within a point of each other on agent readiness, 69.6 (B) and 69 (B). BoxLang AI leads on reliability, security & auth and transparency & trust.

Are BoxLang AI and Terse Durable Actors open source?

Yes. BoxLang AI is open source (Apache-2.0). Terse Durable Actors is open source (MIT).

Other comparisons with BoxLang AI or Terse Durable Actors

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.