A Review No Longer Vanishes When Its Machine Is Offline
A review queued for an offline machine used to fail quietly and never resume; it now tells you right away and restarts once the machine reconnects.
Summary
A reviewer agent runs on a specific machine, and if that machine was offline when a review was queued, the review used to wait briefly, fail quietly, and never be looked at again — with the pull request sometimes merging with no review at all. Reviews now tell you immediately when this happens, and pick themselves back up automatically once the machine reconnects.
What You Gain
This gap was easy to miss: a pull request could look like it had simply skipped review, with no clear reason why, until someone went digging and realized the machine the reviewer needed had been offline at the critical moment. In the meantime, that code could already be merged with nobody having actually looked at it — not a great position to discover after the fact.
Now you're told right away if a review is waiting on a machine that isn't currently connected, naming which reviewer and which machine it's waiting for. If the machine comes back online before anything else has reviewed that same code, the review picks up automatically, with no need for anyone to manually re-trigger it.
How It Works
- You're notified immediately if a review is queued for a machine that isn't currently online, with the reviewer and machine named clearly.
- The review resumes automatically once the machine reconnects, as long as the pull request is still open at the same commit and nothing else has reviewed it since.
- Reviews are stricter about exactly which commit they look at — they always check the precise commit the review was opened for, so a later change gets its own fresh review rather than being silently skipped or double-counted.
- A commit that no longer exists (for example, if the branch history changed) ends the review cleanly with that explanation, rather than retrying endlessly.
Where to Find It
This applies automatically to every project with agent-driven review — there's nothing to configure. The notification and auto-resume take effect immediately; keeping the desktop app and CLI current ensures the rest of the reliability improvements apply too.
See what else shipped that month on the Effigate Command Center changelog, or try Effigate Command Center with your own team.