Cloud agent session sharing

Cloud agent session sharing lets you open, inspect, and continue interacting with agent tasks that are running on remote virtual machines. Whether a cloud agent was triggered from integrations like Slack, Linear, GitHub Actions, or the Oz CLI, you can view its full session, follow along in real time, ask follow-up questions, and even "fork" the work into your local Derp environment.

Use cloud agent session sharing when you need to inspect a cloud agent run, debug a failed automation, or give teammates a shared record of what the agent did. The shared session is the review surface for the run: it shows the prompt, plan, commands, logs, outputs, and follow-up messages where available.

This makes cloud agent runs observable, steerable, and collaborative — even if they weren't initiated from your machine.

---

What it enables

With cloud agent session sharing, you can view the full remote session for a cloud agent run and:

• See every command the agent executed in the virtual environment
• Inspect context, logs, and outputs directly in Derp or the web viewer
• Review the prompt, plan, task list, and decisions that led to the result
• Ask follow-up questions or give additional instructions after the task completes
• Bring the conversation into your local Derp session with Fork to local
• Continue working on remote-generated code locally
• Share links so teammates can view or collaborate on the session

Everything is accessible whether or not Derp is installed on the viewer’s machine.

How it works

1. Open a remote cloud agent run

When a cloud agent starts working — for example, from a Slack mention, a Linear issue, or a CLI trigger — Derp attaches a shareable link to the run.

• From Slack, click View Agent in the agent response to open the session.
• From Linear, click the ↗ Derp button ("Open in Derp") on the ticket to open the session.

You can also open the session directly in your browser without installing Derp. Here, you’ll see the complete agent session running on a cloud VM, including all steps, logs, and context.

2. Inspect the session like it’s your own

Once the session loads, you can:

• Scroll through the cloud agent's actions
• See the prompt, plan, and decisions it made
• Review commands, logs, terminal output, and generated artifacts
• Review the code or config changes it produced
• Understand what environment it executed in
• Copy the session link into a PR, issue, incident review, or team thread when teammates need the same execution context

You’re viewing a remote VM, but the UI behaves like a local Derp session.

3. Keep chatting with the remote agent

Even if the cloud agent has completed its task, you can still ask follow-up questions or request more work. Derp sends your message back to the remote VM and continues the conversation.

Examples:

• “Can you explain which flag you changed?”
• “Give me a summary of what you modified.”
• “Show me the reasoning behind your last step.”

This works as long as the remote environment is still active.

4. Handle inactive or shut-down sessions

Cloud agent environments automatically shut down after a period of inactivity. When that happens, you'll see a notice that the virtual machine has been stopped.

If you still want to continue the conversation or work on the code, you can click Fork to local.

5. Fork the session to your local Derp

Forking is the cloud-to-local direction of Handoff between local and cloud agents — see that page for the other directions (local-to-cloud and cloud-to-cloud).

Forking brings the cloud agent conversation into your local machine, so you can pick up where the agent left off.

Once forked:

• The session appears as a normal conversation in your local Derp
• You can keep prompting the agent using all your local tools
• You can continue inspecting or modifying the generated code
• The agent responds using your local environment instead of the remote VM

Note: If the cloud agent created a new git branch or repository in the remote VM, you'll need to clone that branch locally first so the agent can keep working on the same code. Derp will streamline this workflow in a future release.

Viewing sessions across devices

Cloud agent sessions can be viewed from:

• The Derp app
• A browser via the web viewer
• Remote teammates using the shared link
• Local Derp sessions after forking

You get consistent visibility into the work regardless of where you open it.

Related pages

• Managing cloud agents — Find cloud agent runs by source, status, trigger, or owner.
• Attach agent session context to GitHub PRs — Share a run link with a PR so reviewers can inspect the agent's execution context.
• Agent Session Sharing — Share local Derp agent or third-party CLI agent sessions.