This guide covers common problems and their solutions. If your issue isn’t listed here, check the Pentagon GitHub repository for open issues.
Installation Issues
Gatekeeper Warning
macOS may show “Pentagon can’t be opened because it is from an unidentified developer.”
Fix: Right-click (or Control-click) the app and select Open. Click Open in the confirmation dialog. You only need to do this once.
”App Is Damaged” Error
If macOS says Pentagon is damaged and can’t be opened:
xattr -cr /Applications/Pentagon.app
This removes the quarantine attribute macOS applies to downloaded apps. Then open Pentagon normally.
Permissions Not Granted on First Launch
If you clicked “Don’t Allow” when Pentagon requested file access:
- Open System Settings > Privacy & Security
- Click Files and Folders (or Full Disk Access)
- Find Pentagon in the list
- Toggle on the required access
See Permissions for the full list of directories Pentagon needs.
Claude Code Issues
Claude Code Not Found
Pentagon can’t locate the claude binary.
Symptoms: Agents fail to start with a “command not found” error.
Fix:
- Verify Claude Code is installed:
- If not installed, install it following the Claude Code documentation
- Make sure
claude is on your PATH — Pentagon searches standard paths (/usr/local/bin, /opt/homebrew/bin, ~/.local/bin)
API Key Issues
Agents start but fail with authentication errors.
Fix:
- Verify your API key is set:
- If not set, add it to your shell profile (
~/.zshrc or ~/.bashrc):
export ANTHROPIC_API_KEY="sk-ant-..."
- Restart Pentagon after updating your shell profile
Agent Issues
Agent Won’t Start
The agent desk appears but the session never initializes.
Check:
- Verify Claude Code works standalone:
- Check that the project directory exists and is accessible
- Ensure macOS permissions are granted (see Permissions)
- Try spawning an agent in a different directory
Agent Stuck in Active State
The agent shows a yellow “Active” ring but nothing is happening.
Cause: Pentagon performs a stale sweep — if an agent reports active status for more than 60 seconds without any tool calls or output, it may be stale.
Fix:
- Check the terminal tab for any output or errors
- Wait for the stale sweep (60 seconds) to reset the status
- If still stuck, respawn the agent from its context menu (right-click the desk)
Agent Not Responding
The agent is in “Ready” state but ignores input.
Fix:
- Click the agent desk to make sure it’s selected
- Press Cmd + L to focus the terminal input
- Type your message and press Enter
- If unresponsive, respawn the agent (right-click > Respawn)
Respawning kills the current process and starts a fresh Claude Code session. The agent’s soul, tasks, and memory persist.
Canvas Issues
Agent Desks Not Appearing
You spawned an agent but nothing shows on the canvas.
Check:
- Look in the sidebar agent list — if the agent appears there, it exists but may be off-screen
- Use the minimap (bottom-right) to locate the desk
- Click the reset view button (scope icon) to reset zoom and position
- Check if the canvas panel is hidden — press Cmd + E to toggle it
If the canvas feels slow:
- Reduce the number of active agents — terminate or set idle agents to dormant
- Check Activity Monitor for CPU usage
- Restart Pentagon
File Permission Issues
Agents Can’t Read or Write Files
Fix:
- Grant Full Disk Access to Pentagon:
- System Settings > Privacy & Security > Full Disk Access
- Toggle Pentagon on
- Verify
~/.pentagon/ exists:
- If the directory is missing, Pentagon creates it on first launch — try restarting the app
History or Settings Not Saving
If configurations reset when you relaunch:
- Check that
~/.pentagon/ is writable:
touch ~/.pentagon/test && rm ~/.pentagon/test
- If permission denied, fix ownership:
sudo chown -R $(whoami) ~/.pentagon/
Data Recovery
Restoring from Backup
Pentagon stores all data in ~/.pentagon/. If you use Time Machine or another backup tool:
- Open Time Machine (or your backup tool)
- Navigate to
~/.pentagon/
- Restore the directory to recover agents, settings, and history
Full Reset
If Pentagon is in a broken state and nothing else works:
This deletes all agent data, settings, and history. Pentagon will recreate the directory on next launch with default settings.
After resetting, relaunch Pentagon. You’ll need to reconfigure your preferences and spawn new agents.
Getting Help
If your issue persists:
- Check the terminal tab for error messages — they often explain what went wrong
- Look at Console.app for Pentagon-specific log entries
- File an issue on the Pentagon GitHub repository with steps to reproduce
Next Steps