How to Install Devin CLI on Linux (Ubuntu, Debian, Fedora)

Quick answer: install Devin CLI on Linux in one line

# Official installer for macOS, Linux and WSL
curl -fsSL https://cli.devin.ai/install.sh | bash

# Verify the install
devin --version

# Start it inside a project
cd ~/my-project
devin

The commands in this guide come from the official Devin CLI installation page and the official command reference.

Requirements

• A 64-bit Linux on x64 (x86_64) or ARM64 (aarch64). The installer stops with "Unsupported platform" on any other architecture.
• Bash and curl, plus tar and sha256sum (or shasum). The installer uses them to download the release and check its checksum.
• A Devin account with CLI access. On Enterprise plans, your administrator has to give you a role with the "Use Devin CLI" permission.

What the installer puts on your system

Everything stays in your home folder, which is why no sudo is needed. To update later, run devin update. Add --force to reinstall the current version.

First run and logging in (also over SSH)

• The installer starts devin setup when it finishes. It walks you through login and MCP configuration. You can run it again at any time.
• To log in on its own, run devin auth login. It opens the browser sign-in.
• On a server or over SSH, where no browser can open, run devin auth login --force-manual-token-flow and paste the token by hand. devin setup --force-manual-token-flow does the same inside the wizard.
• Check the result with devin auth status. devin auth logout removes the stored credentials.

Enterprise users pick "Log in with Devin for Enterprise" to sign in through their company identity provider. See the official authentication page.

Common Linux errors and how to fix them

• "devin: command not found" after installing: ~/.local/bin is not on your PATH. Open a new terminal, or add export PATH="$HOME/.local/bin:$PATH" to your ~/.bashrc or ~/.zshrc.
• "Error: Unsupported platform": your machine is not x86_64 or aarch64. Check it with uname -m. 32-bit systems are not supported.
• "Cannot verify checksum (no sha256sum or shasum)": install coreutils (it provides sha256sum) from your package manager and run the installer again.
• "Failed to fetch manifest": the machine cannot reach Devin's download servers. Check your proxy or firewall and try again.
• Login never finishes over SSH: the browser flow cannot reach your server. Use --force-manual-token-flow as shown above.

For anything else, run devin doctor. It checks your local configuration and exits with an error if something is wrong.

Running several Devin sessions on Linux

With Devin working, the next limit shows up quickly: one terminal runs one task at a time. You give Devin a job and wait. Opening more tabs in GNOME Terminal or tmux helps, until you lose track of which session finished, which one is waiting for you and what each one changed.

CodeAgentSwarm is a desktop app for exactly that, and it now runs on Linux as a .deb (Ubuntu, Debian and derivatives) or an AppImage (Fedora and most other distros), for x64 and ARM64. On Linux it can install Devin CLI for you and launch it. It puts several agent terminals side by side, mixes Devin with Claude Code, Codex and other agents, and adds desktop notifications, searchable history across every session and a live diff of what each terminal changed.

Next steps: how to use Devin CLI for your first tasks, and Devin CLI MCP and history to resume conversations and add tools.

Conclusion

On Linux, Devin CLI is one curl command away and lives in your home folder. Use --force-manual-token-flow to log in over SSH, devin doctor when something looks off and devin update to stay current. When one terminal is not enough, CodeAgentSwarm lets you run several at once.