Share & Resume
Hand off any AI conversation. Teammates resume it natively in their own agent.
Inside Claude Code, Codex, or Claude Desktop, tell your agent to share this conversation with a teammate. The entire transcript, tool calls, files, and decisions land in their inbox. They resume it natively in their own agent on their own machine. No copy-paste, no lossy summaries, no losing the thread. Save a conversation for yourself the same way: a perfect checkpoint to resume tomorrow or next week.
Next step: verify the env var rotation on the worker, then re-deploy.
Open question: do we need a backfill cron for legacy rows, or run it inline?
Note: before compacting context, save the Day 5 rewrite reasoning.
Access from anywhere
Web Dashboard
AI Ecosystem
Apps
What should we work on today?
Open the Conversations tab in your workspace to browse shares sent, shares received, and saved conversations. Each entry shows the title, source agent, message count, work mode, and a one-click resume button.
Open in dashboardCLI
Capabilities
Native Cross-Agent Handoff
Share a Claude Code session and your teammate resumes it natively in Claude Code or Claude Desktop. Share a Codex session and they resume in Codex CLI or Codex Desktop. The full transcript, tool calls, and tool results travel intact, byte-for-byte.
Universal Transcript Fallback
Every share also includes a verbatim Markdown transcript. So even when your teammate is in Cursor, Windsurf, Antigravity, Gemini CLI, or Microsoft Copilot, they can paste a single prompt and pick up the conversation with full context.
Save Your Own Conversation
Tell your agent "save this convo" and it lands in your personal inbox. Resume it tomorrow, next week, or after you switch machines. Perfect checkpoint before a context wipe, a long break, or a risky next step.
Conversations Inbox
A dedicated workspace tab for shares you sent, shares you received, and conversations you saved. Each one shows the title, sender, source agent, message count, and a one-click resume button.
Email + Desktop Notifications
When someone shares a conversation with you, you get an email and a desktop notification. Open the share, hit resume, and your local agent launches with the conversation already loaded.
Resume from the CLI
runwork inbox lists your shares. runwork resume <id> drops the conversation into your local agent's session store and launches the agent. Built for the terminal-first workflow without leaving the keyboard.
Smart Metadata + Auto Title
Every share is tagged with the source agent, work mode, topic keywords, last user intent, suggested next step, and open questions. So your teammate knows what they're walking into before they hit resume.
Audit Log + Expiry
Every share is logged: created, opened, downloaded, resumed, deleted. Shares expire after 7 days by default and soft-deletes are recoverable within a week. Senders stay in control of who sees what and for how long.
Use Cases
Why It Matters
- Cross-user, cross-agent, cross-machine. No other AI tool ships this end-to-end.
- Native resume preserves every tool call and tool result, byte-for-byte
- Universal transcript fallback works with every agent that speaks MCP
- Save and resume your own conversations: a checkpoint you can come back to
- Triggered from inside your agent: no UI to learn, no copy-paste
How It Works
Share & Resume moves an entire AI conversation, including transcript, tool calls, tool results, and surrounding context, from one teammate to another. It works across users, across agents, and across machines. This does not exist in the rest of the AI ecosystem: native share-link features in Claude, Codex, and ChatGPT either produce read-only snapshots or fork into a new thread in the same product. None of them let your teammate continue the conversation natively in their own tool on their own laptop.
From inside your agent
Tell your agent "share this conversation with alex@yourco.com". The Runwork skill for sharing kicks in: it asks Runwork CLI to capture the current session, then uploads the bundle through the Runwork MCP server. The same flow works for "save this conversation", with you as the sole recipient.
Tier 1: native, byte-for-byte resume
For Claude Code, Claude Desktop Cowork, Codex CLI, and Codex Desktop, Runwork captures the raw session file (the Claude JSONL transcript or the Codex rollout) directly from your machine. When your teammate resumes, that file is placed into their own agent's session store. Their agent picks it up and continues from exactly the same state, with the same tool history, the same files, and the same context. No lossy reconstruction.
Tier 3: universal transcript fallback
Every share also includes a verbatim Markdown transcript: every user message, every assistant message, every tool call, every tool result, transcribed faithfully by the LLM at share time. Your teammate can resume in Cursor, Windsurf, Antigravity, Gemini CLI, Cline, Microsoft Copilot, ChatGPT, Claude Desktop Chat mode, or any other agent that speaks MCP. They paste a single prompt, their agent fetches the bundle, and the conversation continues with full context.
The Conversations inbox
Open the Conversations tab in your workspace dashboard to browse shares sent, shares received, and conversations you saved. Each entry shows the title (auto-generated by the LLM at capture time), the source agent, message count, work mode, topic tags, the last user intent, and a suggested next step. One click downloads the bundle. One more click resumes the conversation in your local agent.
Notifications across every surface
When a share arrives, you get an email, a desktop app notification, and an inbox entry. From the desktop app, hit resume and Runwork launches your local agent with the conversation already loaded. From the CLI, run runwork inbox to list incoming shares and runwork resume <id> to pick one up without leaving the terminal.
Audit, expiry, and recovery
Every action on every share is logged: created, opened, bundle downloaded, resumed, deleted. Shares expire after 7 days by default to keep your workspace tidy. Senders can soft-delete a share at any time, and deletions are recoverable within a 7-day window. Permission to share with a non-member email reuses the same gate as team invites, so you can't accidentally exfiltrate context to someone outside your workspace.