Agent skill

Working Across Computers

by letta-ai in letta-ai/letta-code

Guides work across Cloud, local, and other available computers, including teleporting conversations, running remote subagents, and transferring files.

Apache-2.0Auto-check passedAgent Workflows

Install Working Across Computers

skills CLI
$ npx skills add letta-ai/letta-code --skill working-across-computers -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install letta-ai/letta-code working-across-computers --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/letta-ai/letta-code.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/skills/builtin/working-across-computers .claude/skills/working-across-computers && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
working-across-computers
GitHub stars
3.6k
Token cost
~1.4k tokens
SKILL.md length
617 words
Files
3 (incl. references, assets)
Skills in repo
25
Repo updated
First seen
Licence
Apache-2.0

At a glance

Guides work across Cloud, local, and other available computers, including teleporting conversations, running remote subagents, and transferring files.

  • Tasks that involve Subagents
  • SKILL.md covers Discover access before…, Choose where to work, Move this conversation and Transfer files to or from Cloud, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Working Across Computers is an agent skill from letta-ai/letta-code. 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.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files and assets (for example `references/connect-a-computer-for-remote-access.md`).

It sits in Agent Workflows, covering Subagents. It works with Letta. The repository describes itself as: Stateful agents that are like people, with memory, identity, and the ability to learn and adapt. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Subagents

Example prompts

  • “s laptop or another machine”
  • “Use the working-across-computers skill to guide work across Cloud, local, and other available computers, including teleporting conversations…”
  • “/working-across-computers”

What it can do on your machine

Read from SKILL.md and the folder at commit d31b879. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Working Across Computers loads about 1.4k tokens when it runs, and up to ~2.4k if it reads all its reference files. Until then it costs about 104 tokens; SKILL.md has 617 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~104
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from letta-ai/letta-code at commit d31b879, republished under its Apache-2.0 licence (© letta-ai). 617 words, ~1,410 tokens.

Download SKILL.mdSave it as .claude/skills/working-across-computers/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
working-across-computers
description
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.

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. 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.
IntentMechanism
Run work elsewhere while staying hereAgent
Bring a remote file into a Cloud conversationRemote agent: sandbox upload
Put a Cloud file onto another computerRemote agent: sandbox download
Continue this conversation elsewhereteleport

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.

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>

With exactly one online Desktop, open with Remote Access enabled, you can use the shortcut:

bash
letta teleport local
Show full SKILL.md (252 more words)Show less

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.

© letta-ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references, assets) in src/skills/builtin/working-across-computers of letta-ai/letta-code.

  • SKILL.md
  • assets/allow-remote-access-from-desktop.png
  • references/connect-a-computer-for-remote-access.md

Open the folder on GitHubat commit d31b879

Compare with similar skills

Working Across Computers next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Working Across Computers compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Working Across Computers this skillletta-ai/letta-code3.6k—~1.4kAutomated safety check: PassApache-2.0
Claude Code Agent Developmentanthropics/claude-plugins-official38k7 repos~2.8kAutomated safety check: PassApache-2.0
Subagent Driven DevelopmentAsvarox/allkaraoke26137 repos~1.2kAutomated safety check: PassNone
Dispatching Parallel Agentsultralisp/ultralisp25840 repos~1.5kAutomated safety check: PassNone
Paseo Advisor Second Opiniongetpaseo/paseo20k1 repos~756Automated safety check: PassCustom licence
Task Observerrebelytics/one-skill-to-rule-them-all3.2k1 repos~11kAutomated safety check: PassCC-BY-4.0

Similar skills

  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed
  • Subagent Driven Development

    Asvarox/allkaraoke

    A skill your agent uses when executing implementation plans with independent tasks in the current session

    261 GitHub starsUsed in 37 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • Dispatching Parallel Agents

    ultralisp/ultralisp

    A skill your agent uses when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

    258 GitHub starsUsed in 40 repos~1.5k tokens
    Agent WorkflowsAuto-check passed
  • Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.

    20k GitHub starsUsed in 1 repo~756 tokens
    Agent WorkflowsAuto-check passed
  • Task Observer

    rebelytics/one-skill-to-rule-them-all

    Monitors task execution for skill improvement opportunities.

    3.2k GitHub starsUsed in 1 repo~11k tokens
    Agent WorkflowsAuto-check passed
  • O2 Review Loop

    openobserve/openobserve

    Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.

    22k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from letta-ai/letta-code

