OpenCode vs Devin

Agent access

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

   weight 2 · round to Devin
   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

   Devin✓fullprobed9/10

   Devin's own docs site serves llms.txt (HTTP 200, confirmed by probe) and per-page .md variants, and also supports AGENTS.md as an agent-oriented instructions standard, directly matching the story. Missing for 10: no independent/community confirmation that external agents have actually consumed llms.txt successfully.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.devin.ai/llms.txt # Devin Docs - [Desktop (100 pages)](https://docs.devin.ai/_llms/en/desktop.md):…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.devin.ai/get-started/devin-intro.md > ## Documentation Index > Fetch the complete documentation inde…”
   • [claimed-docs] “Devin supports AGENTS.md - a simple, open standard for providing context and instructions to AI agents.”

   proof ↗⚑ flag

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

   weight 2 · round to OpenCode
   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

   Devin✓fullclaimed8/10

   Devin offers a full API for creating/managing sessions programmatically (including create_as_user_id for automation on behalf of users), a CLI with a --sandbox flag for OS-level isolated headless runs, and explicit CI/CD pipeline integration for responding to static analysis findings and PR checks, all supporting headless/automated usage without a human in the loop. Missing for 10: no independent/hands-on report specifically validating CI automation workflows end-to-end, and no explicit CI example (e.g., GitHub Actions snippet) beyond doc references.

   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”
   • [claimed-docs] “you can create sessions on behalf of any user in your organization using the create_as_user_id parameter”
   • [claimed-docs] “Integrate Devin into your CI/CD pipeline to respond to findings from static analysis tools like SonarQube, Fortify, or Veracode.”
   • [claimed-docs] “With Auto-Fix enabled, Devin automatically responds to code review comments, fixes flagged bugs, and iterates on CI failures — creating a cl…”
   • [claimed-docs] “The --sandbox flag runs the CLI with OS-level isolation, enforcing writable paths and deny rules at the operating-system level and optionall…”
   • [claimed-docs] “a local command-line coding agent with deep Devin Cloud integration”

   proof ↗⚑ flag

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

   weight 3 · round to OpenCode
   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

   Devin—none0/10

   The evidence only documents Devin exposing its own MCP server so other agents/IDEs can call Devin's tools (session management, playbooks, knowledge, scheduling) — the reverse direction of this story. There is no evidence that a user can configure Devin itself to consume/plug in external MCP servers so Devin can use their tools.

   • [claimed-docs] “it gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [claimed-docs] “gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [probe] “official MCP server documented at https://docs.devin.ai/work-with-devin/devin-mcp”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to OpenCode
   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

   Devin✓fullprobed8/10

   Devin has an official CLI ('Devin CLI, a local command-line coding agent with deep Devin Cloud integration') with documented usage examples and a sandbox flag for OS-level isolation, confirmed by both docs and probe. Missing for 10: independent/hands-on community verification of the CLI specifically (community evidence covers the web/session product, not CLI usage).

   • [claimed-docs] “Devin CLI, a local command-line coding agent with deep Devin Cloud integration.”
   • [claimed-docs] “devin -- check out this code and suggest a feasible, helpful feature”
   • [claimed-docs] “The --sandbox flag runs the CLI with OS-level isolation, enforcing writable paths and deny rules at the operating-system level and optionall…”
   • [claimed-docs] “a local command-line coding agent with deep Devin Cloud integration”
   • [probe] “official CLI documented at https://docs.devin.ai/cli/index”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   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

   Devin✓fullprobed8/10

   Devin ships a documented public API (docs-7) with session creation, org-level features like create_as_user_id (docs-8), plus a CLI and MCP server for programmatic/agentic control (docs-4, docs-6, probe-4, probe-5), directly enabling AI-native users to drive it programmatically. Missing for 10: a discoverable OpenAPI/swagger spec (probe-3 found 404s on all candidate paths) and independent hands-on corroboration of API usage.

   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”
   • [claimed-docs] “you can create sessions on behalf of any user in your organization using the create_as_user_id parameter”
   • [claimed-docs] “Devin CLI, a local command-line coding agent with deep Devin Cloud integration.”
   • [claimed-docs] “it gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [probe] “official MCP server documented at https://docs.devin.ai/work-with-devin/devin-mcp”
   • [probe] “official CLI documented at https://docs.devin.ai/cli/index”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.devin.ai/openapi.json, https://docs.devin.ai/swagger.json, https://docs.devin.ai/api/op…”

   proof ↗⚑ flag

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

   weight 2 · round to OpenCode
   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

   Devin—none0/10

   Devin exposes a general API (devin-docs-7) and can act on behalf of a specified user via create_as_user_id (devin-docs-8), but there is no evidence of scoped/least-privilege API key or token issuance, role-based permission scopes, or credential-level restriction mechanisms for agent access.

   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”
   • [claimed-docs] “you can create sessions on behalf of any user in your organization using the create_as_user_id parameter”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to OpenCode
   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

   Devin~partialprobed4/10

   Devin provides an API for integration (docs-7, docs-8) allowing developers to build applications and automate workflows, but the evidence never mentions dedicated official SDKs/client libraries (e.g., Python/JS packages), and probes for an OpenAPI spec that would back SDK generation all returned 404s (devin-probe-3). Missing for 10: named SDK packages in specific languages, SDK installation/usage docs, and a published OpenAPI/schema artifact confirming SDK-generation support.

   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”
   • [claimed-docs] “you can create sessions on behalf of any user in your organization using the create_as_user_id parameter”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.devin.ai/openapi.json, https://docs.devin.ai/swagger.json, https://docs.devin.ai/api/op…”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   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

   Devin—none0/10

   No evidence in the pack mentions webhooks or event subscription mechanisms; Devin's API/MCP docs describe session creation and management but nothing about outbound webhook notifications for events.

   ⚑ flag

