Claude Code vs OpenCode

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Claude Code
   Claude Code~partialprobed5/10

   Claude Code itself ships llms.txt files (docs.claude.com/llms.txt, code.claude.com/docs/llms.txt) confirming it is agent-oriented-docs-aware for its own product, and its agentic search/MCP tooling means it can fetch and consume arbitrary web docs including llms.txt if pointed at them via URL fetch or MCP. However, there is no explicit documented feature or first-party guidance describing 'point Claude Code at llms.txt of a third-party site' as a supported workflow. missing for 10: explicit product feature/docs describing consuming arbitrary llms.txt/agent-oriented docs as a first-class capability, independent hands-on confirmation of this specific use case.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.claude.com/llms.txt # Anthropic Developer Documentation This file provides an overview of the Anth…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.claude.com/en/docs/claude-code/overview.md > ## Documentation Index > Fetch the complete documentati…”
   • [claimed-docs] “Claude Code maps and explains entire codebases in a few seconds. It uses agentic search to understand project structure and dependencies wit…”
   • [claimed-docs] “Claude Code can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”

   proof ↗⚑ flag

   OpenCode~partialprobed4/10

   OpenCode's own llms.txt file returns 404, so there is no dedicated llms.txt for agents, but probes show that docs pages are available in machine-readable Markdown form (.md suffix returns 200), which serves an analogous agent-oriented documentation function. There's no first-party statement about llms.txt support or explicit agent-doc pointing workflow. Missing for 10: an actual llms.txt endpoint, documentation instructing users to point agents at machine-readable docs, and confirmation that agents can consume the .md docs as intended.

   • [probe] “PROBE llms.txt: HTTP 404 at https://opencode.ai/llms.txt”
   • [probe] “PROBE docs-md: HTTP 200 at https://opencode.ai/docs/.md import { Tabs, TabItem } from "@astrojs/starlight/components" import config from "..…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round drawn
   Claude Code✓fullclaimed9/10

   Docs explicitly describe running Claude Code in CI (GitHub Actions/GitLab CI/CD) for automated code review and issue triage, piping logs into it, and scheduled/headless runs for repeated automation tasks, plus GitHub Action integration for automatic PR review. This directly matches the headless/CI automation story with strong first-party documentation. Missing for 10: independent/hands-on confirmation of a working CI pipeline (community evidence is silent on CI usage specifically).

   • [claimed-docs] “Claude Code is composable and follows the Unix philosophy. Pipe logs into it, run it in CI, or chain it with other tools”
   • [claimed-docs] “Run Claude on a schedule to automate work that repeats: morning PR reviews, overnight CI failure analysis, weekly dependency audits, or sync…”
   • [claimed-docs] “In CI, you can automate code review and issue triage with GitHub Actions or GitLab CI/CD.”
   • [claimed-docs] “Get automatic code review on every PR | GitHub Code Review”

   proof ↗⚑ flag

   OpenCode✓fullprobed9/10

   OpenCode explicitly supports headless/CI use via `opencode run` for non-interactive execution, `opencode serve` for a headless HTTP server with OpenAPI, `--auto` for unattended permission approval, a JS/TS SDK for programmatic control, and a first-party GitHub Actions integration triggered by PR comments. This covers CLI scripting, server automation, and CI pipelines with concrete docs and an OpenAPI endpoint confirmed live. missing for 10: independent third-party validation of CI reliability at scale (community evidence mostly covers interactive TUI use, not CI-specific automation).

   • [claimed-docs] “opencode run "Explain how closures work in JavaScript"”
   • [claimed-docs] “The opencode serve command runs a headless HTTP server that exposes an OpenAPI endpoint that an opencode client can use.”
   • [claimed-docs] “The `opencode serve` command runs a headless HTTP server that exposes an OpenAPI endpoint that an opencode client can use.”
   • [claimed-docs] “Start OpenCode with `--auto` to automatically approve permission requests that are not explicitly denied.”
   • [claimed-docs] “Start OpenCode with --auto to automatically approve permission requests that are not explicitly denied.”
   • [claimed-docs] “OpenCode integrates with your GitHub workflow. Mention /opencode or /oc in your comment, and OpenCode will execute tasks within your GitHub …”
   • [claimed-docs] “Mention `/opencode` or `/oc` in your comment, and OpenCode will execute tasks within your GitHub Actions runner.”
   • [claimed-docs] “The opencode JS/TS SDK provides a type-safe client for interacting with the server. Use it to build integrations and control opencode progra…”
   • [probe] “PROBE openapi: HTTP 200 at https://opencode.ai/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round drawn
   Claude Code✓fullclaimed9/10

   Claude Code has extensive first-party MCP documentation showing users can add MCP servers (e.g. `claude mcp add --transport http notion ...`), supporting stdio/HTTP transports, connecting to hundreds of external tools like Jira, Slack, Google Drive, Postgres, and even scaffolding new servers via a dev plugin. This is well corroborated across multiple doc pages with concrete CLI examples and use cases. Missing for 10: independent/hands-on community confirmation specifically of MCP tool usage (community evidence covers other topics, not MCP plugging in).

   • [claimed-docs] “With MCP, Claude Code can read your design docs in Google Drive, update tickets in Jira, pull data from Slack, or use your own custom toolin…”
   • [claimed-docs] “Claude Code can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”
   • [claimed-docs] “Implement features from issue trackers: "Add the feature described in JIRA issue ENG-4521 and create a PR on GitHub."”
   • [claimed-docs] “claude mcp add --transport http notion https://mcp.notion.com/mcp”
   • [claimed-docs] “Stdio servers run as local processes on your machine. They're ideal for tools that need direct system access or custom scripts.”
   • [claimed-docs] “You can also have Claude scaffold a server for you with the official mcp-server-dev plugin”
   • [claimed-docs] “an MCP server can also act as a channel that pushes messages into your session, so Claude reacts to Telegram messages, Discord chats, or web…”

   proof ↗⚑ flag

   OpenCode✓fullclaimed9/10

   OpenCode has first-party documentation dedicated to adding external tools via MCP, supporting both local and remote servers, directly matching the story. This is corroborated indirectly by community discussion of OpenCode's tool/agent ecosystem, though no hands-on account specifically tests MCP server plugging. Missing for 10: independent/hands-on confirmation specifically of MCP server usage (community evidence discusses agents/tools generally but not MCP specifically).

   • [claimed-docs] “You can add external tools to OpenCode using the _Model Context Protocol_, or MCP. OpenCode supports both local and remote servers.”
   • [claimed-docs] “You can add external tools to OpenCode using the Model Context Protocol, or MCP.”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round drawn
   Claude Code✓fullprobed9/10

   Claude Code is itself an official CLI tool with documented install (curl install script), usage (`cd project && claude`), cross-platform support (macOS/Linux/Windows), and deep terminal-native workflows (git, MCP, hooks, CI). GitHub repo and docs confirm first-party CLI status with active community usage corroborating real-world use. Missing for 10: independent benchmarking of CLI robustness/UX beyond mixed community sentiment.

   • [claimed-docs] “cd your-project claude”
   • [claimed-docs] “curl -fsSL https://claude.ai/install.sh | bash”
   • [claimed-docs] “Available for macOS, Linux, and Windows.”
   • [github] “Use it in your terminal, IDE, or tag @claude on Github.”
   • [github] “helps you code faster by executing routine tasks, explaining complex code, and handling git workflows -- all through natural language comman…”
   • [probe] “official CLI documented at https://code.claude.com/docs/en/setup”

   proof ↗⚑ flag

   OpenCode✓fullprobed9/10

   OpenCode ships an official CLI with documented commands (opencode run, opencode serve, init, install via curl/npm) and dedicated CLI docs, corroborated by community users who actively use it as their primary daily-driver harness. Missing for 10: independent benchmarking of CLI completeness/stability beyond anecdotal community reports (some bug complaints noted but not disputing existence of an official CLI).

   • [claimed-docs] “You can add external tools to OpenCode using the _Model Context Protocol_, or MCP. OpenCode supports both local and remote servers.”
   • [claimed-docs] “curl -fsSL https://opencode.ai/install | bash”
   • [claimed-docs] “opencode run "Explain how closures work in JavaScript"”
   • [claimed-docs] “The opencode serve command runs a headless HTTP server that exposes an OpenAPI endpoint that an opencode client can use.”
   • [claimed-docs] “npm install -g opencode-ai”
   • [probe] “official CLI documented at https://opencode.ai/docs/cli/”
   • [community] “i've been using this as my primary harness for llama.cpp models, Claude, and Gemini for a few months now. the LSP integration is great.”
   • [community] “This replaced Aider for me a couple months back. I use it with Qwen 3.5 running locally when my daily limits run out on my other subscriptio…”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round drawn
   Claude Code✓fullclaimed8/10

   Claude Code exposes multiple documented programmatic surfaces: the Agent SDK for building custom agents with full control over orchestration/tools/permissions, a CLI (claude, claude mcp serve) that can be scripted/piped/run in CI, and ANTHROPIC_API_KEY-based direct API access, all documented in first-party docs. This goes beyond a closed UI and gives AI-native users documented, programmatic control paths. Missing for 10: independent/hands-on validation of the Agent SDK's API surface and no explicit REST/OpenAPI reference beyond the SDK and CLI docs.

   • [claimed-docs] “the Agent SDK lets you build your own agents powered by Claude Code's tools and capabilities, with full control over orchestration, tool acc…”
   • [claimed-docs] “Use Claude Code as an MCP server. You can use Claude Code itself as an MCP server that other applications can connect to: claude mcp serve (…”
   • [claimed-docs] “If you've set the ANTHROPIC_API_KEY environment variable, Claude Code skips the login prompt and asks you to approve the key instead.”
   • [claimed-docs] “ANTHROPIC_API_KEY environment variable. Sent as the X-Api-Key header. Use this for direct Anthropic API access with a key from the Claude Co…”
   • [claimed-docs] “Claude Code is composable and follows the Unix philosophy. Pipe logs into it, run it in CI, or chain it with other tools”
   • [claimed-docs] “Claude Code can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”

   proof ↗⚑ flag

   OpenCode✓fullprobed8/10

   OpenCode ships a documented headless server (`opencode serve`) exposing an OpenAPI endpoint, confirmed live via probe (opencode-probe-3), plus a type-safe JS/TS SDK for programmatic control, and its CLI supports non-interactive scripted use (`opencode run`). missing for 10: independent third-party corroboration of SDK/API usage in production, and no evidence of versioning/stability guarantees or broader language SDK support beyond JS/TS.

   • [claimed-docs] “The opencode serve command runs a headless HTTP server that exposes an OpenAPI endpoint that an opencode client can use.”
   • [claimed-docs] “The `opencode serve` command runs a headless HTTP server that exposes an OpenAPI endpoint that an opencode client can use.”
   • [claimed-docs] “The opencode JS/TS SDK provides a type-safe client for interacting with the server. Use it to build integrations and control opencode progra…”
   • [claimed-docs] “The opencode JS/TS SDK provides a type-safe client for interacting with the server.”
   • [claimed-docs] “Use it to build integrations and control opencode programmatically.”
   • [claimed-docs] “opencode run "Explain how closures work in JavaScript"”
   • [probe] “PROBE openapi: HTTP 200 at https://opencode.ai/openapi.json — contains "openapi" key”
   • [claimed-docs] “Attach a terminal to an already running OpenCode backend server started via `serve` or `web` commands.”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Claude Code
   Claude Code~partialclaimed4/10

   Enterprise IAM docs mention role-based permissions, managed policy settings, and SSO/domain capture for org-wide configurations, plus sandboxing controls that restrict file/network access at runtime, suggesting some least-privilege controls exist. However, there is no explicit documentation of issuing scoped or limited-permission API keys/credentials specifically for an agent's use. Missing for 10: explicit scoped API key creation/management flow, granular credential scoping documentation, and independent verification of least-privilege credential issuance.

   • [claimed-docs] “Claude for Enterprise: adds SSO, domain capture, role-based permissions, compliance API, and managed policy settings for organization-wide C…”
   • [claimed-docs] “Single sign-on (SSO/SAML) and domain capture”
   • [claimed-docs] “Learn how Claude Code's sandboxed Bash tool provides filesystem and network isolation for safer, more autonomous agent execution. The Bash s…”
   • [claimed-docs] “If you've set the ANTHROPIC_API_KEY environment variable, Claude Code skips the login prompt and asks you to approve the key instead.”
   • [claimed-docs] “You can sign in to your Console account without creating an API key, even when your organization doesn't let developers create them.”

   proof ↗⚑ flag

   OpenCode~partialclaimed3/10

   OpenCode's permission config lets you restrict which actions (edit, bash, etc.) an agent may auto-run, prompt for, or block, and enterprise SSO integration centralizes access to an internal AI gateway — both are adjacent to least-privilege agent control, but neither is a mechanism for issuing scoped API credentials/keys specifically to an agent. missing for 10: explicit scoped API-key/credential issuance for agents, credential expiry/rotation, per-agent key scoping documentation, independent verification of this capability.

   • [claimed-docs] “OpenCode uses the `permission` config to decide whether a given action should run automatically, prompt you, or be blocked.”
   • [claimed-docs] “Start OpenCode with `--auto` to automatically approve permission requests that are not explicitly denied.”
   • [claimed-docs] “This centralized config can integrate with your SSO provider and ensures all users access only your internal AI gateway.”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Claude Code✓fullclaimed8/10

   Claude Code offers the official Agent SDK, letting developers build their own agents with full control over orchestration, tool access, and permissions, on top of Claude Code's tools/capabilities — a direct SDK for AI-native builders. This is backed by first-party docs and complemented by API-key-based programmatic access (ANTHROPIC_API_KEY) for direct integration. Missing for 10: independent/hands-on developer reports building production apps with the Agent SDK, and deeper docs on SDK language coverage/versioning.

   • [claimed-docs] “the Agent SDK lets you build your own agents powered by Claude Code's tools and capabilities, with full control over orchestration, tool acc…”
   • [claimed-docs] “If you've set the ANTHROPIC_API_KEY environment variable, Claude Code skips the login prompt and asks you to approve the key instead.”
   • [claimed-docs] “ANTHROPIC_API_KEY environment variable. Sent as the X-Api-Key header. Use this for direct Anthropic API access with a key from the Claude Co…”

   proof ↗⚑ flag

   OpenCode✓fullprobed8/10

   OpenCode documents a dedicated JS/TS SDK ('type-safe client for interacting with the server... use it to build integrations and control opencode programmatically') plus a headless server mode (`opencode serve`) exposing an OpenAPI endpoint, confirmed live by probe (openapi.json returns valid schema). This gives AI-native users official, documented programmatic access beyond the CLI/TUI. Missing for 10: independent hands-on developer reports of building against the SDK, and broader multi-language SDK coverage beyond JS/TS.

   • [claimed-docs] “The opencode JS/TS SDK provides a type-safe client for interacting with the server. Use it to build integrations and control opencode progra…”
   • [claimed-docs] “Use it to build integrations and control opencode programmatically.”
   • [claimed-docs] “The opencode JS/TS SDK provides a type-safe client for interacting with the server.”
   • [claimed-docs] “The opencode serve command runs a headless HTTP server that exposes an OpenAPI endpoint that an opencode client can use.”
   • [claimed-docs] “The `opencode serve` command runs a headless HTTP server that exposes an OpenAPI endpoint that an opencode client can use.”
   • [probe] “PROBE openapi: HTTP 200 at https://opencode.ai/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to Claude Code
   Claude Code~partialclaimed4/10

   Claude Code doesn't offer a first-party webhook subscription feature, but docs note that an MCP server can act as a channel pushing events—including webhook events—into a Claude Code session while the user is away, enabling indirect event subscription via custom MCP tooling. Missing for 10: a native/first-party webhook subscription mechanism, official documentation or example of setting up webhook-triggered sessions, and independent confirmation this works in practice.

   • [claimed-docs] “an MCP server can also act as a channel that pushes messages into your session, so Claude reacts to Telegram messages, Discord chats, or web…”
   • [claimed-docs] “an MCP server can also act as a channel that pushes messages into your session, so Claude reacts to Telegram messages, Discord chats, or web…”
   • [claimed-docs] “Claude Code can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”

   proof ↗⚑ flag

   OpenCode—none0/10

   Evidence shows OpenCode has a headless server (`opencode serve`) exposing an OpenAPI/HTTP endpoint and an SDK for programmatic control, but there is no mention anywhere of webhook subscriptions or event-push notifications that clients could register for.

   • [claimed-docs] “The opencode serve command runs a headless HTTP server that exposes an OpenAPI endpoint that an opencode client can use.”
   • [claimed-docs] “The `opencode serve` command runs a headless HTTP server that exposes an OpenAPI endpoint that an opencode client can use.”
   • [claimed-docs] “The opencode JS/TS SDK provides a type-safe client for interacting with the server. Use it to build integrations and control opencode progra…”
   • [claimed-docs] “The opencode JS/TS SDK provides a type-safe client for interacting with the server.”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round drawn
   Claude Code✓fullclaimed7/10

   Claude Code generates AI-driven insights and suggestions from a user's data: it maps/explains entire codebases automatically, reviews code and PRs for security issues with explanations, and via MCP can query databases (e.g., PostgreSQL) or pull data from Slack/Jira/Google Drive to answer questions and suggest actions. This is all documented first-party capability with concrete examples (codebase mapping, automatic PR/security review, data queries via MCP). missing for 10: independent/hands-on corroboration specifically validating the quality of data-driven insights (community evidence is mostly about coding reliability, not insight generation), and no dedicated analytics/dashboard-style insight feature beyond code/data-source querying.

   • [claimed-docs] “Claude Code maps and explains entire codebases in a few seconds. It uses agentic search to understand project structure and dependencies wit…”
   • [claimed-docs] “Claude helps security teams and developers by reviewing code for security issues, drafts patches, and explains the risk in language your who…”
   • [claimed-docs] “Get automatic code review on every PR | GitHub Code Review”
   • [claimed-docs] “Find emails of 10 random users who used feature ENG-4521, based on our PostgreSQL database.”
   • [claimed-docs] “With MCP, Claude Code can read your design docs in Google Drive, update tickets in Jira, pull data from Slack, or use your own custom toolin…”
   • [claimed-docs] “Claude Code can read your design docs in Google Drive, update tickets in Jira, pull data from Slack, or use your own custom tooling.”

   proof ↗⚑ flag

   OpenCode✓fullcommunity7/10

   OpenCode's plan/explore agents let users get AI-generated code analysis and suggested changes without modifying the codebase, directly matching the story of AI-generated insights over the user's data (their code) (opencode-docs-7, opencode-docs-60, opencode-docs-61). Community mentions confirm active use of the agent for analysis/harness work (opencode-comm-1, opencode-comm-3). Missing for 10: independent examples of insight quality/output, and no evidence of insights beyond code (e.g., broader data analytics).

   • [claimed-docs] “Use the plan agent to analyze code and review suggestions without making any code changes.”
   • [claimed-docs] “This agent is useful when you want the LLM to analyze code, suggest changes, or create plans without making any actual modifications to your…”
   • [claimed-docs] “A fast, read-only agent for exploring codebases. Cannot modify files.”
   • [community] “I really like how their subagents work, as a bonus I get to choose which model is in which agent.”
   • [community] “i've been using this as my primary harness for llama.cpp models, Claude, and Gemini for a few months now. the LSP integration is great.”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Claude Code
   Claude Code✓fullclaimed8/10

   Docs describe explicit background-automation features: scheduled runs for recurring tasks (morning PR reviews, overnight CI analysis, weekly audits), cloud/web sessions for long-running tasks you check back on, GitHub Actions/GitLab CI integration for automated review/triage, and MCP servers that push events (Telegram/Discord/webhooks) into a session while the user is away. Missing for 10: independent/hands-on corroboration that scheduled or background jobs run reliably unattended over time (only first-party docs cited).

   • [claimed-docs] “Run Claude on a schedule to automate work that repeats: morning PR reviews, overnight CI failure analysis, weekly dependency audits, or sync…”
   • [claimed-docs] “Step away from your desk and keep working from your phone or any browser with Remote Control”
   • [claimed-docs] “Kick off a long-running task on the web or the Claude mobile app, then pull it into your terminal with `claude --teleport`.”
   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”
   • [claimed-docs] “Kick off long-running tasks and check back when they're done, work on repos you don't have locally, or run multiple tasks in parallel.”
   • [claimed-docs] “Run Claude Code in your browser with no local setup. Kick off long-running tasks and check back when they're done, work on repos you don't h…”
   • [claimed-docs] “In CI, you can automate code review and issue triage with GitHub Actions or GitLab CI/CD.”
   • [claimed-docs] “an MCP server can also act as a channel that pushes messages into your session, so Claude reacts to Telegram messages, Discord chats, or web…”
   • [claimed-docs] “an MCP server can also act as a channel that pushes messages into your session, so Claude reacts to Telegram messages, Discord chats, or web…”

   proof ↗⚑ flag

   OpenCode~partialcommunity6/10

   OpenCode ships a documented GitHub Actions integration where mentioning /opencode or /oc in a comment triggers it to autonomously work in a new branch and submit a PR, plus a headless `serve` mode and `--auto` permission flag that let it run unattended, supporting background automations. However there's no dedicated scheduling/cron mechanism, and community evidence flags reliability issues (stuck sessions, tool-call failures) that undercut confidence in unattended runs. missing for 10: scheduled/triggered automation beyond GitHub comment mentions, independent evidence of long-running unattended background jobs succeeding reliably.

   • [claimed-docs] “Ask OpenCode to fix an issue or implement a feature. And it will work in a new branch and submits a PR with all the changes.”
   • [claimed-docs] “Mention `/opencode` or `/oc` in your comment, and OpenCode will execute tasks within your GitHub Actions runner.”
   • [claimed-docs] “OpenCode integrates with your GitHub workflow. Mention /opencode or /oc in your comment, and OpenCode will execute tasks within your GitHub …”
   • [claimed-docs] “This will walk you through installing the GitHub app, creating the workflow, and setting up secrets.”
   • [claimed-docs] “Start OpenCode with `--auto` to automatically approve permission requests that are not explicitly denied.”
   • [claimed-docs] “The `opencode serve` command runs a headless HTTP server that exposes an OpenAPI endpoint that an opencode client can use.”
   • [community] “There are random bugs with loading/restoring state of the session; Model/Provider selection switch across sessions/projects is often annoyin…”
   • [community] “I've been trying various harnesses like Pi, OpenCode, Qwen Code, and Nanocoder. A common problem I keep running into is failed tool calls, r…”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to OpenCode
   Claude Code✓fullcommunity8/10

   Claude Code's entire premise is delegating tasks to a built-in AI agent: docs describe it planning approaches, writing code across files, running tests, handling git workflows, and autonomously completing multi-step tasks (docs-2, docs-3, docs-20, docs-28, gh-3). This is corroborated by extensive first-party documentation and some community confirmation that it performs well as a coding assistant, though other community reports describe reliability issues and failure modes in autonomous execution. Missing for 10: independent benchmark-level validation of consistent task delegation success and stronger consensus on reliability (community reports show notable failure cases).

   • [claimed-docs] “Describe what you want in plain language. Claude Code plans the approach, writes the code across multiple files, and verifies it works.”
   • [claimed-docs] “Claude Code works directly with git. It stages changes, writes commit messages, creates branches, and opens pull requests.”
   • [claimed-docs] “Claude Code handles the tedious tasks that eat up your day: writing tests for untested code, fixing lint errors across a project, resolving …”
   • [claimed-docs] “Claude Code plans the approach, writes the code across multiple files, and verifies it works.”
   • [github] “helps you code faster by executing routine tasks, explaining complex code, and handling git workflows -- all through natural language comman…”
   • [community] “Claude is significantly better than other models at code assistant tasks, or at least in the way I use it.”
   • [community] “I've been using Claude Code daily for months on a project with Elixir, Rust, and Python. The worst failure mode is when it does a replace_al…”
   • [community] “I've tried to use Claude code for a month now. It has a 100% failure rate so far. Comparing that to creating a project and just chatting wit…”

   proof ↗⚑ flag

   OpenCode✓fullcommunity9/10

   OpenCode's core function is exactly this: an AI coding agent you delegate tasks to via CLI/TUI/IDE/desktop ('opencode run "Explain how closures work..."'), with multiple agent personas (build, plan, explore) and multi-session parallel delegation, richly documented and corroborated by extensive hands-on community use as a daily coding harness. Missing for 10: no independent benchmark of delegation reliability across all model backends (some community reports of failed tool calls/edits with local models).

   • [claimed-docs] “OpenCode is an open source AI coding agent. It's available as a terminal-based interface, desktop app, or IDE extension.”
   • [claimed-docs] “opencode run "Explain how closures work in JavaScript"”
   • [claimed-docs] “**Multi-session** Start multiple agents in parallel on the same project”
   • [claimed-docs] “Multi-session Start multiple agents in parallel on the same project”
   • [claimed-docs] “You can use the **Tab** key to switch between primary agents during a session.”
   • [claimed-docs] “This agent is useful when you want the LLM to analyze code, suggest changes, or create plans without making any actual modifications to your…”
   • [community] “i've been using this as my primary harness for llama.cpp models, Claude, and Gemini for a few months now. the LSP integration is great.”
   • [community] “This replaced Aider for me a couple months back. I use it with Qwen 3.5 running locally when my daily limits run out on my other subscriptio…”
   • [community] “Claude is much better in OpenCode then in Claude Code, OpenCode is just better than Claude Code. Claude Code feels like a complete mess to u…”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to OpenCode
   Claude Code✓fullclaimed8/10

   Claude Code is explicitly designed to be operated via plain-language instructions—describing tasks, git workflows, MCP tool use, and even natural-language chat commands (@claude in Slack, GitHub) all documented as core interaction modes, and GitHub docs explicitly state it works 'all through natural language commands.' missing for 10: independent hands-on benchmarking specifically confirming natural-language command comprehension breadth/accuracy versus slash-command or scripted usage, and some community reports note failure modes/hallucination under natural language instructions reducing reliability.

   • [claimed-docs] “Describe what you want in plain language. Claude Code plans the approach, writes the code across multiple files, and verifies it works.”
   • [claimed-docs] “Claude Code plans the approach, writes the code across multiple files, and verifies it works.”
   • [claimed-docs] “Claude Code works directly with git. It stages changes, writes commit messages, creates branches, and opens pull requests.”
   • [github] “helps you code faster by executing routine tasks, explaining complex code, and handling git workflows -- all through natural language comman…”
   • [claimed-docs] “Route tasks from team chat: mention @Claude in Slack with a bug report and get a pull request back”
   • [claimed-docs] “cd your-project claude”

   proof ↗⚑ flag

   OpenCode✓fullcommunity9/10

   OpenCode's core interface is natural-language driven: the CLI example `opencode run "Explain how closures work in JavaScript"` and TUI/desktop/IDE modes are all built around conversational prompts to an AI agent that then edits code, opens branches, and submits PRs. Community usage (comm-1, comm-3, comm-4, comm-11) confirms this is how real users operate it day-to-day as their primary coding harness. Missing for 10: no independent benchmark specifically validating breadth of natural-language command coverage beyond docs/anecdotes.

   • [claimed-docs] “opencode run "Explain how closures work in JavaScript"”
   • [claimed-docs] “OpenCode is an open source AI coding agent. It's available as a terminal-based interface, desktop app, or IDE extension.”
   • [claimed-docs] “Ask OpenCode to fix an issue or implement a feature. And it will work in a new branch and submits a PR with all the changes.”
   • [community] “i've been using this as my primary harness for llama.cpp models, Claude, and Gemini for a few months now. the LSP integration is great.”
   • [community] “This replaced Aider for me a couple months back. I use it with Qwen 3.5 running locally when my daily limits run out on my other subscriptio…”
   • [community] “Claude is much better in OpenCode then in Claude Code, OpenCode is just better than Claude Code. Claude Code feels like a complete mess to u…”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round to OpenCode
   Claude Code—none0/10

   The evidence pack shows standard documentation pages and an Agent SDK reference, but nothing describing an interactive API reference with runnable/executable code examples (e.g., an in-browser sandbox or live API explorer). No such capability is evidenced anywhere in the docs, GitHub, or community items.

   ⚑ flag

   OpenCode~partialprobed3/10

   OpenCode exposes a raw OpenAPI spec via `opencode serve` and openapi.json, and offers an SDK for programmatic use, but there is no evidence of an actual interactive API reference UI (e.g., Swagger/Redoc-style docs) with runnable/try-it examples. Missing for 10: dedicated interactive API explorer page, runnable code examples, independent confirmation of such a UI existing.

   • [claimed-docs] “The opencode serve command runs a headless HTTP server that exposes an OpenAPI endpoint that an opencode client can use.”
   • [claimed-docs] “The opencode JS/TS SDK provides a type-safe client for interacting with the server. Use it to build integrations and control opencode progra…”
   • [probe] “PROBE openapi: HTTP 200 at https://opencode.ai/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round to OpenCode
   Claude Code—none0/10

   The evidence pack shows Claude Code as a CLI/agent tool with SDK, MCP, and CI integrations, but no mention of a downloadable OpenAPI or equivalent machine-readable API spec for Claude Code itself. This axis is plausible for a product with an Agent SDK and API-key based access, but the pack contains no such artifact.

   ⚑ flag

   OpenCode✓fullprobed9/10

   The docs explicitly state that `opencode serve` runs a headless HTTP server exposing an OpenAPI endpoint, and a live probe confirms a downloadable machine-readable OpenAPI spec at https://opencode.ai/openapi.json. This directly satisfies the story of downloading a machine-readable API spec. Missing for 10: independent/community corroboration of using this OpenAPI spec in practice.

   • [claimed-docs] “The opencode serve command runs a headless HTTP server that exposes an OpenAPI endpoint that an opencode client can use.”
   • [claimed-docs] “The `opencode serve` command runs a headless HTTP server that exposes an OpenAPI endpoint that an opencode client can use.”
   • [probe] “PROBE openapi: HTTP 200 at https://opencode.ai/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Claude Code
   Claude Code~partialclaimed5/10

   Claude Code documents a sandboxed Bash tool that enforces filesystem and network isolation, letting Claude execute commands within OS-enforced boundaries rather than freely touching arbitrary systems — this supports the spirit of testing in isolation, but the docs don't specifically describe spinning up a 'sandbox vs production' environment or protecting production data per se. Missing for 10: explicit documentation of test/staging vs production environment separation, guidance on preventing production data access, and independent/hands-on validation that the sandbox reliably prevents production data exposure.

   • [claimed-docs] “Learn how Claude Code's sandboxed Bash tool provides filesystem and network isolation for safer, more autonomous agent execution. The Bash s…”

   proof ↗⚑ flag

   OpenCode—none0/10

   OpenCode's docs describe permission controls, --auto approval, and external_directory restrictions, but there is no evidence of a dedicated sandbox/staging environment or mechanism to test against non-production data separate from the user's actual working directory/production files. Community reports even flag security gaps in the local server (opencode-comm-18) rather than any sandboxing feature for safe testing.

   • [claimed-docs] “OpenCode uses the `permission` config to decide whether a given action should run automatically, prompt you, or be blocked.”
   • [claimed-docs] “Start OpenCode with `--auto` to automatically approve permission requests that are not explicitly denied.”
   • [claimed-docs] “Use external_directory to allow tool calls that touch paths outside the working directory where OpenCode was started.”
   • [community] “When server is enabled, any web page served from localhost/127.0.0.1 can execute code; any local process can execute code without authentica…”

   proof ↗⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Claude Code—none0/10

   No evidence pack items mention API versioning schemes, version numbers, or a documented deprecation policy for Claude Code's APIs/CLI/SDK; the pack covers features, integrations, and community sentiment but nothing about API stability or deprecation commitments.

   ⚑ flag

   OpenCode—none0/10

   OpenCode does expose programmatic surfaces (the JS/TS SDK, `opencode serve` HTTP server, and an OpenAPI spec at openapi.json), so an API-versioning/deprecation-policy axis is applicable. However, none of the evidence mentions API version numbers, backward-compatibility guarantees, or any documented deprecation policy/process for the SDK or server API.

   • [claimed-docs] “The opencode JS/TS SDK provides a type-safe client for interacting with the server. Use it to build integrations and control opencode progra…”
   • [claimed-docs] “The opencode serve command runs a headless HTTP server that exposes an OpenAPI endpoint that an opencode client can use.”
   • [claimed-docs] “The `opencode serve` command runs a headless HTTP server that exposes an OpenAPI endpoint that an opencode client can use.”
   • [probe] “PROBE openapi: HTTP 200 at https://opencode.ai/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to OpenCode
   Claude Code!disputedcontradicted6/10

   Claude Code's docs explicitly support bulk operations — fixing lint errors 'across a project', multi-file writes, spawning multiple agents to work on different parts of a task simultaneously, and running multiple sessions/tasks in parallel or on a schedule — which strongly matches the story. However, a hands-on community report describes a concrete failure mode during a bulk-style replace_all operation that corrupted code (turning a constant into 'GROQ_URL = GROQ_URL'), with the user stating you 'absolutely can't trust it to self-verify' on such operations, directly contradicting reliable execution of bulk changes at scale. Missing for 10: independent corroboration that large-scale bulk operations complete reliably without manual review, and resolution/acknowledgment of the reported failure mode.

   • [claimed-docs] “writing tests for untested code, fixing lint errors across a project, resolving merge conflicts, updating dependencies, and writing release …”
   • [claimed-docs] “Spawn multiple Claude Code agents that work on different parts of a task simultaneously. A lead agent coordinates the work, assigns subtasks…”
   • [claimed-docs] “Claude Code handles the tedious tasks that eat up your day: writing tests for untested code, fixing lint errors across a project, resolving …”
   • [claimed-docs] “Spawn multiple Claude Code agents that work on different parts of a task simultaneously.”
   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”
   • [claimed-docs] “Kick off long-running tasks and check back when they're done, work on repos you don't have locally, or run multiple tasks in parallel.”
   • [community] “I've been using Claude Code daily for months on a project with Elixir, Rust, and Python. The worst failure mode is when it does a replace_al…”

   proof ↗⚑ flag

   OpenCode~partialclaimed4/10

   OpenCode's CLI (`opencode run`), SDK, and headless `opencode serve` provide programmatic hooks that could be scripted to loop over many files/tasks, and 'multi-session' lets multiple agents run in parallel on a project — but there is no documented first-class 'bulk operation' feature (e.g. batch refactor, mass file edit) or example of applying one command across many items at once. Missing for 10: explicit bulk/batch operation feature, documentation or examples of running the same task across many files/repos, independent evidence of successful large-scale batch use.

   • [claimed-docs] “**Multi-session** Start multiple agents in parallel on the same project”
   • [claimed-docs] “Multi-session Start multiple agents in parallel on the same project”
   • [claimed-docs] “The opencode JS/TS SDK provides a type-safe client for interacting with the server. Use it to build integrations and control opencode progra…”
   • [claimed-docs] “Use it to build integrations and control opencode programmatically.”
   • [claimed-docs] “The opencode serve command runs a headless HTTP server that exposes an OpenAPI endpoint that an opencode client can use.”
   • [claimed-docs] “opencode run "Explain how closures work in JavaScript"”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Claude Code
   Claude Code~partialclaimed6/10

   Claude Code supports Hooks (shell commands triggered before/after actions like auto-formatting or lint on edits) and scheduled runs plus MCP channels (Telegram/Discord/webhook events) that push messages into a session automatically, which together constitute event-triggered automation rules. However, there's no unified declarative 'rules engine' with conditions/triggers documented — it's a patchwork of hooks, cron-like scheduling, and MCP event channels rather than a first-class rule-definition system. missing for 10: a unified rules/trigger definition UI or config, broader event types beyond hooks/schedule/MCP channels, and independent/hands-on validation of these automation triggers working reliably.

   • [claimed-docs] “Hooks let you run shell commands before or after Claude Code actions, like auto-formatting after every file edit or running lint before a co…”
   • [claimed-docs] “Run Claude on a schedule to automate work that repeats: morning PR reviews, overnight CI failure analysis, weekly dependency audits, or sync…”
   • [claimed-docs] “an MCP server can also act as a channel that pushes messages into your session, so Claude reacts to Telegram messages, Discord chats, or web…”
   • [claimed-docs] “an MCP server can also act as a channel that pushes messages into your session, so Claude reacts to Telegram messages, Discord chats, or web…”
   • [claimed-docs] “In CI, you can automate code review and issue triage with GitHub Actions or GitLab CI/CD.”

   proof ↗⚑ flag

   OpenCode~partialclaimed5/10

   OpenCode supports some automatic rule-triggered behavior: GitHub integration lets a PR/issue comment mention (`/opencode` or `/oc`) automatically trigger the agent to execute tasks in a GitHub Actions runner, and the `permission` config lets you define rules for auto-approving, prompting, or blocking specific tool actions. This covers event-triggered automation in a narrow sense, but there's no general-purpose, user-defined event/rule engine (e.g., file-change hooks, cron-like triggers, custom event listeners) described in the docs. Missing for 10: a general automation/hooks system beyond GitHub comment mentions and permission gating, and independent evidence confirming reliability of these triggers in practice.

   • [claimed-docs] “Mention `/opencode` or `/oc` in your comment, and OpenCode will execute tasks within your GitHub Actions runner.”
   • [claimed-docs] “OpenCode integrates with your GitHub workflow. Mention /opencode or /oc in your comment, and OpenCode will execute tasks within your GitHub …”
   • [claimed-docs] “This will walk you through installing the GitHub app, creating the workflow, and setting up secrets.”
   • [claimed-docs] “OpenCode uses the `permission` config to decide whether a given action should run automatically, prompt you, or be blocked.”
   • [claimed-docs] “OpenCode uses the permission config to decide whether a given action should run automatically, prompt you, or be blocked.”
   • [claimed-docs] “For most permissions, you can use an object to apply different actions based on the tool input.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Claude Code
   Claude Code✓fullclaimed7/10

   Docs explicitly describe running Claude Code on a schedule for recurring automation (PR reviews, CI failure analysis, dependency audits, doc syncing) and mention 'schedule recurring tasks' as a feature. Missing for 10: independent/hands-on confirmation of the scheduling mechanism and details on configuration (cron syntax, triggers, reliability).

   • [claimed-docs] “Run Claude on a schedule to automate work that repeats: morning PR reviews, overnight CI failure analysis, weekly dependency audits, or sync…”
   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”

   proof ↗⚑ flag

   OpenCode—none0/10

   No evidence of any scheduling, cron-like, or recurring workflow trigger capability; OpenCode's docs cover CLI, agents, MCP, permissions, SDK, GitHub Actions triggers, and server mode but none describe scheduling or recurring automation. missing for 10: any scheduler/cron feature, recurring job configuration, or workflow trigger on a schedule.

   ⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round to Claude Code
   Claude Code~partialclaimed5/10

   Automations in Claude Code (CLAUDE.md, skills, hooks, slash commands) are plain files that live in the repo, so they inherit git's version history, and Claude Code natively works with git (staging, commits, diffs) and supports visual diff review (claude-code-docs-3, claude-code-docs-13, claude-code-docs-32, claude-code-docs-33, claude-code-docs-22). However, there is no dedicated feature for versioning/rolling back automations themselves (e.g., no automation-specific history log, no built-in 'revert this hook/skill run' or undo mechanism) — reviewers rely entirely on generic git workflows rather than a purpose-built automation-lifecycle tool. missing for 10: a dedicated automation versioning/audit history UI, an explicit rollback/undo command for skills or hooks, and independent hands-on confirmation that rollback of automations works as intended.

   • [claimed-docs] “Claude Code works directly with git. It stages changes, writes commit messages, creates branches, and opens pull requests.”
   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”
   • [claimed-docs] “Create skills to package repeatable workflows your team can share, like `/review-pr` or `/deploy-staging`.”
   • [claimed-docs] “Hooks let you run shell commands before or after Claude Code actions, like auto-formatting after every file edit or running lint before a co…”
   • [claimed-docs] “CLAUDE.md is a markdown file you add to your project root that Claude Code reads at the start of every session. Use it to set coding standar…”

   proof ↗⚑ flag

   OpenCode—none0/10

   Evidence covers agent creation, permissions, sessions, and sharing, but there is no documentation or community mention of versioning automations, reviewing change history, or rolling back agent/workflow configurations — session share links are for reference/debugging, not version control or rollback.

   • [claimed-docs] “**Share links** Share a link to any session for reference or to debug”
   • [claimed-docs] “Share links Share a link to any session for reference or to debug”
   • [claimed-docs] “OpenCode uses the `permission` config to decide whether a given action should run automatically, prompt you, or be blocked.”
   • [claimed-docs] “This command will guide you through creating a new agent with a custom system prompt and permission configuration.”

   proof ↗⚑ flag

Background execution

1. ai-native userHave a cloud agent build, test, and demo a feature end-to-end for my review

   weight 2 · round to Claude Code
   Claude Code~partialcommunity7/10

   Docs show Claude Code can run as a cloud/browser session for long-running tasks (web, mobile, remote control, teleport), plan and write code across files, write tests, and open PRs with diff review for others to inspect — covering build, test, and reviewable-artifact steps end-to-end without local setup (claude-code-docs-9,10,13,14,26,28,3,12). However there's no explicit 'demo' feature (e.g., live preview/staging deploy) beyond PR/diff review, and independent hands-on reports raise reliability concerns about self-verification on complex tasks. Missing for 10: dedicated demo/preview-environment tooling, independent corroboration of full cloud build-test-PR pipelines succeeding end-to-end without human intervention.

   • [claimed-docs] “Step away from your desk and keep working from your phone or any browser with Remote Control”
   • [claimed-docs] “Kick off a long-running task on the web or the Claude mobile app, then pull it into your terminal with `claude --teleport`.”
   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”
   • [claimed-docs] “Kick off long-running tasks and check back when they're done, work on repos you don't have locally, or run multiple tasks in parallel.”
   • [claimed-docs] “Run Claude Code in your browser with no local setup. Kick off long-running tasks and check back when they're done, work on repos you don't h…”
   • [claimed-docs] “Claude Code plans the approach, writes the code across multiple files, and verifies it works.”
   • [claimed-docs] “Claude Code works directly with git. It stages changes, writes commit messages, creates branches, and opens pull requests.”
   • [claimed-docs] “Get automatic code review on every PR | GitHub Code Review”
   • [community] “I've been using Claude Code daily for months on a project with Elixir, Rust, and Python. The worst failure mode is when it does a replace_al…”

   proof ↗⚑ flag

   OpenCode~partialclaimed6/10

   OpenCode's GitHub integration lets it work in a new branch and submit a PR autonomously when mentioned via `/opencode` in GitHub Actions, and its share-links/session feature lets a reviewer inspect the agent's work — together covering 'build' and 'demo for review' in a cloud context. However, there is no explicit documentation of an automated testing step as part of this workflow, and the 'cloud agent' aspect relies on self-hosted GitHub Actions runners rather than a dedicated managed cloud agent service. Missing for 10: explicit test-execution/validation step in the PR workflow, and a first-party fully-hosted cloud agent (not just Actions-runner based) with demo artifacts.

   • [claimed-docs] “Ask OpenCode to fix an issue or implement a feature. And it will work in a new branch and submits a PR with all the changes.”
   • [claimed-docs] “Mention `/opencode` or `/oc` in your comment, and OpenCode will execute tasks within your GitHub Actions runner.”
   • [claimed-docs] “OpenCode integrates with your GitHub workflow. Mention /opencode or /oc in your comment, and OpenCode will execute tasks within your GitHub …”
   • [claimed-docs] “**Share links** Share a link to any session for reference or to debug”
   • [claimed-docs] “Share links Share a link to any session for reference or to debug”
   • [claimed-docs] “**Multi-session** Start multiple agents in parallel on the same project”

   proof ↗⚑ flag

2. developerDelegate longer-running coding tasks to run in the background in an isolated cloud environment

   weight 3 · round to Claude Code
   Claude Code✓fullclaimed7/10

   Docs describe running Claude Code in-browser with no local setup, kicking off long-running tasks and checking back later, working on repos not present locally, running multiple tasks in parallel, and remote control/teleport features to move sessions between web/mobile and terminal — matching the delegate-to-cloud story directly. Missing for 10: independent/hands-on confirmation of the cloud environment's isolation guarantees (the sandboxing docs cited relate to local Bash tool isolation, not the cloud session itself) and details on how isolated/secure the cloud runtime is.

   • [claimed-docs] “Step away from your desk and keep working from your phone or any browser with Remote Control”
   • [claimed-docs] “Kick off a long-running task on the web or the Claude mobile app, then pull it into your terminal with `claude --teleport`.”
   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”
   • [claimed-docs] “Kick off long-running tasks and check back when they're done, work on repos you don't have locally, or run multiple tasks in parallel.”
   • [claimed-docs] “Run Claude Code in your browser with no local setup. Kick off long-running tasks and check back when they're done, work on repos you don't h…”

   proof ↗⚑ flag

   OpenCode~partialclaimed5/10

   OpenCode documents GitHub integration where mentioning /opencode or /oc triggers it to work in a new branch and submit a PR, executing tasks inside the GitHub Actions runner (an isolated cloud environment), which supports background delegation of coding tasks. However, there's no dedicated general-purpose 'cloud agent' product, persistent cloud session management, or evidence of handling arbitrarily long-running tasks outside the GitHub Actions context. missing for 10: a dedicated hosted/cloud sandbox environment independent of GitHub Actions, evidence of long-running task monitoring/resumption in the cloud, and independent hands-on confirmation of this workflow succeeding.

   • [claimed-docs] “Ask OpenCode to fix an issue or implement a feature. And it will work in a new branch and submits a PR with all the changes.”
   • [claimed-docs] “Mention `/opencode` or `/oc` in your comment, and OpenCode will execute tasks within your GitHub Actions runner.”
   • [claimed-docs] “OpenCode integrates with your GitHub workflow. Mention /opencode or /oc in your comment, and OpenCode will execute tasks within your GitHub …”
   • [claimed-docs] “This will walk you through installing the GitHub app, creating the workflow, and setting up secrets.”

   proof ↗⚑ flag

3. developerConfigure a reproducible cloud environment with the dependencies and setup steps my repository needs

   weight 2 · round to Claude Code
   Claude Code~partialclaimed3/10

   Docs mention running Claude Code in the cloud/browser with no local setup and working on repos you don't have locally, implying some environment is provisioned, but there's no documentation of configuring a reproducible environment (e.g., setup scripts, dependency installation, devcontainer-style config) for cloud sessions. missing for 10: explicit environment/config file for cloud sandboxes, dependency installation steps, reproducibility guarantees across runs.

   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”
   • [claimed-docs] “Kick off long-running tasks and check back when they're done, work on repos you don't have locally, or run multiple tasks in parallel.”
   • [claimed-docs] “Run Claude Code in your browser with no local setup. Kick off long-running tasks and check back when they're done, work on repos you don't h…”

   proof ↗⚑ flag

   OpenCode—none0/10

   The evidence shows OpenCode as a terminal/IDE agent with GitHub PR automation and a headless `serve` mode, but nothing describes a mechanism for developers to declare a reproducible cloud environment (base image, dependencies, setup scripts) that the agent provisions before running. Missing for 10: any devcontainer/config-file spec for cloud sandbox provisioning, dependency installation steps, or documented cloud execution environment configuration.

   • [claimed-docs] “Ask OpenCode to fix an issue or implement a feature. And it will work in a new branch and submits a PR with all the changes.”
   • [claimed-docs] “The opencode serve command runs a headless HTTP server that exposes an OpenAPI endpoint that an opencode client can use.”
   • [claimed-docs] “This centralized config can integrate with your SSO provider and ensures all users access only your internal AI gateway.”

   proof ↗⚑ flag

Parallel agents

1. ai-native userLaunch fleets of autonomous agents that work in parallel on different tasks for hours or days

   weight 2 · round to Claude Code
   Claude Code✓fullclaimed7/10

   Docs explicitly describe spawning multiple Claude Code agents with a lead agent coordinating subtasks, running multiple sessions/tasks in parallel in the cloud, scheduling recurring/long-running tasks, and remote/teleport control to check back later — directly matching the fleet/parallel/long-duration story. Missing for 10: independent hands-on verification of multi-day unattended fleet runs and clearer guarantees on stability over very long horizons (community reports note reliability/quality drift over extended sessions).

   • [claimed-docs] “Spawn multiple Claude Code agents that work on different parts of a task simultaneously. A lead agent coordinates the work, assigns subtasks…”
   • [claimed-docs] “Spawn multiple Claude Code agents that work on different parts of a task simultaneously.”
   • [claimed-docs] “Spawn multiple Claude Code agents that work on different parts of a task simultaneously. A lead agent coordin”
   • [claimed-docs] “Run Claude on a schedule to automate work that repeats: morning PR reviews, overnight CI failure analysis, weekly dependency audits, or sync…”
   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”
   • [claimed-docs] “Kick off long-running tasks and check back when they're done, work on repos you don't have locally, or run multiple tasks in parallel.”
   • [claimed-docs] “Run Claude Code in your browser with no local setup. Kick off long-running tasks and check back when they're done, work on repos you don't h…”
   • [claimed-docs] “Step away from your desk and keep working from your phone or any browser with Remote Control”
   • [claimed-docs] “Kick off a long-running task on the web or the Claude mobile app, then pull it into your terminal with `claude --teleport`.”

   proof ↗⚑ flag

   OpenCode~partialcommunity6/10

   OpenCode documents multi-session support ('Start multiple agents in parallel on the same project'), subagents with per-agent model choice, and GitHub Actions integration where mentioning /opencode lets it execute unattended tasks and open PRs — all pointing toward parallel, semi-autonomous agent operation. However, there is no explicit documentation or evidence of orchestrating large 'fleets' of agents or of sustained autonomous operation over hours/days, and community reports note agents 'randomly stuck, especially for long/nested sessions,' undercutting long-horizon reliability. Missing for 10: dedicated fleet-management/orchestration tooling, explicit hours/days-long autonomous run support, and independent confirmation of stable long-running parallel agent execution.

   • [claimed-docs] “**Multi-session** Start multiple agents in parallel on the same project”
   • [claimed-docs] “Multi-session Start multiple agents in parallel on the same project”
   • [community] “I really like how their subagents work, as a bonus I get to choose which model is in which agent.”
   • [claimed-docs] “Mention `/opencode` or `/oc` in your comment, and OpenCode will execute tasks within your GitHub Actions runner.”
   • [claimed-docs] “OpenCode integrates with your GitHub workflow. Mention /opencode or /oc in your comment, and OpenCode will execute tasks within your GitHub …”
   • [claimed-docs] “The `opencode serve` command runs a headless HTTP server that exposes an OpenAPI endpoint that an opencode client can use.”
   • [community] “There are random bugs with loading/restoring state of the session; Model/Provider selection switch across sessions/projects is often annoyin…”

   proof ↗⚑ flag

2. developerRun several task attempts in parallel and compare results before choosing one

   weight 1 · round to Claude Code
   Claude Code~partialclaimed6/10

   Docs mention running 'multiple sessions side by side' and reviewing diffs visually in the web/cloud interface, plus running multiple tasks in parallel and spawning multiple agents—supporting parallel execution and comparison, though not explicitly framed as multiple attempts at the *same* task with a selection step. Missing for 10: explicit documentation of running several independent attempts at one identical task and a UI/workflow for choosing the best among them, and independent hands-on confirmation of this specific workflow.

   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”
   • [claimed-docs] “Kick off long-running tasks and check back when they're done, work on repos you don't have locally, or run multiple tasks in parallel.”
   • [claimed-docs] “Run Claude Code in your browser with no local setup. Kick off long-running tasks and check back when they're done, work on repos you don't h…”
   • [claimed-docs] “Spawn multiple Claude Code agents that work on different parts of a task simultaneously. A lead agent coordinates the work, assigns subtasks…”
   • [claimed-docs] “Spawn multiple Claude Code agents that work on different parts of a task simultaneously.”

   proof ↗⚑ flag

   OpenCode~partialcommunity4/10

   OpenCode documents 'multi-session' support to start multiple agents in parallel on the same project (opencode-docs-17/38) and share links to sessions for reference/debugging (opencode-docs-18/37), which enables running parallel work and inspecting different sessions. However, there is no documented feature for running multiple attempts at the *same* task specifically to compare outcomes and pick a winner (e.g., no diff/compare UI or attempt-ranking workflow), and community threads discuss general session-state bugs rather than this comparison workflow. Missing for 10: explicit same-task multi-attempt spawning, a built-in comparison/diff view across attempts, and evidence of choosing/merging the best result.

   • [claimed-docs] “**Multi-session** Start multiple agents in parallel on the same project”
   • [claimed-docs] “Multi-session Start multiple agents in parallel on the same project”
   • [claimed-docs] “**Share links** Share a link to any session for reference or to debug”
   • [claimed-docs] “Share links Share a link to any session for reference or to debug”
   • [community] “You can start a service via 'opencode serve', it can be accessed from anywhere and has great experience on mobile except a few bugs... The W…”

   proof ↗⚑ flag

Scheduled automation

1. ai-native userSet up always-on agents that run on schedules or triggers to maintain and fix my software autonomously

   weight 2 · round to Claude Code
   Claude Code~partialcommunity7/10

   First-party docs show robust support for scheduled/triggered automation: 'Run Claude on a schedule' for recurring maintenance tasks (docs-8), 'schedule recurring tasks' in the web UI (docs-13), MCP servers that push Telegram/Discord/webhook events into a session 'while you're away' (docs-31/54), and Slack @mentions triggering PRs (docs-11), plus CI integration for automated review/triage (docs-36). However, community reports raise real concerns about autonomous reliability over sustained/unsupervised runs (e.g. degrading output quality, self-verification failures, 'can't trust it to self-verify' — comm-16, comm-17, comm-19, comm-20), which tempers confidence that always-on autonomous maintenance works robustly in practice. Missing for 10: independent/hands-on validation that scheduled/triggered agents reliably self-maintain software over time without human correction, and no explicit multi-day/continuous 'always-on' uptime evidence beyond scheduled/triggered runs.

   • [claimed-docs] “Run Claude on a schedule to automate work that repeats: morning PR reviews, overnight CI failure analysis, weekly dependency audits, or sync…”
   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”
   • [claimed-docs] “an MCP server can also act as a channel that pushes messages into your session, so Claude reacts to Telegram messages, Discord chats, or web…”
   • [claimed-docs] “an MCP server can also act as a channel that pushes messages into your session, so Claude reacts to Telegram messages, Discord chats, or web…”
   • [claimed-docs] “Route tasks from team chat: mention @Claude in Slack with a bug report and get a pull request back”
   • [claimed-docs] “In CI, you can automate code review and issue triage with GitHub Actions or GitLab CI/CD.”
   • [community] “I've been using Claude Code daily for months on a project with Elixir, Rust, and Python. The worst failure mode is when it does a replace_al…”
   • [community] “Whenever the phrase 'simplest fix' appears, it's time to pull the emergency break. This has gotten much worse over the past few weeks. It wi…”
   • [community] “I've tried to use Claude code for a month now. It has a 100% failure rate so far. Comparing that to creating a project and just chatting wit…”
   • [community] “A month ago the agents researched, designed, and implemented a compelling app idea with minimal guidance and felt super human. A month later…”

   proof ↗⚑ flag

   OpenCode—none0/10

   OpenCode documents CLI/TUI/desktop agents, permission automation, GitHub Actions integration triggered by comments, and a headless server/SDK, but there is no evidence of scheduling (cron-like) or event-trigger-based always-on autonomous agents that proactively maintain/fix software without a user or PR-comment invocation. The GitHub integration is triggered by manual mentions, not autonomous scheduled monitoring. Missing for 10: scheduled/cron-based agent runs, event-driven triggers beyond manual mentions, autonomous 'always-on' background maintenance capability.

   • [claimed-docs] “Ask OpenCode to fix an issue or implement a feature. And it will work in a new branch and submits a PR with all the changes.”
   • [claimed-docs] “Mention `/opencode` or `/oc` in your comment, and OpenCode will execute tasks within your GitHub Actions runner.”
   • [claimed-docs] “OpenCode integrates with your GitHub workflow. Mention /opencode or /oc in your comment, and OpenCode will execute tasks within your GitHub …”
   • [claimed-docs] “The `opencode serve` command runs a headless HTTP server that exposes an OpenAPI endpoint that an opencode client can use.”
   • [claimed-docs] “OpenCode uses the `permission` config to decide whether a given action should run automatically, prompt you, or be blocked.”
   • [claimed-docs] “Start OpenCode with `--auto` to automatically approve permission requests that are not explicitly denied.”

   proof ↗⚑ flag