All 25 skills in this repo
  • Creating Skills

    letta-ai/letta-code

    Guide for creating effective skills. An agent skill from letta-ai/letta-code.

    3.6k GitHub stars~4.6k tokensUpdated today
    Auto-check passed
  • Generating Mod Envs

    letta-ai/letta-code

    Generates and reviews mod learning env JSON files for Letta Code local mods.

    3.6k GitHub stars~1.5k tokensUpdated today
    Auto-check passed
  • Initializing Memory

    letta-ai/letta-code

    Comprehensive guide for initializing or reorganizing agent memory.

    3.6k GitHub stars~4.8k tokensUpdated today
    Auto-check passed
  • Self Configuration

    letta-ai/letta-code

    Inspect or modify Letta Code's own memory, model, context window, system prompt, compaction, permissions, toolsets, mods, skills, channels, schedules, agent secrets, and local runtime settings.

    3.6k GitHub stars~7k tokensUpdated today
    Auto-check passed
  • Browser Use

    letta-ai/letta-code

    Control a real browser to navigate pages, click, type, fill forms, inspect rendered UI, take screenshots, or record video.

    3.6k GitHub stars~3.3k tokensUpdated today
    Auto-check passed
  • Creating Mods

    letta-ai/letta-code

    Creates and edits trusted local Letta Code mods, including tools, slash commands, local-only model providers, lifecycle/turn events, scoped conversation helpers, panels, and capability-gated behavior.

    3.6k GitHub stars~2.5k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Working Across Computers

What does Working Across Computers do?

Guides work across Cloud, local, and other available computers, including teleporting conversations, running remote subagents, and transferring files. Working Across Computers is an agent skill from letta-ai/letta-code. Guides work across Cloud, local, and other available computers, including teleporting conversations, running remote subagents, and transferring files.

When should I use Working Across Computers?

Working Across Computers fits situations like: tasks that involve Subagents.

How do I install Working Across Computers in Claude Code?

Run `npx skills add letta-ai/letta-code --skill working-across-computers -a claude-code`. Or copy the skill folder (src/skills/builtin/working-across-computers in letta-ai/letta-code) into .claude/skills/working-across-computers in your project. Claude Code loads it when a task matches its description.

How do I install Working Across Computers in Codex?

Run `npx skills add letta-ai/letta-code --skill working-across-computers -a codex`. Or copy the skill folder (src/skills/builtin/working-across-computers in letta-ai/letta-code) into .agents/skills/working-across-computers in your project. Codex loads it when a task matches its description.

Can I use Working Across Computers in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add letta-ai/letta-code --skill working-across-computers -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/working-across-computers, .gemini/skills/working-across-computers, .github/skills/working-across-computers and .opencode/skills/working-across-computers in your project.

What does Working Across Computers need to run?

SKILL.md names no scripts, command-line tools or credentials: Working Across Computers is instructions for the agent only.

Does Working Across Computers access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Working Across Computers safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Working Across Computers use?

Working Across Computers is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Working Across Computers use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 999 tokens, read only when the agent opens those files.

What are the alternatives to Working Across Computers?

Skills that share tags, products or a category with Working Across Computers: Claude Code Agent Development (anthropics/claude-plugins-official, 38k stars), Subagent Driven Development (Asvarox/allkaraoke, 261 stars), Dispatching Parallel Agents (ultralisp/ultralisp, 258 stars) and Paseo Advisor Second Opinion (getpaseo/paseo, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Working Across Computers?

letta-ai (a GitHub organization) maintains it in letta-ai/letta-code, which has 3,562 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 10, 2026.

Source: letta-ai/letta-code on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.