A handoff transfers an agent's work to another host. Shared access lets another person view or approve work on its current host.
The browser and desktop apps provide both features through the gateway.
Requirements
Pair the app with a gateway first. Both hosts must be online for a transfer. Offline delivery is unavailable.
The destination needs a repository checkout, the agent CLI, and its own agent login.
Transfer work to your host
- Pair the app with both hosts using full access.
- Open the source pane menu.
- Select Hand off this pane….
- Select the destination host.
- If the agent is active, wait for its turn to finish. To interrupt the turn, select Interrupt and hand off instead.
- Review the branch, changes, files, conversation, and skipped items in the transfer summary.
- Confirm the transfer.
- If Vibeke cannot find the repository on your destination host, enter its path.
Vibeke creates a new worktree on the destination. It applies the changes and attempts to resume the agent.
A handoff copies work after an agent turn. It does not move process memory or close the source workspace. Both copies remain available.
Transfer contents
| Item | Behavior |
|---|---|
| Git commits | A Git bundle includes local commits when necessary. |
| File changes | A patch includes uncommitted changes. |
| Untracked files | Includes eligible regular files up to 5 MiB each. Skips ignored files, symlinks, and recognized secret files. |
| Claude Code or Codex conversation | Uses an available transcript for native resume. Rewrites paths for the destination. |
| Other agents or missing transcripts | Transfers the files. A supported agent can start with a handoff note instead of the previous conversation. |
| Credentials | Does not transfer agent logins, subscriptions, or credential stores. |
The destination uses its own credentials. Secret filters and transcript redaction cannot identify every possible secret. Review the transfer summary before you send it.
Bundles have a 200 MiB limit. Temporary bundle storage expires after one hour.
Transfer work to a teammate
The recipient prepares the destination:
- Open Settings → Receive a handoff.
- Create an invitation.
- Send the invitation to the sender.
- Make the repository available in a Vibeke workspace on the destination host.
The sender completes the transfer:
- Open the invitation in the app.
- Select the recipient's host in the source pane's handoff flow.
- Review the summary.
- Confirm the transfer.
The gateway matches the repository origin. The invitation does not permit access to other panes or arbitrary repository paths.
Vibeke imports the work into a new workspace. It does not start an agent automatically. The recipient receives a notification and decides when to resume.
Share a pane or workspace
- Select Share this pane… in the app.
- Select the pane or its workspace.
- Select View or View + approve access.
- Set an expiry time.
- Create the invitation.
Approval access permits answers to requests within the selected scope. It does not give full host administration access.
The gateway refuses expired shares. Use Settings → Devices to revoke access earlier. See device recovery.
Recover from a connection failure
If the import result is unknown, inspect the destination before another attempt. The work can already be present.
If the import succeeds but the agent fails to start, the worktree remains available. Correct the agent setup before you resume.