Agentic features

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

   weight 2 · round drawn
   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

   Devin✓fullclaimed7/10

   Devin generates insights/suggestions from a user's own codebase data via 'Ask Devin' (code structure/dependency Q&A), auto-generated DeepWiki documentation, and Devin Review's automated PR feedback, all built on repository indexing. Missing for 10: independent/hands-on validation of the quality of these AI-generated insights (community evidence covers general task execution issues, not this specific feature) and no benchmark of insight accuracy.

   • [claimed-docs] “Ask Devin can answer questions about code structure and dependencies, and help you scope and plan tasks before implementation.”
   • [claimed-docs] “Devin Review provides automated first-pass reviews on pull requests, checking for correctness and conformance with organizational best pract…”
   • [claimed-docs] “Use DeepWiki to navigate architecture and code with auto-generated documentation.”
   • [claimed-docs] “Indexing your repositories allows Devin to understand your codebase and enables powerful features like Ask Devin and DeepWiki”

   proof ↗⚑ flag

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

   weight 2 · round to Devin
   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

   Devin✓fullclaimed8/10

   Devin explicitly supports background/autonomous execution: cloud sessions run in their own VM and 'keep going after you close your laptop' (devin-docs-13), MCP access includes 'scheduling' (devin-docs-6/23), the API lets you 'automate workflows' and create sessions programmatically (devin-docs-7/8), CI/CD integration triggers Devin on findings (devin-docs-19), and Auto-Fix creates a closed loop that iterates PRs 'without you in the loop' (devin-docs-18). This spans scheduled triggers, API-driven automation, and hands-off background operation. Missing for 10: independent/community verification that scheduled automations run reliably unattended, and more detail on a dedicated 'automation/schedule' UI beyond scattered doc mentions.

   • [claimed-docs] “The cloud session gets its own VM with a shell, browser, and full repo access, so it can keep going after you close your laptop.”
   • [claimed-docs] “it gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [claimed-docs] “gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”
   • [claimed-docs] “you can create sessions on behalf of any user in your organization using the create_as_user_id parameter”
   • [claimed-docs] “With Auto-Fix enabled, Devin automatically responds to code review comments, fixes flagged bugs, and iterates on CI failures — creating a cl…”
   • [claimed-docs] “Integrate Devin into your CI/CD pipeline to respond to findings from static analysis tools like SonarQube, Fortify, or Veracode.”
   • [claimed-docs] “Carve out independent tasks and run them simultaneously.”

   proof ↗⚑ flag

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

   weight 3 · round to OpenCode
   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

   Devin~partialcommunity6/10

   Devin's core product is designed for task delegation — via Ask Devin, ticket assignment, Slack/Teams tagging, and a conversational IDE (devin-docs-1, devin-docs-3, devin-docs-24) — so the axis clearly applies and is well documented. However, hands-on community reports show real caveats: Devin can add extraneous unrequested changes it can't undo, gets stuck for long periods without asking for help, and requires active babysitting/session termination to get value (devin-comm-1, devin-comm-2, devin-comm-5), undercutting a fully seamless delegation experience. Missing for 10: independent verification that delegated tasks reliably complete without extraneous side-effects or getting stuck, and stronger corroboration beyond one HN thread.

   • [claimed-docs] “Ask Devin to tackle Linear/Jira tickets, implement entirely new features, repro and fix bugs, build internal tools, and more!”
   • [claimed-docs] “Devin is designed to be a conversational user interface, and allows you to follow and take over Devin's development process in the embedded …”
   • [claimed-docs] “Tag Devin on a Slack or Teams thread about a bug you're discussing with coworkers”
   • [community] “Trialed Devin, it's quite impressive when it understands code formatting and local test setup, but it always adds extraneous changes beyond …”
   • [community] “One thing that surprised me is there doesn't seem to be an 'ask for help' escape hatch in Devin - it would work away for literally days on a…”
   • [community] “I've learned to just click 'Terminate Session' immediately after spotting Devin doing something hopeless. I've managed to get real work done…”

   proof ↗⚑ flag

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

   weight 2 · round to OpenCode
   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

   Devin✓fullcommunity8/10

   Devin is explicitly designed as a conversational agent: users assign tasks via natural language (Slack/Teams tagging, chat interface, CLI prompts like 'devin -- check out this code...'), and it interprets these into autonomous coding/dev actions across IDE, CLI, and cloud sessions. Community evidence corroborates it operates on natural-language task descriptions in practice, though with noted friction around scope creep and knowing when to stop. Missing for 10: independent benchmarking of NL command accuracy/robustness and richer detail on how ambiguous instructions are resolved.

   • [claimed-docs] “Ask Devin to tackle Linear/Jira tickets, implement entirely new features, repro and fix bugs, build internal tools, and more!”
   • [claimed-docs] “Tagging Devin on a Slack or Teams thread about a bug you're discussing with coworkers”
   • [claimed-docs] “Devin is designed to be a conversational user interface, and allows you to follow and take over Devin's development process in the embedded …”
   • [claimed-docs] “devin -- check out this code and suggest a feasible, helpful feature”
   • [claimed-docs] “Tag Devin on a Slack or Teams thread about a bug you're discussing with coworkers”
   • [community] “Trialed Devin, it's quite impressive when it understands code formatting and local test setup, but it always adds extraneous changes beyond …”
   • [community] “I've learned to just click 'Terminate Session' immediately after spotting Devin doing something hopeless. I've managed to get real work done…”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round to OpenCode
   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

   Devin—none0/10

   Devin has an API reference overview but the openapi.json probe returned 404 on all candidate paths, and there's no mention of an interactive reference with runnable examples (e.g., 'try it' console) in the docs pack.

   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.devin.ai/openapi.json, https://docs.devin.ai/swagger.json, https://docs.devin.ai/api/op…”

   proof ↗⚑ flag

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

   weight 2 · round to OpenCode
   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

   Devin—none0/10

   Devin has a documented API (devin-docs-7) but a direct probe for a machine-readable OpenAPI/swagger spec returned 404 on all candidate paths, and no documentation item references a downloadable spec file.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.devin.ai/openapi.json, https://docs.devin.ai/swagger.json, https://docs.devin.ai/api/op…”
   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”

   proof ↗⚑ flag

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

   weight 1 · round to Devin
   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

   Devin~partialclaimed6/10

   Devin sessions run in isolated cloud VMs with their own shell/browser/full repo access, configurable environment blueprints for a 'known-good state,' and a CLI --sandbox flag enforcing OS-level write/network isolation, all of which support testing in isolated environments away from live infrastructure. However, there is no explicit documentation addressing production-data isolation or masking, or confirmation that these sandboxes are guaranteed free of production data. missing for 10: explicit statement on production-data separation/masking, independent hands-on confirmation that sandbox testing never touches production data.

   • [claimed-docs] “The cloud session gets its own VM with a shell, browser, and full repo access, so it can keep going after you close your laptop.”
   • [claimed-docs] “Configure it once, and every session boots into that known-good state.”
   • [claimed-docs] “The --sandbox flag runs the CLI with OS-level isolation, enforcing writable paths and deny rules at the operating-system level and optionall…”
   • [claimed-docs] “The `--sandbox` flag runs the CLI with OS-level isolation, enforcing writable paths and `deny` rules at the operating-system level”
   • [claimed-docs] “Outposts lets you run Devin sessions inside infrastructure you control — your own VMs, containers, Kubernetes clusters, or even a Mac Mini o…”
   • [claimed-docs] “Devin inspects your repository, figures out which tools, runtimes, and dependencies are needed, and generates the blueprint for you.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Devin—none0/10

   There's an API reference (devin-docs-7) and even an OpenAPI probe, but that probe found no OpenAPI spec (devin-probe-3), and no evidence anywhere mentions API versioning scheme or a documented deprecation policy for the API.

   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.devin.ai/openapi.json, https://docs.devin.ai/swagger.json, https://docs.devin.ai/api/op…”

   proof ↗⚑ flag

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

   weight 2 · round to Devin
   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

   Devin~partialcommunity5/10

   Devin's API supports programmatic session creation (including on behalf of other users) and docs explicitly encourage carving out independent tasks to run simultaneously, which together enable bulk-style automation across many tickets/items, but there is no dedicated 'bulk operations' or batch-processing feature documented, and community feedback raises concerns about reliability/oversight needed per session that would complicate true bulk workflows. Missing for 10: an explicit batch/bulk API endpoint or UI for processing many items in one request, and independent evidence of successful large-scale bulk runs.

   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”
   • [claimed-docs] “you can create sessions on behalf of any user in your organization using the create_as_user_id parameter”
   • [claimed-docs] “Carve out independent tasks and run them simultaneously.”
   • [claimed-docs] “Ask Devin to tackle Linear/Jira tickets, implement entirely new features, repro and fix bugs, build internal tools, and more!”
   • [community] “Trialed Devin, it's quite impressive when it understands code formatting and local test setup, but it always adds extraneous changes beyond …”

   proof ↗⚑ flag

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

   weight 3 · round to Devin
   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

   Devin~partialclaimed6/10

   Devin supports several built-in event-triggered automations — Auto-Fix responds automatically to PR review comments and CI failures, CI/CD integration triggers Devin off static-analysis findings (SonarQube/Fortify/Veracode), and MCP exposes 'scheduling' as a capability — but there's no evidence of a general-purpose, user-defined rules/webhook engine for arbitrary custom triggers. Missing for 10: documentation of a configurable custom-rule/webhook trigger system, details on the scheduling feature's flexibility, and independent confirmation that these automations work reliably as event triggers.

   • [claimed-docs] “With Auto-Fix enabled, Devin automatically responds to code review comments, fixes flagged bugs, and iterates on CI failures — creating a cl…”
   • [claimed-docs] “Integrate Devin into your CI/CD pipeline to respond to findings from static analysis tools like SonarQube, Fortify, or Veracode.”
   • [claimed-docs] “Enable Devin Review with Auto-Fix so Devin automatically responds to code review comments, fixe”
   • [claimed-docs] “it gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [claimed-docs] “gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Devin
   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

   Devin~partialclaimed3/10

   Devin's MCP docs mention 'scheduling' as one of the capabilities exposed to MCP-compatible agents, implying some scheduling functionality exists, but there is no dedicated documentation, UI, or examples describing recurring jobs, cron-like triggers, or workflow automation configuration. missing for 10: dedicated scheduling feature docs, examples of recurring/cron jobs, independent confirmation of scheduled workflows in practice.

   • [claimed-docs] “it gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [claimed-docs] “gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   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

   Devin—none0/10

   The evidence shows Devin has knowledge, playbooks, and scheduling features but nothing about versioning, reviewing, or rolling back those automation configurations themselves; Devin Review/Auto-Fix pertains to PR code review, not to the automation definitions. Missing for 10: version history for playbooks/knowledge, a review workflow for automation changes, and a rollback mechanism for automations.

   ⚑ 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 Devin
   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

   Devin~partialcommunity7/10

   Devin's cloud sessions run in dedicated VMs with shell/browser/full repo access, can implement features, run tests, and continue autonomously after handoff, then present PRs for review (docs-1,13,17). However, community hands-on reports describe unreliable autonomy — extraneous breaking changes, inability to self-correct, and needing frequent human monitoring/termination — undercutting the 'build, test, demo end-to-end' promise. missing for 10: reliable independent verification of unattended end-to-end demo quality, and clearer evidence of a built-in demo/walkthrough artifact for reviewers beyond PR creation.

   • [claimed-docs] “Ask Devin to tackle Linear/Jira tickets, implement entirely new features, repro and fix bugs, build internal tools, and more!”
   • [claimed-docs] “The cloud session gets its own VM with a shell, browser, and full repo access, so it can keep going after you close your laptop.”
   • [claimed-docs] “Devin Review provides automated first-pass reviews on pull requests, checking for correctness and conformance with organizational best pract…”
   • [claimed-docs] “With Auto-Fix enabled, Devin automatically responds to code review comments, fixes flagged bugs, and iterates on CI failures — creating a cl…”
   • [community] “Trialed Devin, it's quite impressive when it understands code formatting and local test setup, but it always adds extraneous changes beyond …”
   • [community] “One thing that surprised me is there doesn't seem to be an 'ask for help' escape hatch in Devin - it would work away for literally days on a…”
   • [community] “I've learned to just click 'Terminate Session' immediately after spotting Devin doing something hopeless. I've managed to get real work done…”

   proof ↗⚑ flag

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

   weight 3 · round to Devin
   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

   Devin✓fullcommunity9/10

   Devin runs tasks in isolated cloud VMs with full shell/browser/repo access that persist after the user disconnects, explicitly supporting long-running background work and parallel independent tasks, corroborated by community reports of multi-day autonomous runs. Missing for 10: independent third-party benchmarking of long-running task reliability/quality beyond anecdotal HN reports.

   • [claimed-docs] “The cloud session gets its own VM with a shell, browser, and full repo access, so it can keep going after you close your laptop.”
   • [claimed-docs] “Carve out independent tasks and run them simultaneously.”
   • [claimed-docs] “Configure it once, and every session boots into that known-good state.”
   • [claimed-docs] “Hand a task off to a cloud Devin session and keep working locally.”
   • [community] “One thing that surprised me is there doesn't seem to be an 'ask for help' escape hatch in Devin - it would work away for literally days on a…”
   • [community] “You can set a 'max work time' before Devin pauses so it won't go for days endlessly spending your credits. By default it's set to 10 credits…”

   proof ↗⚑ flag

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

   weight 2 · round to Devin
   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

   Devin✓fullclaimed9/10

   Devin explicitly supports configuring environment 'blueprints' that specify tools, runtimes, and dependencies so 'every session boots into that known-good state,' with auto-detection of requirements from the repo (docs-31, docs-32), plus indexing (docs-27), knowledge/AGENTS.md context files (docs-29, docs-30), and VPN access for internal dependencies (docs-28), all running in isolated cloud VMs (docs-13). Missing for 10: independent/hands-on confirmation that blueprint-based environments reliably reproduce across sessions in practice.

   • [claimed-docs] “Configure it once, and every session boots into that known-good state.”
   • [claimed-docs] “Devin inspects your repository, figures out which tools, runtimes, and dependencies are needed, and generates the blueprint for you.”
   • [claimed-docs] “Indexing your repositories allows Devin to understand your codebase and enables powerful features like Ask Devin and DeepWiki”
   • [claimed-docs] “Knowledge is a collection of instructions and advice that Devin can reference in all sessions.”
   • [claimed-docs] “Devin supports AGENTS.md - a simple, open standard for providing context and instructions to AI agents.”
   • [claimed-docs] “Devin can connect to a VPN from inside its workspace, so sessions can reach internal services such as package registries, databases, and int…”
   • [claimed-docs] “The cloud session gets its own VM with a shell, browser, and full repo access, so it can keep going after you close your laptop.”

   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 drawn
   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

   Devin~partialcommunity6/10

   Docs confirm parallel task execution ('Carve out independent tasks and run them simultaneously'), cloud sessions that persist after closing the laptop, and an API to spin up multiple sessions programmatically (including on behalf of other users), which together support a 'fleet of parallel long-running agents' story. However, community hands-on reports show real friction with the 'hours/days autonomous' claim: sessions can get stuck without an escape hatch, users must babysit and manually terminate sessions every 10-15 minutes, and there's a default max-work-time cap limiting unsupervised runtime. Missing for 10: independent verification of successful multi-day/multi-task fleets running unattended, and evidence addressing the reported lack of a reliable 'ask for help' escalation during long runs.

   • [claimed-docs] “Carve out independent tasks and run them simultaneously.”
   • [claimed-docs] “The cloud session gets its own VM with a shell, browser, and full repo access, so it can keep going after you close your laptop.”
   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”
   • [claimed-docs] “you can create sessions on behalf of any user in your organization using the create_as_user_id parameter”
   • [community] “One thing that surprised me is there doesn't seem to be an 'ask for help' escape hatch in Devin - it would work away for literally days on a…”
   • [community] “Devin does ask for help when it can't do something, but it really hates asking for help if it's a skill issue - it would prefer running in c…”
   • [community] “You can set a 'max work time' before Devin pauses so it won't go for days endlessly spending your credits. By default it's set to 10 credits…”
   • [community] “I've learned to just click 'Terminate Session' immediately after spotting Devin doing something hopeless. I've managed to get real work done…”

   proof ↗⚑ flag

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

   weight 1 · round to OpenCode
   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

   Devin—none0/10

   Devin's docs mention running multiple independent tasks simultaneously (devin-docs-25) but this describes parallelizing different tasks, not running several parallel attempts of the SAME task to compare and choose the best result. No evidence describes a compare/choose-best-attempt workflow.

   • [claimed-docs] “Carve out independent tasks and run them simultaneously.”

   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 Devin
   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

   Devin~partialcommunity6/10

   Devin supports trigger-based autonomous work (Slack/Teams tags, PR review comments, CI/CD/static-analysis findings) and Auto-Fix creates a closed loop that iterates on CI failures without a human in the loop, and MCP exposes 'scheduling' as a session capability, all suggesting some always-on/triggered agent operation. However there's no dedicated docs for cron-like recurring schedules, and community reports describe sessions needing frequent human monitoring/termination rather than fully unattended long-running maintenance. Missing for 10: explicit scheduling/cron configuration docs, independent evidence of reliable unattended multi-day maintenance loops, and confirmation that Auto-Fix/CI triggers work without human oversight in practice.

   • [claimed-docs] “it gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [claimed-docs] “With Auto-Fix enabled, Devin automatically responds to code review comments, fixes flagged bugs, and iterates on CI failures — creating a cl…”
   • [claimed-docs] “Integrate Devin into your CI/CD pipeline to respond to findings from static analysis tools like SonarQube, Fortify, or Veracode.”
   • [claimed-docs] “Tag Devin on a Slack or Teams thread about a bug you're discussing with coworkers”
   • [community] “One thing that surprised me is there doesn't seem to be an 'ask for help' escape hatch in Devin - it would work away for literally days on a…”
   • [community] “You can set a 'max work time' before Devin pauses so it won't go for days endlessly spending your credits. By default it's set to 10 credits…”

   proof ↗⚑ flag

