Working Across Computers
Guides work across Cloud, local, and other available computers, including teleporting conversations, running remote subagents, and transferring files. Load when a request needs the user's laptop or another machine's files, apps, or tools; when connecting a computer; or when moving or delegating work between local and Cloud in either direction, including running Cloud subagents from local.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Working Across Computers when an AI agent needs a reusable SKILL.md workflow for this job: Guides work across Cloud, local, and other available computers, including teleporting conversations, running remote subagents, and transferring files. Load when a request needs the user's laptop or another machine's files, apps, or tools; when connecting a computer; or when moving or delegating work between local and Cloud in either direction, including running Cloud subagents from local.
When not to use it
Skip Working Across Computers when the task is outside the writing category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/working-across-computers # Save SKILL.md to ~/.claude/skills/working-across-computers/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/working-across-computers/SKILL.md. For a shared project, commit the folder at .claude/skills/working-across-computers/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Working Across Computers skill for this task: Use Working Across Computers when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Working Across Computers
## Discover access before declaring a limitation
The current filesystem is not the full set of computers you can use. When a request needs another computer, run `letta teleport list`. If a suitable computer is available, delegate there; otherwise follow the [connection instructions](references/connect-a-computer-for-remote-access.md). Do not infer that another computer is inaccessible merely because you are running in Cloud.
## Choose where to work
- When running in Cloud, prefer staying there and delegating local work to subagents on the relevant computer. - If the user explicitly asks to move this conversation locally or elsewhere, teleport it. - Moving a conversation that started locally into Cloud is a normal workflow: transfer needed files first, then teleport.
| Intent | Mechanism | |---|---| | Run work elsewhere while staying here | `Agent` | | Bring a remote file into a Cloud conversation | Remote agent: `sandbox upload` | | Put a Cloud file onto another computer | Remote agent: `sandbox download` | | Continue this conversation elsewhere | `teleport` |
Conversation history and agent memory follow the conversation. Files, working directories, installed tools, credentials, and running services belong to each computer; teleporting does not copy the workspace.
For remote subagents, set `computer` and pass source paths and destination conversation IDs explicitly. Use the `Agent` tool definition for invocation and resume options.
If the user wants to connect a new computer, `letta teleport list` has no suitable target, or the requested local machine is missing or unreachable, read [Connect a computer for remote access](references/connect-a-computer-for-remote-access.md).
## Keep active Monitors on their computer
A Monitor belongs to the computer where it started. While this conversation has an active Monitor, use a subagent on the requested computer instead of teleporting the parent conversation. If the user explicitly insists on moving the parent conversation, explain that they must stop the Monitor before teleporting the parent conversation; do not retry teleport while the Monitor remains active.
## Move this conversation
**Run the teleport handoff alone as the final tool call.** After success, do not poll or run more source-side tools; the same conversation resumes at the destination automatically. Set the working directory and check required setup there. If teleport fails, stay on the source and resolve the error before retrying. The Cloud sandbox remains available while you work elsewhere.
### Local → Cloud
Upload any files needed in Cloud:
```bash letta sandbox upload <local-path> ```
Keep the returned paths, repository/branch, and next action in context, then create or resume this conversation's Cloud sandbox:
```bash letta teleport cloud ```
### Cloud → other computers
List available computers:
```bash letta teleport list ```
Have a remote subagent download any needed files and verify completion before moving. Use a returned computer name, device ID, or connection ID:
```bash letta teleport <computer> ```
## Transfer files to or from Cloud
Run upload where the local file exists; run download where the local copy should be saved.
```bash # Use the executing conversation's Cloud sandbox letta sandbox upload <local-path> letta sandbox download <sandbox-path> --to <local-path>
# Explicit Cloud conversation (sandboxes are per-conversation) letta sandbox upload <local-path> --conversation <destination-conversation-id> letta sandbox download <sandbox-path> \ --conversation <source-conversation-id> --to <local-path>
# An agent's main/default conversation letta sandbox upload <local-path> --agent <agent-id> letta sandbox download <sandbox-path> --agent <agent-id> --to <local-path> ```
- `--agent` alone selects that agent's main/default conversation. Concrete `--conversation` IDs resolve their owning agent. - Target flags override the executing session without changing its identity. Do not replace the subagent's identity environment variables with the parent's. - The executing computer's credentials must authorize access to the target. - Commands return JSON. Use the exact upload path returned; never reconstruct it from the filename. - Download sources must be under `/root/downloads`; `--to` selects the destination path on the receiving computer. Without `--to`, download saves under the source file's basename. - Transfer files directly, not as base64 or file contents through model messages. Return the path and destination IDs; verify received contents or checksums. - These commands transfer files to/from Cloud sandboxes, not arbitrary remote filesystems. No sandbox ID or separate wake command is needed.
## Share a live view of a Cloud sandbox desktop
When someone outside chat (Slack, email, a teammate) needs to watch or drive the sandbox desktop, mint a viewer link:
```bash letta sandbox desktop-link # this conversation's sandbox letta sandbox desktop-link --conversation <conv-id> # another Cloud conversation ```
It prints `{ url, expiresAt }`. The URL opens the desktop in a browser tab with no sign-in. Anyone holding it can view and control the desktop until `expiresAt` (about one hour), so hand it to the person who asked, in a private message or thread, and say when it expires. Mint a new one if it lapses. The sandbox must be a ready Linux VM with desktop support; the command reports the server's error otherwise.
Intended uses
- Use Working Across Computers when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.