mrkeyoor.comAsk

opencode-ai/opencodetested 13 Oct 2026commit 73ee493

opencode review

OpenCode's archived Go checkout installed in 111 seconds and built in 72 seconds in our sandbox, then its test command failed.

  • README install 99 s
  • README usage failed
6/9passed, run exited non-zero
  • Install 111 s
  • Build 72 s
LLM Toolsevaluationupdated 17 Nov 2026
+11stars / 7d

OpenCode, specifically opencode-ai/opencode, is an archived Go assistant that lets a model search files, change code and run commands from a terminal. Its README points ongoing development to Crush; Anomaly's similarly named OpenCode is a separate product.

Verdict

OpenCode's archived Go checkout installed in 111 seconds and built in 72 seconds in our sandbox, then its test command failed. Use it to investigate an existing installation or study its tools; skip it for a new production coding workflow. Evaluate Crush first for the continuation named by the original project, and keep Anomaly's modern OpenCode documentation separate.

opencode infographic: search files, change code and run commands from a terminal, plus our test result and who it suits
Tested 17 November 2026: the README command failed. Before that: 13 Oct: 6 of 9 source tests passed; go install took 99 s.

We ran it

Lab card: what happened when we ran opencode
Lab card from our sandbox run
Screenshot of opencode (github.com/opencode-ai/opencode)
github.com/opencode-ai/opencode
Install✓ · 111s228 packages
Build✓ · 72s
Tests✗ · 16s6 passed · 3 failed of 9 (go test)
Repo162 files~42,357 lines of source · 1.4 MB · 2 CI workflows

Answers from our run

Does opencode build from source?

Dependencies installed in 111 seconds (228 packages), and the build succeeded in 72 seconds. We cloned commit 73ee493 into a clean Debian container with 3 CPUs and no project-specific setup.

Do opencode's tests pass?

No. The project's own test command finished in 16 seconds and reported 6 passed, 3 failed (go test).

Who should not use opencode?

New production deployments: the repository is archived and its README warns that it is not ready for production use.

What are the alternatives to opencode?

Crush, Claude Code, OpenHands. OpenCode's archived Go checkout installed in 111 seconds and built in 72 seconds in our sandbox, then its test command failed.

Setup4/5In our 2026-11-17 run it installed as the README says in 99 s and its command responded; the README gave no task we could run as written.Editor’s note: Source installation and build succeeded, but the CLI quickstart stopped before an authenticated coding task; complete user setup was not assessed.
Docs4/5The README has an install section (“Installation”) and a usage section (“Usage”); we did not run its quickstart ourselves.Editor’s note: The README documents configuration and permissions, but the quickstart recipe disagreed with its usage examples; documentation usability was not scored.
Community1/5The repository is archived, last push on 2025-09-18, 13,908 stars and maintainers answered or closed 9 of the 10 most-discussed issues we sampled.Editor’s note: The sampled issues contain maintainer replies and user workarounds, while this repository is archived; current support capacity was not assessed.
Maturity1/5Latest release v0.0.55 on 2025-06-27 (pre-1.0), repository created 2025-03-16 and its test suite did not pass in our sandbox (6 of 9 passed).Editor’s note: The README warns against production use and the source test command failed; production reliability and security were not assessed.

How we score

Discussed on

  1. hnOpencode: AI coding agent, built for the terminal319 points
  2. hnOpencode – AI coding agent, built for the terminal6 points
  3. hnopencode - AI coding agent built for the terminal4 points
  4. hnOpenCode AI coding agent hit by critical unauthenticated RCE vulnerability3 points
  5. hnOpencode: AI coding agent, built for the terminal3 points

Who it’s for

Existing users inspecting configuration and saved sessions before evaluating Crush.
Go developers studying terminal interfaces, provider adapters and coding-agent tools.
Developers reproducing the specific file-search or instruction-following reports in this archive.

Who it’s NOT for

New production deployments: the repository is archived and its README warns that it is not ready for production use.
Scripts that depend on an approval prompt before shell commands or file changes: non-interactive mode auto-approves permissions.
Users seeking Anomaly OpenCode Go, Zen or Browse: those product records describe a different application.

Setup reality

Our October 13, 2026 sandbox run at commit 73ee493 installed successfully in 111 seconds with 228 dependencies and built in 72 seconds. Tests exited 1 after 16 seconds; the recorded Go summary reports 6 passed and 3 failed of 9. The retained tail names TestLsTool_Run in internal/llm/tools without showing its cause.

