---
source: crewkit documentation
url: https://crewkit.io/docs/pick-up-and-hand-over.md
title: "Picking up tomorrow and handing work over"
description: "Every way to continue your own work later or pass it to a colleague, side by side, with who can read each one and whether it reaches other people's sessions."
---


A **handover** is what you leave so that you, tomorrow, or a colleague can continue where a session stopped. crewkit has several, and they differ in who can read them. This page compares them, then shows which one to use for each job.

---

## The routes side by side

| Route | Who can read it, and for how long | Does it reach other people's sessions? |
|---|---|---|
| **Save state** (MCP tool `save_state`; read back with `load_state`) | Only you. One per person per project: each save overwrites the last. Your agent writes it and saves only after you approve the text. | No. It is added to the start of your own next session on the project. |
| **Team digest** (read with `load_state`, layer `team`) | Every member of the project's organization. Built once a day, at the organization's end-of-day hour, from each contributor's session summaries: one for weekdays and one for weekends. | Yes. It is added to the start of new sessions on the project, beside your save state. |
| **Note** (MCP tool `add_note`) | Everyone in the organization. Stored and indexed for search. Your agent saves it only after you approve the title and body. | Yes. It can surface in other people's sessions long after yours ends. |
| **Work update** (MCP tool `share_update`) | Teammates on the project. One line of at most 280 characters; a second update within 3 minutes is folded into the first. | Yes. It reaches teammates' open sessions, so they can avoid overlapping with you. |
| **Work save and pickup** (`crewkit work save` / `crewkit work pickup`) | Anyone who can fetch the repository: the uncommitted changes are pushed to its origin, usually to `refs/crewkit/wip/<branch>` (or `refs/heads/wip/<branch>` when the host hides that namespace). In a workspace only. | No. It moves code, not context. |
| **Share link** (`crewkit sessions share`) | Signed-in members of your organization, or, for a public link that an admin creates, anyone with the link. Until it is revoked or expires. | No. See [Sharing](/docs/sharing). |
| **Session message** | The colleague's session you write to. | Yes, but [Session messaging](/docs/session-messaging) is off by default; an admin turns it on. |

**In a [sensitive session](/docs/sensitive-sessions)**, `save_state`, `add_note` and `share_update` refuse and save nothing.

**Team digests carry summaries of teammates' sessions into everyone's sessions on the project.** Launch with `crewkit code --no-context` to start a session without your save state and the team digest.

---

## Continuing your own conversation

`crewkit code -r <session id>` resumes a conversation by its id, and the project search tools stay on. A launch that continues a conversation without naming it by its id (`crewkit code -c`, `crewkit code -r <name>`, the resume picker, or a fork) turns the three search tools off for that launch. See [Sensitive sessions](/docs/sensitive-sessions).

---

## Which route for which job

**If you want to continue tomorrow yourself:** resume by id. If you will start a new conversation instead, ask your agent to save a state before you stop; your next session on the project starts with it.

**If you want to hand a work item to a colleague in a workspace:** run `crewkit work save`, assign the item, and they run `crewkit work pickup`. Each step is in [Hand off a work item](/docs/workspace-handoff#hand-off-a-work-item). A project that is not a workspace has no `crewkit work`: save a state for yourself, and use a note or a share link for the colleague.

**If you want the team to know a decision for good:** ask your agent for a note. Write it for a stranger: everyone in the organization can read it.

## Next steps

- [From your phone](/docs/from-your-phone): what you can do without a terminal.
- [MCP server](/docs/mcp): every tool a session has.
