Head to head · Agent frameworks · October 2026 research run

guilds.run vs Terse Durable Actors

Terse Durable Actors scores 69.6 (B) on agent readiness against guilds.run's 57.2 (C), and leads in 4 of 7 scored categories. guilds.run leads on security & auth and transparency & trust. Both do agent frameworks.

Best agent frameworks and SDKs · All 190 frameworks comparisons

Which one, for what

guilds.run C

Best for A person or small team that wants a standing, inspectable team of agents with schedules, shared tables and a web app, run on one machine, and is comfortable tracking main.

Ahead on

  • Security & auth, 68 against 49
  • Transparency & trust, 60 against 53

Watch for

No tagged release, version number or published image on 4 November 2026. Users install whatever is on main, including breaking changes

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

  • Reliability, 51 against 43
  • Schema & documentation, 81 against 58
  • Agent ergonomics, 89 against 67
  • Maintenance & community, 83 against 21

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.

Maintenance & community Terse Durable Actors +62

guilds.run 21

No tagged release, version or dated changelog entry. Main, which the install clones and SECURITY.md names as the supported version, last changed on 3 November 2026 (1,072 of the commits since 14 October by one author), but commits with no version or tag aren't releases in this run (hyperqwen, brave-search-mcp), and CONTRIBUTING.md itself defines a release as a vMAJOR.MINOR.PATCH tag, so nothing has been released (0, from 20). No releases or dated changelog entries in the 90 days from 6 August (0). Issues and pull requests per the 14 October check (eight, all closed, the three issues within an hour), not re-read on 4 November (15 of 25). No published package (0). CI on every push with a frozen pnpm lockfile, and still no Dependabot configuration in the repository (6 of 10). 0 + 0 + 15 + 0 + 6 = 21.

Terse Durable Actors 83

v0.18.7 tagged on 18 November 2026, the day of the check (30). 118 tags since v0.1.0 on 2 September 2026, with eight between 15 and 18 November (20). 23 open issues, three of them with long threads (7, 9 and 15 replies) and most with none. Pull requests from five outside contributors were merged between 2 October and 3 November 2026, and CONTRIBUTING.md says GitHub issues are triaged into the team's tracker (10 of 25). Current official TypeScript and Python SDKs at 0.18.7. The MCP endpoint is self-hosted and not in the official registry, which was not searched (15). CI with pinned action versions and lockfiles for Bun, Cargo and uv (8 of 10). Total 83.

Schema & documentation Terse Durable Actors +23

guilds.run 58

Framework reading. No OpenAPI document for the HTTP API. The recipe format guilds.recipe v2 rejects unknown keys, and connector manifests are validated with TypeBox at load (12 of 25). No llms.txt on docs.guilds.run (404 on 4 November). The docs are Markdown in the repository with an AGENTS.md (5 of 10). Pages state what the code does today, which page to read for which job, and the trust boundary in numbered rules (15 of 20). Tool input schemas, recipe caps and typed manifest fields (11 of 15). The getting-started walk says what you should see at each step, and the Operate page explains each startup error message (11 of 15). CHANGELOG.md (since 15 October) holds only an Unreleased section with no version or date, and the security register keeps dated history (4 of 15, the earlier partial kept). 12 + 5 + 15 + 11 + 11 + 4 = 58.

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.

Agent ergonomics Terse Durable Actors +22

guilds.run 67

Framework reading, scored on what it takes to run a tool-calling team with MCP. No code is needed. Three commands and a model key start a guild, and each agent is offered only the tools turned on for it (18 of 25). max_tool_calls defaults to 50 per run, max_input_tokens trims old tool results and hands off to a new run, and remaining_tool_calls is appended to each result after the platform cap (15 of 20). Runs end with named codes such as generation.max_tool_calls and workspace.full, and interrupted tool calls get an error result so the next model request is valid (13 of 20). readOnlyHint and destructiveHint are stored for each MCP tool and writing tools start Off. Startup does not replay a model call (14 of 20). Sensible defaults and a guided first-run dialogue, but it is an application with an HTTP API and no SDK in any language (7 of 15). Confirmed on 4 November in the clone (max_tool_calls default 50, 200 for a new coding agent).

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.

Security & auth guilds.run +19

guilds.run 68

