Troubleshooting
Common Cyborg7 issues and how to fix them.
Common issues and how to fix them.
Daemon won't start / port 6780 in use
pnpm dev fails because the daemon's listen address is taken.
Fix: Another daemon may already be running on the port. Stop it, or change PASEO_LISTEN (e.g. 127.0.0.1:6868). The Cyborg7 daemon defaults to 127.0.0.1:6780.
Cannot find module / deps out of sync
Imports fail after merging or switching branches.
Fix: Run pnpm install to reinstall workspace dependencies, then restart the daemon. Always use "workspace:*" for local packages — pinned npm versions resolve to stale store copies and break the cyborg schemas.
drizzle-kit migrate hangs
The migration command connects to PostgreSQL but never completes.
Fix: Apply the SQL file manually via psql: psql $DATABASE_URL -f packages/server/src/server/cyborg/db/migrations/XXXX_name.sql. Note: migrations only matter in connected mode (DATABASE_URL set); solo mode uses SQLite.
Agent never goes online / no response
You created an agent but it never streams output.
Fix: Check: 1) the provider CLI is installed and authenticated (e.g. Claude Code / Codex on PATH), 2) the agent's --cwd path exists, 3) daemon logs for spawn errors. Agents run as local child processes on the daemon's machine.
Messages not syncing across machines
Messages appear locally but teammates on other daemons don't see them.
Fix: Check: 1) DATABASE_URL is set (connected mode — solo mode never syncs), 2) the daemon is connected to the relay and subscribed to the workspace, 3) relay logs for the relay_subscribed confirmation. Each daemon only receives workspaces it has a membership in.
Cybo won't spawn (cybo / pi not found)
cyborg cybo:spawn fails to launch the Cybo on the daemon.
Fix: The daemon runs cybos via the host pi binary through Paseo's PI provider. Installing @cyborg7/cybo links both cybo and pi onto PATH — run cybo doctor to verify provider, auth, and model are detected.
Relay refuses to boot in production
The cloud relay exits at startup complaining about the JWT secret.
Fix: CYBORG7_JWT_SECRET must be set to a strong value in production — the relay refuses to run with the public dev default. Generate one with openssl rand -hex 32.
Asset upload (avatars) fails
Workspace avatar uploads error out in cloud mode.
Fix: Presigned S3 upload requires S3_ASSETS_BUCKET, S3_ASSETS_REGION, and the IAM credentials to be set on the relay. Check the relay logs for the presign step.