Docs/When setup or work gets stuck

When setup or work gets stuck

Check the smallest likely cause before restarting the whole workflow.

Source-reviewed guide · deployment verification pending8 September 2026

I signed in but cannot access the project

Check the email address, beta status, active organization and project membership. A successful sign-in does not grant membership in every organization. Ask the owner to check invitations and roles.

The CLI is signed in but the machine is not listed

acc login is personal sign-in. Use acc runner login to enroll the execution machine, then check Agents → Runners.

A task is waiting and nothing is running

Inspect dependencies, approvals, provider authentication and available runner capacity. Run acc doctor on the execution host. Confirm the machine can access the correct repository and has not gone to sleep.

Local changes exist but a PR was not created

Check the repository's push remote and permissions. Local repository registration alone does not set up a GitHub remote. Avoid discarding local work while resolving the connection.

A check or review failed

Read the linked evidence and request a targeted correction. Do not repeatedly start new tasks with the same unresolved cause. Keep the intended outcome and latest decisions attached to the work.

What to send support

Send the affected step, non-sensitive error, timestamp, version and task reference. Never send API keys, browser session tokens or device approval codes.