Support

Report an Issue

Found a bug or have a feature request? Open an issue on GitHub or email us at support@withdispatch.dev.

Common Issues

Agent CLI Not Detected

Dispatch auto-detects Claude, Codex and Gemini CLIs from 40+ installation paths. If your CLI isn't detected:

  1. Open Settings and check the Adapters section
  2. Click "Refresh" to re-scan
  3. If still not found, manually set the path under Custom CLI Paths

Dispatch auto-detects CLIs from most common installation methods.

Spec Generation Fails

If spec generation shows "Agent could not be reached":

  1. Verify the agent CLI works in your terminal: claude --version, codex --version or gemini --version
  2. Make sure you're authenticated: claude login, codex login or gemini login
  3. Check that your project directory exists on disk
  4. Try clicking Retry: the goal stays retryable after failures

Token Usage Seems High

  • Check Settings > Pipeline Automation > Per-task token budget to set a cap
  • Check Observatory (Cmd+6) for per-adapter cost breakdown and cache hit ratios
  • Disable Dual-agent security review if you don't need it (saves Codex tokens)
  • Use Auto-approval rules for low-risk changes (skips unnecessary review cycles)
  • Check Token Efficiency in the Observatory for red flag alerts on low cache ratios

Pipeline Takes a While to Start

When you create a goal, Dispatch runs multiple stages before implementation begins:

  1. Spec generation from your goal description
  2. Test requirements generation
  3. Security analysis

These run to ensure code quality and security from the start. To speed things up:

  • Test and security specs run in parallel after spec approval
  • Availability checks are cached after the first successful detection
  • You can disable dual-agent security review in Settings to skip the second security pass

Mission Takes a Long Time

Mission duration depends on the mode:

  • Standard missions cap at 1000 tokens for concise answers and typically complete in seconds
  • Research and Audit missions use a 4000 token cap and may take longer for thorough analysis
  • You can minimize a running mission and keep working. The streaming UI shows results as they arrive.
  • If a mission seems stuck, check that the assigned agent CLI is responsive in your terminal

Goal Shows "No agents running" on Floor

The Floor view shows live agent activity only while tasks are actively running. Between pipeline stages (for example, after spec approval but before implementation starts), the Floor may appear empty. This is normal. Check Agentflow (Cmd+3) for full pipeline status and to see which stage the goal is currently in.

How Do I See What Agents Changed?

Open the Vault (Cmd+5) and select a replay. The decision timeline shows every file change, verify result and review decision as color-coded cards. Click any decision card to see details including affected files, timestamps and any deviations from the approved spec.

How Do I Access Dispatch from My Phone or Tablet?

  1. Enable Browser Access in Settings > Remote Access
  2. Dispatch generates a self-signed TLS certificate automatically
  3. Access via the HTTPS URL shown in Settings from any device on your network
  4. Install the CA certificate on your device for trusted connections (the Settings page provides download instructions)

App Stuck on Loading Screen

This usually means the sidecar server didn't start. Try:

  1. Quit Dispatch completely (Cmd+Q)
  2. Check for zombie processes: ps aux | grep dispatch | grep -v grep
  3. Kill any stale processes and relaunch

Contact

Ad Astra Computing Inc.