Triggers

Triggers

Every poll (every two minutes by default), Fast Lane compares each open item with what it saw last time. A change that matters is a trigger. A trigger can start a Claude session for the item, or resume the item's last session so Claude keeps what it already learned. If that session is still working, the trigger waits until it finishes its turn.

Trigger	Kinds	Fires when
opened	all	An item shows up after you started watching the repo
changes_requested	PRs	Someone submits a review requesting changes
checks_failed	PRs	CI fails on the head commit
conflict	PRs	The PR picks up merge conflicts with its base branch
commented	PRs, issues	Someone comments, or leaves a review with a comment
review_requested	PRs	Your review is requested, on any repo
mentioned	PRs, issues	Someone @-mentions you, on any repo
assigned	PRs, issues	You're assigned, on any repo
ready_for_review	PRs	A draft is marked ready
pushed	PRs	Someone else pushes new commits
labeled	PRs, issues	Labels are added

review_requested, mentioned and assigned come from your inbox, so they work on repos you don't watch too. On repos you do watch, polling also catches review requests; either way, each one fires once.

Rules of the road

• Your own activity never triggers anything. Claude acts as you, so its own pushes and comments don't loop back. Comments from bots don't trigger anything either.
• Each change fires once. Checks failing on one commit, or one particular comment, fire once even if the state flaps or Fast Lane restarts. A new commit that fails again is a new change.
• One action per item per poll. When one poll finds several changes on an item, Fast Lane acts on the first one, in the order of the table above, that has an auto rule.
• Nothing old fires. The first poll of a newly watched repo only records what's open. The first poll after Fast Lane starts compares against what it saw before it quit.
• Auto-run has a limit. max_auto_runs (default 5) caps how many times auto-run acts on one item, so a fix that keeps failing CI can't loop forever. Sessions you start yourself don't count.

What auto-runs

• opened follows the repo's auto-run setting, and the rules if there are any. With no rules at all, every newly opened item on a repo with auto-run on starts a session.

• Other repo triggers (checks_failed, commented, …) auto-run only when a rule names them, such as pull_request:checks_failed.

• The personal triggers (review_requested, mentioned, assigned) follow the inbox setting instead and auto-run even without a rule.

• On a repo in full auto, every trigger runs, with its rule's prompt, model and effort when one matches.

Changed items get a ● and a tag on the Events tab either way, so you can act on them by hand.