Head to head · Agent harnesses · October 2026 research run

Auggie CLI vs OpenAI Agents API

OpenAI Agents API scores 73.3 (BB) on agent readiness against Auggie CLI's 49.3 (D), and leads in every scored category. Both do agent harnesses.

Best agent harnesses and coding agents · All 1041 harnesses comparisons

Which one, for what

Auggie CLI D

Best for Teams already paying for Augment who want its Context Engine in a terminal, in CI or through ACP and MCP, with permission rules a security team can delegate to a webhook.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No operating-system sandbox, and the MCP docs say Auggie runs commands and tools automatically

OpenAI Agents API BB

Best for Teams that want OpenAI to run the agent loop, with sandboxes, MCP tools and subagents, and are fine with a beta API, US-only data residency and no Zero Data Retention.

Ahead on

  • Reliability, 60 against 43
  • Schema & documentation, 88 against 67
  • Agent ergonomics, 80 against 65
  • Security & auth, 87 against 47
  • Payments & pricing, 30 against 20
  • Maintenance & community, 87 against 38
  • Transparency & trust, 85 against 59

Also in its favour

  • Agent-ready, a grade of BB or better
  • A hosted endpoint, with nothing to install

Watch for

Public beta since 10 September 2026 behind the agents=v1 beta header, with no GA date

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 OpenAI Agents API +49

Auggie CLI 38

Graded on the stable line, as the brief asks. 0.36.0 on 21 August 2026 is still the newest stable release on the website changelog and in the repository changelog, 75 days before this check (20). In the 90 days from 6 August 2026 the stable line has two dated releases, 0.35.0 on 13 August and 0.36.0 on 21 August. The 1.2.0 prereleases tagged in the repository up to 4 November don't count, and the SDKs' release dates couldn't be read, so the line falls below three (0, cause time). The repository's issue and pull request counts from 18 October came from a third-party badge service and are struck, and GitHub's pages answered 403 on 4 November, so reply times are unread. A support portal, a subreddit and a dated website changelog. Earlier partial value kept and flagged (6). TypeScript SDK 0.2.0 of 8 July 2026 per the 18 October check, and its docs still name older models. The Python SDK's version couldn't be read (8). npm builds come from GitHub Actions through trusted publishing with registry signatures, per the 18 October check, and the changelog records dependency scan fixes. No public CI for the CLI (4). 20+0+6+8+4 = 38.

OpenAI Agents API 87

Closed API. Last dated change 16 October 2026, Ultrafast mode and document skills (30). Four dated changelog entries in the 57 days since release, 10 September, 29 September, 9 October and 16 October (20). Changelog and help centre, as the openai-api listing reads them (12 of 15). Official SDKs carry beta.agents (15). SDK CI, per the openai-api listing (10). 30 + 20 + 12 + 15 + 10 = 87.

Security & auth OpenAI Agents API +40

Auggie CLI 47

Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines as for the other harnesses. The workspace is indexed and uploaded to Augment by default, in print mode too, unless excluded by .gitignore or .augmentignore. A telemetry endpoint is listed with no description or opt-out found. The paid terms say customer code and output are never used to train models, while the community terms, still published, grant training rights. Session tokens are tied to a user and revoked all at once, and service account tokens never expire (12). Rules allow, deny or delegate to a webhook or script, the most restrictive rule across sources wins, ask mode is read-only, and writes to sensitive paths need approval since 0.34.0. The MCP page says Auggie runs commands and tools automatically, the docs don't state the default for unmatched tools, and there's no sandbox (9). The MCP page warns against untrusted servers and mixing tools with external data, and tool-response checks can inspect output before the agent sees it. No network control was found (6). Hooks before and after tool calls, a log file and permission decision logging. Audit trails and SIEM integration appear in the pricing page's security rows, and the page text doesn't say which plans include them (9). A disclosure address and GitHub private reporting in SECURITY.md, SOC 2 Type II and ISO/IEC 42001 named. No security.txt and no bug bounty found. On 4 November osv.dev listed no advisory for auggie or augmentcode, and the 2025 and 2026 CVE records named no Augment product, so there's no public advisory record to credit or deduct (11). 12+9+6+9+11 = 47.

OpenAI Agents API 87

Project keys with restricted per-endpoint permissions, service accounts and workload identity, per the openai-api listing; we didn't confirm a key can be limited to /v1/agents (27 of 30). Automatic review for approvals, a sandbox network restricted to a host allowlist, vaults for secrets and a sandbox security guide (17 of 20). The agent reads web pages, MCP results and browser content; the sandbox security guide and approval flow are the mitigations, with no prompt-injection guide of its own found (8 of 15). Tracing, observability and usage per session and admin audit logs (15). SOC 2 Type 2, ISO 27001 family, Bugcrowd bounty and a disclosure policy, per the openai-api listing (20). Not ZDR-eligible and US residency only, recorded under transparency. 27 + 17 + 8 + 15 + 20 = 87.

