Omniscio documentation
Browse all documentation
  1. Getting Started19
  2. Sessions & Agents145
  3. Inbox & Notifications74
  4. Projects & Tasks105
  5. Automation & Scheduling80
  6. Knowledge & Memory29
  7. AI Features75
  8. Integrations118
  9. Plugins & Marketplace45
  10. Cloud & Teams57
  11. Settings & Customization83
  12. Account & Billing31
  13. Troubleshooting89
  14. CLI & API Reference29
  15. Legal & Policies5
  16. Uncategorised25

PR hand-off tracker

When a session hands a finished branch to the Sync Overseer, Omniscio itself writes the hand-off down at that moment and keeps checking GitHub until a pull request contains that exact commit. It stays quiet while things are on time, tells the Dev Ops Overseer after four hours, and gives you one inbox card per branch only if a pull request is still missing after six hours.

What it does

  • When a session sends the Sync Overseer a message that names one of its own branches, Omniscio records that hand-off right away: the branch, its exact commit, the folder, the session that sent it and the time.
  • The sending session gets a receipt in the reply naming what was recorded, so it can finish as soon as it has handed off.
  • Every 30 minutes Omniscio asks GitHub, in one combined question, which waiting hand-offs now have an open or merged pull request containing their commit.
  • It does not matter which computer or account opened the pull request; only the commit counts.

When you hear about it

  • Under 4 hours: nothing. Publishing takes time and nobody is interrupted.
  • At 4 hours with no pull request: the Dev Ops Overseer gets one message listing the late branches.
  • At 6 hours with no pull request: you get one inbox card per branch, naming it. The card removes itself when the pull request appears.
  • A closed pull request that was never merged does not count; the branch stays on the late list.
  • If GitHub cannot be reached, nothing is escalated or cleared on that check. A long outage is reported to the Dev Ops Overseer, never to you as missing work.

What it does not cover

  • It stops watching a branch once a pull request containing it exists; review and merging are tracked elsewhere.
  • Each computer tracks the hand-offs sent on it.
  • If the Sync Overseer rebuilds a branch onto a new commit, it declares that commit so the tracker follows it.

Last verified 2026-10-29