Debugging

1. developerDebug issues and troubleshoot using natural-language queries

   weight 2 · round to OpenCode
   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

   Devin~partialcommunity7/10

   Docs clearly support NL-driven debugging: 'repro and fix bugs', 'Ask Devin can answer questions about code structure...help you scope and plan tasks', and tagging Devin in Slack/Teams about a bug thread. However, hands-on community reports describe practical caveats—Devin adding extraneous changes it can't undo, getting stuck without escalating, requiring manual babysitting—that temper reliability for troubleshooting workflows. Missing for 10: independent benchmark/case study specifically on debugging accuracy, and resolution of the 'getting stuck on bugs' community complaint.

   • [claimed-docs] “Ask Devin to tackle Linear/Jira tickets, implement entirely new features, repro and fix bugs, build internal tools, and more!”
   • [claimed-docs] “Tagging Devin on a Slack or Teams thread about a bug you're discussing with coworkers”
   • [claimed-docs] “Ask Devin can answer questions about code structure and dependencies, and help you scope and plan tasks before implementation.”
   • [claimed-docs] “Tag Devin on a Slack or Teams thread about a bug you're discussing with coworkers”
   • [community] “Trialed Devin, it's quite impressive when it understands code formatting and local test setup, but it always adds extraneous changes beyond …”
   • [community] “One thing that surprised me is there doesn't seem to be an 'ask for help' escape hatch in Devin - it would work away for literally days on a…”
   • [community] “Devin does ask for help when it can't do something, but it really hates asking for help if it's a skill issue - it would prefer running in c…”

   proof ↗⚑ flag

