Model-neutral agent desktop/runtime for private, enterprise, and OpenAI-compatible / Anthropic-compatible model API. Tested on DeepSeek, Qwen, Kimi, GLM models. Supports MCP, Skills,and local code search.
See the codeDevo is an open-source coding agent with a Desktop app, terminal TUI/CLI, and model-neutral Rust runtime for private, enterprise, and OpenAI-compatible model environments. Connect DeepSeek, Qwen, Kimi, Anthropic-compatible APIs, local gateways, or your own model endpoint.
English | 简体中文 | 繁體中文 | 日本語 | Русский
Why Devo · Screenshots · Features · Tested Models · Tested Platforms · Install · Quick Start · Docs
Devo is for teams that need a coding agent outside a single hosted model ecosystem. It keeps the desktop experience, terminal workflow, model choice, runtime behavior, and workspace execution under your control.
devo mcp add|list|enable|disable|remove
(see Configuration).code_search / devo-code-search-mcp), not installed or enabled by
default. Runs a local CPU code-embedding model and combines dense retrieval
with BM25 keyword matching to reduce code-search context versus grep/find-only
agents. Install it explicitly with --with-code-search, then enable it with
devo mcp enable code_search or TUI /mcps.
Devo's built-in model catalog includes tested model definitions for Qwen, Kimi, MiniMax, GLM, and DeepSeek. Provider endpoints remain configurable through provider/model Connections.
Devo has been tested on macOS, Linux, Windows, and Kylin OS.
Kylin OS coverage is called out because domestic operating systems are often part of real deployment requirements in Chinese enterprise environments. HarmonyOS support is on the roadmap; contributors with HarmonyOS devices are welcome to build, test, and publish releases for that platform.
Devo can be installed in two forms. Pick the Desktop app for a graphical coding agent workspace, the terminal-native TUI/CLI for shell-first development, or install both on the same machine.
Start here if you want the graphical Devo experience. Download the latest Devo Desktop package from GitHub Releases, then choose the asset that matches your operating system and architecture:
devo-desktop-...-mac-... .dmg or .zip asset.devo-desktop-...-windows-... .exe asset.devo-desktop-...-linux-... .AppImage, .deb, or
.rpm asset.If macOS reports that Devo.app is damaged and cannot be opened, this is
expected. Current macOS Desktop builds are unsigned, so after installing,
run the following command so macOS can launch the app:
sudo xattr -dr com.apple.quarantine /Applications/Devo.app
Install the terminal-native devo command if you prefer the TUI, want shell
automation, or want to use Devo alongside the Desktop app.
Linux / macOS:
curl -fsSL https://raw.githubusercontent.com/7df-lab/devo/main/install.sh | sh
Windows:
irm 'https://raw.githubusercontent.com/7df-lab/devo/main/install.ps1' | iex
The online installer places devo under the Devo home directory and installs
the rg sidecar used for fast repository search. It does not install the
code_search MCP or its local model by default.
code_search MCP and local modelUse this only if you want the code-search MCP and its Hugging Face model installed during setup.
Linux / macOS:
curl -fsSL https://raw.githubusercontent.com/7df-lab/devo/main/install.sh | sh -s -- --with-code-search
Windows:
$env:DEVO_INSTALL_CODE_SEARCH = "1"; irm 'https://raw.githubusercontent.com/7df-lab/devo/main/install.ps1' | iex
Upgrade an existing installation to the latest release:
devo upgrade
The upgrade command runs the same platform installer, and the installer prints
the version transition, for example Version: v0.1.12 -> v0.1.15.
For air-gapped or intranet installs, see Offline Installation.
Configure a provider, open a repository, and start the TUI:
cd /path/to/your/repo
devo onboard
Useful commands:
devo # start the interactive TUI in the current repo
devo resume <session-id>
devo onboard is the recommended setup path. It writes provider Connections
and model directories to providers.json and stores your API key in
user-scoped auth.json.
To bring your own key with a custom model manually:
provider.<id>.models.<model-id> entry in providers.json and set
the active model as provider/model.DEVO_HOME/auth.json and reference that credential id from
provider.<id>.credential — never put the API key itself in providers.json.wire_api to match the endpoint protocol:
openai_chat_completions, openai_responses, or anthropic_messages.Full worked example (custom model parameters + API key) and protocol details: Configuration.
Provider responses are not subject to an application-level response timeout, so local models may take as long as necessary to load or generate output. Provider connections still have an internal connection-establishment deadline, and every request can be cancelled by the user.
Devo is pre-1.0 and actively developed. It is ready for local evaluation, experiments, and contributor use; public APIs and configuration may still change.
Built-in model metadata currently covers Qwen, Kimi, MiniMax, GLM, and DeepSeek families. Any model endpoint that supports OpenAI-compatible Chat Completions, OpenAI-compatible Responses, or the Anthropic Messages API can be connected through provider/model Connections.
Use devo onboard, or manually define a custom provider/model in
providers.json, store the key in user-scoped auth.json, and set
wire_api to openai_chat_completions, openai_responses, or
anthropic_messages. See
Configuration.
Use the Desktop app when you want visual onboarding, session browsing, and a graphical coding workspace. Use the TUI/CLI when you want terminal-native automation, remote shell workflows, or a coding agent that stays inside your existing command-line setup. Both surfaces target the same local Devo runtime.
Contributions are welcome while the project is still early:
Open an issue or pull request to discuss changes.
This project is licensed under the MIT License.
If you find Devo useful, please consider giving it a star.
Rust
76.6%
TypeScript
20.1%
MDX
1.9%
Model-neutral agent desktop/runtime for private, enterprise, and OpenAI-compatible / Anthropic-compatible model API. Tested on DeepSeek, Qwen, Kimi, GLM models. Supports MCP, Skills,and local code search.
See the codeDevo is an open-source coding agent with a Desktop app, terminal TUI/CLI, and model-neutral Rust runtime for private, enterprise, and OpenAI-compatible model environments. Connect DeepSeek, Qwen, Kimi, Anthropic-compatible APIs, local gateways, or your own model endpoint.
English | 简体中文 | 繁體中文 | 日本語 | Русский
Why Devo · Screenshots · Features · Tested Models · Tested Platforms · Install · Quick Start · Docs
Devo is for teams that need a coding agent outside a single hosted model ecosystem. It keeps the desktop experience, terminal workflow, model choice, runtime behavior, and workspace execution under your control.
devo mcp add|list|enable|disable|remove
(see Configuration).code_search / devo-code-search-mcp), not installed or enabled by
default. Runs a local CPU code-embedding model and combines dense retrieval
with BM25 keyword matching to reduce code-search context versus grep/find-only
agents. Install it explicitly with --with-code-search, then enable it with
devo mcp enable code_search or TUI /mcps.
Devo's built-in model catalog includes tested model definitions for Qwen, Kimi, MiniMax, GLM, and DeepSeek. Provider endpoints remain configurable through provider/model Connections.
Devo has been tested on macOS, Linux, Windows, and Kylin OS.
Kylin OS coverage is called out because domestic operating systems are often part of real deployment requirements in Chinese enterprise environments. HarmonyOS support is on the roadmap; contributors with HarmonyOS devices are welcome to build, test, and publish releases for that platform.
Devo can be installed in two forms. Pick the Desktop app for a graphical coding agent workspace, the terminal-native TUI/CLI for shell-first development, or install both on the same machine.
Start here if you want the graphical Devo experience. Download the latest Devo Desktop package from GitHub Releases, then choose the asset that matches your operating system and architecture:
devo-desktop-...-mac-... .dmg or .zip asset.devo-desktop-...-windows-... .exe asset.devo-desktop-...-linux-... .AppImage, .deb, or
.rpm asset.If macOS reports that Devo.app is damaged and cannot be opened, this is
expected. Current macOS Desktop builds are unsigned, so after installing,
run the following command so macOS can launch the app:
sudo xattr -dr com.apple.quarantine /Applications/Devo.app
Install the terminal-native devo command if you prefer the TUI, want shell
automation, or want to use Devo alongside the Desktop app.
Linux / macOS:
curl -fsSL https://raw.githubusercontent.com/7df-lab/devo/main/install.sh | sh
Windows:
irm 'https://raw.githubusercontent.com/7df-lab/devo/main/install.ps1' | iex
The online installer places devo under the Devo home directory and installs
the rg sidecar used for fast repository search. It does not install the
code_search MCP or its local model by default.
code_search MCP and local modelUse this only if you want the code-search MCP and its Hugging Face model installed during setup.
Linux / macOS:
curl -fsSL https://raw.githubusercontent.com/7df-lab/devo/main/install.sh | sh -s -- --with-code-search
Windows:
$env:DEVO_INSTALL_CODE_SEARCH = "1"; irm 'https://raw.githubusercontent.com/7df-lab/devo/main/install.ps1' | iex
Upgrade an existing installation to the latest release:
devo upgrade
The upgrade command runs the same platform installer, and the installer prints
the version transition, for example Version: v0.1.12 -> v0.1.15.
For air-gapped or intranet installs, see Offline Installation.
Configure a provider, open a repository, and start the TUI:
cd /path/to/your/repo
devo onboard
Useful commands:
devo # start the interactive TUI in the current repo
devo resume <session-id>
devo onboard is the recommended setup path. It writes provider Connections
and model directories to providers.json and stores your API key in
user-scoped auth.json.
To bring your own key with a custom model manually:
provider.<id>.models.<model-id> entry in providers.json and set
the active model as provider/model.DEVO_HOME/auth.json and reference that credential id from
provider.<id>.credential — never put the API key itself in providers.json.wire_api to match the endpoint protocol:
openai_chat_completions, openai_responses, or anthropic_messages.Full worked example (custom model parameters + API key) and protocol details: Configuration.
Provider responses are not subject to an application-level response timeout, so local models may take as long as necessary to load or generate output. Provider connections still have an internal connection-establishment deadline, and every request can be cancelled by the user.
Devo is pre-1.0 and actively developed. It is ready for local evaluation, experiments, and contributor use; public APIs and configuration may still change.
Built-in model metadata currently covers Qwen, Kimi, MiniMax, GLM, and DeepSeek families. Any model endpoint that supports OpenAI-compatible Chat Completions, OpenAI-compatible Responses, or the Anthropic Messages API can be connected through provider/model Connections.
Use devo onboard, or manually define a custom provider/model in
providers.json, store the key in user-scoped auth.json, and set
wire_api to openai_chat_completions, openai_responses, or
anthropic_messages. See
Configuration.
Use the Desktop app when you want visual onboarding, session browsing, and a graphical coding workspace. Use the TUI/CLI when you want terminal-native automation, remote shell workflows, or a coding agent that stays inside your existing command-line setup. Both surfaces target the same local Devo runtime.
Contributions are welcome while the project is still early:
Open an issue or pull request to discuss changes.
This project is licensed under the MIT License.
If you find Devo useful, please consider giving it a star.
Rust
76.6%
TypeScript
20.1%
MDX
1.9%