The README documents provider keys, .opencode.json, external language-server commands and MCP connections. Our November 17 quickstart reached version and help output, then the recipe stopped at its usage step. It reported finding no runnable example, although the current README contains usage commands.

The October sandbox configuration lists 3 CPUs, 8 GB RAM and image golang:1.24-bookworm. The image label does not identify the actual runtime version. The November quickstart warned that Ripgrep and FZF were missing from PATH. The archive notice directs new development to Crush.

OpenCode's archived Go repository installed and built in our sandbox, then its test command failed. Use this checkout to investigate an existing installation or study its tools; skip it for a new production coding workflow. Its own README directs ongoing development to Crush. Modern OpenCode Go, Zen and Browse coverage belongs to a separate product identity, so choosing the repository comes before choosing a model.

This OpenCode is archived and points to Crush

The opencode-ai/opencode README says the repository is no longer maintained and identifies Crush as its continuation. That changes the recommendation more than any feature comparison: a new user should evaluate the continuation before spending time repairing this archive. An existing user has a different job, preserving configuration and sessions while deciding what to replace. OpenCode README

GitHub's public metadata fetched on November 17, 2026 lists Go, an archived repository and a last push on September 18, 2025. The latest release endpoint returns v0.0.55, dated June 27, 2025. The archive notice, dated push and issue reports together describe the maintenance boundary. An old release tag alone would be a weaker reason to walk away. Repository history and archive · Release record

Name you encounter What it identifies Where to start
opencode-ai/opencode The archived Go terminal assistant reviewed here Its README and the Crush continuation notice
Anomaly's OpenCode The separate product identified as anomalyco/opencode in Design for AI's comparison Its own repository and version-specific documentation
sst/opencode The other repository named by a commenter correcting their advice in issue #164 Check the repository before copying the comment's configuration
openCode.de A platform presenting public-sector digital-sovereignty use cases Its platform documentation
Alibaba Open Code Review A separately named code-review CLI alibaba/open-code-review

The distinction is visible inside the support record itself. In issue #164, sameepvicky retracts advice meant for sst/opencode. The public-sector platform and Alibaba tool have their own use-case page and repository description. Searching “opencode ai” or “opencode github” without an owner name can lead you to instructions for a different application.

What people use opencode for

Users of this Go project report working local-model connections and a useful tool rewrite, alongside unreliable compliance with standing instructions. Those are more useful adoption signals than a feature inventory because each report names a task and an outcome.

Who used it What they did What happened
isaac-scarrott, issue #55 Used OpenCode to replace its glob implementation with ripgrep Reported that hanging improved; explicitly left the working-directory bug for separate work. Report
Mathematical-Methods, issue #164 Connected Ollama through an OpenAI-compatible endpoint ending in /v1 Reported success after a maintainer pointed to merged PR #155, while saying broader feature testing was incomplete. Report
possibilities, issue #90 Added standing instructions asking Sonnet to consult Context7 MCP Logging showed the instructions reached the model, but longer rule files still failed to trigger the tool reliably. Report

The glob story is particularly useful. The reporter already had ripgrep installed. A maintainer initially discussed grep, then corrected that misunderstanding: ripgrep was used by grep, not glob. The reporter built a replacement inspired by grep.go and described an improvement. Simply telling every affected user to install ripgrep would miss what this thread actually says.

The modern ecosystem has different examples. In a Reddit hobby-app discussion, pendelhaven describes free models implementing changes and DeepSeek through OpenRouter, together with Free Zen, reviewing them. They say it works with slower progress than paid models. In the supplied desktop setup video, whose extract does not name the channel, the presenter shows a worktree with a separate folder and branch. The presenter also shows an added OpenCode Marimo plugin. These examples explain interest in the modern product; they are not outcomes from this archived binary.

What happened when we ran it

Our November 17, 2026 quickstart run reached v0.0.55 version and help output, then stopped at a failed usage step. It used commit 73ee493265ac in a fresh unprivileged container configured with 2 CPUs, 4 GB RAM, no published ports and no secrets. The recorded image was golang:1.24-bookworm.

Quickstart step Recorded outcome What the result means
Clone Completed The quickstart recipe obtained the source.
Install route The record names go install github.com/opencode-ai/opencode@latest This was the Go route from the repository README.
Version Exit 0, v0.0.55; warnings that Ripgrep and FZF were absent from PATH The binary responded, with optional-tool warnings.
Help Exit 0; the same Ripgrep and FZF warnings Help output worked.
Usage FAILED: recipe reported no runnable opencode command in the README's usage/examples sections The recipe stopped before a coding task.
Teardown ok Cleanup completed.