Feature implementation

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

   weight 3 · round to OpenCode
   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

   Devin~partialcommunity6/10

   Devin's docs explicitly describe taking Linear/Jira tickets and implementing full features, with Devin Review/Auto-Fix looping PRs toward merge-ready status without human involvement, covering the issue-to-PR pipeline end-to-end. However, hands-on community reports describe practical friction — extraneous unrelated changes that can break things, inability to easily undo them, and agents getting stuck for days rather than asking for help — casting doubt on how cleanly the 'complete' PR is delivered without oversight. Missing for 10: independent verification of a clean ticket→merged-PR flow without manual intervention, and resolution of the reported reliability/quality issues.

   • [claimed-docs] “Ask Devin to tackle Linear/Jira tickets, implement entirely new features, repro and fix bugs, build internal tools, and more!”
   • [claimed-docs] “Devin Review provides automated first-pass reviews on pull requests, checking for correctness and conformance with organizational best pract…”
   • [claimed-docs] “With Auto-Fix enabled, Devin automatically responds to code review comments, fixes flagged bugs, and iterates on CI failures — creating a cl…”
   • [claimed-docs] “Code migrations, refactors, and modernization”
   • [community] “Trialed Devin, it's quite impressive when it understands code formatting and local test setup, but it always adds extraneous changes beyond …”
   • [community] “One thing that surprised me is there doesn't seem to be an 'ask for help' escape hatch in Devin - it would work away for literally days on a…”
   • [community] “Devin does ask for help when it can't do something, but it really hates asking for help if it's a skill issue - it would prefer running in c…”
   • [community] “I've learned to just click 'Terminate Session' immediately after spotting Devin doing something hopeless. I've managed to get real work done…”

   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
   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

   Devin!disputedcontradicted5/10

   Devin's docs strongly claim end-to-end feature/bug implementation across a full repo (Linear/Jira tickets, multi-file fixes, code migrations) with full workspace/VM access [devin-docs-1, devin-docs-13, devin-docs-21, devin-docs-27], but hands-on community reports concretely contradict smooth delivery: it 'always adds extraneous changes beyond the task that can break other things, and can't undo those changes if asked' and required constant supervision/termination to get real work done [devin-comm-1, devin-comm-5], with another user noting it can run for days without an escape hatch when stuck [devin-comm-2]. Missing for 10: independent benchmark data on multi-file correctness, and resolution of the extraneous-change/undo failure mode reported by users.

   • [claimed-docs] “Ask Devin to tackle Linear/Jira tickets, implement entirely new features, repro and fix bugs, build internal tools, and more!”
   • [claimed-docs] “The cloud session gets its own VM with a shell, browser, and full repo access, so it can keep going after you close your laptop.”
   • [claimed-docs] “Code migrations, refactors, and modernization”
   • [claimed-docs] “Indexing your repositories allows Devin to understand your codebase and enables powerful features like Ask Devin and DeepWiki”
   • [community] “Trialed Devin, it's quite impressive when it understands code formatting and local test setup, but it always adds extraneous changes beyond …”
   • [community] “One thing that surprised me is there doesn't seem to be an 'ask for help' escape hatch in Devin - it would work away for literally days on a…”
   • [community] “I've learned to just click 'Terminate Session' immediately after spotting Devin doing something hopeless. I've managed to get real work done…”

   proof ↗⚑ flag

Maintenance automation

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

   weight 3 · round drawn
   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

   Devin~partialcommunity6/10

   Docs show Devin is a general-purpose coding agent that can fix bugs, implement features, iterate on CI failures, respond to review comments (Auto-Fix), and handle code migrations/refactors/modernization, which plausibly covers lint fixes and CI-related work, but none of the docs explicitly mention writing tests, resolving merge conflicts, or updating dependencies as named capabilities. Community reports (devin-comm-1) also note Devin can introduce extraneous changes and struggles to cleanly undo them, tempering confidence in reliably delivering these specific maintenance tasks. Missing for 10: explicit documentation/evidence of test-writing, lint-fixing, merge-conflict resolution, and dependency-update workflows, plus independent hands-on confirmation of these specific tasks succeeding.

   • [claimed-docs] “Ask Devin to tackle Linear/Jira tickets, implement entirely new features, repro and fix bugs, build internal tools, and more!”
   • [claimed-docs] “With Auto-Fix enabled, Devin automatically responds to code review comments, fixes flagged bugs, and iterates on CI failures — creating a cl…”
   • [claimed-docs] “Integrate Devin into your CI/CD pipeline to respond to findings from static analysis tools like SonarQube, Fortify, or Veracode.”
   • [claimed-docs] “Code migrations, refactors, and modernization”
   • [community] “Trialed Devin, it's quite impressive when it understands code formatting and local test setup, but it always adds extraneous changes beyond …”

   proof ↗⚑ flag

Multimodal generation

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

   weight 2 · round drawn
   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

   Devin—none0/10

   No evidence anywhere in the pack that Devin accepts a sketch/image/PDF design as input and generates a working app from it; documentation focuses on text-based tasks, tickets, Slack threads, code review, and CLI/desktop environment features with no multimodal design-to-app capability mentioned.

   ⚑ flag