Code completion

1. developerReceive inline code completions and next-edit suggestions as I type

   weight 3 · round drawn
   Claude Code—none0/10

   Claude Code's documented interaction model is conversational/agentic (terminal commands, plan-then-execute, PR generation) and its IDE extensions offer inline diffs and @-mentions, not ghost-text style inline completions or next-edit suggestions as the user types. No evidence pack item describes autocomplete-style inline suggestions.

   • [claimed-docs] “The VS Code extension provides inline diffs, @-mentions, plan review, and conversation history directly in your editor.”
   • [claimed-docs] “A plugin for IntelliJ IDEA, PyCharm, WebStorm, and other JetBrains IDEs with interactive diff viewing and selection context sharing.”

   proof ↗⚑ flag

   OpenCode—none0/10

   OpenCode is presented as an agent-driven terminal/desktop/IDE-extension tool that responds to explicit prompts, runs agents, and edits files via chat-like sessions — there is no mention of inline ghost-text completions or next-edit suggestions as the developer types. The IDE integration docs describe opening a terminal split and inserting file references, not autocomplete.

   • [claimed-docs] “OpenCode integrates with VS Code, Cursor, or any IDE that supports a terminal. Just run `opencode` in the terminal to get started.”
   • [claimed-docs] “Use Cmd+Esc (Mac) or Ctrl+Esc (Windows/Linux) to open OpenCode in a split terminal view”
   • [claimed-docs] “Use Cmd+Option+K (Mac) or Alt+Ctrl+K (Linux/Windows) to insert file references.”
   • [claimed-docs] “OpenCode is an open source AI coding agent. It's available as a terminal-based interface, desktop app, or IDE extension.”

   proof ↗⚑ flag