The usage result needs care. The recipe reports that it found no runnable command, yet the current README visibly contains opencode and prompt-mode examples. That is a discrepancy between the recipe result and the document, rather than proof that OpenCode cannot accept a task. A version response and a help screen leave a reader short of seeing an agent inspect files, make a change and explain it.

Our harness recorded installation, build and tests as separate steps, retaining the exit status and log tail for each. The October 13, 2026 source run used commit 73ee493, with 3 CPUs and 8 GB RAM under the same image label. Installation succeeded in 111 seconds, and the build succeeded in 72 seconds. Tests exited 1 after 16 seconds. The supplied Go test summary reports 6 passed and 3 failed out of 9; treat that as the recorded summary, rather than an independently reconciled count of individual test cases.

October source check Result from our sandbox
Install Succeeded in 111 seconds; 228 dependencies recorded
Build Succeeded in 72 seconds
Tests Failed, exit 1, in 16 seconds; recorded summary: 6 passed, 3 failed of 9
Source scan 162 files, about 42,357 source lines, 1.4 MB checkout
Repository signals 2 CI workflow files; no Dockerfile and no tests directory detected

The retained tail names TestLsTool_Run and marks internal/llm/tools as failing. It also shows passing prompt, dialog and theme packages, plus packages with no test files. A missing tests directory therefore does not mean there are no tests. The excerpt does not explain the failure's cause or account for every failure in the aggregate. Neither the container image label nor the failed command identifies the actual runtime version or proves that a live coding session is broken.

Where people get stuck: keys, model names and rules

Issue #119 reports first-launch failures on v0.0.46, and the sampled issues show startup errors including “agent coder not found” and provider-validation failures. Use the error and the repository identity together when choosing a workaround. The support threads themselves contain advice that switches applications.

Symptom and source What the thread supports Status in the supplied record
“agent coder not found,” #119 and #298 Infinnerty and connor-k-smith report recovery after setting or resetting API keys. Other users still report the error. #119 · #298 Open; npm or opencode.ai reinstall advice can refer to another product
Provider validation rejects a model, #182 A maintainer supplies internal model identifiers; GratefulDave reports success after correcting configuration and enabling models. #182 Workaround for that report; other provider cases continue
Context7 instruction ignored, #90 Pasting the instruction into the session worked for the reporter. They reproduced the problem after PR #86 changed the prompts. #90 Closed, with continuing failure in the discussion
Custom provider URL needed, #183 Users ask for LiteLLM and third-party Anthropic endpoints; one LOCAL_ENDPOINT attempt panics. #183 Open; a maintainer discusses later configuration work
tmux hotkey conflict, #89 Contributors discuss configurable remapping and a PR. #89 Open; the extract stops short of a merged solution

For an existing installation, start with the archive's own configuration structure: .opencode.json, provider entries and agent model identifiers. In #182, the maintainer explicitly says the raw API model name is not used. That makes copying a provider's model string into an agent entry a poor shortcut. Keep coder, task and title configuration aligned with the version you actually run, and keep credentials out of shared troubleshooting output.

Large projects expose file-search and instruction problems

Issue #90 reports that a Context7 instruction worked alone but failed in a 32-line rule file; issue #55 reports glob hanging on a large project. These are specific reports worth reproducing with your own repository. Neither gives a universal file-count threshold or an accuracy score.

For file search, isaac-scarrott also reports that glob ignores the requested working directory and describes copying the binary into the desired directory as a workaround. Their ripgrep rewrite addressed hanging while leaving that directory bug separate. For standing instructions, possibilities checked the outgoing content with logging, so “the file was never loaded” is a poor explanation for that particular report. Shortening or repeating a rule helped their workflow, but the thread's closure should not be read as a durable fix. Glob report · Instruction report

If your decision depends on a large monorepo or a long team rule file, use those as acceptance tasks. Ask for a file outside the current folder and require a specific documentation lookup before an edit. Check the selected files and actual tool calls. A model saying that it followed a rule is weaker evidence than seeing the call in the session.

Scripted mode approves permissions automatically

The archived README says all permissions are auto-approved for a non-interactive prompt session. Because its documented tools include shell execution and file writes, invoking the CLI from a script changes the approval boundary. Run an evaluation in a disposable checkout with only the access needed for that task. Prompt-mode documentation

The separate opencode-reviewer project documents loading configuration after checking out the target branch, including review prompts and optional tool files. My recommendation for such an integration is to treat branch-controlled instructions as untrusted input and keep publishing credentials outside the review execution environment. That follows from where the integration loads its files; it is not a reported exploit or a vulnerability finding against this Go archive. Integration configuration

