Remote Desktop Testing Linux logo

Remote Desktop Testing Linux

Organization
letta-ai
remote-desktop-testing-linux

Test any GUI app or change on a Daytona Linux (Ubuntu xfce4 + noVNC) remote desktop sandbox. Use to launch a GUI program, sync a local project, take a screenshot, record a video, or share a clickable live-desktop link with a teammate. Generic — the only dependency is Daytona. For Windows, use remote-desktop-testing-windows.

Overview

Publisherletta-ai
Repositoryskills
Skill nameremote-desktop-testing-linux
Stars
144
Forks
25
Bundled files
1
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by letta-ai on GitHub. Read the source before you install it.

Installation

Install the Remote Desktop Testing Linux AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/letta-ai/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/tools/remote-desktop-testing-linux .claude/skills/remote-desktop-testing-linux
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Remote Desktop Testing Linux in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Remote Desktop Testing Linux on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Remote Desktop Testing Linux is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Remote Desktop Testing on Linux

Overview

Generic Daytona Linux desktop sandbox driver. It creates (or reuses) a sandbox running an xfce4 desktop streamed over noVNC, and provides the primitives for visual testing of any GUI app: sync code, run shell commands, launch GUI programs on the live desktop, screenshot, record video, and mint a clickable desktop link a teammate can open to drive the app.

When to Use

  • Demo or visually verify a GUI app (Electron, browser, native X11) on Linux without a local Linux desktop
  • Produce a screenshot + video + clickable live-desktop link for a teammate
  • Debug Linux-specific desktop behavior of a cross-platform app
  • Run throwaway desktop sessions that are fully disposable (stop with cleanup)

Usage

Run the bundled script with Node from the skill directory:

bash
node scripts/remote-desktop.mjs <command> [options]

Credentials: DAYTONA_API_KEY (and optionally DAYTONA_API_URL/DAYTONA_TARGET) from the environment or a dotenv file — ./.env by default, override with --env-path <file>. The script auto-installs @daytona/sdk under ~/.letta/skill-state/remote-desktop-testing-linux/ on first use and remembers the active sandbox id there, so later commands don't need --sandbox.

Typical flow

bash
# 1. Start (or reuse) a desktop sandbox. Default: image daytonaio/sandbox:0.8.0, cpu 2 / mem 4 / disk 5.
node scripts/remote-desktop.mjs start

# 2. (Optional) push a local project to /home/daytona/remote-desktop/workspace
node scripts/remote-desktop.mjs sync --project-path ~/repos/my-app --sync-mode working_tree

# 3. Set up / build with shell commands (runs bash in the sandbox)
node scripts/remote-desktop.mjs shell \
  --command "cd /home/daytona/remote-desktop/workspace && npm install"

# 4. Launch the GUI app on the live desktop and verify its window appeared
node scripts/remote-desktop.mjs launch \
  --command "./my-app --some-flag" --label my-app --wait-window "My App"

# 5. Deliverables: screenshot, video, and a clickable live-desktop link
node scripts/remote-desktop.mjs screenshot --output /tmp/demo.png
node scripts/remote-desktop.mjs record --output /tmp/demo.mp4 --mp4 --duration 12
node scripts/remote-desktop.mjs preview

Always confirm the result visually (open the screenshot, or check windows / --wait-window) before reporting success — never report success from process existence alone. When sharing with a teammate, send the desktopUrl from preview (signed noVNC link, expires ~6h; re-run preview to refresh). Pass --port <n> to preview to also mint a signed URL for an app's HTTP port.

Commands

CommandWhat it does
startCreate/reuse a sandbox and start the desktop. --fresh forces a new one.
syncSync --project-path to /home/daytona/remote-desktop/workspace (git_archive = committed HEAD, working_tree = uncommitted too; preserves remote node_modules).
shell --command SHRun a bash command. --timeout <s> for long ones.
launch --command CMDLaunch a GUI command on the xfce4 desktop (detached, DISPLAY set, logged to /home/daytona/remote-desktop/launch-<label>.log). --wait-window <regex> verifies a matching window title appears.
windowsList visible desktop windows.
screenshotSave a PNG of the full desktop locally.
previewPrint signed desktopUrl (noVNC), plus appUrl if --port given.
recordRecord the live desktop via Playwright + local Chrome (--duration <s>, --mp4).
recording-start/stop/downloadNative Daytona recording (installs ffmpeg in-sandbox on first use).
snapshot --snapshot <name>Bake the sandbox into a snapshot (stops, snapshots, restarts).
cleanupStop the active sandbox.

Sizing and snapshots

  • Daytona's default Linux sandbox is tiny (cpu 1 / mem 1 / disk 3GB). This skill creates from the desktop-capable image daytonaio/sandbox:0.8.0 with --cpu 2 --memory 4 --disk 5 by default; raise them for big projects (--cpu 4 --memory 8 --disk 10). Disk is capped at 10GB per sandbox.
  • resources cannot be combined with a snapshot — --snapshot <name> creates with whatever size was baked in. Use snapshot to bake a prepared box (deps installed, caches warm) so future start --snapshot <name> runs skip setup. Revert throwaway edits before baking.

Gotchas

  • Electron/Chromium apps need --no-sandbox inside the container, and often --disable-gpu --disable-dev-shm-usage too; put those flags in your launch --command.
  • launch runs the command detached with DISPLAY pointed at the live desktop (detected from /tmp/.X11-unix, falls back to :0). Check the launch log via shell if nothing appears.
  • For the shareable link, send desktopUrl (the interactive desktop), not a raw app-port URL — the app URL only serves HTTP and shows nothing of the desktop.
  • record runs Playwright locally: it resolves playwright/playwright-core from --project-path first, else auto-installs playwright-core into skill state, and drives the local Chrome binary (--chrome-path, default macOS Chrome). --mp4 needs local ffmpeg.
  • The base image has xfce4-terminal, chromium, and xeyes available for quick desktop sanity checks (e.g. launch --command "xfce4-terminal" --wait-window Terminal).

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Remote Desktop Testing Linux AI skill do?

Test any GUI app or change on a Daytona Linux (Ubuntu xfce4 + noVNC) remote desktop sandbox. Use to launch a GUI program, sync a local project, take a screenshot, record a video, or share a clickable live-desktop link with a teammate. Generic — the only dependency is Daytona. For Windows, use remote-desktop-testing-windows.

Why use Remote Desktop Testing Linux on TypingMind?

Because you install it once and use it with any model. Remote Desktop Testing Linux is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Remote Desktop Testing Linux in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/letta-ai/skills/tree/main/tools/remote-desktop-testing-linux. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Remote Desktop Testing Linux?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Remote Desktop Testing Linux?

As many as you like. As long as a model supports skills, you can use Remote Desktop Testing Linux with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Remote Desktop Testing Linux AI skill free?

It is published on GitHub by letta-ai. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