Transparency & trust OpenAI Agents API +26

Auggie CLI 59

Proprietary. The licence is clear on subscription, redistribution and modification, but it says commercial use needs a separate agreement while plans are sold to businesses, and it names Augment Computing, Inc., which sold the CLI to Harness on 8 October. On 4 November the licence, terms and privacy policy still named Augment Computing, Inc., while the website footer read Harness, Inc. (12). The paid terms rule out training on customer code and treat it as confidential. The privacy policy (28 August 2025) gives no retention periods and lists no subprocessors, referring both to a request, and the docs say indexed code is stored by Augment without a retention period (12). The 1.x guide lists breaking changes and retired parts, and the terms promise no materially reduced functionality during an order, but no date for 1.x becoming the default and no notice period were found (8). A telemetry endpoint is disclosed on the network page, with no description of what's sent and no opt-out (3). 12+12+8+3 = 35.

OpenAI Agents API 85

Closed service with clear terms, Apache-2.0 SDKs (15). Session state retained until deleted, deletable sessions and artifacts, not ZDR-eligible, US residency only, and the data-controls guide agrees; no retention period for artifacts after a sandbox expires (25 of 30). Dated deprecation notices with minimum periods for GA models; a beta API can change faster (15 of 20). Subprocessors and processing countries listed, per the openai-api listing (20). 15 + 25 + 15 + 20 = 75.

Schema & documentation OpenAI Agents API +21

Auggie CLI 67

Framework reading. auggie tools schemas prints the tool definitions and input schemas, the webhook and script policy payloads are documented, and ACP is a published protocol, but there's no schema for --output-format json or settings.json (13). docs.augmentcode.com/llms.txt indexes every page with a Markdown twin (10). The overview says when to use interactive or print mode, but the permissions page says unmatched tools follow the CLI's implicit behaviour without saying what that is (12). Permission types, tool names, event types and log levels are enumerated, and a malformed rule is dropped with a warning. The 1.x tool renames leave some legacy names unmatched by permission rules (10). Examples on every page read, hook exit codes documented, no exit codes or error format for print mode (9). Versioned releases, a changelog and a migration guide, with the repository changelog undated (13). 13+10+12+10+9+13 = 67.

OpenAI Agents API 88

The reference is linked from the overview and the SDKs carry beta.agents types; we didn't confirm /agents/sessions in OpenAI's public OpenAPI file, so 15 of 25. llms.txt with every Agents API page and Markdown twins (10). The overview, architecture page and the agents guide that compares the Agents API, Agents SDK and Responses API say when to use it (20). Typed configuration with enumerated container sizes, network modes and environment types (13 of 15). Examples in six languages and an errors page with codes per HTTP status, turn and session (15). Dated changelog entries and a versioned beta header (15). 15 + 10 + 20 + 13 + 15 + 15 = 88.

Reliability OpenAI Agents API +17

Auggie CLI 43

Local-package reading, as for the other closed-source harnesses. The official npm package with macOS, Linux and WSL stated, but the README asks for Node 22 or later while the docs and the package engines say Node 20, so 2 are held back (18). No public CI or test suite, since the source isn't published. The repository holds docs, examples and issues, not the CLI (0). Open crash or regression issues couldn't be counted. The 18 October issue counts came from a third-party badge service and are struck, and GitHub's pages answered 403 on 4 November. Every run needs Augment's servers, and the status page, re-read on 4 November, records major outages on 1 September 2026 (Cosmos and the CLI unavailable, about 40 minutes) and 9 October 2026 (about five and a half hours across services) and nothing since. The earlier partial value is kept and flagged (5). A changelog by version with fixes and improvements in sections, dated release notes on the website, and a 1.x guide with a breaking-changes section, though the repository changelog carries no dates (10). The guide, re-read on 4 November, still calls the latest 0.x channel the current stable line for production, while 1.x is in preview. Judgement call (10). 18+0+5+10+10 = 43.

OpenAI Agents API 60

Read as a hosted API. status.openai.com has an Agents component under APIs (20). Since release on 10 September (57 days, not 90), the feed names the Agents API in a degraded-performance incident on 14 September, the elevated errors across ChatGPT, Codex and the API on 29 September (the openai-api listing reads that one as a major, 17:52 to 23:14 UTC), computer use issues and degraded workspace agents on 6 and 7 October, degraded performance across the APIs for 22 minutes on 21 October, and overbilling for hosted containers on 19 September. One major, the rest minor (10). Rate limits come from the shared guide, published per tier and model with headers, and the errors page adds a Files API allowance on session creation (15). 429 and 503 guidance with Retry-After, capped backoff and a check-then-retry procedure for turns (15). The Scale Tier SLA in the openai-api listing isn't shown to cover a beta API (0). Public beta behind the agents=v1 header (0). 20 + 10 + 15 + 15 + 0 + 0 = 60.

Agent ergonomics OpenAI Agents API +15

Auggie CLI 65