Anomaly's tools documentation describes host-user shell authority and browser operations without individual permission prompts. Those defaults belong to that documented product. The Go archive separately documents SQLite storage for conversations and sessions. “Runs locally” should prompt a storage and permissions check, rather than being treated as a promise that nothing is retained. Modern tool permissions · Archive storage

OpenCode Go, Zen and free models belong to the modern product

OpenCode Go is listed at $10 per month in the supplied Anomaly documentation; it is a model-access subscription, separate from this repository's Go implementation. The November 17 source snapshot lists it at $10 per month. OpenCode Zen is described in Design for AI's comparison as the team's pay-as-you-go gateway. The modern homepage also offers free models and existing-subscription connections. Go documentation · Zen description · Homepage

OpenCode free models should not be budgeted as a guarantee of uninterrupted access. In the Hy4 Flash discussion, Yann27 reports exhausting daily free messages while Agile_Rain4486 reports hours of continuous use. These conflicting experiences matter more to a hobby developer than the promotion's wording. Keep the dated promotion separate from a recurring quota promise, and keep both separate from the archive's provider configuration. Free-model reports

OpenCode vs Claude Code, Crush and OpenHands

Crush is the first alternative to evaluate for a new workflow because the archived project's own README names it as the continuation. Its README documents multiple model providers, session switching, LSP context and MCP connections. That is a concrete reason to start there before choosing an unrelated agent. Crush README

Choice Evidence for considering it Pick it when
Crush The archive names it as the continuation; Crush documents provider choice and MCP You want to evaluate the continuation of this project's terminal workflow
Claude Code Anthropic's README describes terminal coding, explanations and Git workflows; Design for AI compares it with Anomaly's OpenCode You want Anthropic's terminal-agent workflow; judge its access terms separately
OpenHands The OpenHands team's comparison positions its product around scheduled and governed agent work You need to evaluate unattended workflows across repositories
Archived opencode-ai/opencode Our checkout built; the README says maintenance moved You need to inspect or preserve an existing installation

The OpenCode vs Claude Code comparison in this pack concerns Anomaly's product, so its provider and interface advantages cannot be transferred to this archive. OpenHands' comparison is written by a competitor. Its interactive-versus-automation distinction is useful positioning, but the separate opencode-reviewer integration shows that OpenCode-based automation exists too. Design for AI comparison · OpenHands comparison · Review integration · Claude Code README

For “opencode vs pi,” the supplied records offer no controlled winner. Choose the workflow you need to compare, hold the model and task constant where possible, then inspect the resulting changes. Provider throughput anecdotes answer a different question from whether an agent produces a correct patch.

What the other reviews get wrong

Design for AI identifies the modern product as Anomaly's OpenCode, while issue #164 explicitly separates the older repositories. Applying modern opencode.ai instructions to opencode-ai/opencode erases a distinction that has already confused people seeking help. Keep the repository owner in every installation note. Comparison identity · Corrected comment

Design for AI also says OpenCode lacks built-in browser tools. The supplied modern tools documentation describes a browser namespace attached through the desktop app. The official November 16 Browse announcement says its Rust rewrite removed Playwright. OpenCode Browse therefore needs a product and version label, and an older Playwright description should not stand in for that announcement. Tools documentation · Official announcement record

The OpenHands comparison's bring-your-own-key pricing description omits the optional Go subscription shown in the official documentation. Its statement about not storing code or context also needs a distinction between hosted retention and local state: the modern troubleshooting documentation describes local application data. Finally, the official October 30 account post announces Claude subscription availability. That dates blanket availability advice in older comparisons; it is not a substitute for contractual terms. Go · Troubleshooting · Subscription announcement

Questions people ask

OpenCode here means opencode-ai/opencode, the archived Go terminal assistant whose README directs ongoing development to Crush. The owner name resolves the most consequential setup question before you copy a command. Archive notice

Which OpenCode repository does this review cover, and how does it relate to sst/opencode or anomalyco/opencode?

This page covers opencode-ai/opencode. Issue #164 distinguishes it from sst/opencode, and the supplied comparison identifies Anomaly's product as anomalyco/opencode. Use the corresponding documentation for each. Issue #164 · Product identity

What is OpenCode, and what does it actually do?

The archived project is a Go terminal assistant with tools to search files, edit code and execute commands, plus saved conversations. Those are documented capabilities; our recorded quickstart reached help output before its usage step stopped. Archive README · Quickstart outcome

How do I install OpenCode and choose the right major version?

