Devin CLI on Windows: native install and troubleshooting
By CodeAgentSwarm · Updated September 11, 2026
Install from PowerShell
Open PowerShell and run the official installer. Reopen your terminal afterwards. Cognition installation instructions.
irm https://static.devin.ai/cli/setup.ps1 | iex
devin --versionDevin running in the Windows beta
If Windows cannot find devin
Get-Command devin -All
where.exe devinIf these return no result, close and reopen the terminal after installation. If the terminal finds Devin but CodeAgentSwarm does not, reopen CodeAgentSwarm too. A process opened before the installer can keep its earlier PATH.
If multiple executables appear, compare their paths and versions. In our native Windows verification, installer discovery and process execution were checked separately: detecting a file is only useful if that executable can actually start.
Connect the account and open a Windows project
devin auth login
devin auth status
Set-Location C:\Projects\sample-app
devinUse your actual project path. In CodeAgentSwarm beta, select that same project when creating a Devin session. If you authenticated inside WSL, repeat the login in the native Windows CLI before expecting the native app to use it.
Find the actual configuration and history files
| Data | Native Windows location |
|---|---|
| Configuration | %APPDATA%\devin |
| History | %APPDATA%\devin\cli\sessions.db |
These are the locations verified with our native Windows installation. The executable can be installed under Local while Devin keeps its account and session data under Roaming. CodeAgentSwarm beta resolves these locations separately.
Do not move account files between those folders to fix discovery. Verify the CLI version and the actual environment first. For additional MCP files and scopes, see MCP and history.
Check the complete workflow
- Ask Devin to read a known file and verify the answer.
- Close the conversation and find it in history.
- Resume it and ask a question about the previous turn.
- Check the selected model and account quota before a longer task.
The getting started guide includes a small first prompt. The quota guide explains why a valid installation can still encounter an account limit.
Devin in CodeAgentSwarm: beta status
The integration is being tested for an upcoming CodeAgentSwarm release. The screenshots show that beta, not a promise that the current public installer already includes Devin. Sign in with the official Devin CLI on the computer that runs the agent.
FAQ
The official CLI provides a native Windows installer. WSL is an alternative environment, not a requirement for the native installation.
Check Get-Command devin -All and reopen the terminal and app after installation. They may still have the PATH from before the install.
Our native installation stored sessions under %APPDATA%\devin\cli\sessions.db, separately from configuration in %APPDATA%\devin.
Devin Chat, installation and history are in CodeAgentSwarm beta testing for an upcoming release. The button downloads the current public app; check its release notes for Devin availability.