<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: RockDesk</title>
    <description>The latest articles on DEV Community by RockDesk (@rockdeskio).</description>
    <link>https://dev.to/rockdeskio</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4251772%2Ff510c1b2-a1de-4f11-be94-bd9aec1c99ba.png</url>
      <title>DEV Community: RockDesk</title>
      <link>https://dev.to/rockdeskio</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/rockdeskio"/>
    <language>en</language>
    <item>
      <title>Let Claude Code operate remote computers as if they were local (Codex and Gemini CLI too)</title>
      <dc:creator>RockDesk</dc:creator>
      <pubDate>Thu, 19 Nov 2026 14:07:39 +0000</pubDate>
      <link>https://dev.to/rockdeskio/let-claude-code-operate-remote-computers-as-if-they-were-local-codex-and-gemini-cli-too-2chc</link>
      <guid>https://dev.to/rockdeskio/let-claude-code-operate-remote-computers-as-if-they-were-local-codex-and-gemini-cli-too-2chc</guid>
      <description>&lt;p&gt;&lt;em&gt;Disclosure: this post is from the RockDesk team. RockDesk is the tool the setup below uses.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Claude Code, Codex and Gemini CLI work well on the machine they run on. This guide lets them operate your other computers and devices the same way:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;run shell scripts on them across networks&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;mount a remote project and edit it in place&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;see the screen through screenshots&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;forward ports&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It works by machine ID, with nothing to open on the router, and takes about five minutes to set up. The other machine can be a Windows PC, a Mac, a Linux server without a screen, a robot or dev board running Linux, or an Android phone (screen, taps and typing).&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Run shell scripts across networks
&lt;/h2&gt;

&lt;p&gt;The other machine can sit behind a home router, on the office network or on a mobile connection. The agent runs commands there the way it runs them locally and gets the real exit code back, so &lt;code&gt;&amp;amp;&amp;amp;&lt;/code&gt;, &lt;code&gt;||&lt;/code&gt; and &lt;code&gt;if&lt;/code&gt; behave as they do over ssh. A local script can be piped in, and long jobs keep running after the call returns.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;rds 123456789 shell -c &lt;span class="s2"&gt;"uptime; df -h /"&lt;/span&gt;
cat deploy.sh &lt;span class="o"&gt;|&lt;/span&gt; rds 123456789 shell -c &lt;span class="s2"&gt;"bash -s"&lt;/span&gt;
rds 123456789 spawn &lt;span class="s2"&gt;"cd ~/proj &amp;amp;&amp;amp; make -j8"&lt;/span&gt;      &lt;span class="c"&gt;# detached: prints the pid and its log file&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;On a Windows machine &lt;code&gt;shell -c&lt;/code&gt; runs PowerShell, so the agent writes PowerShell there.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Mount a remote project and edit it in place
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;rds 123456789 mount :/home/me/project ~/remote-project
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The remote project now looks like an ordinary local folder. The agent's usual file tools, searches, editors and builds work on it directly, and every change is written straight to the remote machine. When it is done: &lt;code&gt;rds 123456789 umount ~/remote-project&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Linux mounts it with FUSE, macOS needs nothing extra, and on Windows the installer brings what is needed and the mount can be a drive letter (&lt;code&gt;Z:&lt;/code&gt;). For one-off transfers there are &lt;code&gt;rds &amp;lt;id&amp;gt; cp&lt;/code&gt; and &lt;code&gt;rds &amp;lt;id&amp;gt; sync&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. See the screen
&lt;/h2&gt;

&lt;p&gt;For apps that have no command line, the agent takes a screenshot, reads it, clicks and types, then takes another screenshot to check the result.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;rds 123456789 screenshot -o shot.png
rds 123456789 click 812 440
rds 123456789 &lt;span class="nb"&gt;type&lt;/span&gt; &lt;span class="s2"&gt;"quarterly report"&lt;/span&gt;
rds 123456789 key Return
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  4. Forward ports
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;rds 123456789 forward 15432:db.internal:5432
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A database, a web UI or a device that only the remote machine can reach is now on &lt;code&gt;127.0.0.1:15432&lt;/code&gt; here. The host name is resolved on the remote side, so names that only exist on that network work. &lt;code&gt;rds 123456789 unforward 15432&lt;/code&gt; stops it.&lt;/p&gt;

&lt;p&gt;There is more: clipboard, file copy and sync, serial ports, USB devices and a VPN to the remote network. Here it is on a Windows PC and on a Mac:&lt;/p&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/VIFOqMNGUW8" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/uddhlpvHFV0" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;h2&gt;
  
  
  How it works, in three sentences
&lt;/h2&gt;

&lt;p&gt;Every machine that runs RockDesk gets a 9-digit ID. The &lt;code&gt;rds&lt;/code&gt; command line hands each command to the RockDesk service on your own machine, which keeps one encrypted connection per peer: direct when it can get through the NAT, through a relay otherwise. Nothing has to be opened on the router and the other machine needs no sshd, and that machine decides who may connect.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: install RockDesk on both machines
&lt;/h2&gt;

&lt;p&gt;Download it from &lt;a href="https://rockdesk.io/#download" rel="noopener noreferrer"&gt;rockdesk.io&lt;/a&gt;. There are builds for Windows, macOS (Apple silicon and Intel), Linux (.deb, x86_64 and arm64) and Android. Install it on the computer your agent runs on &lt;strong&gt;and&lt;/strong&gt; on every computer you want it to work on. New devices start with a free trial.&lt;/p&gt;

&lt;p&gt;Note the 9-digit ID shown on the machine you want to control.&lt;/p&gt;

