---
title: "Troubleshooting"
description: "Common issues and how to fix them"
icon: "wrench"
---

## Installation Issues

<AccordionGroup>
  <Accordion title="Install command fails (macOS / Linux / WSL)">
    If the install script fails to download:

    1. Check your internet connection
    2. Verify curl is installed: `which curl`
    3. Try with verbose output: `curl -fsSL -v https://cli.devin.ai/install.sh | bash`

    If you're behind a corporate proxy, you may need to configure proxy settings:
    ```bash
    export https_proxy=http://your-proxy:port
    curl -fsSL https://cli.devin.ai/install.sh | bash
    ```
  </Accordion>

  <Accordion title="Install command fails (Windows)">
    If the PowerShell install script fails:

    1. Check your internet connection
    2. Ensure you are running PowerShell as a regular user (not as Administrator unless necessary)
    3. If you see an execution policy error, try:
       ```powershell
       Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned
       irm https://static.devin.ai/cli/setup.ps1 | iex
       ```
    4. If you're behind a corporate proxy, configure proxy settings in PowerShell before running the install command

    As an alternative to the PowerShell script, you can download and run the standalone installer directly:
    - [x86_64](https://static.devin.ai/cli/devin-updater-x86_64-pc-windows.exe)
    - [ARM64](https://static.devin.ai/cli/devin-updater-aarch64-pc-windows.exe)
  </Accordion>

  <Accordion title="Permission denied during install">
    The installer needs write access to install the binary. If you see permission errors:

    1. Check the install location has write permissions
    2. Do not run the installer with `sudo` — this can cause ownership issues
    3. If installing to a system directory, ensure your user has appropriate permissions
  </Accordion>

  <Accordion title="Binary not found after install">
    If the install completes but `devin` isn't found:

    **macOS / Linux / WSL:**
    1. Restart your terminal or run `source ~/.bashrc` (or `~/.zshrc`)
    2. Check if the binary location is in your PATH: `echo $PATH`
    3. Verify the binary exists: `ls -la ~/.local/bin/devin` (or the install location shown during setup)

    **Windows:**
    1. Restart your PowerShell session
    2. Check if the binary location is in your PATH: `$env:PATH -split ';'`
    3. Verify the binary exists in the install location shown during setup
  </Accordion>

  <Accordion title="'irm' or 'iex' command not found (Windows)">
    `irm` and `iex` are PowerShell aliases. If you see this error, you're running the install command in Git Bash or CMD instead of PowerShell.

    **Fix:** Open **PowerShell** and run the install command there:
    ```powershell
    irm https://static.devin.ai/cli/setup.ps1 | iex
    ```

    Alternatively, from Git Bash or CMD you can invoke PowerShell explicitly:
    ```bash
    powershell -Command "irm https://cli.devin.ai/install.ps1 | iex"
    ```

    After installation, you can use Devin CLI from **PowerShell**, **Windows Terminal**, or **Git Bash**.
  </Accordion>
</AccordionGroup>

---

## Authentication Issues

<AccordionGroup>
  <Accordion title="Login fails or times out">
    If browser-based login doesn't work:

    1. Try the manual token flow for remote/SSH sessions:
       ```bash
       devin auth login --force-manual-token-flow
       ```
    2. Check that your browser can reach the authentication URL
    3. Verify your enterprise account has Devin CLI access enabled
  </Accordion>

  <Accordion title="'Not authorized' or permission errors">
    If you see authorization errors after logging in:

    1. Verify your account has the the correct permission needed to access Devin CLI. You may need to ask your admin. For enterprises, see [Devin Auth](/enterprise/devin-auth#configuring-access) or [Windsurf Auth](/enterprise/windsurf-auth#prerequisites) on how to configure access.
    2. Try logging out and back in: `devin auth logout && devin auth login`
    3. Check your authentication status: `devin auth status`
  </Accordion>

  <Accordion title="Token expired">
    Authentication tokens expire periodically. Simply run:
    ```bash
    devin auth login
    ```
    to refresh your credentials.
  </Accordion>
</AccordionGroup>

---

## Runtime Issues

<AccordionGroup>
  <Accordion title="Model not available">
    If you see errors about a model not being available:

    1. Check if your enterprise restricts available models in [Team Settings](/enterprise/team-settings)
    2. Verify the model name is correct — use `/model` to see available options
    3. Try a different model: `devin --model sonnet -- your prompt`
  </Accordion>

  <Accordion title="Rate limiting or quota exceeded">
    If you hit usage limits:

    1. Wait a few minutes before retrying
    2. Check your organization's usage dashboard for quota status
    3. Contact your admin if you need higher limits
  </Accordion>

  <Accordion title="Agent seems stuck or unresponsive">
    If the agent stops responding:

    1. Press `Ctrl+C` to interrupt the current operation
    2. Try `/clear` to start a fresh session
    3. Check your network connection
    4. Restart Devin CLI
  </Accordion>
</AccordionGroup>

---

## MCP Server Issues

<AccordionGroup>
  <Accordion title="Server won't start">
    If an MCP server fails to start:

    1. Verify the command works outside Devin CLI:
       ```bash
       npx -y @modelcontextprotocol/server-github
       ```
    2. Check that all required environment variables are set
    3. Look for error messages in the server output
  </Accordion>

  <Accordion title="Tools not appearing">
    If MCP tools don't show up:

    1. The server may need a moment to initialize — wait a few seconds
    2. Check that the server is configured correctly in your config file
    3. Verify your enterprise allows MCP servers in [Team Settings](/enterprise/team-settings)
  </Accordion>

  <Accordion title="Permission denied for MCP tools">
    MCP tools default to prompting for approval. To auto-approve specific tools, add them to your permissions config:

    ```json
    {
      "permissions": {
        "allow": ["mcp__github__list_issues"]
      }
    }
    ```
  </Accordion>
</AccordionGroup>

---

## Getting Help

If you're still experiencing issues:

- **Email support:** [support@cognition.ai](mailto:support@cognition.ai)
- **Submit a bug report:** Use the `/bug` command inside Devin CLI to report issues directly to the Devin CLI developers
- **Check for updates:** Run `devin update` to ensure you're on the latest version
