OpenRig
← All examples

Keep work moving across machines.

Your laptop can come and go while an always-on home team builds and a VPS dogfood team keeps using the app. OpenRig carries messages and tracked work between them, so findings become repairs and you can come back to a useful result.

What happens

  1. Give the home team ownership

    Your laptop coordinator discovers the home project owner and assigns the change. The owner reads and claims it before the laptop goes away.

  2. Put the app through dogfood

    Home gives the VPS team a revision to use. Dogfood finds an error and sends an actionable task back to the home owner.

  3. Turn a finding into a repair

    Home reads and claims the finding, then creates a repair slice in the local project mission. The corrected revision goes back to Dogfood for another check.

  4. Keep the result with the project

    Dogfood reports to Home while the laptop is away. Home records the outcome and retains the next action.

  5. Return to a useful answer

    Once the laptop reconnects, its coordinator asks the home owner for progress and tells you what is ready to try.

What OpenRig does

Host routing connects the teams. Messages name the sender and recipient; queue tasks keep work assigned; the project mission and repair slice live on Home. Pairing does not sync files, credentials or agent context.

What Claude or Codex does

The agents interpret the idea, build the app, investigate failures, make repairs and explain the result. They use the project's repository to access revisions on each machine.

When this helps

Use this when different machines have different jobs and you want work to stay with an online team while your personal laptop is away.