Debugging

1. developerDebug issues and troubleshoot using natural-language queries

   weight 2 · round drawn
   Claude Code✓fullcommunity7/10

   Docs explicitly cover debugging: 'Debug live web applications' (Chrome integration), 'overnight CI failure analysis', explaining complex code, and codebase-wide understanding to trace issues via natural-language prompts. This is core positioning ('Build, debug, and ship from your terminal, IDE...'). missing for 10: independent hands-on validation specifically of debugging workflows (community evidence instead highlights reliability issues like self-verification failures and bugs introduced during edits, which are adjacent but not direct proof debugging-via-NL fails).

   • [claimed-docs] “Debug live web applications | Chrome”
   • [claimed-docs] “Run Claude on a schedule to automate work that repeats: morning PR reviews, overnight CI failure analysis, weekly dependency audits, or sync…”
   • [claimed-docs] “Work with Claude directly in your codebase. Build, debug, and ship from your terminal, IDE, Slack, web, and more.”
   • [claimed-docs] “It understands your entire codebase and can work across multiple files and tools to get things done.”
   • [github] “helps you code faster by executing routine tasks, explaining complex code, and handling git workflows -- all through natural language comman…”
   • [community] “I've been using Claude Code daily for months on a project with Elixir, Rust, and Python. The worst failure mode is when it does a replace_al…”

   proof ↗⚑ flag

   OpenCode✓fullcommunity7/10

   OpenCode is a terminal/IDE-based coding agent that takes natural-language queries (e.g. `opencode run "Explain how closures work..."`), can explore/read codebases via a dedicated read-only agent, and auto-loads LSPs so it can surface diagnostics/errors while chatting, all of which supports NL-driven debugging and troubleshooting; community users confirm using it as a daily 'harness' with good LSP integration for real work. missing for 10: no dedicated 'debug' or troubleshooting workflow docs, and community reports of failed tool calls/unreliable file edits with some models introduce real-world friction.

   • [claimed-docs] “opencode run "Explain how closures work in JavaScript"”
   • [claimed-docs] “A fast, read-only agent for exploring codebases.”
   • [claimed-docs] “A fast, read-only agent for exploring codebases. Cannot modify files.”
   • [claimed-docs] “LSP enabled Automatically loads the right LSPs for the LLM”
   • [community] “i've been using this as my primary harness for llama.cpp models, Claude, and Gemini for a few months now. the LSP integration is great.”
   • [community] “I've been trying various harnesses like Pi, OpenCode, Qwen Code, and Nanocoder. A common problem I keep running into is failed tool calls, r…”

   proof ↗⚑ flag