Framework reading. 30 for what leaves the machine by default, 20 for approvals and sandboxing, 15 for prompt injection, 15 for audit and 20 for the security programme. Model keys go only to their provider and Sentry starts only when SENTRY_DSN is set, with user info, bodies and model inputs and outputs excluded. Graft left the runtime image on 13 October (SEC-9), so its version lookup is gone, but the box fetches the models.dev catalogue on first read and hourly (switch MODELS_DEV_URL, documented) and the OAuth pages load Google Fonts (27). Each machine is an OpenSandbox container with dropped capabilities and no_new_privileges, writing MCP tools start Off and Studio changes wait for the operator. Agents on one machine share it and run commands as root with open egress (SEC-6, SEC-24), no per-call approval gate for tool calls was found, and the default AUTH_MODE compat-cookie has no login (10). The coding prompt says repository content is data, Studio wraps evidence as untrusted, and known secret values are redacted from transcripts. SEC-8, injection into coding agents, and SEC-47, GitHub content steering writes, are open (8). Every run keeps the prompt, each tool call and result, and versioned memory with who changed it (14). SECURITY.md with GitHub private reporting and no acknowledgement time, and a public register of 58 issues on 4 November with exposure and residual risk, 28 still open (18 open, 10 open and accepted). No security.txt (404), bounty or published advisory (9). 27 + 10 + 8 + 14 + 9 = 68. Sixteen register fixes dated 17 October to 3 November are on main with no release and no advisory; no term, because packages is empty and there is no hosted product, as ayrshare's plugin fix was read.

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.

Reliability Terse Durable Actors +8

guilds.run 43

Read with the local-software lines, because the owner runs it. Docker with Compose is the stated requirement, and the install is a git clone of main plus ./setup.sh, which builds the images. No package, tagged release or published image exists, since the image workflow runs only on a v* tag and the remote still has none on 4 November 2026 (10 of 20, the earlier partial kept). The verify workflow runs scripts/check.sh on every push, with typecheck, lint, orchestrator, UI and web tests and a smoke test of the Compose stack, and the clone has 356 test files. GitHub's Actions pages and API answered 403 on 4 November, so the pass state on main is unread (15 of 25, down from 25 on the 14 October reading of 13 passing runs). Open issues per the 14 October check, not re-read on 4 November (18 of 25). CHANGELOG.md, added on 15 October, marks each change no impact, rebuild or breaking and CONTRIBUTING.md defines a semver tag policy, but no version has been cut (0, the earlier value kept). Not versioned or declared stable (0). 10 + 15 + 18 + 0 + 0 = 43.

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.

Transparency & trust guilds.run +7

guilds.run 60

AGPL-3.0-only, OSI approved (30). No privacy policy or terms. The footer still links to both and they returned 404 on 4 November 2026. The docs say where data lives (PostgreSQL and STATE_ROOT on your host), that model keys go only to their provider, and that stored credentials are encrypted under one master key in .env (12 of 30). No deprecation policy or dated notices. CHANGELOG.md marks breaking changes with steps, undated, and the security register is dated (3 of 20, the earlier partial kept). Sentry is opt-in and documented on the Configure page, and the models.dev catalogue fetch and the connector registry address are documented with their switches (18 of 20). 30 + 12 + 3 + 18 = 63.

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.

Score by category

CategoryWeightguilds.runTerse Durable ActorsEdge
Reliability16%4351Terse Durable Actors +8
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5881Terse Durable Actors +23
Agent ergonomics13%6789Terse Durable Actors +22
Security & auth14%6849guilds.run +19
Payments & pricing10%9090even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%2183Terse Durable Actors +62
Transparency & trust7%6053guilds.run +7
Negative events≤15-20
TotalC 57.2/100B 69.6/100

Facts side by side

Factguilds.runTerse Durable Actors
KindAgent frameworkAgent framework
VendorCigale AITerse
Hosted endpointno (local only)no (local only)
TransportsStreamable HTTP
AuthAPI keyAPI key
PricingFreeFreemium
x402nono
LicenceAGPL-3.0-onlyMIT
Tools exposednone10
Read-only variant documentednono
llms.txtnoyes
Last releasenone2026-11-18
Terms last updatedno document linked2026-05-14
Privacy policy last updatedno document linked2026-05-14
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetyes
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetyes
Arbitration or class-action waivernot read yetnot found in the text
Popularity57 stars368 stars

How the scores have moved

Verdicts

guilds.run

A self-hosted multi-agent system that records each run's prompt, tool calls and memory changes, with per-agent models and tools and no telemetry by default. It has no tagged release, version or package, so users track main, its own security register lists 28 open issues of 58, and the site's terms and privacy links return 404.

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

guilds.run

  1. Keep the box on loopback or behind an authenticating proxy with AUTH_MODE=trusted-header. The default mode does not authenticate
  2. Put agents that hold different secrets or GitHub tokens on different machines. Agents on one machine can read each other's homes and tokens
  3. Back up the .env file written by ./setup.sh. It holds the only copy of the key that encrypts stored credentials
  4. Pin a commit of main when you deploy and read CHANGELOG.md's Unreleased section before pulling. Breaking changes land on main
  5. Set MODELS_DEV_URL empty for an offline box. The model catalogue is otherwise fetched from models.dev hourly

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, guilds.run or Terse Durable Actors?

Terse Durable Actors scores 69.6 (B) on agent readiness against guilds.run's 57.2 (C), and leads in 4 of 7 scored categories. guilds.run leads on security & auth and transparency & trust.

Are guilds.run and Terse Durable Actors open source?

Yes. guilds.run is open source (AGPL-3.0-only). Terse Durable Actors is open source (MIT).

Other comparisons with guilds.run 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.