Troubleshooting
Fixes for common problems.
An agent shows "Not installed"
Korev looks for claude and codex on your login shell's PATH, plus ~/.local/bin, ~/.npm-global/bin, ~/.bun/bin, /opt/homebrew/bin and /usr/local/bin. Check that claude --version or codex --version works in a new terminal window, then restart Korev.
macOS says Korev can't be opened
The build is not signed. Right-click Korev.app and choose Open, or run xattr -dr com.apple.quarantine Korev.app.
"Setup script failed"
Open the Setup tab in the terminal panel to see the output. Fix the script, then press Rerun setup. To archive a workspace that failed to create, press Archive workspace.
Workspaces are named from the first words of the task
Korev names workspaces and Ask chats with Claude Haiku through the claude CLI. Without claude, or with Settings → Git → Name workspaces from the task off, it uses the first words of the task.
My MCP servers are missing
Korev has no MCP settings of its own. Each agent uses the MCP servers from its own config. Add them with claude mcp or in Codex's config.toml.
Two workspaces use the same port
Use $KOREV_PORT in your run scripts instead of a fixed port. See Environment variables.
Spotlight will not turn on
The root checkout must be clean, with no merge or rebase in progress. Commit or stash your changes in the main checkout first.