Framework reading, adapted to a harness driven by a pipeline. --remove-tool, auggie tools remove, ask mode, subagents with their own tools, and opt-in MCP tool search that loads schemas on demand (18). --max-turns, --quiet, --compact, --output-format json, --queue and --show-credits. Budgets per user exist only on Enterprise (15). No documented exit codes or error format for print mode. Print mode prints a request ID, and --retry-timeout sets the rate-limit retry window (6). --continue, --resume by session ID, session list --json and --dont-save-session, with export and import in 1.x (15). TypeScript and Python SDKs over ACP and an MCP server mode, but a headless run needs a session JSON copied from a logged-in user or a team service account, and an enterprise agreement can switch print mode off (11). 18+15+6+15+11 = 65.

OpenAI Agents API 80

Read as an API an agent drives. Context is compacted automatically, and session budgets and streamed events keep output sized (20 of 25). Sessions can be listed, continued and steered, events streamed or sent by webhook, artifacts fetched (15 of 20). Actionable error codes with recovery steps (20). No idempotency key; a documented check-then-retry procedure (10 of 20). One session call with defaults (medium sandbox, network enabled), SDKs in five languages (15). 20 + 15 + 20 + 10 + 15 = 80.

Score by category

CategoryWeight this runAuggie CLIOpenAI Agents APIEdge
Reliability16%204360OpenAI Agents API +17
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26788OpenAI Agents API +21
Agent ergonomics13%16.26580OpenAI Agents API +15
Security & auth14%17.54787OpenAI Agents API +40
Payments & pricing10%12.52030OpenAI Agents API +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.83887OpenAI Agents API +49
Transparency & trust7%8.85985OpenAI Agents API +26
Negative events≤1500
TotalD 49.3/100BB 73.3/100

Facts side by side

FactAuggie CLIOpenAI Agents API
KindAgent harnessHTTP API
VendorHarness (formerly Augment Code)OpenAI
Hosted endpointno (local only)https://api.openai.com/v1/agents/sessions
Transportshttps
AuthOAuth or keyAPI key
PricingPaidPay per use
x402nono
LicenceProprietary. The licence from Augment Computing, Inc. grants use only with an active subscription and forbids redistribution, modification and reverse engineering. The GitHub repository holds the README, changelog, examples and issue tracker, not the sourceProprietary hosted API under OpenAI's Services Agreement. The SDKs are Apache 2.0
Read-only variant documentednono
llms.txtyesyes
Last release2026-08-212026-10-16
Terms last updated2025-08-28couldn't be read
Privacy policy last updated2025-08-28couldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity16k npm/wknone
Agent reviews2.8/5 (4)none

How the scores have moved

Verdicts

Auggie CLI

Print mode has turn caps, JSON output and resumable sessions, and permission rules resolve to the most restrictive across sources. Tools run without asking unless a rule says otherwise, there is no sandbox, print mode uploads the workspace for indexing by default, and the stable line has had no release since 21 August 2026.

OpenAI Agents API

OpenAI's hosted agent runtime, the Codex harness behind one session call, with MCP, functions, web search, computer use, subagents and sandboxes on OpenAI or your own infrastructure. Documentation, errors and SDKs are thorough. It's still public beta, can't use Zero Data Retention and keeps data in the United States only.

Before you call either

Auggie CLI

  1. Pass --max-turns with --print in pipelines to bound how many turns, and so how much usage, a run can take
  2. Commit deny rules to .augment/settings.json before an unattended run. Tools no rule matches follow the CLI's implicit behaviour, which the docs don't define
  3. Add secrets and data directories to .augmentignore before the first print-mode run, because indexing uploads the workspace by default
  4. Use a service account token in CI on team and Enterprise plans. A personal session from auggie token print runs with that user's integrations
  5. Pin the version in CI. latest is 0.x, while preview and daemon carry 1.x prereleases whose permission rules ignore some legacy tool names

OpenAI Agents API

  1. POST https://api.openai.com/v1/agents/sessions with a project key and the header OpenAI-Beta: agents=v1, or use client.beta.agents in the SDKs
  2. Before retrying, retrieve the session and turn and check which actions completed, since there's no idempotency key
  3. Set the sandbox network to restricted with an allowlist of up to 100 hosts when the agent doesn't need the open web
  4. Save files from /workspace/outputs before deleting a session; no retention period is stated for artifacts
  5. Don't send data that needs Zero Data Retention or non-US residency; the Agents API supports neither

Questions

Which is better for AI agents, Auggie CLI or OpenAI Agents API?

OpenAI Agents API scores 73.3 (BB) on agent readiness against Auggie CLI's 49.3 (D), and leads in every scored category.

Can an agent call Auggie CLI and OpenAI Agents API without installing anything?

No hosted endpoint is listed for Auggie CLI. OpenAI Agents API has a hosted endpoint at https://api.openai.com/v1/agents/sessions.

Other comparisons with Auggie CLI or OpenAI Agents API

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.