For this archive, the README lists go install github.com/opencode-ai/opencode@latest. Anomaly's similarly named versions use separate documentation and can replace the shared opencode binary. Resolve the repository and version before following an opencode install guide. Archive README · Version distinction

How do I use OpenCode from beginner setup through more advanced workflows?

The archive documents Ctrl+O for its model-selection dialog, launching opencode in a project, custom Markdown commands and MCP configuration. Begin with an explanation-only task in a disposable checkout before permitting edits. Non-interactive prompt mode auto-approves permissions. Usage and commands

How do I update OpenCode?

The archive's README points ongoing development to Crush. Reinstalling the archived application and moving to Crush are separate decisions. Preserve the old configuration and sessions before evaluating a replacement, and use its own instructions. Continuation notice

How do I configure an API key for OpenCode?

The archive documents provider-specific environment variables, including ANTHROPIC_API_KEY, OPENAI_API_KEY and GEMINI_API_KEY, along with provider entries in .opencode.json. An opencode api key question needs the provider and repository name: modern gateway sign-in instructions describe a different configuration. Configuration

Why does OpenCode say 'agent coder not found' on first launch?

Issue #119 includes users who recovered after setting or resetting API-key environment variables. Issue #298 includes continuing failures, even after keys were added. Both extracts are open, and reinstall suggestions sometimes switch to a different OpenCode distribution. #119 · #298

How do I connect OpenCode to a local Ollama model?

Issue #164 includes a successful user report using Ollama's OpenAI-compatible endpoint with /v1 after PR #155 merged. The archive README documents LOCAL_ENDPOINT. Keep that report separate from the later commenter's retracted sst/opencode configuration. Ollama report · Endpoint variable

Can I configure multiple Ollama endpoints for different machines?

In issue #164, yordis asks for multiple endpoints because they use different machines. The supplied thread contains a request rather than a demonstrated multi-endpoint configuration. Endpoint request

How do I configure a custom base URL or LiteLLM proxy?

Issue #183 contains that request and a reported panic after a LOCAL_ENDPOINT attempt. The maintainer discusses improving configuration after a refactor; the extract provides no confirmed fix to copy. Custom URL discussion

Why does provider validation reject my Gemini, OpenRouter or local model?

Issue #182 shows that the archive uses internal model identifiers rather than raw provider API names. GratefulDave reports success after changing the configuration and enabling models; the thread also contains unresolved reports for other providers. Provider validation

Is there a reliable way to use GitHub Copilot with OpenCode?

Issue #270 reports a Copilot attempt failing with “base url is not set.” The archive README documents a Copilot configuration path, but that issue prevents treating the documented path as universal evidence of success. Copilot report · Archive README

What we have not tested yet

Our evidence covers source checks and a CLI quickstart, not a completed coding assignment. We did not authenticate a provider, measure patch correctness, price a completed task, compare agents on the same workload or test migration to Crush. The November recipe stopped before a real task, so there are no known-answer results, coding latency measurements or application screenshots to show.

The October test tail gives a named failing test and package, but no supported root-cause diagnosis. Raw toolchain logs would be needed to establish actual runtime versions and reconcile the aggregate test summary. The later quickstart used a different resource configuration, so it should not be treated as a repeat of the October source harness.

Modern free-model quota allocation, provider-speed comparisons and subscription terms remain outside our measured results. So do the Browse announcement's memory and size claims. We have no independent security result for branch-loaded review tools, the archive's permission enforcement or hosted retention. The video extract lacks channel identification and a completed application outcome. Search intents indicate questions, not measured search volume or adoption.

For an existing installation, the next useful artifact is a list of the configuration, saved sessions and external tools you depend on. Evaluate the continuation against that list in a separate checkout before replacing the old workflow.

Alternatives

ProjectWhat it isPick it when
Crush gh↗The continuation named in this archive's README, with multiple model providers, LSP context and MCP support documented in its own README.Evaluate it first when you want the continuation of this project's terminal workflow.
Claude Code gh↗Anthropic's coding tool for terminal tasks, code explanations and Git workflows.Choose it for evaluation when you want Anthropic's terminal-agent workflow and its access options fit your account.
OpenHandsAn agent platform whose team's comparison emphasizes scheduled and governed workflows.Evaluate it when unattended work across repositories matters more than preserving this archived terminal setup.

What people are saying

  1. [github-trending] opencode-ai/opencode
  2. [techcrunch-ai] Hackers hit AI coding tool OpenCode, running up charges on users’ AI accounts

Sources

  1. OpenCode archive README
  2. Crush README
  3. Claude Code README
  4. OpenCode release v0.0.55

More llm tools reviews