Skip to content

Recover the dashboard preview

runbookobservedEvidence reviewed 2026-10-06

One managed preview on Shipyard port 3003 is shared. Coordinate before changing its owner or restarting it.

Read the selected API task status and ~/dev-environment/state/orca/active-dashboard.json locally. Compare the active root with the intended task. Check direct API health and http://127.0.0.1:3003/health on Shipyard. Look at the task’s dashboard log privately.

Do not assume Mac localhost is Shipyard. In the Linux browser use http://localhost:3003. An Auth0 callback rejection differs from an application error boundary. The existing allowed preview ports were configured separately; do not switch to arbitrary ports or edit Auth0 as a generic repair.

If the intended task should own the preview, use orca-task.py dashboard --root "$TASK_ROOT" after coordinating the handoff. It manages the previously owned process and preserves files. If an unrelated process owns 3003, identify it and ask its owner; do not kill it automatically.

After an API restart the UI may retain an error boundary; reload once after API health recovers. Normal Auth0 consent may appear. Verify a real read-only application operation and that the preview targets the intended API. Browser login or viewer issues use the browser recipe.