Workspace handoffs with the context to continue.

What is a workspace handoff?

A workspace handoff is a selected set of task resources and instructions that lets another person continue the work. Depending on the task, it can include files, links, notes, logs, reproduction steps, and a setup recipe.

Stowen’s planned flow starts from a workspace or selected resources. You’ll preview the exact package, then create a recipient-restricted link. Shared and received workspaces will have a basic list, and you’ll be able to revoke access to an existing link.

The recipient should be able to continue independently after you go offline, provided they have the required apps, permissions, and resources. That does not remove dependencies on external services or repository access.

A task handoff checklist you can use today.

Use this outline in your current issue tracker or shared document. Include enough detail for someone to begin without guessing, and remove material that is unrelated or sensitive.

1. Goal and expected result. What needs to change? How will the recipient know it is done?
2. Current progress. What is complete, what is unfinished, and what is blocked?
3. Reproduction or starting steps. What exact action exposes the problem or opens the work?
4. Selected resources. Which files, URLs, logs, and references are needed? Which are optional background?
5. Setup requirements. List the apps, repository permissions, local data, dependencies, and working directories required.
6. Commands to review. Explain each startup command, its order, and how to check readiness. Never put credentials in the instructions.
7. Changes already made. Identify the branch or known base commit, and explain selected uncommitted changes where relevant.
8. What to return. Name the deliverables, requested checks, and any question the completion note must answer.

Example: handing off a reproduction task.

“Reproduce the empty-state issue using the steps in the linked ticket. I confirmed the request contains the expected items, but have not checked the view’s filtered count. Start from the recorded base commit, review the supplied patch, and run the documented local setup with your own configuration. Return the selected fix, verification results, and any remaining uncertainty.”

This gives the recipient a goal, a finding, a starting point, and a return expectation. Attach the actual ticket, base commit, and setup instructions before sending.

Give the recipient’s work its own context.

Opening someone else’s task should not mean losing the task already in progress. Stowen is being designed to preserve the recipient’s current workspace before opening a handoff in a separate temporary working context.

The planned flow applies the recipient’s app preferences and device mappings, checks repository access and required local resources, and explains missing setup. A browser preview will show included resources, task instructions, and requirements before desktop installation.

When setup is ready, the web companion will guide sign-in and opening the handoff in the desktop app. Imported commands must be shown for approval before execution.

Transfer selected code changes against a known base.

A folder of changed files does not always explain which version they belong to. Stowen’s planned code handoffs will transfer selected uncommitted changes against a known base commit and apply them in an isolated Git worktree.

A worktree provides a separate working directory for the code task. It does not automatically install dependencies, provide credentials, grant repository permissions, or make commands safe. Those requirements still need explicit setup and review.

Keep the package focused. Include the changes required for the task, relevant evidence, and a note about what has or has not been tested. Read more about development setup and local changes.

Return the results with a completion note.

The planned return flow lets the recipient select code changes, files, or other deliverables and attach an editable completion note. Finishing the handoff should then restore their previous workspace.

The assistant is planned to help summarize selected changes, prepare a return package, and coordinate saving results before returning to previous work. Generated summaries remain editable and must separate recorded facts from inference.

Share resources without transferring accounts.

Recipients use their own accounts and permissions. Credentials, browser cookies, and authenticated sessions are excluded from transfers. The planned controls let you review content before sharing and exclude sensitive apps, paths, and files.

Encrypted synced and shared content is in the MVP scope. Recipient restrictions and revocation control access to the shared link; revoking a link should not be treated as a way to erase copies someone has already downloaded.

Stowen is still in development, and handoffs are not available to try yet. Initial restoration coverage will depend on the announced desktop integrations. Contact us about your team’s handoff requirements or review the planned beta plans.