&lt;p&gt;On a Linux machine without a screen (a server, a robot, a dev board):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo systemctl &lt;span class="nb"&gt;enable&lt;/span&gt; --now rockd   &lt;span class="c"&gt;# starts at boot&lt;/span&gt;
sudo rds status                     &lt;span class="c"&gt;# prints this machine's ID&lt;/span&gt;
sudo rds otp                        &lt;span class="c"&gt;# prints a one-time password&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Step 2: give your agent the skill
&lt;/h2&gt;

&lt;p&gt;The skill is a single file that teaches the agent the &lt;code&gt;rds&lt;/code&gt; commands. It also tells the agent to check that RockDesk is installed and to send you to the download page if it isn't.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Claude Code:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;/plugin marketplace add rockdesk-io/rockdesk-skill
/plugin install rockdesk@rockdesk
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Codex:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;codex plugin marketplace add rockdesk-io/rockdesk-skill
codex plugin add rockdesk@rockdesk
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Gemini CLI:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;gemini extensions install https://github.com/rockdesk-io/rockdesk-skill
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Any other agent that reads agent skills:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx skills add rockdesk-io/rockdesk-skill
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;If you prefer MCP:&lt;/strong&gt; &lt;code&gt;rds mcp&lt;/code&gt; is an MCP server over stdio with 18 tools (shell, spawn, copy, ls, screenshot, click, type, key, scroll, clipboard, port forwarding and more). Screenshots come back as images.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;claude mcp add -s user rockdesk -- rds mcp
codex mcp add rockdesk -- rds mcp
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;rds&lt;/code&gt; is not on the PATH on macOS and Windows. Use &lt;code&gt;/Applications/rockd.app/Contents/MacOS/rds&lt;/code&gt; or &lt;code&gt;C:\Program Files\rockd\rds.exe&lt;/code&gt; there.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: let it in
&lt;/h2&gt;

&lt;p&gt;The machine being controlled decides who gets in, and an ID on its own doesn't get anyone in. Pick whichever suits you:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Click "allow"&lt;/strong&gt; on the other machine when the first command arrives. It covers that one connection.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A one-time password&lt;/strong&gt;, shown on the other machine's home screen (&lt;code&gt;sudo rds otp&lt;/code&gt; on a headless Linux box). It changes after each use.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A fixed password&lt;/strong&gt;: run &lt;code&gt;rds &amp;lt;id&amp;gt; auth&lt;/code&gt; once and it is remembered.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A key pair, like ssh&lt;/strong&gt;: &lt;code&gt;rds key gen&lt;/code&gt; on your machine, then &lt;code&gt;rds authorize "&amp;lt;the public line&amp;gt;"&lt;/code&gt; on the other one. After that you get in with no password.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Mounting folders, port forwarding and the other features can be switched on or off on the other machine.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: ask
&lt;/h2&gt;

&lt;p&gt;Some things to try:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;"123456789 is my build server. Run ./scripts/release.sh there and tell me if anything fails."&lt;/li&gt;
&lt;li&gt;"Mount ~/app from 123456789 and fix the failing test."&lt;/li&gt;
&lt;li&gt;"Take a screenshot of 123456789 and tell me what is open."&lt;/li&gt;
&lt;li&gt;"Forward the Postgres on 123456789 to port 15432 here and list its tables."&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The first command to a machine takes a moment to connect. Later commands reuse the same connection and are almost instant.&lt;/p&gt;

&lt;h2&gt;
  
  
  Staying safe
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;The agent can only reach machines that let it in (step 3).&lt;/li&gt;
&lt;li&gt;The skill tells the agent to say what it will run and wait for your OK before anything destructive or hard to undo: deleting or overwriting files, restarting services, sending messages.&lt;/li&gt;
&lt;li&gt;Clipboard history can contain passwords and codes. The skill tells the agent not to pass it to third-party services unless you ask.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Skill or MCP?
&lt;/h2&gt;

&lt;p&gt;Use whichever you like. The skill works in any agent that can run shell commands, and it also covers things that aren't MCP tools yet: mounting folders, file sync, the VPN, serial ports and USB. MCP gives you native tools in clients that support it, and screenshots arrive as images. You can install both.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Do both machines need to be on the same network?&lt;/strong&gt; No. That's the point of the ID: it works across NATs and between networks, and falls back to a relay when a direct path isn't possible.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does the other machine need a screen?&lt;/strong&gt; No. On headless Linux use the commands from step 1.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Is there a web version?&lt;/strong&gt; Yes, at &lt;a href="https://rockdesk.io/web/" rel="noopener noreferrer"&gt;rockdesk.io/web&lt;/a&gt;, for people. Agents need the &lt;code&gt;rds&lt;/code&gt; command line, which comes with the desktop app.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What does it cost?&lt;/strong&gt; New devices start with a free trial. See &lt;a href="https://rockdesk.io/pricing.html" rel="noopener noreferrer"&gt;pricing&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Links
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;RockDesk: &lt;a href="https://rockdesk.io" rel="noopener noreferrer"&gt;rockdesk.io&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Quickstart: &lt;a href="https://rockdesk.io/quickstart.html" rel="noopener noreferrer"&gt;rockdesk.io/quickstart.html&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;RockDesk for AI agents: &lt;a href="https://rockdesk.io/ai-agents.html" rel="noopener noreferrer"&gt;rockdesk.io/ai-agents.html&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;The skill, the Claude Code plugin, the Codex plugin and the Gemini extension: &lt;a href="https://github.com/rockdesk-io/rockdesk-skill" rel="noopener noreferrer"&gt;github.com/rockdesk-io/rockdesk-skill&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you try it, tell us what you'd like your agent to do on your other machines. We read every comment.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>claude</category>
      <category>mcp</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