Feature implementation

1. developerTurn a tracked issue into a complete pull request end-to-end

   weight 3 · round drawn
   Claude Code✓fullcommunity7/10

   Docs explicitly describe the full loop: reading tracked issues (Jira, GitHub, Slack) via MCP, generating code across multiple files, running tests, creating branches, and opening PRs — e.g. 'Add the feature described in JIRA issue ENG-4521 and create a PR on GitHub' and 'reading issues, writing code, running tests, and submitting PRs—all from your terminal.' Community reports corroborate real-world usage but also note reliability issues (self-verification failures, quality degradation over time), so results aren't guaranteed to be flawless end-to-end. Missing for 10: independent case studies quantifying success rate of full issue-to-PR automation, and detail on how failures/test verification are handled when the generated PR doesn't pass CI.

   • [claimed-docs] “Claude Code works directly with git. It stages changes, writes commit messages, creates branches, and opens pull requests.”
   • [claimed-docs] “Claude Code integrates with GitHub, GitLab, and your command line tools to handle the entire workflow—reading issues, writing code, running …”
   • [claimed-docs] “Implement features from issue trackers: "Add the feature described in JIRA issue ENG-4521 and create a PR on GitHub."”
   • [claimed-docs] “Add the feature described in JIRA issue ENG-4521 and create a PR on GitHub.”
   • [claimed-docs] “Route tasks from team chat: mention @Claude in Slack with a bug report and get a pull request back”
   • [community] “I've been using Claude Code daily for months on a project with Elixir, Rust, and Python. The worst failure mode is when it does a replace_al…”
   • [community] “I've tried to use Claude code for a month now. It has a 100% failure rate so far. Comparing that to creating a project and just chatting wit…”

   proof ↗⚑ flag

   OpenCode✓fullclaimed7/10

   Docs explicitly state OpenCode can be asked to fix an issue or implement a feature, working in a new branch and submitting a PR with all changes, and it integrates with GitHub Actions via /opencode mentions to run tasks end-to-end. This directly covers issue-to-PR automation, though evidence is vendor-documented only without independent hands-on confirmation of the full issue-to-PR flow succeeding. Missing for 10: independent/community verification of a successful end-to-end issue-to-PR run, and detail on how issue tracking (e.g., linking to GitHub issues specifically) is handled beyond the GitHub Actions integration.

   • [claimed-docs] “Ask OpenCode to fix an issue or implement a feature. And it will work in a new branch and submits a PR with all the changes.”
   • [claimed-docs] “OpenCode integrates with your GitHub workflow. Mention /opencode or /oc in your comment, and OpenCode will execute tasks within your GitHub …”
   • [claimed-docs] “This will walk you through installing the GitHub app, creating the workflow, and setting up secrets.”
   • [claimed-docs] “Mention `/opencode` or `/oc` in your comment, and OpenCode will execute tasks within your GitHub Actions runner.”

   proof ↗⚑ flag

2. developerDescribe a feature or bug in plain language and have the agent implement or fix it across multiple files

   weight 3 · round to OpenCode
   Claude Code!disputedcontradicted6/10

   Docs strongly claim the core capability: describe a feature/bug in plain language and Claude Code plans, implements, and verifies code changes across multiple files (claude-code-docs-2/28/51/20, claude-code-gh-3). However, hands-on community reports cite concrete failures undermining reliability of multi-file edits, e.g. a replace_all bug corrupting a constant (GROQ_URL=GROQ_URL) and inability to self-verify, plus a user reporting a '100% failure rate' and quality degradation over time (claude-code-comm-16, claude-code-comm-17, claude-code-comm-19, claude-code-comm-20), balanced against other users praising its code-assistant ability (claude-code-comm-5). missing for 10: consistent independent benchmarks confirming reliability across diverse multi-file tasks, resolution of reported failure modes.

   • [claimed-docs] “Describe what you want in plain language. Claude Code plans the approach, writes the code across multiple files, and verifies it works.”
   • [claimed-docs] “Claude Code plans the approach, writes the code across multiple files, and verifies it works.”
   • [claimed-docs] “It understands your entire codebase and can work across multiple files and tools to get things done.”
   • [claimed-docs] “Claude Code handles the tedious tasks that eat up your day: writing tests for untested code, fixing lint errors across a project, resolving …”
   • [github] “helps you code faster by executing routine tasks, explaining complex code, and handling git workflows -- all through natural language comman…”
   • [community] “I've been using Claude Code daily for months on a project with Elixir, Rust, and Python. The worst failure mode is when it does a replace_al…”
   • [community] “Whenever the phrase 'simplest fix' appears, it's time to pull the emergency break. This has gotten much worse over the past few weeks. It wi…”
   • [community] “I've tried to use Claude code for a month now. It has a 100% failure rate so far. Comparing that to creating a project and just chatting wit…”
   • [community] “A month ago the agents researched, designed, and implemented a compelling app idea with minimal guidance and felt super human. A month later…”
   • [community] “Claude is significantly better than other models at code assistant tasks, or at least in the way I use it.”

   proof ↗⚑ flag

   OpenCode✓fullcommunity8/10

   OpenCode is explicitly a coding agent that takes plain-language instructions and edits code, with docs describing it fixing issues/implementing features and submitting PRs (opencode-docs-12), a CLI for prompting tasks (opencode-docs-22), and permission/auto-approve config for autonomous multi-file changes (opencode-docs-13/14). Community reports corroborate real-world multi-file coding use, with several users calling it their primary harness replacing Aider/Claude Code (opencode-comm-1, opencode-comm-3, opencode-comm-4, opencode-comm-11, opencode-comm-14), though some report unreliable file edits with certain local models and failed tool calls in general (opencode-comm-10, opencode-comm-12). Missing for 10: independent benchmark data on multi-file edit accuracy, and resolution of the reported local-model editing reliability issues.

   • [claimed-docs] “OpenCode is an open source AI coding agent. It's available as a terminal-based interface, desktop app, or IDE extension.”
   • [claimed-docs] “Ask OpenCode to fix an issue or implement a feature. And it will work in a new branch and submits a PR with all the changes.”
   • [claimed-docs] “OpenCode uses the `permission` config to decide whether a given action should run automatically, prompt you, or be blocked.”
   • [claimed-docs] “Start OpenCode with `--auto` to automatically approve permission requests that are not explicitly denied.”
   • [claimed-docs] “opencode run "Explain how closures work in JavaScript"”
   • [community] “I really like how their subagents work, as a bonus I get to choose which model is in which agent.”
   • [community] “i've been using this as my primary harness for llama.cpp models, Claude, and Gemini for a few months now. the LSP integration is great.”
   • [community] “This replaced Aider for me a couple months back. I use it with Qwen 3.5 running locally when my daily limits run out on my other subscriptio…”
   • [community] “Claude is much better in OpenCode then in Claude Code, OpenCode is just better than Claude Code. Claude Code feels like a complete mess to u…”
   • [community] “OpenCode is awesome. Claude Code is nothing special at all. Last month I switched to just using OpenCode with a Codex $200/mo subscription, …”
   • [community] “I haven't been able to successfully get their CLI to reliably edit files when using local models, anybody else having the same problem?”
   • [community] “I've been trying various harnesses like Pi, OpenCode, Qwen Code, and Nanocoder. A common problem I keep running into is failed tool calls, r…”

   proof ↗⚑ flag

Maintenance automation

1. developerHave the agent write tests, fix lint errors, resolve merge conflicts, and update dependencies for me

   weight 3 · round to Claude Code
   Claude Code✓fullcommunity8/10

   First-party docs explicitly list this exact story's capabilities verbatim ('writing tests for untested code, fixing lint errors across a project, resolving merge conflicts, updating dependencies') and Claude Code is broadly documented as an agentic coding assistant that edits files, runs commands, and manages projects end-to-end. Community feedback confirms general coding competence but also raises reliability concerns (e.g., self-verification failures) not specific to these four tasks. Missing for 10: independent hands-on verification specifically for lint-fixing, merge-conflict resolution, and dependency updates rather than general coding tasks.

   • [claimed-docs] “writing tests for untested code, fixing lint errors across a project, resolving merge conflicts, updating dependencies, and writing release …”
   • [claimed-docs] “Claude Code handles the tedious tasks that eat up your day: writing tests for untested code, fixing lint errors across a project, resolving …”
   • [claimed-docs] “Claude Code maps and explains entire codebases in a few seconds. It uses agentic search to understand project structure and dependencies wit…”
   • [claimed-docs] “Claude Code integrates with GitHub, GitLab, and your command line tools to handle the entire workflow—reading issues, writing code, running …”
   • [community] “Claude is significantly better than other models at code assistant tasks, or at least in the way I use it.”

   proof ↗⚑ flag

   OpenCode~partialcommunity6/10

   OpenCode is documented as a general-purpose coding agent that can edit files, run shell commands, and even autonomously fix issues and submit PRs (opencode-docs-12, opencode-docs-58), which implies it can perform tasks like writing tests, fixing lint, resolving conflicts, and updating deps as generic coding actions. However, none of the docs explicitly call out test-writing, lint-fixing, merge-conflict resolution, or dependency updates as named capabilities, and community reports note reliability gaps such as failed tool calls and unreliable file edits especially with local models (opencode-comm-10, opencode-comm-12). Missing for 10: explicit documentation or hands-on evidence of test generation, lint-fix workflows, merge-conflict resolution, and dependency-update automation.

   • [claimed-docs] “Ask OpenCode to fix an issue or implement a feature. And it will work in a new branch and submits a PR with all the changes.”
   • [claimed-docs] “OpenCode integrates with your GitHub workflow. Mention /opencode or /oc in your comment, and OpenCode will execute tasks within your GitHub …”
   • [claimed-docs] “OpenCode uses the `permission` config to decide whether a given action should run automatically, prompt you, or be blocked.”
   • [community] “i've been using this as my primary harness for llama.cpp models, Claude, and Gemini for a few months now. the LSP integration is great.”
   • [community] “This replaced Aider for me a couple months back. I use it with Qwen 3.5 running locally when my daily limits run out on my other subscriptio…”
   • [community] “I haven't been able to successfully get their CLI to reliably edit files when using local models, anybody else having the same problem?”
   • [community] “I've been trying various harnesses like Pi, OpenCode, Qwen Code, and Nanocoder. A common problem I keep running into is failed tool calls, r…”

   proof ↗⚑ flag

Multimodal generation

1. ai-native userGenerate a working app from a sketch, image, or PDF design

   weight 2 · round drawn
   Claude Code—none0/10

   The evidence pack describes Claude Code's general coding, git, MCP, and automation capabilities but never mentions accepting a sketch, image, or PDF as design input to scaffold or generate an app. The closest reference (claude-code-docs-23) only describes updating an email template from Figma designs shared in Slack, not app generation from visual designs. Missing for 10: any documentation or example of image/PDF/sketch-to-code app generation, multimodal input support in the CLI, or a demonstrated workflow turning a design mockup into a working application.

   ⚑ flag

   OpenCode—none0/10

   OpenCode's evidence pack shows a terminal/IDE-based coding agent with text prompts, MCP, agents, and CLI/SDK, but there is no mention anywhere of image, sketch, or PDF design input being converted into a working app — no vision/multimodal input capability is documented.

   ⚑ flag

Codebase mapping

