Repository navigation
Troubleshooting
Lane Holloway edited this page Oct 21, 2026
·
1 revision
Start with the Settings tab (5): its Prerequisites section checks most of what can go wrong and says how to fix it. c runs the checks again after you fix something.
-
"the GitHub CLI (gh) is required": install it from cli.github.com and run
gh auth login. -
"gh auth: … (run
gh auth login)": Fast Lane uses the GitHub CLI's login. Rungh auth login, thengh auth statusto check. -
A config error naming a file and setting: the config has something Fast Lane can't use, such as a filter that doesn't apply to its kind (
labelson an alert), an unknown action, an unknown effort, or a prompt that doesn't parse. Fix that entry, or move the file aside to start fresh.
A missing claude doesn't stop Fast Lane from starting: the Settings tab shows it, and you can set Claude path there.
-
Private or organization repos don't show up: the GitHub login needs the
repoandread:orgscopes. Rungh auth refresh -s repo,read:org. - No Dependabot or code scanning alerts: the repo must have them enabled, and you need permission to see its security alerts. Repos where they aren't available are skipped quietly.
-
A repo shows "failed to sync": the message says why. Network trouble clears up on the next poll;
Rretries now.
Work through these in order:
-
Is auto-run on? For repo triggers, the repo must show
autoon the Repos tab. Inbox triggers follow the inbox setting on the Rules or Settings tab instead. -
Was the item there before? Items that existed when you started watching never auto-run, and the first poll after you upgrade Fast Lane only records state. Start these by hand with
enter. -
Do the rules cover it? Once any rule exists, only the keys the rules list auto-run. A
checks_failedchange needs apull_request:checks_failedrule. A repo with rules of its own ignores the global rules. -
Does it pass the filters?
authorsmeans who opened the item, not who commented. The status line says how many new changes "didn't match auto rules". - Was it your own activity? Your pushes and comments, and bot comments, never trigger anything.
- Has it hit the limit? The status line says when an item "reached max_auto_runs". Raise it on the Settings tab if you need to.
-
A session failed while preparing: the transcript shows the git error. A failed
git fetchisn't fatal; a failedgit worktree addorgh repo cloneis. Check that the checkout or the workspace folder is writable and thatgitworks there. - "branch is already checked out at …": you have that branch checked out in your own checkout. Claude knows to check it out under another name and push to the original branch; if it gets stuck, reply telling it to do that.
-
A session says "interrupted when Fast Lane exited": Fast Lane was quit mid-turn. Press
enteron it and reply to continue. -
Claude keeps asking for permission for the same thing: answer
ain the dialog to allow it for the rest of the session, add the action to the rule'sallowlist, or add the tool to Allowed tools on the Settings tab for every session. -
Something went wrong and you want the details: each session's raw log is in
~/.local/state/fast-lane/logs/session-<n>.jsonl.
-
Review requests or mentions don't show up: the Settings tab's Notifications check must pass; it needs the
repoornotificationsscope. The first read after you turn the inbox on only records the time, so only newer notifications appear. -
Too much from the inbox: set it to list only (
ion the Rules tab), or add rules forpull_request:mentioned,issue:mentionedand the others with filters such asskip_labels.
Worktrees share your checkouts' git objects, so they're small, but each one is a full copy of the files. Worktrees of sessions finished over a week ago are removed at startup; D on the Sessions tab removes one right away. Clones of repos without a local checkout stay in the workspace until you delete them.
Open an issue with what you did, what you expected, and the version from fast-lane -version.