Leave a collaboration

rig disconnect            # stop syncing, keep the local files
rig disconnect --purge    # stop syncing AND remove manifest-tracked files

What rig disconnect does

It's a local checkout operation — the remote workspace, your membership, and your collaborators are untouched.

1. Stops the daemon. Graceful shutdown of this device's tapd.
2. Drops the local binding pointer — removes .rig/tap-binding.local.json.
3. Leaves your files in place by default. The workspace is now an unbound copy of the rig.

After rig disconnect, this checkout stops syncing. You can keep using it as a solo workspace, or delete the directory. To also revoke yourself server-side, ask the owner to run rig unshare <your-email>.

What --purge does

Everything rig disconnect does, plus:

• Removes every file that was tracked by [package] (manifest-listed files).
• Skips untracked files — anything you created locally that wasn't synced stays.
• Skips [local].dirs contents — those were always yours.

The intent of --purge is to undo the rig install without nuking your local work. If you want to wipe everything, just rm -rf the directory yourself.

When to use which

Flags

What it doesn't do

• Doesn't remove the binding from the relay (other devices keep working).
• Doesn't notify other collaborators (relay-level activity events surface in their daemon logs, that's it).
• Doesn't touch your auth or other rigs.

To remove the entire binding

Only the binding owner can delete a binding. The relay endpoint requires owner auth — see How collab works — admin endpoints. The short story: rig disconnect is per-device; full binding teardown is out of scope for the CLI today.

See also

• Daemon
• [sync] reference
• Publishing a synced rig — what to do before leaving if you have unsaved publishes.