Codebase mapping

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

   weight 3 · round drawn
   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

   Devin✓fullclaimed7/10

   Devin explicitly indexes repositories to power 'Ask Devin' and 'DeepWiki', which answer questions about code structure and dependencies and help developers scope/plan where to start making changes, directly matching the story. missing for 10: independent/hands-on evidence validating DeepWiki/Ask Devin's accuracy on real codebases (community evidence only covers task execution, not codebase-understanding features).

   • [claimed-docs] “Use DeepWiki to navigate architecture and code with auto-generated documentation.”
   • [claimed-docs] “Ask Devin can answer questions about code structure and dependencies, and help you scope and plan tasks before implementation.”
   • [claimed-docs] “Indexing your repositories allows Devin to understand your codebase and enables powerful features like Ask Devin and DeepWiki”

   proof ↗⚑ flag

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

   weight 3 · round to Devin
   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

   Devin✓fullclaimed7/10

   Docs describe repo indexing that lets Devin understand the codebase and power 'Ask Devin' and DeepWiki auto-generated architecture docs, directly enabling exploration/explanation of an unfamiliar codebase without manual file selection (devin-docs-27, devin-docs-15, devin-docs-16). No community evidence contradicts this specific capability. Missing for 10: independent/hands-on verification of codebase-mapping accuracy and no concrete example of DeepWiki output quality.

   • [claimed-docs] “Indexing your repositories allows Devin to understand your codebase and enables powerful features like Ask Devin and DeepWiki”
   • [claimed-docs] “Use DeepWiki to navigate architecture and code with auto-generated documentation.”
   • [claimed-docs] “Ask Devin can answer questions about code structure and dependencies, and help you scope and plan tasks before implementation.”

   proof ↗⚑ flag

Context management

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

   weight 2 · round to Devin
   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

   Devin~partialclaimed5/10

   Devin supports persistent cross-session context via "Knowledge" (instructions referenced in all sessions), AGENTS.md, and environment blueprints that let every session boot into a known-good state, which enables some recall across sessions. However, these mechanisms are largely user-configured/onboarded rather than autonomously built by the agent from its own experience, and there's no evidence of automatic memory creation or recall behavior demonstrated in practice. Missing for 10: evidence the agent automatically extracts/updates memory from its own task experience without manual setup, and independent confirmation that recalled memory improves subsequent session performance.

   • [claimed-docs] “Knowledge is a collection of instructions and advice that Devin can reference in all sessions.”
   • [claimed-docs] “Devin supports AGENTS.md - a simple, open standard for providing context and instructions to AI agents.”
   • [claimed-docs] “Configure it once, and every session boots into that known-good state.”
   • [claimed-docs] “Indexing your repositories allows Devin to understand your codebase and enables powerful features like Ask Devin and DeepWiki”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Devin—none0/10

   No evidence describes attaching or indexing multiple project directories/repositories within a single Devin session; docs discuss single-repo indexing, knowledge, and environment setup but not multi-directory context in one session.

   ⚑ flag

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

   weight 3 · round to Devin
   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

   Devin✓fullclaimed9/10

   Devin explicitly supports AGENTS.md, an open standard for providing context and instructions to AI agents, plus a separate 'Knowledge' feature for instructions/advice referenced across all sessions, directly covering project-level coding standards/conventions. Missing for 10: independent/hands-on confirmation that these instructions are reliably followed in practice.

   • [claimed-docs] “Devin supports AGENTS.md - a simple, open standard for providing context and instructions to AI agents.”
   • [claimed-docs] “Knowledge is a collection of instructions and advice that Devin can reference in all sessions.”

   proof ↗⚑ flag

Issue diagnosis

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

   weight 3 · round to Devin
   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

   Devin~partialcommunity6/10

   Docs explicitly claim Devin can 'repro and fix bugs' (devin-docs-1), use Ask Devin/DeepWiki to narrow root causes via codebase understanding (devin-docs-15, devin-docs-16, devin-docs-27), and verify fixes through CI iteration/Auto-Fix loops (devin-docs-18). However, hands-on community testimony reports Devin often adds extraneous changes beyond the task scope and cannot reliably undo them when asked, undermining clean verification of fixes (devin-comm-1), and lacks an escape hatch when stuck on root-cause diagnosis (devin-comm-2, devin-comm-3). Missing for 10: independent verification of successful bug reproduction/root-cause narrowing at scale, and resolution of the reported inability to cleanly revert unwanted changes during fix verification.

   • [claimed-docs] “Ask Devin to tackle Linear/Jira tickets, implement entirely new features, repro and fix bugs, build internal tools, and more!”
   • [claimed-docs] “Use DeepWiki to navigate architecture and code with auto-generated documentation.”
   • [claimed-docs] “Ask Devin can answer questions about code structure and dependencies, and help you scope and plan tasks before implementation.”
   • [claimed-docs] “With Auto-Fix enabled, Devin automatically responds to code review comments, fixes flagged bugs, and iterates on CI failures — creating a cl…”
   • [claimed-docs] “Indexing your repositories allows Devin to understand your codebase and enables powerful features like Ask Devin and DeepWiki”
   • [community] “Trialed Devin, it's quite impressive when it understands code formatting and local test setup, but it always adds extraneous changes beyond …”
   • [community] “One thing that surprised me is there doesn't seem to be an 'ask for help' escape hatch in Devin - it would work away for literally days on a…”
   • [community] “Devin does ask for help when it can't do something, but it really hates asking for help if it's a skill issue - it would prefer running in c…”

   proof ↗⚑ flag

Marketplace

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

   weight 1 · round to OpenCode
   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

   Devin~partialclaimed6/10

   Devin supports several skill-like extension mechanisms — 'Knowledge' (persistent instructions/advice for all sessions), AGENTS.md for structured agent instructions, and 'Playbooks' exposed via MCP — plus an open-source 'Devin Handoff' explicitly described as a 'plugin and skill'. This gives developers real levers to encode specialized, reusable task behavior, but the docs don't show a dedicated skill-authoring UI/marketplace or detailed examples of building a complex custom skill, and there is no independent/community evidence confirming this works well in practice. Missing for 10: concrete examples/tutorials of authoring a non-trivial custom skill, a discoverable skills registry, and independent hands-on corroboration.

   • [claimed-docs] “Knowledge is a collection of instructions and advice that Devin can reference in all sessions.”
   • [claimed-docs] “Devin supports AGENTS.md - a simple, open standard for providing context and instructions to AI agents.”
   • [claimed-docs] “it gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [claimed-docs] “gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [claimed-docs] “Devin Handoff is an open-source plugin and skill that brings the same handoff workflow to any coding agent — Claude Code, Codex, Cursor, and…”

   proof ↗⚑ flag

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

   weight 1 · round to OpenCode
   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

   Devin~partialprobed4/10

   Devin exposes an MCP server so external MCP-compatible agents/IDEs can access its session management and tools, and its open-source 'Devin Handoff' plugin interoperates with other coding agents (Claude Code, Codex, Cursor), showing some cross-agent workflow integration. However there is no evidence of a partner/marketplace ecosystem of third-party agent apps being integrated into Devin's own workflows. Missing for 10: a documented partner-app marketplace or catalog, evidence of installing/configuring third-party agent apps within Devin, and any case study of an engineering-lead orchestrating partner-built agents through Devin.

   • [claimed-docs] “it gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [claimed-docs] “Devin Handoff is an open-source plugin and skill that brings the same handoff workflow to any coding agent — Claude Code, Codex, Cursor, and…”
   • [claimed-docs] “gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [probe] “official MCP server documented at https://docs.devin.ai/work-with-devin/devin-mcp”

   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 Devin
   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

   Devin~partialclaimed6/10

   Devin offers building blocks for a team-wide source of truth — repo indexing that powers 'Ask Devin' and DeepWiki architecture docs, org-wide 'Knowledge' referenced in all sessions, and AGENTS.md support for shared context — which collectively let a lead centralize docs/repo knowledge for the team. However, there's no explicit product feature framed as a 'shared workspace' UI for team-wide docs/repo browsing outside of Devin's own agent sessions. Missing for 10: a dedicated shared workspace/knowledge-base product surface for humans to browse, independent evidence of teams using it as a collaborative source of truth, and clarity on cross-repo doc aggregation beyond per-session knowledge.

   • [claimed-docs] “Indexing your repositories allows Devin to understand your codebase and enables powerful features like Ask Devin and DeepWiki”
   • [claimed-docs] “Knowledge is a collection of instructions and advice that Devin can reference in all sessions.”
   • [claimed-docs] “Devin supports AGENTS.md - a simple, open standard for providing context and instructions to AI agents.”
   • [claimed-docs] “Use DeepWiki to navigate architecture and code with auto-generated documentation.”
   • [claimed-docs] “Devin inspects your repository, figures out which tools, runtimes, and dependencies are needed, and generates the blueprint for you.”

   proof ↗⚑ flag

