Corey
Troubleshooting Corey
In progressMost Corey issues fall into three categories: the MCP connector not appearing in Claude Desktop, the CLI failing to connect, or permissions errors on the Corey folder. Check that the connector is installed for the right scope, that Claude Desktop has been restarted, and that your Corey folder path matches the configured value.
This page is a work in progress. Common issues and their fixes are being documented.
Claude Desktop and connector issues
TODO: Cover the most common cause - the MCP connector installed with --scope local instead of --scope user, meaning it is not available globally in Claude Desktop. Describe the fix: reinstall with the correct scope and restart Claude Desktop.
TODO: Explain that Claude Desktop must be fully quit and restarted (not just the window closed) for MCP connector changes to take effect. Include the quit shortcut for macOS and Windows.
TODO: Document the COREY_HOME environment variable and what to do if the folder was moved or renamed. Include the command to verify the current value and how to update it.
CLI and permissions errors
TODO: Cover the most common CLI errors after quick-start-cli - missing ANTHROPIC_API_KEY, claude command not found (PATH issue), and connector not loaded. Provide the diagnostic commands.
TODO: Explain macOS and Linux file permission issues that prevent Corey from reading or writing its folder. Include the fix (chmod/chown where appropriate) and note the macOS Full Disk Access setting if relevant.
TODO: Link to the Hetzner guide and cover server-specific issues: Doppler not finding the project, systemd service failing to start, and claude not found on PATH for the service user.
TODO: Explain how to check the installed connector version and update it. Include the update command.
Still stuck?
If you cannot find a fix here, contact kristian@pressonetwork.com with the output of claude --version and a description of what you were doing when the error occurred.