The open source AI coding agent.
Important
OpenCode Classic is an unofficial Linux-focused fork that tracks upstream, defaults to the classic desktop layout, and keeps the redesigned layout available in Settings. Its releases and updater are maintained independently at LogicLyra/opencode-classic. Deeper content is inherited from upstream and may lag.
English | 简体中文 | 繁體中文 | 한국어 | Deutsch | Español | Français | Italiano | Dansk | 日本語 | Polski | Русский | Bosanski | العربية | Norsk | Português (Brasil) | ไทย | Türkçe | Українська | বাংলা | Ελληνικά | Tiếng Việt
OpenCode Classic Desktop uses a separate profile for its built-in server.
Settings > Chat import and the first-launch dialog offer Chats only
and Everything (full setup). The following chat-merge behavior applies to
Chats only:
On first launch, or under Settings > Chat import, choose Check default
OpenCode database or select a .db file. Close OpenCode first, review the
source, destination and counts, then choose Import eligible chats.
- The default source is
$XDG_DATA_HOME/opencode/opencode.db, normally~/.local/share/opencode/opencode.db. Choose a file for custom paths or development-channel databases. The destination is the active built-in desktop server's database under the Classic desktop profile'ssidecardirectory. Remote and experimental background-server connections are not supported by this importer. - The initial importer supports matching SQLite schemas and migration histories. It does not migrate source files or import legacy JSON storage. If compatibility checks fail, use compatible OpenCode and Classic versions and preview again.
- Completed local chats retain their IDs, titles, timestamps, messages, parts, v2 history, todos and original project paths. Existing chat IDs are skipped as a whole; re-importing does not update an already imported chat. The source is read-only, including its WAL history, and each import commits atomically.
- Chats with queued prompts, unfinished work or explicit workspace placement are excluded and counted. Importing never starts a prompt or runs a command. Credentials, account state, permission grants, project commands, share ownership, external attachments, Git snapshots and desktop drafts are not copied. Sign in separately and keep your project folders at their original paths. Historical undo snapshots are unavailable; embedded attachment data remains in the transcript, while external files must still exist.
- Open the original project folder in Classic to see its imported chats. This is a one-time copy, not ongoing synchronization between applications.
Close OpenCode and stop other writers first. Choose Preview default setup,
or Choose setup folders and select the OpenCode data, config, then
state folders. These normally reside at ~/.local/share/opencode,
~/.config/opencode, and ~/.local/state/opencode; XDG overrides are honored.
Review the counts, acknowledge that you trust the setup, confirm in the native
dialog, then restart Classic to activate the staged profile.
- Requires an empty Classic built-in Linux profile. Existing chats, providers, custom settings, accounts and registered projects are never overwritten. Generated default config/plugin files are recognized as bootstrap state.
- Copies all 19 application database tables, provider
auth.json, cloud accounts, integration credentials, permissions, share metadata, config files (including JSONC), agents, skills, plugins, state, plans, tool output, workspace files and snapshots. Pending prompts stay queued; import does not execute them. - External project paths stay unchanged on the same machine. Internal paths, permission patterns and snapshot keys are remapped. Linked worktrees receive private Git metadata, and snapshot object alternates are materialized so the copies do not depend on the original object stores.
- SQLite reads a private copy of the source DB/WAL. Source DB, WAL and shared-memory
files are left unchanged. Staging uses private permissions and a durable
ownership journal. Activation occurs before the built-in server starts and
recovers interrupted directory renames. The original empty/bootstrap profile
is retained under
.profile-import-retained-<operation-id>in Classic's desktop profile for inspection; it is not automatically deleted. - Credentials remain protected local files. Full setup also preserves executable behavior: account refresh, dependency installation, plugins, MCP connections, project commands, Git hooks/helpers and permission grants can take effect during normal use after activation. Only import a setup you trust. OAuth token rotation can require signing in again when both applications are used.
- Logs, caches and process locks are regenerated. System programs, shell environment variables, upstream desktop window/sidebar preferences and desktop drafts are not copied. External project files are already shared at their original paths. Open the original project folder to access its chats.
- Requires matching SQLite migration history and schema. Full setup currently
reads
opencode.db; environment-provided database/config/auth overrides must be removed before using it. Legacy JSON-only stores, cyclic or unsupported Git object references, device nodes, and profiles above 50 GiB or 500,000 inventory entries are refused with a specific reason. External symlinks are copied through (materialized); dangling links, sockets and fifos are skipped and counted in the summary. Configuration files up to 64 MB are supported. Additional disk space is required for staging. - Close OpenCode before importing. The preview warns when a running instance is detected, snapshot copies retry automatically, and a continuously written source reports a dedicated busy error asking you to close it.
The standalone Classic CLI still uses OpenCode's default XDG roots unless you
override them. Its uninstall command preserves data, credentials, configuration,
cache and state by default, including with --force. Deleting those shared roots
requires --remove-shared-data; --keep-data and --keep-config override that
request for their respective roots. Use uninstall --dry-run to review paths.
Upstream's own uninstall may still delete shared CLI data. The fork refuses to
open databases containing unknown migrations; update Classic rather than editing
or deleting a migration journal.
curl -fsSL https://github.com/LogicLyra/opencode-classic/releases/latest/download/install | bashWarning
The opencode-ai npm package and existing Homebrew, Scoop, Chocolatey, AUR, and Nix packages distribute upstream OpenCode, not OpenCode Classic.
OpenCode Classic desktop builds support Linux only and are available from the fork's releases page.
| Platform | Download |
|---|---|
| Linux x64 | opencode-classic-desktop-linux-* (.deb or .rpm) |
AppImage is intentionally not distributed. Ubuntu 24.04 and newer can force Electron AppImages to disable Chromium sandboxing under the default AppArmor policy; the installed deb and RPM formats retain the sandbox integration expected by the distribution.
Maintainers can reproduce the complete build, package, installed-deb, and visual release gate with the Linux VM release QA runbook.
The install script respects the following priority order for the installation path:
$OPENCODE_INSTALL_DIR- Custom installation directory$XDG_BIN_DIR- XDG Base Directory Specification compliant path$HOME/bin- Standard user binary directory (if it exists or can be created)$HOME/.opencode/bin- Default fallback
# Examples
OPENCODE_INSTALL_DIR=/usr/local/bin curl -fsSL https://github.com/LogicLyra/opencode-classic/releases/latest/download/install | bash
XDG_BIN_DIR=$HOME/.local/bin curl -fsSL https://github.com/LogicLyra/opencode-classic/releases/latest/download/install | bashOpenCode includes two built-in agents you can switch between with the Tab key.
- build - Default, full-access agent for development work
- plan - Read-only agent for analysis and code exploration
- Denies file edits by default
- Asks permission before running bash commands
- Ideal for exploring unfamiliar codebases or planning changes
Also included is a general subagent for complex searches and multistep tasks.
This is used internally and can be invoked using @general in messages.
Learn more about agents.
For more info on how to configure OpenCode, head over to our docs.
If you're interested in contributing to OpenCode, please read our contributing docs before submitting a pull request.
If you are working on a project that's related to OpenCode and is using "opencode" as part of its name, for example "opencode-dashboard" or "opencode-mobile", please add a note to your README to clarify that it is not built by the OpenCode team and is not affiliated with us in any way.