Tool integration

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

   weight 3 · round to Devin
   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

   Devin~partialclaimed6/10

   Devin can be tagged in Slack/Teams threads and work Jira/Linear tickets, giving it direct workflow-tool integration, and its MCP server plus API enable further extension to other tools. However there is no explicit documented Google Drive integration, and no independent/hands-on corroboration of these integrations actually working in practice. missing for 10: Google Drive connector evidence, independent verification of Jira/Slack integration reliability.

   • [claimed-docs] “Ask Devin to tackle Linear/Jira tickets, implement entirely new features, repro and fix bugs, build internal tools, and more!”
   • [claimed-docs] “Tagging Devin on a Slack or Teams thread about a bug you're discussing with coworkers”
   • [claimed-docs] “Tag Devin on a Slack or Teams thread about a bug you're discussing with coworkers”
   • [claimed-docs] “it gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”

   proof ↗⚑ flag

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

   weight 2 · round to Devin
   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

   Devin~partialclaimed6/10

   Docs confirm Devin can be invoked from Linear/Jira tickets and Slack/Teams threads, plus API integration for building custom workflow triggers, but there's no explicit mention of GitHub or GitLab issue/PR-based task kickoff in the evidence pack. Community evidence doesn't directly contradict the integration claims, only general effectiveness concerns. Missing for 10: explicit GitHub/GitLab-triggered task creation documentation, independent hands-on confirmation of these specific integrations working.

   • [claimed-docs] “Ask Devin to tackle Linear/Jira tickets, implement entirely new features, repro and fix bugs, build internal tools, and more!”
   • [claimed-docs] “Tagging Devin on a Slack or Teams thread about a bug you're discussing with coworkers”
   • [claimed-docs] “Tag Devin on a Slack or Teams thread about a bug you're discussing with coworkers”
   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”
   • [claimed-docs] “you can create sessions on behalf of any user in your organization using the create_as_user_id parameter”

   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 Devin
   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

   Devin✓fullclaimed7/10

   Devin's cloud sessions run in a dedicated VM that persists independent of the local device (docs-13), can be started from Slack/Teams, IDE, CLI, or API and continued/taken over in the embedded IDE or web UI (docs-3, docs-4, docs-7, docs-24), and Devin Handoff explicitly lets you start work locally and continue in a cloud session accessible from a browser (docs-38). missing for 10: no explicit first-party walkthrough of resuming the same session from a different browser/device login, and no independent/community confirmation of cross-device continuity.

   • [claimed-docs] “Devin is designed to be a conversational user interface, and allows you to follow and take over Devin's development process in the embedded …”
   • [claimed-docs] “Devin CLI, a local command-line coding agent with deep Devin Cloud integration.”
   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”
   • [claimed-docs] “The cloud session gets its own VM with a shell, browser, and full repo access, so it can keep going after you close your laptop.”
   • [claimed-docs] “Tag Devin on a Slack or Teams thread about a bug you're discussing with coworkers”
   • [claimed-docs] “Hand a task off to a cloud Devin session and keep working locally.”

   proof ↗⚑ flag

Ide integration

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

   weight 3 · round to OpenCode
   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

   Devin~partialclaimed5/10

   Devin exposes a conversational interface via its own embedded IDE within cloud sessions (devin-docs-3) and its Desktop app that imports VS Code/Cursor settings (devin-docs-9), plus an MCP server letting 'any MCP-compatible AI agent or IDE' access sessions (devin-docs-6/23). However there's no evidence of a native extension that lets a developer chat with Devin directly inside their own existing IDE (e.g., a VS Code/JetBrains plugin) — Devin's model is its own IDE/Desktop environment or MCP bridging rather than embedding in the user's IDE. Missing for 10: a first-party IDE extension for VS Code/JetBrains enabling in-IDE chat, and independent confirmation of this workflow working well in practice.

   • [claimed-docs] “Devin is designed to be a conversational user interface, and allows you to follow and take over Devin's development process in the embedded …”
   • [claimed-docs] “Import VS Code or Cursor settings, configure themes, and start coding with AI-powered assistance.”
   • [claimed-docs] “it gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [claimed-docs] “gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”

   proof ↗⚑ flag

Session management

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

   weight 2 · round to OpenCode
   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

   Devin~partialclaimed4/10

   Devin has a documented Desktop app (docs-9) and supports running multiple independent sessions in parallel (docs-25), but there is no evidence of a visual diff review feature or explicit side-by-side session UI within the desktop app itself. Missing for 10: explicit documentation of an in-app diff viewer, UI showing multiple sessions simultaneously in one window, and any hands-on/community confirmation of this desktop workflow.

   • [claimed-docs] “Import VS Code or Cursor settings, configure themes, and start coding with AI-powered assistance.”
   • [claimed-docs] “Devin is designed to be a conversational user interface, and allows you to follow and take over Devin's development process in the embedded …”
   • [claimed-docs] “Carve out independent tasks and run them simultaneously.”

   proof ↗⚑ flag

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

   weight 2 · round to OpenCode
   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

   Devin~partialcommunity6/10

   Devin supports running multiple parallel sessions ('carve out independent tasks and run them simultaneously'), an API to create sessions on behalf of users, and an embedded IDE/CLI/desktop app to interact with sessions, which together enable a lead-like workspace for managing several agent sessions. However, there's no dedicated 'unified workspace' dashboard evidence for an engineering-lead specifically monitoring/managing a team's multiple concurrent sessions, and community feedback highlights session reliability issues that would complicate multi-session oversight. missing for 10: explicit multi-session dashboard/UI for a lead role, team-level session oversight features, independent corroboration of smooth multi-session management at scale.

   • [claimed-docs] “Carve out independent tasks and run them simultaneously.”
   • [claimed-docs] “you can create sessions on behalf of any user in your organization using the create_as_user_id parameter”
   • [claimed-docs] “Devin is designed to be a conversational user interface, and allows you to follow and take over Devin's development process in the embedded …”
   • [claimed-docs] “Devin CLI, a local command-line coding agent with deep Devin Cloud integration.”
   • [community] “Trialed Devin, it's quite impressive when it understands code formatting and local test setup, but it always adds extraneous changes beyond …”
   • [community] “I've learned to just click 'Terminate Session' immediately after spotting Devin doing something hopeless. I've managed to get real work done…”

   proof ↗⚑ flag

Terminal workflow