1. developerUnderstand how a codebase fits together to find where to start making changes

   weight 3 · round drawn
   Claude Code✓fullclaimed7/10

   Docs explicitly claim Claude Code 'maps and explains entire codebases in a few seconds' using agentic search to understand project structure and dependencies without manual context selection, and separately states it 'understands your entire codebase' across files; CLAUDE.md further lets teams encode architecture decisions for onboarding. Missing for 10: independent/hands-on corroboration specifically validating codebase-mapping accuracy, and no benchmark or case study showing it correctly locates the right starting point in a large real-world repo.

   • [claimed-docs] “Claude Code maps and explains entire codebases in a few seconds. It uses agentic search to understand project structure and dependencies wit…”
   • [claimed-docs] “It understands your entire codebase and can work across multiple files and tools to get things done.”
   • [claimed-docs] “CLAUDE.md is a markdown file you add to your project root that Claude Code reads at the start of every session.”
   • [claimed-docs] “CLAUDE.md is a markdown file you add to your project root that Claude Code reads at the start of every session. Use it to set coding standar…”

   proof ↗⚑ flag

   OpenCode✓fullcommunity7/10

   OpenCode ships a dedicated read-only 'explore' agent for scanning codebases and a 'plan' agent that analyzes code and proposes changes without modifying files, backed by automatic LSP loading for the right language context and skills that surface repo-specific instructions; community notes call the LSP integration 'great' for understanding code. Missing for 10: no dedicated codebase-mapping/visualization feature, no independent benchmark of comprehension quality, and no first-hand user account describing successful architecture-level onboarding via these agents.

   • [claimed-docs] “A fast, read-only agent for exploring codebases.”
   • [claimed-docs] “A fast, read-only agent for exploring codebases. Cannot modify files.”
   • [claimed-docs] “Use the plan agent to analyze code and review suggestions without making any code changes.”
   • [claimed-docs] “This agent is useful when you want the LLM to analyze code, suggest changes, or create plans without making any actual modifications to your…”
   • [claimed-docs] “LSP enabled Automatically loads the right LSPs for the LLM”
   • [claimed-docs] “Agent skills let OpenCode discover reusable instructions from your repo or home directory. Skills are loaded on-demand via the native `skill…”
   • [community] “i've been using this as my primary harness for llama.cpp models, Claude, and Gemini for a few months now. the LSP integration is great.”

   proof ↗⚑ flag

2. developerHave the agent map and explain an entire unfamiliar codebase without manually selecting context files

   weight 3 · round to Claude Code
   Claude Code✓fullclaimed7/10

   Claude Code's own product page explicitly states it 'maps and explains entire codebases in a few seconds' using 'agentic search to understand project structure and dependencies without you having to manually select context files,' directly matching the story, and other docs reinforce that it 'understands your entire codebase' across multiple files. Missing for 10: independent/hands-on evidence specifically corroborating the automatic codebase-mapping claim (community evidence covers general coding quality/trust issues but not this specific feature).

   • [claimed-docs] “Claude Code maps and explains entire codebases in a few seconds. It uses agentic search to understand project structure and dependencies wit…”
   • [claimed-docs] “It understands your entire codebase and can work across multiple files and tools to get things done.”
   • [claimed-docs] “CLAUDE.md is a markdown file you add to your project root that Claude Code reads at the start of every session.”

   proof ↗⚑ flag

   OpenCode~partialcommunity6/10

   OpenCode ships a dedicated read-only 'explore' agent explicitly for exploring codebases and a plan agent for analyzing code without edits, plus automatic LSP loading that gives it broader code awareness without manual file picking. However there's no documented feature for generating a full repo map/summary or explicit 'explain this whole codebase' workflow beyond agent tool use (e.g. grep/glob/read), and no independent hands-on evidence confirming it successfully maps a large unfamiliar codebase end-to-end. Missing for 10: explicit repo-map/codebase-summary feature, hands-on/independent confirmation of whole-codebase explanation without manual context selection.

   • [claimed-docs] “A fast, read-only agent for exploring codebases.”
   • [claimed-docs] “A fast, read-only agent for exploring codebases. Cannot modify files.”
   • [claimed-docs] “This agent is useful when you want the LLM to analyze code, suggest changes, or create plans without making any actual modifications to your…”
   • [claimed-docs] “LSP enabled Automatically loads the right LSPs for the LLM”
   • [claimed-docs] “opencode run "Explain how closures work in JavaScript"”
   • [community] “i've been using this as my primary harness for llama.cpp models, Claude, and Gemini for a few months now. the LSP integration is great.”

   proof ↗⚑ flag

Context management

1. developerHave the agent build and recall memory automatically across sessions

   weight 2 · round to Claude Code
   Claude Code~partialclaimed4/10

   Claude Code supports persistent project context via CLAUDE.md, which it reads at the start of every session, giving some continuity of 'memory' across sessions, and the VS Code extension keeps conversation history in-editor. However, this is a manually authored/maintained file, not an automatically built or recalled memory system that captures learnings from prior sessions without user intervention. Missing for 10: evidence of automatic memory formation/summarization from past sessions, automatic recall of prior task context without a manually maintained file, and any documentation of a persistent 'agent memory' feature beyond CLAUDE.md.

   • [claimed-docs] “CLAUDE.md is a markdown file you add to your project root that Claude Code reads at the start of every session.”
   • [claimed-docs] “CLAUDE.md is a markdown file you add to your project root that Claude Code reads at the start of every session. Use it to set coding standar…”
   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”

   proof ↗⚑ flag

   OpenCode—none0/10

   No evidence in the pack describes any persistent memory feature that automatically builds or recalls context/knowledge across separate sessions; docs cover sessions, sharing, agents, MCP, skills, and permissions, but nothing about automatic cross-session memory persistence or recall.

   ⚑ flag

2. developerInclude multiple project directories in a single session for broader context

   weight 2 · round drawn
   Claude Code—none0/10

   The evidence pack describes Claude Code understanding a single project's entire codebase and working across multiple files within it, but there is no mention of including multiple separate project directories in one session (e.g., an --add-dir style flag or multi-root workspace support).

   ⚑ flag

   OpenCode—none0/10

   The evidence shows a permission flag (`external_directory`) that lets tool calls touch paths outside the working directory, but there is no documentation or community report describing a way to add multiple project directories into a single session for combined context. Multi-session and multi-agent features are about running parallel sessions, not merging directories into one context.

   • [claimed-docs] “Use external_directory to allow tool calls that touch paths outside the working directory where OpenCode was started.”
   • [claimed-docs] “**Multi-session** Start multiple agents in parallel on the same project”
   • [claimed-docs] “Multi-session Start multiple agents in parallel on the same project”

   proof ↗⚑ flag

3. developerAdd a project instructions file to set coding standards and conventions the agent follows

   weight 3 · round to Claude Code
   Claude Code✓fullcommunity9/10

   First-party docs explicitly describe CLAUDE.md as a project-root markdown file read at every session start, used to set coding standards, architecture decisions, preferred libraries, and review checklists (claude-code-docs-5, claude-code-docs-22). Community evidence (claude-code-comm-15) independently confirms real-world use of CLAUDE.md files for guiding the agent, corroborating the feature exists and is actively used. Missing for 10: broader independent/hands-on documentation of best practices or examples beyond a single community mention.

   • [claimed-docs] “CLAUDE.md is a markdown file you add to your project root that Claude Code reads at the start of every session.”
   • [claimed-docs] “CLAUDE.md is a markdown file you add to your project root that Claude Code reads at the start of every session. Use it to set coding standar…”
   • [community] “I've found that I have to add more and more CLAUDE.md guide rails, and my CLAUDE.md files have been exploding since around mid-March... I've…”

   proof ↗⚑ flag

   OpenCode~partialclaimed5/10

   OpenCode's docs mention an `opencode init` step to set up a project (docs-21/39/56) and 'Agent skills' that let OpenCode discover reusable instructions from a repo or home directory (docs-8/28), which suggests some mechanism for project-level guidance, but no evidence explicitly describes a dedicated instructions/config file (e.g., AGENTS.md) for coding standards and conventions. Missing for 10: explicit documentation of a project instructions file format, guidance on writing coding-standards content into it, and independent/hands-on confirmation that the agent actually follows such a file.

   • [claimed-docs] “initialize OpenCode for the project by running the following command.”
   • [claimed-docs] “Next, initialize OpenCode for the project by running the following command.”
   • [claimed-docs] “initialize OpenCode for the project by running the following command”
   • [claimed-docs] “Agent skills let OpenCode discover reusable instructions from your repo or home directory. Skills are loaded on-demand via the native `skill…”
   • [claimed-docs] “Agent skills let OpenCode discover reusable instructions from your repo or home directory.”

   proof ↗⚑ flag

Issue diagnosis