1. developerRun a coding agent locally from my terminal

   weight 3 · round to OpenCode
   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

   Devin✓fullprobed8/10

   Devin CLI is explicitly documented as a local command-line coding agent that can be invoked from terminal (e.g. `devin -- check out this code...`), with local sandboxing (--sandbox flag) and deep integration with Devin Cloud for handoff. Missing for 10: independent/hands-on community verification specifically of the CLI experience (community evidence only covers the cloud/browser Devin product, not the local CLI).

   • [claimed-docs] “Devin CLI, a local command-line coding agent with deep Devin Cloud integration.”
   • [claimed-docs] “devin -- check out this code and suggest a feasible, helpful feature”
   • [claimed-docs] “a local command-line coding agent with deep Devin Cloud integration”
   • [claimed-docs] “The --sandbox flag runs the CLI with OS-level isolation, enforcing writable paths and deny rules at the operating-system level and optionall…”
   • [claimed-docs] “The `--sandbox` flag runs the CLI with OS-level isolation, enforcing writable paths and `deny` rules at the operating-system level”
   • [probe] “official CLI documented at https://docs.devin.ai/cli/index”

   proof ↗⚑ flag

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

   weight 2 · round to OpenCode
   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

   Devin✓fullclaimed7/10

   Devin exposes a documented API for creating sessions programmatically (including on behalf of users) and explicit CI/CD pipeline integration to auto-respond to static-analysis findings, plus a CLI (`devin -- <prompt>`) that can be invoked headlessly, all pointing to non-interactive, scriptable automation. Missing for 10: independent/hands-on confirmation of headless CLI scripting in real CI pipelines and more detail on CLI exit codes/output for scripting.

   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”
   • [claimed-docs] “Integrate Devin into your CI/CD pipeline to respond to findings from static analysis tools like SonarQube, Fortify, or Veracode.”
   • [claimed-docs] “Devin CLI, a local command-line coding agent with deep Devin Cloud integration.”
   • [claimed-docs] “devin -- check out this code and suggest a feasible, helpful feature”
   • [claimed-docs] “With Auto-Fix enabled, Devin automatically responds to code review comments, fixes flagged bugs, and iterates on CI failures — creating a cl…”
   • [claimed-docs] “a local command-line coding agent with deep Devin Cloud integration”

   proof ↗⚑ flag

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

   weight 2 · round to OpenCode
   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

   Devin~partialprobed5/10

   Devin exposes a documented API (session creation, create_as_user_id) and an MCP server giving 'full access to session management, playbooks, knowledge, and scheduling', suggesting broad programmatic parity, but there's no explicit claim of full UI/API feature parity, and probes for an OpenAPI spec all 404'd, indicating the full API surface isn't transparently documented. Missing for 10: explicit parity statement covering UI-only features like Devin Review/Auto-Fix/Computer Use/desktop app settings, a discoverable OpenAPI schema, and independent confirmation that all UI actions are API-reachable.

   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”
   • [claimed-docs] “you can create sessions on behalf of any user in your organization using the create_as_user_id parameter”
   • [claimed-docs] “it gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [claimed-docs] “gives any MCP-compatible AI agent or IDE full access to session management, playbooks, knowledge, and scheduling”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.devin.ai/openapi.json, https://docs.devin.ai/swagger.json, https://docs.devin.ai/api/op…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   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

   Devin—none0/10

   No evidence of a data export feature or open-format export/portability mechanism for Devin sessions, knowledge, or artifacts; the docs cover API, CLI, MCP, and infrastructure but nothing about exporting all user data in open formats to leave the platform.

   ⚑ flag

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

   weight 2 · round to OpenCode
   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

   Devin—none0/10

   Devin is a closed, proprietary commercial product; no evidence indicates its source code is available under an open license. The only mention of 'open-source' is for the separate Devin Handoff plugin/skill, not Devin itself.

   • [claimed-docs] “Devin Handoff is an open-source plugin and skill that brings the same handoff workflow to any coding agent — Claude Code, Codex, Cursor, and…”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to OpenCode
   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

   Devin—none0/10

   Devin is a cloud-based SaaS agent; Outposts lets you run sessions on your own infrastructure but the core Devin model/orchestration itself remains Cognition-hosted, and there's no evidence of a self-hostable core product/model package. No mention of on-prem/self-hosted deployment of the core Devin engine.

   • [claimed-docs] “Outposts lets you run Devin sessions inside infrastructure you control — your own VMs, containers, Kubernetes clusters, or even a Mac Mini o…”

   proof ↗⚑ flag

Authentication

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

   weight 2 · round to OpenCode
   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

   Devin~partialprobed6/10

   Devin has a documented API (devin-docs-7) intended for programmatic integration, implying API key auth as an alternative to account login, and even supports creating sessions on behalf of other users (devin-docs-8), suggesting a service-level credential model. However, no explicit documentation of API key generation/management or authentication mechanics is present in the evidence pack. Missing for 10: explicit API key creation/management docs, confirmation that API key auth fully replaces login flows, and independent/community verification of this workflow.

   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”
   • [claimed-docs] “you can create sessions on behalf of any user in your organization using the create_as_user_id parameter”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.devin.ai/openapi.json, https://docs.devin.ai/swagger.json, https://docs.devin.ai/api/op…”

   proof ↗⚑ flag

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

   weight 2 · round to OpenCode
   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

   Devin—none0/10

   No evidence of SSO/SAML, OIDC, or enterprise identity provider integration (e.g., Okta, Azure AD, Google Workspace) for authentication; the only related item is API session creation on behalf of a user, which is not enterprise identity/SSO authentication.

   ⚑ flag

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

   weight 2 · round to OpenCode
   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

   Devin—none0/10

   The evidence describes Devin's own subscription tiers (Pro, Max, Core/Team/Enterprise) but nothing about letting a developer sign in using an existing external subscription (e.g., an existing LLM provider or IDE subscription) to access the agent. No mention of SSO-linked billing or bring-your-own-subscription support.

   • [claimed-docs] “Max is for individual users who consistently exceed the Pro quota. It includes everything in Pro, plus a significantly larger weekly usage q…”
   • [claimed-docs] “Power users who need more quota”

   proof ↗⚑ flag

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

   weight 1 · round to OpenCode
   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

   Devin—none0/10

   Evidence only describes paid tiers (Pro, Max, 'power users who need more quota') and API key based integration; there's no mention of a free tier accessible via personal account sign-in without API key management.

   • [claimed-docs] “Max is for individual users who consistently exceed the Pro quota. It includes everything in Pro, plus a significantly larger weekly usage q…”
   • [claimed-docs] “Power users who need more quota”
   • [claimed-docs] “The Devin API enables you to integrate Devin into your applications, automate workflows, and build powerful tools.”

   proof ↗⚑ flag

Model choice

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

   weight 1 · round drawn
   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

   Devin—none0/10

   No evidence that Devin offers automatic model selection or model-routing based on task complexity; docs discuss quotas, tiers (Pro/Max), and features but never mention choosing among multiple underlying models per task.

   ⚑ flag

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

   weight 2 · round to OpenCode
   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

   Devin—none0/10

   No evidence in the pack mentions selecting or switching between multiple underlying AI model providers (e.g., choosing between different LLMs) for a Devin session; documentation covers agent capabilities, environments, and billing tiers but not model selection.

   ⚑ flag

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

   weight 2 · round drawn
   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

   Devin—none0/10

   No evidence of data residency/region selection controls for where Devin stores data; the pack covers deployment options (Outposts, VPN, sandbox isolation) but nothing about choosing storage region/jurisdiction.

   ⚑ flag

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

   weight 3 · round drawn
   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

   Devin—none0/10

   The evidence pack contains no mention of data-training opt-out, data usage policy, or privacy controls for AI model training; nothing in the docs or community sources addresses this axis.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   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

   Devin—none0/10

   No evidence pack items address data retention policies, data deletion controls, or privacy/data-handling settings for user data or session data; the closest items concern sandboxing/isolation of execution environments, not retention/deletion of stored data.

   ⚑ flag

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

   weight 2 · round to OpenCode
   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

   Devin—none0/10

   No evidence pack item mentions telemetry opt-out, usage tracking settings, or privacy controls of that kind; the docs cover features, sandboxing, and infrastructure but not data-collection opt-out mechanisms.

   ⚑ flag

Data governance

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

   weight 1 · round drawn
   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

   Devin—none0/10

   No evidence in the pack addresses data usage, training opt-out, or privacy/data-handling policies for Devin; nothing documents an opt-out mechanism for code/prompt use in model training.

   ⚑ flag

Pr review

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

   weight 3 · round drawn
   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

   Devin~partialcommunity6/10

   Devin's docs describe it implementing features/fixing bugs and producing pull requests that get automated review and iteration (devin-docs-17, devin-docs-18), implying it handles the full git workflow (branch, commit, PR) autonomously, but no doc explicitly details staging, commit-message generation, or branch creation as discrete steps. Community feedback (devin-comm-1) also notes it can add extraneous changes it can't cleanly undo, a real caveat on commit hygiene. Missing for 10: explicit documentation of commit/staging/branch mechanics and independent confirmation that generated commits/PRs are clean and reviewable.

   • [claimed-docs] “Ask Devin to tackle Linear/Jira tickets, implement entirely new features, repro and fix bugs, build internal tools, and more!”
   • [claimed-docs] “Devin Review provides automated first-pass reviews on pull requests, checking for correctness and conformance with organizational best pract…”
   • [claimed-docs] “With Auto-Fix enabled, Devin automatically responds to code review comments, fixes flagged bugs, and iterates on CI failures — creating a cl…”
   • [claimed-docs] “Carve out independent tasks and run them simultaneously.”
   • [community] “Trialed Devin, it's quite impressive when it understands code formatting and local test setup, but it always adds extraneous changes beyond …”

   proof ↗⚑ flag

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

   weight 3 · round to Devin
   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

   Devin✓fullclaimed8/10

   Devin Review is explicitly documented as an automated first-pass PR reviewer checking correctness and org best-practice conformance, with Auto-Fix closing the loop by responding to review comments and CI failures. This directly matches the story of automatic contextual code review on PRs, though evidence is vendor-documentation only with no independent hands-on validation of review quality/contextual accuracy. Missing for 10: independent/community corroboration of review quality, and detail on how 'contextual feedback' is surfaced per-PR beyond docs description.

   • [claimed-docs] “Devin Review provides automated first-pass reviews on pull requests, checking for correctness and conformance with organizational best pract…”
   • [claimed-docs] “With Auto-Fix enabled, Devin automatically responds to code review comments, fixes flagged bugs, and iterates on CI failures — creating a cl…”
   • [claimed-docs] “Integrate Devin into your CI/CD pipeline to respond to findings from static analysis tools like SonarQube, Fortify, or Veracode.”
   • [claimed-docs] “Enable Devin Review with Auto-Fix so Devin automatically responds to code review comments, fixe”

   proof ↗⚑ flag

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

   weight 3 · round to Devin
   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

   Devin✓fullclaimed8/10

   Devin's docs describe Devin Review, which performs automated first-pass PR reviews checking correctness and org conformance, plus CI/CD integration to respond to static-analysis findings (SonarQube, Fortify, Veracode) and Auto-Fix iterating on CI failures — directly enabling developers to inspect diffs and run checks before merge. This is corroborated by explicit SDLC integration workflow docs, not just a single mention. missing for 10: independent/hands-on evidence confirming Devin Review's diff-inspection quality in practice, and detail on how diffs are surfaced/inspected by the developer (UI specifics) beyond docs claims.

   • [claimed-docs] “Devin Review provides automated first-pass reviews on pull requests, checking for correctness and conformance with organizational best pract…”
   • [claimed-docs] “With Auto-Fix enabled, Devin automatically responds to code review comments, fixes flagged bugs, and iterates on CI failures — creating a cl…”
   • [claimed-docs] “Integrate Devin into your CI/CD pipeline to respond to findings from static analysis tools like SonarQube, Fortify, or Veracode.”
   • [claimed-docs] “Enable Devin Review with Auto-Fix so Devin automatically responds to code review comments, fixe”

   proof ↗⚑ flag

Safe execution

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

   weight 2 · round to OpenCode
   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

   Devin~partialclaimed6/10

   Devin exposes some admin-level controls over its access—an org-wide 'Enable desktop mode' toggle for Computer Use, a CLI --sandbox flag enforcing OS-level writable-path/deny rules and network restriction, and Outposts for running sessions in infra you control—giving leads levers to constrain what Devin can reach or do. However there's no documented centralized policy/allowlist for specific external integrations (e.g., disabling Slack, Jira, GitHub, VPN access per-tool) or granular permission/audit management for engineering leads. missing for 10: a unified integration-permission/allowlist admin panel, per-tool enable/disable controls beyond desktop mode, and independent verification of these controls in practice.

   • [claimed-docs] “Computer Use is controlled by the Enable desktop mode toggle in your organization's customization options.”
   • [claimed-docs] “The --sandbox flag runs the CLI with OS-level isolation, enforcing writable paths and deny rules at the operating-system level and optionall…”
   • [claimed-docs] “The `--sandbox` flag runs the CLI with OS-level isolation, enforcing writable paths and `deny` rules at the operating-system level”
   • [claimed-docs] “Outposts lets you run Devin sessions inside infrastructure you control — your own VMs, containers, Kubernetes clusters, or even a Mac Mini o…”
   • [claimed-docs] “Devin can connect to a VPN from inside its workspace, so sessions can reach internal services such as package registries, databases, and int…”

   proof ↗⚑ flag

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

   weight 2 · round to Devin
   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

   Devin✓fullclaimed8/10

   Devin runs cloud sessions in isolated VMs (devin-docs-13) and provides an explicit CLI --sandbox flag enforcing OS-level isolation, writable path restrictions, deny rules, and optional network restriction (devin-docs-12, devin-docs-37), directly matching the sandboxed code/tool/network isolation story. Missing for 10: independent/hands-on verification of sandbox robustness and more detail on network isolation guarantees beyond docs claims.

   • [claimed-docs] “The --sandbox flag runs the CLI with OS-level isolation, enforcing writable paths and deny rules at the operating-system level and optionall…”
   • [claimed-docs] “The `--sandbox` flag runs the CLI with OS-level isolation, enforcing writable paths and `deny` rules at the operating-system level”
   • [claimed-docs] “The cloud session gets its own VM with a shell, browser, and full repo access, so it can keep going after you close your laptop.”
   • [claimed-docs] “Devin can connect to a VPN from inside its workspace, so sessions can reach internal services such as package registries, databases, and int…”

   proof ↗⚑ flag

Security checks

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

   weight 1 · round drawn
   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

   Devin—none0/10

   No evidence of license or public-code matching/attribution references for AI-suggested code anywhere in the docs; Devin Review covers correctness and best-practice conformance but nothing about license/provenance matching.

   ⚑ flag

2. developerGet contextual explanations and automatic fixes for security vulnerabilities

   weight 2 · round to Devin
   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

   Devin✓fullclaimed7/10

   Devin's docs describe Devin Review giving automated PR reviews with explanations for correctness/best-practice issues, Auto-Fix automatically responding to review comments and fixing flagged bugs/CI failures, and CI/CD integration to respond to findings from security scanners like SonarQube, Fortify, and Veracode — directly matching contextual explanation plus automatic fixing of vulnerabilities. Missing for 10: independent/hands-on evidence specifically validating security-vulnerability fixes (community evidence only discusses general reliability/scope-creep issues, not security-fix accuracy).

   • [claimed-docs] “Devin Review provides automated first-pass reviews on pull requests, checking for correctness and conformance with organizational best pract…”
   • [claimed-docs] “With Auto-Fix enabled, Devin automatically responds to code review comments, fixes flagged bugs, and iterates on CI failures — creating a cl…”
   • [claimed-docs] “Integrate Devin into your CI/CD pipeline to respond to findings from static analysis tools like SonarQube, Fortify, or Veracode.”
   • [claimed-docs] “Ask Devin can answer questions about code structure and dependencies, and help you scope and plan tasks before implementation.”

   proof ↗⚑ flag