1. developerReproduce issues, narrow down root causes, and verify fixes

   weight 3 · round to OpenCode
   Claude Code!disputedcontradicted5/10

   Docs claim Claude Code can debug live apps, plan fixes, and 'verifies it works' across multi-file changes (claude-code-docs-2/17/28/51), supporting reproduce/root-cause/verify workflows, but hands-on community reports give a concrete counter-example where self-verification failed (a replace_all bug silently corrupted a constant, 'You absolutely can't trust it to self-verify') and describe recurring low-quality 'simplest fix' patches that break things (claude-code-comm-16, claude-code-comm-17). missing for 10: independent benchmark/case study specifically on bug reproduction and root-cause isolation, and resolution of the self-verification reliability concerns raised by users.

   • [claimed-docs] “Describe what you want in plain language. Claude Code plans the approach, writes the code across multiple files, and verifies it works.”
   • [claimed-docs] “Debug live web applications | Chrome”
   • [claimed-docs] “Claude Code plans the approach, writes the code across multiple files, and verifies it works.”
   • [claimed-docs] “It understands your entire codebase and can work across multiple files and tools to get things done.”
   • [community] “I've been using Claude Code daily for months on a project with Elixir, Rust, and Python. The worst failure mode is when it does a replace_al…”
   • [community] “Whenever the phrase 'simplest fix' appears, it's time to pull the emergency break. This has gotten much worse over the past few weeks. It wi…”

   proof ↗⚑ flag

   OpenCode~partialcommunity5/10

   OpenCode's general coding-agent capabilities (shell/tool execution, LSP integration, a read-only 'explore' agent, and a 'plan' agent for analysis without changes) imply support for investigating bugs and iterating on fixes, and community feedback confirms strong LSP-based codebase navigation. However, there is no explicit documentation of a reproduce/debug/verify workflow, test running, or root-cause tooling, and community reports cite failed tool calls and agents getting stuck on long sessions, undermining reliability for this exact workflow. Missing for 10: explicit debugging/test-execution documentation, first-party guidance on reproducing bugs or verifying fixes, and independent hands-on confirmation of successful root-cause workflows.

   • [claimed-docs] “A fast, read-only agent for exploring codebases.”
   • [claimed-docs] “This agent is useful when you want the LLM to analyze code, suggest changes, or create plans without making any actual modifications to your…”
   • [claimed-docs] “A fast, read-only agent for exploring codebases. Cannot modify files.”
   • [community] “i've been using this as my primary harness for llama.cpp models, Claude, and Gemini for a few months now. the LSP integration is great.”
   • [community] “I've been trying various harnesses like Pi, OpenCode, Qwen Code, and Nanocoder. A common problem I keep running into is failed tool calls, r…”
   • [community] “There are random bugs with loading/restoring state of the session; Model/Provider selection switch across sessions/projects is often annoyin…”

   proof ↗⚑ flag

Marketplace

1. developerEquip the agent with custom skills to perform specialized tasks

   weight 1 · round drawn
   Claude Code✓fullclaimed8/10

   Claude Code explicitly supports custom Skills ('Create skills to package repeatable workflows your team can share, like /review-pr or /deploy-staging') plus a scaffolding plugin (mcp-server-dev) for building custom tool integrations, giving developers a documented mechanism to equip the agent with specialized, shareable capabilities. Missing for 10: independent hands-on validation of the skills system's reliability/quality beyond first-party docs.

   • [claimed-docs] “Create skills to package repeatable workflows your team can share, like `/review-pr` or `/deploy-staging`.”
   • [claimed-docs] “You can also have Claude scaffold a server for you with the official mcp-server-dev plugin”
   • [claimed-docs] “Claude Code can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”

   proof ↗⚑ flag

   OpenCode✓fullcommunity8/10

   OpenCode has a dedicated 'Agent Skills' feature that lets it discover reusable, on-demand instructions from repo or home directory via a native `skill` tool, directly matching the custom-skills story, and this is corroborated by community praise for its subagents/customizability. Missing for 10: no independent hands-on report specifically testing custom skill authoring/loading, and no detail on skill packaging/sharing ecosystem.

   • [claimed-docs] “Agent skills let OpenCode discover reusable instructions from your repo or home directory. Skills are loaded on-demand via the native `skill…”
   • [claimed-docs] “Agent skills let OpenCode discover reusable instructions from your repo or home directory.”
   • [community] “I really like how their subagents work, as a bonus I get to choose which model is in which agent.”

   proof ↗⚑ flag

2. engineering-leadIntegrate third-party partner-built agent apps into my workflows

   weight 1 · round to Claude Code
   Claude Code~partialclaimed6/10

   Claude Code supports MCP integration with third-party tools/servers (Notion, Jira, Slack, Google Drive, custom servers) and can be extended via the Agent SDK, plugins, and Slack/GitHub integrations, enabling integration of partner-built apps into workflows. However, there's no explicit evidence of a curated marketplace or formal partner-app ecosystem comparable to a dedicated app store, and integration relies mainly on generic MCP connectors rather than pre-built 'partner agent apps.' Missing for 10: a documented partner/marketplace program for third-party agent apps, independent verification of partner integrations working reliably, and case studies of engineering teams integrating named partner-built agents.

   • [claimed-docs] “With MCP, Claude Code can read your design docs in Google Drive, update tickets in Jira, pull data from Slack, or use your own custom toolin…”
   • [claimed-docs] “Claude Code can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”
   • [claimed-docs] “claude mcp add --transport http notion https://mcp.notion.com/mcp”
   • [claimed-docs] “You can also have Claude scaffold a server for you with the official mcp-server-dev plugin”
   • [claimed-docs] “the Agent SDK lets you build your own agents powered by Claude Code's tools and capabilities, with full control over orchestration, tool acc…”
   • [claimed-docs] “Route tasks from team chat: mention @Claude in Slack with a bug report and get a pull request back”

   proof ↗⚑ flag

   OpenCode~partialclaimed5/10

   OpenCode supports MCP (local/remote servers) to add external tools, has an SDK/headless server for programmatic integrations, and GitHub Actions integration—these enable connecting third-party agent apps/tools into workflows. However, there's no evidence of a curated partner marketplace or vendor-vetted third-party 'agent apps' ecosystem beyond generic MCP/tool integration. missing for 10: a documented partner/marketplace ecosystem of pre-built third-party agent apps, case studies of integrating named partner agents, and independent verification of such integrations working smoothly.

   • [claimed-docs] “You can add external tools to OpenCode using the _Model Context Protocol_, or MCP. OpenCode supports both local and remote servers.”
   • [claimed-docs] “You can add external tools to OpenCode using the _Model Context Protocol_, or MCP.”
   • [claimed-docs] “The opencode JS/TS SDK provides a type-safe client for interacting with the server. Use it to build integrations and control opencode progra…”
   • [claimed-docs] “The opencode serve command runs a headless HTTP server that exposes an OpenAPI endpoint that an opencode client can use.”
   • [claimed-docs] “OpenCode integrates with your GitHub workflow. Mention /opencode or /oc in your comment, and OpenCode will execute tasks within your GitHub …”

   proof ↗⚑ flag

Team knowledge

1. engineering-leadCreate a shared workspace from my docs and repos as a common source of truth for the team

   weight 1 · round to Claude Code
   Claude Code~partialclaimed5/10

   CLAUDE.md gives teams a shared, repo-committed markdown file for coding standards, architecture decisions, and review checklists that Claude reads every session, and shareable Skills (e.g. /review-pr, /deploy-staging) let a lead codify team workflows; MCP integrations let Claude also pull in Google Drive docs, Jira tickets, and Slack data as additional context sources. However, this is scattered configuration/context-injection tooling rather than a dedicated 'workspace' or knowledge-base product that unifies docs and repos into one queryable source of truth for the whole team. Missing for 10: a purpose-built shared workspace/knowledge-base UI, cross-repo aggregation, and evidence of team-wide adoption/governance beyond per-repo CLAUDE.md files.

   • [claimed-docs] “CLAUDE.md is a markdown file you add to your project root that Claude Code reads at the start of every session.”
   • [claimed-docs] “CLAUDE.md is a markdown file you add to your project root that Claude Code reads at the start of every session. Use it to set coding standar…”
   • [claimed-docs] “Create skills to package repeatable workflows your team can share, like `/review-pr` or `/deploy-staging`.”
   • [claimed-docs] “With MCP, Claude Code can read your design docs in Google Drive, update tickets in Jira, pull data from Slack, or use your own custom toolin…”
   • [claimed-docs] “Claude Code can read your design docs in Google Drive, update tickets in Jira, pull data from Slack, or use your own custom tooling.”

   proof ↗⚑ flag

   OpenCode—none0/10

   OpenCode offers session share links, repo-based 'agent skills', and enterprise SSO/config, but there is no evidence of a dedicated shared workspace feature that ingests both docs and repos into a common, persistent team source of truth — these are separate, ad-hoc mechanisms rather than a unified workspace.

   ⚑ flag

Tool integration

1. developerConnect the agent to workflow tools like Jira, Slack, and Google Drive to extend its context

   weight 3 · round to Claude Code
   Claude Code✓fullclaimed9/10

   Docs explicitly state Claude Code can connect via MCP to Jira, Slack, Google Drive, and other custom tooling, with concrete examples (updating Jira tickets, pulling Slack data, Notion MCP server add command) and multiple transport options. Missing for 10: independent/hands-on third-party confirmation of these specific integrations working in practice beyond vendor docs.

   • [claimed-docs] “Claude Code can read your design docs in Google Drive, update tickets in Jira, pull data from Slack, or use your own custom tooling.”
   • [claimed-docs] “With MCP, Claude Code can read your design docs in Google Drive, update tickets in Jira, pull data from Slack, or use your own custom toolin…”
   • [claimed-docs] “Update our standard email template based on the new Figma designs that were posted in Slack”
   • [claimed-docs] “Claude Code can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”
   • [claimed-docs] “Implement features from issue trackers: "Add the feature described in JIRA issue ENG-4521 and create a PR on GitHub."”
   • [claimed-docs] “claude mcp add --transport http notion https://mcp.notion.com/mcp”
   • [claimed-docs] “Add the feature described in JIRA issue ENG-4521 and create a PR on GitHub.”

   proof ↗⚑ flag

   OpenCode~partialclaimed5/10

   OpenCode supports MCP for adding external tools (local and remote servers), which is the generic mechanism by which one could connect Jira/Slack/Google Drive-type integrations, but there is no direct first-party or community evidence of specific Jira, Slack, or Google Drive connectors or integrations. missing for 10: named first-party or community-verified MCP servers/integrations for Jira, Slack, or Google Drive specifically, and any evidence of workflow-tool context extension beyond generic MCP support.

   • [claimed-docs] “You can add external tools to OpenCode using the _Model Context Protocol_, or MCP. OpenCode supports both local and remote servers.”
   • [claimed-docs] “You can add external tools to OpenCode using the Model Context Protocol, or MCP.”
   • [claimed-docs] “You can add external tools to OpenCode using the _Model Context Protocol_, or MCP.”

   proof ↗⚑ flag

2. developerKick off agent tasks directly from GitHub, GitLab, Linear, or Slack

   weight 2 · round to Claude Code
   Claude Code~partialclaimed7/10

   Docs confirm task kickoff from GitHub (@claude mentions, GitHub Code Review, GitHub Actions) and Slack (@Claude mention returns a PR), plus GitLab CI/CD integration, but there is no evidence of Linear integration or a Linear-triggered agent workflow. missing for 10: explicit Linear integration/trigger support, independent/hands-on confirmation of cross-platform task kickoff.

   • [github] “Use it in your terminal, IDE, or tag @claude on Github.”
   • [claimed-docs] “Route tasks from team chat: mention @Claude in Slack with a bug report and get a pull request back”
   • [claimed-docs] “Get automatic code review on every PR | GitHub Code Review”
   • [claimed-docs] “Claude Code integrates with GitHub, GitLab, and your command line tools to handle the entire workflow—reading issues, writing code, running …”
   • [claimed-docs] “In CI, you can automate code review and issue triage with GitHub Actions or GitLab CI/CD.”

   proof ↗⚑ flag

   OpenCode~partialclaimed4/10

   OpenCode has documented GitHub integration where mentioning /opencode or /oc in a comment triggers tasks in GitHub Actions, including issue-to-PR workflows, but there is no evidence of native GitLab, Linear, or Slack integrations for kicking off agent tasks. missing for 10: GitLab integration, Linear integration, Slack integration, independent hands-on confirmation of the GitHub Actions flow working reliably.

   • [claimed-docs] “Ask OpenCode to fix an issue or implement a feature. And it will work in a new branch and submits a PR with all the changes.”
   • [claimed-docs] “Mention `/opencode` or `/oc` in your comment, and OpenCode will execute tasks within your GitHub Actions runner.”
   • [claimed-docs] “OpenCode integrates with your GitHub workflow. Mention /opencode or /oc in your comment, and OpenCode will execute tasks within your GitHub …”
   • [claimed-docs] “This will walk you through installing the GitHub app, creating the workflow, and setting up secrets.”

   proof ↗⚑ flag

Cross device continuity

1. developerStart a task on one device and continue it later from another device or browser

   weight 2 · round to Claude Code
   Claude Code✓fullclaimed8/10

   Docs explicitly describe cross-device continuity: 'Remote Control' lets you continue work from phone/browser (docs-9), and 'claude --teleport' lets you start a task on web/mobile and pull it into your terminal later (docs-10), backed by browser/cloud session support (docs-13, docs-14, docs-26). missing for 10: independent/hands-on confirmation of teleport and remote-control reliability across devices

   • [claimed-docs] “Step away from your desk and keep working from your phone or any browser with Remote Control”
   • [claimed-docs] “Kick off a long-running task on the web or the Claude mobile app, then pull it into your terminal with `claude --teleport`.”
   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”
   • [claimed-docs] “Kick off long-running tasks and check back when they're done, work on repos you don't have locally, or run multiple tasks in parallel.”
   • [claimed-docs] “Run Claude Code in your browser with no local setup. Kick off long-running tasks and check back when they're done, work on repos you don't h…”

   proof ↗⚑ flag

   OpenCode~partialcommunity6/10

   OpenCode supports remote/headless usage via `opencode serve` plus a TUI that can connect to a remote backend, share links for sessions, and a WebUI that can connect to multiple backends from anywhere (including mobile), which enables cross-device continuation of a session. However, this requires manual server setup rather than seamless native cloud sync, and community reports note bugs restoring session state and provider/model selection issues across sessions. missing for 10: first-party seamless cross-device sync without self-hosting a server, official mobile app, and clear documentation/evidence of resuming full task state (not just session sharing) across devices.

   • [claimed-docs] “This allows using the TUI with a remote OpenCode backend.”
   • [claimed-docs] “**Share links** Share a link to any session for reference or to debug”
   • [claimed-docs] “The opencode serve command runs a headless HTTP server that exposes an OpenAPI endpoint that an opencode client can use.”
   • [community] “You can start a service via 'opencode serve', it can be accessed from anywhere and has great experience on mobile except a few bugs... The W…”
   • [community] “There are random bugs with loading/restoring state of the session; Model/Provider selection switch across sessions/projects is often annoyin…”

   proof ↗⚑ flag

Ide integration

1. developerView interactive diffs and share selected code as context from within my JetBrains IDE

   weight 1 · round to Claude Code
   Claude Code✓fullclaimed8/10

   Docs explicitly describe a JetBrains plugin (IntelliJ IDEA, PyCharm, WebStorm, etc.) with interactive diff viewing and selection context sharing, directly matching the story. Missing for 10: independent/hands-on corroboration of the JetBrains plugin specifically (community evidence only covers CLI/terminal experience, not the IDE plugin).

   • [claimed-docs] “A plugin for IntelliJ IDEA, PyCharm, WebStorm, and other JetBrains IDEs with interactive diff viewing and selection context sharing.”

   proof ↗⚑ flag

   OpenCode—none0/10

   Evidence only shows OpenCode integrating with VS Code, Cursor, or 'any IDE that supports a terminal' via keyboard shortcuts for split-terminal view and inserting file references; there is no mention of a JetBrains-specific plugin, interactive diff viewer, or JetBrains context-sharing UI. missing for 10: JetBrains plugin/extension documentation, interactive diff rendering inside JetBrains, JetBrains-specific 'share selected code' mechanism.

   • [claimed-docs] “OpenCode integrates with VS Code, Cursor, or any IDE that supports a terminal. Just run `opencode` in the terminal to get started.”
   • [claimed-docs] “Use Cmd+Esc (Mac) or Ctrl+Esc (Windows/Linux) to open OpenCode in a split terminal view”
   • [claimed-docs] “Use Cmd+Option+K (Mac) or Alt+Ctrl+K (Linux/Windows) to insert file references.”
   • [claimed-docs] “OpenCode integrates with VS Code, Cursor, or any IDE that supports a terminal.”
   • [claimed-docs] “Use `Cmd+Esc` (Mac) or `Ctrl+Esc` (Windows/Linux) to open OpenCode in a split terminal view”
   • [claimed-docs] “Use `Cmd+Option+K` (Mac) or `Alt+Ctrl+K` (Linux/Windows) to insert file references.”

   proof ↗⚑ flag

2. developerChat with the coding assistant directly inside my IDE for contextual help

   weight 3 · round drawn
   Claude Code✓fullclaimed8/10

   Official docs confirm dedicated IDE integrations (VS Code extension with inline diffs, @-mentions, plan review, conversation history; JetBrains plugin with diff viewing and selection context sharing), plus terminal-based chat usable from within an IDE, and GitHub explicitly states 'Use it in your terminal, IDE, or tag @claude on Github.' Missing for 10: independent hands-on validation specifically of the IDE chat experience (community evidence is mostly about CLI/terminal use and general quality, not IDE-embedded chat specifically).

   • [claimed-docs] “The VS Code extension provides inline diffs, @-mentions, plan review, and conversation history directly in your editor.”
   • [claimed-docs] “A plugin for IntelliJ IDEA, PyCharm, WebStorm, and other JetBrains IDEs with interactive diff viewing and selection context sharing.”
   • [github] “Use it in your terminal, IDE, or tag @claude on Github.”
   • [claimed-docs] “Work with Claude directly in your codebase. Build, debug, and ship from your terminal, IDE, Slack, web, and more.”

   proof ↗⚑ flag

   OpenCode✓fullcommunity8/10

   OpenCode ships an IDE extension and integrates directly in VS Code/Cursor with in-editor shortcuts (split terminal view, file-reference insertion) for contextual chat, and community users confirm using it as their daily coding harness with LSP integration inside editors. Missing for 10: independent hands-on review specifically of the IDE-extension chat UX (most community feedback is TUI/CLI-focused) and no screenshots/deep detail on in-IDE chat UI beyond shortcuts.

   • [claimed-docs] “OpenCode integrates with VS Code, Cursor, or any IDE that supports a terminal. Just run `opencode` in the terminal to get started.”
   • [claimed-docs] “Any editor Available as a terminal interface, desktop app, and IDE extension”
   • [claimed-docs] “Use Cmd+Esc (Mac) or Ctrl+Esc (Windows/Linux) to open OpenCode in a split terminal view”
   • [claimed-docs] “Use Cmd+Option+K (Mac) or Alt+Ctrl+K (Linux/Windows) to insert file references.”
   • [community] “i've been using this as my primary harness for llama.cpp models, Claude, and Gemini for a few months now. the LSP integration is great.”
   • [community] “This replaced Aider for me a couple months back. I use it with Qwen 3.5 running locally when my daily limits run out on my other subscriptio…”

   proof ↗⚑ flag

Session management

1. developerReview diffs visually and run multiple sessions side by side in a desktop app

   weight 2 · round to Claude Code
   Claude Code~partialclaimed6/10

   First-party docs explicitly state the capability ('Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions'), closely matching the story, and related IDE integrations (VS Code inline diffs, JetBrains interactive diff viewer) support visual diff review, but this appears to describe a web/desktop companion app rather than a fully detailed, screenshot-documented desktop client, and no independent or hands-on evidence corroborates the side-by-side multi-session desktop UI. Missing for 10: independent/hands-on confirmation of the desktop app's diff viewer and multi-session UI, and richer first-party documentation (screenshots, feature depth) beyond a single summary line.

   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”
   • [claimed-docs] “A plugin for IntelliJ IDEA, PyCharm, WebStorm, and other JetBrains IDEs with interactive diff viewing and selection context sharing.”
   • [claimed-docs] “The VS Code extension provides inline diffs, @-mentions, plan review, and conversation history directly in your editor.”
   • [claimed-docs] “Available for macOS, Linux, and Windows.”

   proof ↗⚑ flag

   OpenCode~partialclaimed5/10

   OpenCode has a documented desktop app with tabs (opencode-docs-19) and multi-session support to run multiple agents in parallel (opencode-docs-17/38), plus session share links; existence of the desktop app is also confirmed on GitHub (opencode-gh-1). However, there is no evidence describing a visual diff-review UI in the desktop app specifically — docs focus on TUI/terminal split views and file references rather than a diff viewer. Missing for 10: explicit documentation or screenshots of a visual diff/code-review interface in the desktop app, and independent/hands-on confirmation of side-by-side session usage in that app.

   • [claimed-docs] “Introducing tabs for desktop. Available on macOS, Windows, and Linux.”
   • [claimed-docs] “**Multi-session** Start multiple agents in parallel on the same project”
   • [claimed-docs] “Multi-session Start multiple agents in parallel on the same project”
   • [github] “OpenCode is also available as a desktop application.”
   • [claimed-docs] “Any editor Available as a terminal interface, desktop app, and IDE extension”

   proof ↗⚑ flag

2. engineering-leadManage multiple agent-driven coding sessions from one unified workspace

   weight 2 · round to OpenCode
   Claude Code✓fullclaimed7/10

   Docs describe running multiple sessions side by side, kicking off parallel/cloud sessions from a browser, and spawning multiple coordinated sub-agents under a lead agent, which directly support a lead managing several agent sessions from one workspace (claude-code-docs-13, -14, -26, -6, -34, -44). Missing for 10: independent/hands-on confirmation of the 'unified workspace' UX (no community reports specifically validate multi-session management) and no detail on session-level access control across a team for the lead-agent view.

   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”
   • [claimed-docs] “Kick off long-running tasks and check back when they're done, work on repos you don't have locally, or run multiple tasks in parallel.”
   • [claimed-docs] “Run Claude Code in your browser with no local setup. Kick off long-running tasks and check back when they're done, work on repos you don't h…”
   • [claimed-docs] “Spawn multiple Claude Code agents that work on different parts of a task simultaneously. A lead agent coordinates the work, assigns subtasks…”
   • [claimed-docs] “Spawn multiple Claude Code agents that work on different parts of a task simultaneously.”
   • [claimed-docs] “Spawn multiple Claude Code agents that work on different parts of a task simultaneously. A lead agent coordin”

   proof ↗⚑ flag

   OpenCode✓fullcommunity8/10

   OpenCode explicitly supports multi-session workflows ('Start multiple agents in parallel on the same project'), tabs for desktop, share links for sessions, and a headless server that a WebUI can connect to across multiple backends, which community evidence corroborates ('WebUI... can connect to multiple OpenCode backends at once'). This directly matches an engineering-lead managing multiple agent sessions from one unified workspace. Missing for 10: no first-party documentation of team/organization-level oversight (e.g., viewing/managing sessions started by other engineers) and some reported bugs in session state restoration temper reliability.

   • [claimed-docs] “**Multi-session** Start multiple agents in parallel on the same project”
   • [claimed-docs] “Introducing tabs for desktop. Available on macOS, Windows, and Linux.”
   • [claimed-docs] “**Share links** Share a link to any session for reference or to debug”
   • [claimed-docs] “Multi-session Start multiple agents in parallel on the same project”
   • [claimed-docs] “Share links Share a link to any session for reference or to debug”
   • [claimed-docs] “The opencode serve command runs a headless HTTP server that exposes an OpenAPI endpoint that an opencode client can use.”
   • [community] “You can start a service via 'opencode serve', it can be accessed from anywhere and has great experience on mobile except a few bugs... The W…”
   • [community] “There are random bugs with loading/restoring state of the session; Model/Provider selection switch across sessions/projects is often annoyin…”

   proof ↗⚑ flag

Terminal workflow

1. developerRun a coding agent locally from my terminal

   weight 3 · round drawn
   Claude Code✓fullcommunity9/10

   Claude Code is explicitly documented as a terminal-native coding agent: install via curl script, run with cd your-project && claude, available on macOS/Linux/Windows, and GitHub README confirms 'Use it in your terminal, IDE, or tag @claude on Github.' Community posts corroborate hands-on terminal use, noting it's 'implemented as a bash tool and not an editor replacement.' Missing for 10: broader independent benchmark or third-party review confirming consistent reliability of local terminal operation beyond a few anecdotal community posts.

   • [claimed-docs] “cd your-project claude”
   • [claimed-docs] “curl -fsSL https://claude.ai/install.sh | bash”
   • [claimed-docs] “Available for macOS, Linux, and Windows.”
   • [github] “Use it in your terminal, IDE, or tag @claude on Github.”
   • [community] “The cost is absurd (compared to other LLM providers these days). I asked 3 questions and the cost was ~0.77c. I do like how this is implemen…”

   proof ↗⚑ flag

   OpenCode✓fullprobed9/10

   OpenCode is explicitly a terminal-based coding agent, installable via curl/npm, run with `opencode` command in any terminal, with rich CLI docs and confirmed hands-on community usage as a daily local terminal harness. Missing for 10: no independent benchmark/security audit fully vetting the terminal experience beyond anecdotal reports (some report TUI compatibility bugs on specific setups).

   • [claimed-docs] “OpenCode is an open source AI coding agent. It's available as a terminal-based interface, desktop app, or IDE extension.”
   • [claimed-docs] “OpenCode integrates with VS Code, Cursor, or any IDE that supports a terminal. Just run `opencode` in the terminal to get started.”
   • [claimed-docs] “curl -fsSL https://opencode.ai/install | bash”
   • [claimed-docs] “opencode run "Explain how closures work in JavaScript"”
   • [claimed-docs] “OpenCode integrates with VS Code, Cursor, or any IDE that supports a terminal.”
   • [probe] “official CLI documented at https://opencode.ai/docs/cli/”
   • [community] “i've been using this as my primary harness for llama.cpp models, Claude, and Gemini for a few months now. the LSP integration is great.”
   • [community] “This replaced Aider for me a couple months back. I use it with Qwen 3.5 running locally when my daily limits run out on my other subscriptio…”

   proof ↗⚑ flag

2. developerRun the agent non-interactively in scripts for workflow automation

   weight 2 · round drawn
   Claude Code✓fullclaimed8/10

   Docs explicitly describe non-interactive automation: piping logs, running in CI, scheduling recurring tasks, GitHub Actions/GitLab CI/CD integration for automated code review and issue triage, and headless-style scripting per Unix philosophy. missing for 10: no explicit mention of a documented --print/non-interactive flag or exit-code behavior, and no independent/hands-on report confirming scripted CI usage works as described.

   • [claimed-docs] “Claude Code is composable and follows the Unix philosophy. Pipe logs into it, run it in CI, or chain it with other tools”
   • [claimed-docs] “Run Claude on a schedule to automate work that repeats: morning PR reviews, overnight CI failure analysis, weekly dependency audits, or sync…”
   • [claimed-docs] “In CI, you can automate code review and issue triage with GitHub Actions or GitLab CI/CD.”
   • [claimed-docs] “Get automatic code review on every PR | GitHub Code Review”

   proof ↗⚑ flag

   OpenCode✓fullclaimed8/10

   The `opencode run` CLI command explicitly supports non-interactive one-shot execution (e.g. `opencode run "Explain how closures work"`), and `--auto` flag auto-approves permissions for unattended runs, plus `opencode serve` exposes a headless HTTP/OpenAPI server and JS/TS SDK for scripted/programmatic control, all fitting workflow automation. Missing for 10: independent hands-on evidence of non-interactive scripting reliability/CI use, and no dedicated exit-code/output-format docs for pipeline integration.

   • [claimed-docs] “opencode run "Explain how closures work in JavaScript"”
   • [claimed-docs] “Start OpenCode with `--auto` to automatically approve permission requests that are not explicitly denied.”
   • [claimed-docs] “Start OpenCode with --auto to automatically approve permission requests that are not explicitly denied.”
   • [claimed-docs] “The `opencode serve` command runs a headless HTTP server that exposes an OpenAPI endpoint that an opencode client can use.”
   • [claimed-docs] “The opencode JS/TS SDK provides a type-safe client for interacting with the server. Use it to build integrations and control opencode progra…”
   • [claimed-docs] “Attach a terminal to an already running OpenCode backend server started via `serve` or `web` commands.”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to OpenCode
   Claude Code~partialclaimed5/10

   Claude Code exposes an Agent SDK for building custom agents with 'full control over orchestration, tool access, and permissions' (docs-18) and supports direct API-key access and CI/headless automation (docs-36, docs-39/40), suggesting core coding capabilities are programmatically accessible. However, evidence doesn't confirm parity for UI-specific features like Remote Control, teleport, mobile app, or Slack routing being fully reachable via the API/SDK. Missing for 10: explicit documentation that all UI-surfaced features (remote control, teleport, IDE-specific interactions) are equally available through the API/SDK, and independent confirmation of this parity.

   • [claimed-docs] “the Agent SDK lets you build your own agents powered by Claude Code's tools and capabilities, with full control over orchestration, tool acc…”
   • [claimed-docs] “In CI, you can automate code review and issue triage with GitHub Actions or GitLab CI/CD.”
   • [claimed-docs] “If you've set the ANTHROPIC_API_KEY environment variable, Claude Code skips the login prompt and asks you to approve the key instead.”
   • [claimed-docs] “ANTHROPIC_API_KEY environment variable. Sent as the X-Api-Key header. Use this for direct Anthropic API access with a key from the Claude Co…”
   • [claimed-docs] “Use Claude Code as an MCP server. You can use Claude Code itself as an MCP server that other applications can connect to: claude mcp serve (…”

   proof ↗⚑ flag

   OpenCode~partialprobed6/10

   OpenCode ships a headless server (`opencode serve`) exposing a documented OpenAPI spec (confirmed live at openapi.json) plus a JS/TS SDK explicitly for 'building integrations and controlling opencode programmatically,' and the TUI/WebUI can drive a remote backend — community confirms this works day-to-day including from mobile. However, no evidence explicitly enumerates full feature parity (e.g., agent skill management, permission config, enterprise SSO settings) as exposed via the API/SDK, and there's no independent audit confirming 1:1 UI/API parity. missing for 10: explicit parity documentation covering all UI-only features (skills, permission prompts, enterprise SSO), independent verification of full API coverage.

   • [claimed-docs] “The opencode JS/TS SDK provides a type-safe client for interacting with the server. Use it to build integrations and control opencode progra…”
   • [claimed-docs] “Use it to build integrations and control opencode programmatically.”
   • [claimed-docs] “The opencode serve command runs a headless HTTP server that exposes an OpenAPI endpoint that an opencode client can use.”
   • [probe] “PROBE openapi: HTTP 200 at https://opencode.ai/openapi.json — contains "openapi" key”
   • [claimed-docs] “This allows using the TUI with a remote OpenCode backend.”
   • [community] “You can start a service via 'opencode serve', it can be accessed from anywhere and has great experience on mobile except a few bugs... The W…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round drawn
   Claude Code—none0/10

   The evidence pack contains no mention of a data export feature, session/conversation history export, or open-format portability guarantees for Claude Code — nothing addresses a user's ability to extract all their data and leave the platform. While Claude Code operates on local files (inherently open), there is no documented mechanism for exporting session logs, configs, or account data in open formats, so this applicable axis is unsupported.

   ⚑ flag

   OpenCode—none0/10

   No evidence describes an explicit data-export feature or open-format portability guarantee for OpenCode; while it is open-source and stores config/sessions locally, there's no documented 'export all my data and leave' capability, and community threads even note telemetry sent to OpenCode's own servers with no way to disable it (opencode-comm-2), undercutting a clean data-portability story.

   • [community] “OpenCode is sending telemetry to their own servers, even when you're using your own locally hosted models. There are no environment variable…”
   • [claimed-docs] “**Share links** Share a link to any session for reference or to debug”
   • [claimed-docs] “Share links Share a link to any session for reference or to debug”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round to OpenCode
   Claude Code—none0/10

   No evidence Claude Code's source is available under an open license; in fact community discussion explicitly contrasts it with an open-source competitor, noting 'Codex CLI is FOSS, unlike Claude Code' — confirming it is closed-source.

   • [community] “Codex CLI is FOSS, unlike Claude Code, so Codex is less likely to do things like that, and it's one more reason to avoid Claude Code and Cla…”

   proof ↗⚑ flag

   OpenCode✓fullcommunity7/10

   OpenCode's docs explicitly describe it as "open source" and a public GitHub repo exists (opencode-gh-1), and community members confirm they read and learned from the actual source code (opencode-comm-6), corroborating that the source is genuinely accessible. missing for 10: explicit citation of the license name/type (e.g., MIT/Apache) in the evidence pack, and a first-party statement pointing to the license file itself.

   • [claimed-docs] “OpenCode is an open source AI coding agent. It's available as a terminal-based interface, desktop app, or IDE extension.”
   • [github] “OpenCode is also available as a desktop application.”
   • [community] “OpenCode source code is even more awesome. I have learned so much from the way they have organized tools, agents, settings and prompts. mode…”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to OpenCode
   Claude Code—none0/10

   Claude Code is a closed-source CLI that requires an Anthropic API key or Claude.ai/Console login to function (docs-37, docs-39, docs-55) — there is no evidence of a self-hostable core model or backend. Community evidence explicitly notes it is not open source, unlike alternatives (comm-4), confirming the product cannot be self-hosted.

   • [claimed-docs] “Claude Pro or Max subscription: log in with your Claude.ai account.”
   • [claimed-docs] “If you've set the ANTHROPIC_API_KEY environment variable, Claude Code skips the login prompt and asks you to approve the key instead.”
   • [claimed-docs] “Individual users can log in with a claude.ai account, while teams can use Claude for Teams or Enterprise, the Claude Console, or a cloud pro…”
   • [community] “Codex CLI is FOSS, unlike Claude Code, so Codex is less likely to do things like that, and it's one more reason to avoid Claude Code and Cla…”

   proof ↗⚑ flag

   OpenCode✓fullprobed8/10

   OpenCode is open source and installable via CLI, with a documented `opencode serve` headless HTTP server exposing an OpenAPI endpoint, plus SDK and remote/TUI client support, enabling full self-hosting of the core agent; community evidence confirms real-world self-hosted use ('opencode serve' accessible remotely) though also flags security hardening gaps around the server. missing for 10: independent audit confirming production-grade self-hosted security, and clearer official self-hosting/deployment guide beyond the serve command docs.

   • [claimed-docs] “curl -fsSL https://opencode.ai/install | bash”
   • [claimed-docs] “The opencode serve command runs a headless HTTP server that exposes an OpenAPI endpoint that an opencode client can use.”
   • [claimed-docs] “The `opencode serve` command runs a headless HTTP server that exposes an OpenAPI endpoint that an opencode client can use.”
   • [claimed-docs] “Attach a terminal to an already running OpenCode backend server started via `serve` or `web` commands.”
   • [claimed-docs] “The opencode JS/TS SDK provides a type-safe client for interacting with the server. Use it to build integrations and control opencode progra…”
   • [probe] “PROBE openapi: HTTP 200 at https://opencode.ai/openapi.json — contains "openapi" key”
   • [community] “You can start a service via 'opencode serve', it can be accessed from anywhere and has great experience on mobile except a few bugs... The W…”
   • [community] “When server is enabled, any web page served from localhost/127.0.0.1 can execute code; any local process can execute code without authentica…”

   proof ↗⚑ flag

Authentication

1. developerAuthenticate with an API key instead of an account login

   weight 2 · round to Claude Code
   Claude Code✓fullclaimed9/10

   Docs explicitly confirm ANTHROPIC_API_KEY env var authentication bypasses the account login prompt, using it for direct API access via X-Api-Key header, as an alternative to Claude.ai account login. missing for 10: independent/hands-on community confirmation of this specific auth flow (only first-party docs cited).

   • [claimed-docs] “If you've set the ANTHROPIC_API_KEY environment variable, Claude Code skips the login prompt and asks you to approve the key instead.”
   • [claimed-docs] “ANTHROPIC_API_KEY environment variable. Sent as the X-Api-Key header. Use this for direct Anthropic API access with a key from the Claude Co…”
   • [claimed-docs] “Claude Pro or Max subscription: log in with your Claude.ai account.”
   • [claimed-docs] “Individual users can log in with a claude.ai account, while teams can use Claude for Teams or Enterprise, the Claude Console, or a cloud pro…”

   proof ↗⚑ flag

   OpenCode✓fullclaimed8/10

   OpenCode explicitly supports configuring API keys for any LLM provider as an alternative to logging in via account-based options like GitHub Copilot or ChatGPT Plus/Pro, giving developers a direct API-key auth path rather than requiring account login. Missing for 10: independent hands-on confirmation of the API key setup flow itself and details on key storage/security beyond docs claims.

   • [claimed-docs] “With OpenCode you can use any LLM provider by configuring their API keys.”
   • [claimed-docs] “**GitHub Copilot** Log in with GitHub to use your Copilot account”
   • [claimed-docs] “**ChatGPT Plus/Pro** Log in with OpenAI to use your ChatGPT Plus or Pro account”
   • [claimed-docs] “OpenCode Zen is a list of tested and verified models provided by the OpenCode team.”

   proof ↗⚑ flag

2. engineering-leadAuthenticate through an enterprise identity or cloud platform for compliance and scalability

   weight 2 · round to Claude Code
   Claude Code✓fullclaimed8/10

   Claude Code documents enterprise authentication via SSO/SAML, domain capture, role-based permissions, compliance API, and managed policy settings under Claude for Enterprise, plus flexible auth options (Console API key, Claude.ai account, Teams/Enterprise, cloud provider) for scaling across org structures. missing for 10: independent/hands-on corroboration of SSO setup working in practice, and no explicit mention of cloud IAM integration (e.g., AWS/GCP native identity federation) beyond 'cloud provider' mention.

   • [claimed-docs] “Claude for Enterprise: adds SSO, domain capture, role-based permissions, compliance API, and managed policy settings for organization-wide C…”
   • [claimed-docs] “Single sign-on (SSO/SAML) and domain capture”
   • [claimed-docs] “Individual users can log in with a claude.ai account, while teams can use Claude for Teams or Enterprise, the Claude Console, or a cloud pro…”
   • [claimed-docs] “Claude Pro or Max subscription: log in with your Claude.ai account.”
   • [claimed-docs] “You can sign in to your Console account without creating an API key, even when your organization doesn't let developers create them.”

   proof ↗⚑ flag

   OpenCode~partialclaimed6/10

   OpenCode has a documented enterprise config that integrates with SSO and enforces a centralized internal AI gateway, directly addressing enterprise identity/compliance needs, and supports login via GitHub Copilot/OpenAI accounts. However, there's no independent corroboration of this enterprise SSO feature in practice, no detail on supported identity providers (SAML/OIDC specifics), and community discussion focuses on telemetry/security concerns rather than confirming enterprise auth workflows. Missing for 10: independent/hands-on validation of SSO integration, details on supported IdPs, and evidence of enterprise customers actually using this for compliance/scalability.

   • [claimed-docs] “This centralized config can integrate with your SSO provider and ensures all users access only your internal AI gateway.”
   • [claimed-docs] “**GitHub Copilot** Log in with GitHub to use your Copilot account”
   • [claimed-docs] “**ChatGPT Plus/Pro** Log in with OpenAI to use your ChatGPT Plus or Pro account”

   proof ↗⚑ flag

3. developerSign in with my existing product subscription plan to use the coding agent

   weight 2 · round to Claude Code
   Claude Code✓fullclaimed9/10

   Docs explicitly confirm developers can log in with their existing Claude Pro or Max subscription (claude.ai account) instead of needing a separate API key, with API key as an alternative for direct API access. Missing for 10: independent/hands-on confirmation of the subscription login flow working smoothly in practice (community evidence focuses on other topics, not this login flow specifically).

   • [claimed-docs] “Claude Pro or Max subscription: log in with your Claude.ai account.”
   • [claimed-docs] “Individual users can log in with a claude.ai account, while teams can use Claude for Teams or Enterprise, the Claude Console, or a cloud pro…”
   • [claimed-docs] “If you've set the ANTHROPIC_API_KEY environment variable, Claude Code skips the login prompt and asks you to approve the key instead.”
   • [claimed-docs] “ANTHROPIC_API_KEY environment variable. Sent as the X-Api-Key header. Use this for direct Anthropic API access with a key from the Claude Co…”

   proof ↗⚑ flag

   OpenCode✓fullcommunity8/10

   OpenCode docs explicitly support signing in with existing subscriptions—GitHub Copilot and ChatGPT Plus/Pro—rather than requiring separate API keys, and community comments confirm using subscriptions (e.g., Codex $200/mo) inside OpenCode. Missing for 10: independent hands-on verification of the Copilot/ChatGPT login flow itself and broader coverage of other subscription providers beyond these two.

   • [claimed-docs] “**GitHub Copilot** Log in with GitHub to use your Copilot account”
   • [claimed-docs] “**ChatGPT Plus/Pro** Log in with OpenAI to use your ChatGPT Plus or Pro account”
   • [claimed-docs] “GitHub Copilot Log in with GitHub to use your Copilot account”
   • [claimed-docs] “ChatGPT Plus/Pro Log in with OpenAI to use your ChatGPT Plus or Pro account”
   • [community] “OpenCode is awesome. Claude Code is nothing special at all. Last month I switched to just using OpenCode with a Codex $200/mo subscription, …”

   proof ↗⚑ flag

4. developerSign in with a personal account to get free-tier access without managing API keys

   weight 1 · round to OpenCode
   Claude Code~partialclaimed6/10

   Docs confirm individual developers can log in with a personal claude.ai account (Pro/Max subscription) instead of managing an API key, and that API-key auth is optional/alternate. However, evidence only references Pro/Max subscription login, not an explicit free tier for Claude Code — missing for 10: explicit confirmation that a free/no-cost claude.ai account grants Claude Code access, and independent user corroboration of free-tier login flow.

   • [claimed-docs] “Claude Pro or Max subscription: log in with your Claude.ai account.”
   • [claimed-docs] “If you've set the ANTHROPIC_API_KEY environment variable, Claude Code skips the login prompt and asks you to approve the key instead.”
   • [claimed-docs] “ANTHROPIC_API_KEY environment variable. Sent as the X-Api-Key header. Use this for direct Anthropic API access with a key from the Claude Co…”
   • [claimed-docs] “Individual users can log in with a claude.ai account, while teams can use Claude for Teams or Enterprise, the Claude Console, or a cloud pro…”

   proof ↗⚑ flag

   OpenCode✓fullcommunity7/10

   OpenCode's docs explicitly offer 'Log in with GitHub to use your Copilot account' and 'Log in with OpenAI to use your ChatGPT Plus or Pro account,' letting a developer authenticate with an existing personal subscription instead of managing provider API keys, and OpenCode Zen is noted to include a free coding model. Missing for 10: independent/hands-on user reports specifically confirming this login flow (community comments focus on API keys/local models, not the Copilot/ChatGPT login path), and clarity on any usage limits tied to the free tier.

   • [claimed-docs] “**GitHub Copilot** Log in with GitHub to use your Copilot account”
   • [claimed-docs] “**ChatGPT Plus/Pro** Log in with OpenAI to use your ChatGPT Plus or Pro account”
   • [claimed-docs] “GitHub Copilot Log in with GitHub to use your Copilot account”
   • [claimed-docs] “ChatGPT Plus/Pro Log in with OpenAI to use your ChatGPT Plus or Pro account”
   • [community] “OpenCode source code is even more awesome. I have learned so much from the way they have organized tools, agents, settings and prompts. mode…”

   proof ↗⚑ flag

Model choice

1. developerLet the tool automatically pick the best model for each task

   weight 1 · round drawn
   Claude Code—none0/10

   No evidence in the pack describes automatic model selection or routing per task; users manually choose models (e.g., Sonnet vs Opus per comm-19) and there's no mention of an auto-select feature. Missing for 10: any docs describing automatic model routing/selection logic based on task complexity or cost.

   ⚑ flag

   OpenCode—none0/10

   Evidence shows OpenCode supports many providers/models and lets users manually assign a model per agent or switch via Tab, but nothing indicates the tool automatically selects the optimal model for a given task — community feedback even confirms model/provider choice is manual and sometimes annoying to manage across sessions.

   • [community] “I really like how their subagents work, as a bonus I get to choose which model is in which agent.”
   • [community] “There are random bugs with loading/restoring state of the session; Model/Provider selection switch across sessions/projects is often annoyin…”
   • [claimed-docs] “You can use the Tab key to switch between primary agents during a session.”
   • [claimed-docs] “75+ LLM providers through Models.dev, including local models”

   proof ↗⚑ flag

2. developerChoose which underlying AI model powers my session from multiple providers

   weight 2 · round to OpenCode
   Claude Code—none0/10

   Evidence shows Claude Code authentication routes (Claude.ai login, API key, Console, Enterprise SSO) are all tied to Anthropic's own Claude models; there is no mention of selecting GPT, Gemini, or other third-party model providers to power a session. Since comparable coding tools do offer multi-provider model selection, this axis applies but is unevidenced here.

   • [claimed-docs] “Claude Pro or Max subscription: log in with your Claude.ai account.”
   • [claimed-docs] “If you've set the ANTHROPIC_API_KEY environment variable, Claude Code skips the login prompt and asks you to approve the key instead.”
   • [claimed-docs] “ANTHROPIC_API_KEY environment variable. Sent as the X-Api-Key header. Use this for direct Anthropic API access with a key from the Claude Co…”
   • [claimed-docs] “Individual users can log in with a claude.ai account, while teams can use Claude for Teams or Enterprise, the Claude Console, or a cloud pro…”

   proof ↗⚑ flag

   OpenCode✓fullcommunity9/10

   OpenCode explicitly supports configuring any LLM provider via API keys, lists 75+ providers through Models.dev including local models, offers a curated OpenCode Zen model list, and supports logging in with GitHub Copilot or ChatGPT Plus/Pro accounts. Community evidence corroborates real-world use with multiple providers (Claude, Gemini, local llama.cpp, Qwen) and per-agent model selection. Missing for 10: some community reports note model/provider switching across sessions can be buggy or annoying, a minor UX caveat.

   • [claimed-docs] “With OpenCode you can use any LLM provider by configuring their API keys.”
   • [claimed-docs] “OpenCode Zen is a list of tested and verified models provided by the OpenCode team.”
   • [claimed-docs] “75+ LLM providers through Models.dev, including local models”
   • [claimed-docs] “Any model 75+ LLM providers through Models.dev, including local models”
   • [claimed-docs] “**GitHub Copilot** Log in with GitHub to use your Copilot account”
   • [claimed-docs] “**ChatGPT Plus/Pro** Log in with OpenAI to use your ChatGPT Plus or Pro account”
   • [community] “I really like how their subagents work, as a bonus I get to choose which model is in which agent.”
   • [community] “i've been using this as my primary harness for llama.cpp models, Claude, and Gemini for a few months now. the LSP integration is great.”
   • [community] “This replaced Aider for me a couple months back. I use it with Qwen 3.5 running locally when my daily limits run out on my other subscriptio…”
   • [community] “There are random bugs with loading/restoring state of the session; Model/Provider selection switch across sessions/projects is often annoyin…”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Claude Code—none0/10

   No evidence pack items mention data residency, regional data storage options, or geographic controls for where Claude Code data is processed/stored; only SSO/domain capture/compliance API for enterprise IAM are mentioned. Missing for 10: any documentation of region selection, data residency guarantees, or geo-specific storage controls.

   ⚑ flag

   OpenCode—none0/10

   No evidence anywhere in the pack of a region/residency selection feature for data storage; OpenCode's docs focus on provider choice, self-hosting, and enterprise SSO, none of which address data residency. In fact, community reports indicate telemetry is always sent to OpenCode's own servers with no way to disable it, further suggesting the user lacks control over where certain data goes.

   • [community] “OpenCode is sending telemetry to their own servers, even when you're using your own locally hosted models. There are no environment variable…”

   proof ↗⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Claude Code—none0/10

   The evidence pack includes enterprise/compliance features (SSO, compliance API, managed policies) but contains no mention of any training-data opt-out, data-usage policy, or explicit statement that user code/conversations are excluded from model training.

   ⚑ flag

   OpenCode—none0/10

   The evidence pack contains no documentation of any setting, policy, or opt-out mechanism for preventing user data/code from being used to train AI models (OpenCode's docs focus on providers, agents, permissions, IDE integration, etc., none addressing training-data usage). Community evidence actually suggests the opposite direction of concern: telemetry is sent to OpenCode's own servers even with locally-hosted models with no way to disable it, which further undermines confidence that user data is protected from being retained/used.

   • [community] “OpenCode is sending telemetry to their own servers, even when you're using your own locally hosted models. There are no environment variable…”

   proof ↗⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Claude Code—none0/10

   The evidence pack shows enterprise features like SSO, domain capture, and a vague 'compliance API' but nothing describing user-controllable data retention settings or deletion of stored conversation/code data. No documentation addresses how users can view, export, or delete retained data.

   ⚑ flag

   OpenCode—none0/10

   No documentation describes any data retention or deletion controls, and community evidence indicates the opposite: OpenCode sends telemetry to its own servers even with local models, with no environment variables or flags to disable it, suggesting no user-facing data controls exist.

   • [community] “OpenCode is sending telemetry to their own servers, even when you're using your own locally hosted models. There are no environment variable…”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round to OpenCode
   Claude Code—none0/10

   The evidence pack contains no documentation or reference to a telemetry/usage-tracking opt-out setting (e.g., no mention of a DISABLE_TELEMETRY flag, privacy settings page, or opt-out toggle) for Claude Code. Community commentary touches on unrelated trust/security concerns (anti-distillation fake tools, undercover mode) but none confirm or deny a telemetry opt-out mechanism.

   ⚑ flag

   OpenCode!disputedcontradicted2/10

   OpenCode's docs make no mention of a telemetry opt-out setting, and a community report explicitly states OpenCode sends telemetry to its own servers even with locally hosted models, with no environment variables, flags, or config options to disable it. This is a first-party-vs-hands-on-evidence conflict: no documented opt-out mechanism exists, and independent evidence claims none is available. missing for 10: any official docs describing a telemetry toggle/opt-out, first-party acknowledgment of telemetry collection, and any evidence the reported issue was fixed.

   • [community] “OpenCode is sending telemetry to their own servers, even when you're using your own locally hosted models. There are no environment variable…”
   • [claimed-docs] “OpenCode uses the `permission` config to decide whether a given action should run automatically, prompt you, or be blocked.”

   proof ↗⚑ flag

Data governance

1. engineering-leadOpt out of having my code and prompts used for AI model training

   weight 1 · round drawn
   Claude Code—none0/10

   The evidence pack contains no documentation or statements about Claude Code's data usage or model-training policies, nor any opt-out mechanism for code/prompt data. Enterprise features mentioned (SSO, compliance API, RBAC) do not address training data usage, and community items are unrelated to this specific concern.

   ⚑ flag

   OpenCode—none0/10

   No documentation exists describing a training-data opt-out or data-use policy for prompts/code; in fact community evidence indicates OpenCode sends telemetry to its own servers with no way to disable it, even when using local models, suggesting the opposite of user control over data usage.

   • [community] “OpenCode is sending telemetry to their own servers, even when you're using your own locally hosted models. There are no environment variable…”

   proof ↗⚑ flag

Pr review

1. developerHave the agent stage changes, write commit messages, create branches, and open pull requests

   weight 3 · round to Claude Code
   Claude Code✓fullclaimed8/10

   First-party docs explicitly state Claude Code 'stages changes, writes commit messages, creates branches, and opens pull requests' and integrates with GitHub/GitLab to handle the entire workflow including submitting PRs, corroborated by the GitHub repo description mentioning it 'handles git workflows'. Missing for 10: independent hands-on verification of a full stage-commit-branch-PR flow (community evidence discusses code quality/trust issues but not this specific git workflow failing).

   • [claimed-docs] “Claude Code works directly with git. It stages changes, writes commit messages, creates branches, and opens pull requests.”
   • [claimed-docs] “Claude Code integrates with GitHub, GitLab, and your command line tools to handle the entire workflow—reading issues, writing code, running …”
   • [github] “helps you code faster by executing routine tasks, explaining complex code, and handling git workflows -- all through natural language comman…”

   proof ↗⚑ flag

   OpenCode~partialclaimed6/10

   Docs explicitly describe GitHub integration where OpenCode 'will work in a new branch and submits a PR with all the changes' and can execute tasks via mentions in GitHub Actions, covering branch creation and PR opening; permission config also governs whether actions like git operations auto-run or prompt. However, there's no explicit mention of staging changes or generating commit messages as a distinct capability, and no independent/community evidence corroborates the PR-creation workflow in practice. missing for 10: explicit documentation of commit message generation/staging step, independent hands-on verification of the branch+PR workflow.

   • [claimed-docs] “Ask OpenCode to fix an issue or implement a feature. And it will work in a new branch and submits a PR with all the changes.”
   • [claimed-docs] “OpenCode integrates with your GitHub workflow. Mention /opencode or /oc in your comment, and OpenCode will execute tasks within your GitHub …”
   • [claimed-docs] “Mention `/opencode` or `/oc` in your comment, and OpenCode will execute tasks within your GitHub Actions runner.”
   • [claimed-docs] “OpenCode uses the `permission` config to decide whether a given action should run automatically, prompt you, or be blocked.”
   • [claimed-docs] “This will walk you through installing the GitHub app, creating the workflow, and setting up secrets.”

   proof ↗⚑ flag

2. developerGet automatic code review with contextual feedback on every pull request

   weight 3 · round to Claude Code
   Claude Code✓fullcommunity7/10

   Docs explicitly advertise 'Get automatic code review on every PR | GitHub Code Review' plus CI-based automated code review/issue triage and enterprise security code review, and CLAUDE.md can encode review checklists; community evidence even notes Claude performs well specifically as a reviewer. missing for 10: independent hands-on validation of the GitHub Code Review integration itself and detail on how contextual feedback is generated/delivered on PRs.

   • [claimed-docs] “Get automatic code review on every PR | GitHub Code Review”
   • [claimed-docs] “In CI, you can automate code review and issue triage with GitHub Actions or GitLab CI/CD.”
   • [claimed-docs] “Claude helps security teams and developers by reviewing code for security issues, drafts patches, and explains the risk in language your who…”
   • [claimed-docs] “CLAUDE.md is a markdown file you add to your project root that Claude Code reads at the start of every session. Use it to set coding standar…”
   • [community] “I have found that Claude Opus 4.6 is a better reviewer than it is an implementer. When Codex implements and Claude reviews, it's usually jus…”

   proof ↗⚑ flag

   OpenCode~partialclaimed4/10

   OpenCode has a GitHub Actions integration (mention /opencode or /oc in a comment) and a read-only 'plan' agent that can review/suggest changes without modifying code, which can be used for PR feedback, but this requires an explicit manual mention rather than automatically triggering contextual review on every PR. Missing for 10: documented automatic/triggerless review on every new PR, evidence of inline contextual comments on diffs, and independent confirmation of this review workflow in practice.

   • [claimed-docs] “Mention `/opencode` or `/oc` in your comment, and OpenCode will execute tasks within your GitHub Actions runner.”
   • [claimed-docs] “OpenCode integrates with your GitHub workflow. Mention /opencode or /oc in your comment, and OpenCode will execute tasks within your GitHub …”
   • [claimed-docs] “This agent is useful when you want the LLM to analyze code, suggest changes, or create plans without making any actual modifications to your…”
   • [claimed-docs] “A fast, read-only agent for exploring codebases. Cannot modify files.”
   • [claimed-docs] “This will walk you through installing the GitHub app, creating the workflow, and setting up secrets.”

   proof ↗⚑ flag

3. developerInspect diffs and run checks to catch problems before merging

   weight 3 · round to Claude Code
   Claude Code~partialcommunity6/10

   Claude Code supports diff inspection (inline diffs in VS Code/JetBrains, visual diff review in web/desktop UI) and can run tests, lint, and CI checks as part of its workflow, plus automatic PR code review via GitHub integration. However, the story's 'inspect diffs and run checks before merging' as a cohesive reviewer workflow is only partially evidenced — there's no dedicated diff/lint/test-gate UI walkthrough, and community reports raise self-verification concerns (e.g., replace_all bugs going undetected). missing for 10: a dedicated pre-merge review workflow with integrated check-gating (not just individual features), independent hands-on validation of diff-review accuracy, and evidence addressing the self-verification skepticism raised in community reports.

   • [claimed-docs] “Review diffs visually, run multiple sessions side by side, schedule recurring tasks, and kick off cloud sessions.”
   • [claimed-docs] “The VS Code extension provides inline diffs, @-mentions, plan review, and conversation history directly in your editor.”
   • [claimed-docs] “A plugin for IntelliJ IDEA, PyCharm, WebStorm, and other JetBrains IDEs with interactive diff viewing and selection context sharing.”
   • [claimed-docs] “Get automatic code review on every PR | GitHub Code Review”
   • [claimed-docs] “Hooks let you run shell commands before or after Claude Code actions, like auto-formatting after every file edit or running lint before a co…”
   • [claimed-docs] “In CI, you can automate code review and issue triage with GitHub Actions or GitLab CI/CD.”
   • [community] “I've been using Claude Code daily for months on a project with Elixir, Rust, and Python. The worst failure mode is when it does a replace_al…”
   • [community] “I have found that Claude Opus 4.6 is a better reviewer than it is an implementer. When Codex implements and Claude reviews, it's usually jus…”

   proof ↗⚑ flag

   OpenCode~partialclaimed4/10

   OpenCode offers a read-only 'plan' agent for reviewing suggested changes without applying them and a permission system that can prompt before actions run, plus GitHub PR/Actions integration for submitting changes — these provide some review-safety scaffolding. However there is no documented diff-viewing UI or built-in test/lint/check-running capability before merge. Missing for 10: explicit diff inspection tooling, integrated test/lint/CI check execution, and independent evidence that these safety mechanisms actually prevent bad merges.

   • [claimed-docs] “Use the plan agent to analyze code and review suggestions without making any code changes.”
   • [claimed-docs] “This agent is useful when you want the LLM to analyze code, suggest changes, or create plans without making any actual modifications to your…”
   • [claimed-docs] “A fast, read-only agent for exploring codebases. Cannot modify files.”
   • [claimed-docs] “OpenCode uses the `permission` config to decide whether a given action should run automatically, prompt you, or be blocked.”
   • [claimed-docs] “Ask OpenCode to fix an issue or implement a feature. And it will work in a new branch and submits a PR with all the changes.”
   • [claimed-docs] “Mention `/opencode` or `/oc` in your comment, and OpenCode will execute tasks within your GitHub Actions runner.”

   proof ↗⚑ flag

Safe execution

1. engineering-leadControl which external tools and integrations the agent is allowed to access

   weight 2 · round to OpenCode
   Claude Code~partialclaimed6/10

   Claude Code supports MCP server allow-listing via config (claude mcp add), sandboxed Bash tool with filesystem/network domain controls, and Enterprise-tier managed policy settings/SSO/role-based permissions that let an engineering lead govern tool and integration access. However, evidence doesn't show granular per-tool allow/deny lists at a team-policy level outside Enterprise, nor independent confirmation these controls reliably block unauthorized MCP/tool use in practice. missing for 10: fine-grained non-enterprise tool permission controls, independent/hands-on verification that access restrictions are enforced, and centralized audit/reporting of which integrations were actually used.

   • [claimed-docs] “Claude Code can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”
   • [claimed-docs] “claude mcp add --transport http notion https://mcp.notion.com/mcp”
   • [claimed-docs] “Stdio servers run as local processes on your machine. They're ideal for tools that need direct system access or custom scripts.”
   • [claimed-docs] “Use Claude Code as an MCP server. You can use Claude Code itself as an MCP server that other applications can connect to: claude mcp serve (…”
   • [claimed-docs] “Learn how Claude Code's sandboxed Bash tool provides filesystem and network isolation for safer, more autonomous agent execution. The Bash s…”
   • [claimed-docs] “Claude for Enterprise: adds SSO, domain capture, role-based permissions, compliance API, and managed policy settings for organization-wide C…”
   • [claimed-docs] “Single sign-on (SSO/SAML) and domain capture”

   proof ↗⚑ flag

   OpenCode✓fullclaimed8/10

   OpenCode's permission system lets leads set actions to auto-run, prompt, or block per tool/input, and MCP servers (external tools) are explicitly added/configured (docs-4/23/41). Enterprise config also lets orgs force use of an internal AI gateway and SSO, further restricting what integrations agents can reach (docs-33/50). Missing for 10: independent/hands-on confirmation that permission rules reliably block disallowed MCP tool calls in practice, and finer detail on allow/deny lists for specific external tool names beyond the general permission object.

   • [claimed-docs] “OpenCode uses the `permission` config to decide whether a given action should run automatically, prompt you, or be blocked.”
   • [claimed-docs] “Start OpenCode with `--auto` to automatically approve permission requests that are not explicitly denied.”
   • [claimed-docs] “OpenCode uses the permission config to decide whether a given action should run automatically, prompt you, or be blocked.”
   • [claimed-docs] “Start OpenCode with --auto to automatically approve permission requests that are not explicitly denied.”
   • [claimed-docs] “For most permissions, you can use an object to apply different actions based on the tool input.”
   • [claimed-docs] “Use external_directory to allow tool calls that touch paths outside the working directory where OpenCode was started.”
   • [claimed-docs] “You can add external tools to OpenCode using the _Model Context Protocol_, or MCP. OpenCode supports both local and remote servers.”
   • [claimed-docs] “You can add external tools to OpenCode using the Model Context Protocol, or MCP.”
   • [claimed-docs] “You can add external tools to OpenCode using the _Model Context Protocol_, or MCP.”
   • [claimed-docs] “This centralized config can integrate with your SSO provider and ensures all users access only your internal AI gateway.”
   • [claimed-docs] “Through the central config, OpenCode can integrate with your organization’s SSO provider for authentication.”

   proof ↗⚑ flag

2. engineering-leadHave the agent operate inside a sandbox when interacting with code, tools, and network resources

   weight 2 · round to Claude Code
   Claude Code✓fullclaimed8/10

   Claude Code documents a dedicated sandboxed Bash tool that enforces filesystem and network isolation via OS-level boundaries, letting the agent run commands autonomously within defined limits rather than requiring per-command approval. missing for 10: independent/hands-on verification of sandbox robustness, and detail on sandboxing coverage for non-Bash tool calls (e.g., MCP tool network access).

   • [claimed-docs] “Learn how Claude Code's sandboxed Bash tool provides filesystem and network isolation for safer, more autonomous agent execution. The Bash s…”

   proof ↗⚑ flag

   OpenCode—none0/10

   OpenCode's documentation only describes a permission system (auto-approve/prompt/block) and an 'external_directory' toggle for path access — not an isolated sandbox for code execution, tool calls, or network access. Community evidence (opencode-comm-18) even flags that the local server mode allows any local process or webpage to execute code without authentication, the opposite of sandboxed isolation, and there is no first-party claim of container/VM-based sandboxing to dispute.

   • [claimed-docs] “OpenCode uses the `permission` config to decide whether a given action should run automatically, prompt you, or be blocked.”
   • [claimed-docs] “Start OpenCode with `--auto` to automatically approve permission requests that are not explicitly denied.”
   • [claimed-docs] “Use external_directory to allow tool calls that touch paths outside the working directory where OpenCode was started.”
   • [community] “When server is enabled, any web page served from localhost/127.0.0.1 can execute code; any local process can execute code without authentica…”

   proof ↗⚑ flag

Security checks

1. engineering-leadSee license and public-code matching references for AI-suggested code

   weight 1 · round drawn
   Claude Code—none0/10

   No evidence anywhere in the pack of license detection, public-code/OSS match references, or provenance attribution for AI-suggested code; Claude Code's documented features focus on code generation, review, MCP integrations, and workflow automation, not license/plagiarism matching.

   ⚑ flag

   OpenCode—none0/10

   No evidence of any license or public-code matching/attribution feature for AI-suggested code in OpenCode's docs or community reports; the product focuses on agent workflows, permissions, and MCP integration but nothing about code provenance or license scanning.

   ⚑ flag

2. developerGet contextual explanations and automatic fixes for security vulnerabilities

   weight 2 · round to Claude Code
   Claude Code✓fullclaimed7/10

   Anthropic's enterprise docs explicitly state Claude Code reviews code for security issues, drafts patches, and explains risk in plain language, directly matching the story's contextual-explanation-plus-fix pattern, and this is reinforced by automatic PR code review integration. Missing for 10: independent/hands-on evidence confirming automatic vulnerability fixes work reliably in practice, and more detail on the security-specific workflow beyond a single marketing mention.

   • [claimed-docs] “Claude helps security teams and developers by reviewing code for security issues, drafts patches, and explains the risk in language your who…”
   • [claimed-docs] “Get automatic code review on every PR | GitHub Code Review”
   • [claimed-docs] “In CI, you can automate code review and issue triage with GitHub Actions or GitLab CI/CD.”

   proof ↗⚑ flag

   OpenCode—none0/10

   OpenCode is a general coding agent with plan/explore/build agents and permission controls, but no evidence describes any security-vulnerability scanning, contextual vulnerability explanations, or automatic security fix generation as a feature. Community evidence even highlights unresolved security reports and vulnerabilities in OpenCode itself, not a capability to detect/fix vulnerabilities in user code.

   ⚑ flag