What Is 9Remote? Remote Terminal, Desktop, Files, and AI Coding from Your Phone

What Is 9Remote? A Simple Guide to decolua/9remote for Remote Terminal, Desktop and AI Coding

Image extracted from GitHub’s Open Graph preview for the decolua/9remote repository. This image is not SVG.¹

Quick summary

9Remote is a remote access tool that lets you control your Mac/Linux/Windows terminal, desktop and file explorer from a phone or browser. The official repository describes it as “Terminal in Your Pocket”: your computer’s terminal, remote desktop and file explorer accessible from any phone or browser, anywhere.²

In plain terms: run 9remote on your development machine, scan a QR code with your phone, then use the host’s terminal, desktop and file explorer through a mobile-friendly browser interface. You can run Claude Code, Codex CLI, Cursor, OpenClaw or any other CLI tool on the host and control it from your phone.³

9Remote is different from 9Router. 9Router is an AI provider router/proxy; 9Remote is a remote access workspace. Used together, you can run AI coding tools on your dev machine, route model calls through 9Router, and control the whole workflow from your phone with 9Remote.

What problem does 9Remote solve?

Traditional remote access often requires SSH keys, firewall rules, port forwarding, VPNs, IP whitelisting, desktop remote apps or poor mobile UX. The 9Remote README lists these pain points and positions 9Remote as a “one command, scan QR, done” tool.⁴

Basic flow:

Mac/Linux/Windows development machine
  ↓ run 9remote
Cloudflare Quick Tunnel or LAN
  ↓
Phone / tablet / browser
  ↓
Terminal + Remote Desktop + File Explorer + Code Editor

The goal is to turn a phone into a developer workspace that can run commands, inspect logs, edit files, commit changes, test local sites and operate AI coding agents.

What 9Remote is not

Important license/status note: the GitHub README says the source code is not open-source yet and the license is currently Proprietary — All Rights Reserved, even though the website contains a line saying “Open source · MIT License.” This article treats the README as the authoritative repo status: the npm package is free during development, source is not yet public, and MIT release is planned after a community milestone.⁵⁶

What stands out in the decolua/9remote repo?

The GitHub page describes decolua/9remote as “Terminal in Your Pocket,” used to control Claude Code, Codex, Gemini CLI and Mac/Linux/Windows machines from any phone or browser. At the time referenced, the repo showed around 259 stars and only a few commits.⁷

README highlights:

• install with npm install -g 9remote;
• run with 9remote;
• scan QR to pair a device;
• no port forwarding, firewall rules or signup;
• Cloudflare Quick Tunnel for outbound-only connectivity;
• remote terminal, desktop, file explorer, code editor and Git integration;
• local sites proxy for ports such as localhost:3000 and localhost:5173;
• AI integration with Claude Code, Codex, Cursor, OpenClaw and any CLI tool.⁸

Quick installation

The Getting Started docs list Node.js 18+ and macOS, Linux or Windows as requirements.⁹

Install globally:

npm install -g 9remote

Verify:

9remote --version

Start server:

9remote

The docs say 9Remote will:

1. Start a local server on port 2208.
2. Create a secure Cloudflare tunnel.
3. Generate a QR code for connection.¹⁰

Then scan the QR code from your phone to connect.¹¹

Connect with QR or key

Two connection options:

Option 1: Scan QR
Option 2: Enter key manually at https://9remote.cc/login

The README says 9Remote generates two keys on first run:

The README says keys are not stored on 9Remote servers after the session ends.¹²

Main features

Remote Terminal

Terminal is the core feature. The docs say 9Remote Terminal gives complete terminal access through the browser, as if you were sitting in front of your computer.¹³

Key capabilities:

• multiple terminal sessions;
• copy/paste between device and terminal;
• themes such as Default, Light, Dracula, Monokai and Solarized;
• mobile keyboard with Ctrl, Alt, Shift, Esc, arrow keys, Tab and F1–F12;
• sessions continue in background while switching tabs;
• useful for shell, Git, build, deploy, Claude Code and Codex CLI.

Example phone workflow:

cd ~/project
git status
npm test
claude
codex "fix the failing checkout test"

The docs recommend using tmux or screen for more persistent shell workflows.¹⁴

Remote Desktop

Remote Desktop lets you view and control the host screen from a browser. The docs list real-time screen streaming, tile-based rendering, quality adjustment, mouse control and keyboard input.¹⁵

On macOS, the README says Remote Desktop needs:

System Settings → Privacy & Security → Screen Recording
System Settings → Privacy & Security → Accessibility

Then enable:

TUI menu → Remote Desktop → Toggle ON

Use Remote Desktop when you need GUI access, browser checks, settings panels or visual debugging.

Limitations from the docs:

• no audio streaming;
• video playback may be choppy;
• not suited for high-FPS gaming;
• multi-monitor support shows primary monitor only;
• performance depends on network speed, host CPU, resolution and screen changes.¹⁶

File Explorer and Code Editor

The docs say File Explorer lets you browse the file system, edit code with syntax highlighting and perform Git operations from the browser.¹⁷

Capabilities:

• file tree navigation;
• breadcrumbs and recent workspaces;
• built-in editor with 20+ language syntax highlighting;
• line numbers, auto-indentation and find/replace;
• create, rename, delete and copy files/folders;
• view Git status, diffs, commit and push;
• search files by name.

Editor shortcuts:

Ctrl+S  Save
Ctrl+F  Find
Ctrl+H  Find and replace
Ctrl+Z  Undo
Ctrl+Y  Redo
Tab     Indent
Shift+Tab Outdent

Limitations from the docs:

• binary files such as images/videos are not supported;
• very large files over 10MB are not suitable;
• upload/download is listed as coming soon;
• large folders may be slow.¹⁸

Local Sites Proxy

The README says 9Remote can auto-detect local development servers and proxy them through the tunnel for phone access.¹⁹

Example:

http://localhost:3000  →  https://<tunnel>/proxy/3000/
http://localhost:5173  →  https://<tunnel>/proxy/5173/

Use it for:

• responsive design testing on real devices;
• mobile UI debugging without USB;
• sharing WIP builds;
• testing local frontend apps.

AI coding from phone

The README and FAQ say 9Remote works with Claude Code, OpenAI Codex CLI, Cursor, OpenClaw and any CLI tool running in a terminal.³

Example:

cd ~/project
claude
# or
codex "review this PR and suggest fixes"
# or
cursor-agent

The AI tool still runs on the host machine. The phone is the control surface.

9Remote vs 9Router

Combined flow:

Phone
  ↓ 9Remote
Host running Claude Code/Codex
  ↓ API endpoint
9Router
  ↓
Real provider/model

Comparison with SSH, VPN, TeamViewer and Chrome Remote Desktop

The README compares 9Remote with Claude Remote, TeamViewer, Chrome Remote Desktop and Termius. According to that comparison, 9Remote combines terminal, remote desktop, file explorer, code editor, Git integration, QR login, auto tunnel, mobile optimization, AI integration and no-account access.²⁰

Practical view:

Technical architecture

The README lists the main tech stack:²¹

Simplified flow:

9remote CLI
  ↓
Local server :2208
  ↓
Cloudflare Quick Tunnel or LAN
  ↓
Web/mobile client
  ↓
Terminal / desktop / file explorer

The README says 9Remote includes a LocalFirstAdapter that races LAN versus tunnel and uses the faster connection; if phone and host are on the same Wi-Fi, traffic can stay local.²²

Supported platforms

According to the README:

Host where the 9Remote agent runs:

• macOS Intel + Apple Silicon
• Linux x64, arm64
• Windows x64

Client where you connect from:

• Chrome, Safari, Firefox, Edge
• iOS 14+
• Android 8+
• Tauri desktop app for macOS, Windows and Linux²³

Practical usage guide

1. Start 9Remote

npm install -g 9remote
9remote

2. Connect from phone

Scan the QR code or open:

https://9remote.cc/login

and enter the access key.

3. Open terminal

cd ~/project
git status
npm run dev

4. Open a local site on phone

If your app runs at:

http://localhost:3000

9Remote can expose it as:

https://<tunnel>/proxy/3000/

5. Use AI coding tools

claude
# or
codex "fix auth bug and run tests"

6. Make a quick file edit

Open File Explorer, select a project, edit a file, save with Ctrl+S, inspect diff, commit and push.

Personal setup guide

Minimal setup:

# Install Node.js 18+
node -v

# Install 9Remote
npm install -g 9remote

# Run
9remote

Recommended practices:

• Use your personal machine first.
• Do not run as root/admin unless necessary.
• Use terminal-only mode on slow networks.
• Use LAN mode on the same Wi-Fi.
• Enable Remote Desktop only when needed.
• Stop desktop streaming when done.
• Review credentials and permissions before running AI coding tools remotely.

Team rollout guide

Phase 1: individual use

• Each developer installs 9Remote on their own machine.
• Use it for terminal, file explorer and local dev server access.
• Pair only personal trusted devices.
• Do not share QR codes or keys.

Phase 2: on-call workflow

• Use it for urgent log checks, restarts and diagnostics.
• Combine with tmux for persistent sessions.
• Define which commands are allowed from phone.
• Do not deploy production from phone without approval.

Phase 3: mobile AI coding

• Run Claude Code or Codex on the dev machine.
• Use 9Router if provider fallback/routing is needed.
• Use 9Remote to prompt, review diffs and run tests.
• Do not let agents run destructive commands from phone without control.

Phase 4: security policy

• Define who can pair devices.
• Revoke devices when a phone is lost.
• Keep Remote Desktop off when not needed.
• Do not store access keys in chats or public notes.
• Avoid using it on highly sensitive machines without policy.
• Control file permissions for the user running 9Remote.

Security notes

9Remote is a remote access tool. Once enabled, approved devices can access terminal, desktop and file system features. Treat it as sensitive infrastructure.

Checklist:

• Pair only devices you control.
• Never send QR codes to others.
• One-time keys expire after 30 minutes, but regenerate if exposed.
• Manage pending/rejected devices from the TUI menu.
• Do not run 9Remote as an overly privileged user unless required.
• Turn off Remote Desktop when not in use.
• Do not leave the paired phone unlocked.
• Revoke a device if it is lost.
• Avoid using on machines with production secrets unless policy allows it.
• If using Cloudflare tunnel, understand that the tunnel creates a reachable URL, even though access still needs keys/pairing.
• For companies, check policies for remote access, tunnels and data exfiltration.

The README says 9Remote uses Pair Device approval, outbound-only Cloudflare tunnel, does not collect terminal output/files/screen data, and does not store keys after the session ends.²⁴ Those claims are useful, but operators still need device and permission hygiene.

Known limitations

From the README and docs:

• Source code is not currently public; MIT release is planned after a community milestone.⁵
• Remote Desktop on macOS requires Screen Recording and Accessibility permissions.²⁵
• Remote Desktop is not suitable for audio streaming, video playback, high-FPS gaming or complex multi-monitor use.¹⁶
• File Explorer is not suitable for binary files, very large files over 10MB, multi-file selection or upload/download according to current docs.¹⁸
• Cloudflare tunnel requires internet; tunnel failures require checking connectivity or cloudflared.²⁶
• Mobile editing is best for quick fixes, not large refactors.
• Website and README currently conflict on open-source/license language; check the repository before claiming it is fully open source.⁵⁶

When should you use 9Remote?

Use it when:

• you want to access your dev machine from phone;
• you need Claude Code/Codex/Cursor from anywhere;
• you need an emergency bug fix without a laptop;
• you want to test a local dev server on a phone;
• you want terminal, file explorer and desktop in one tool;
• you want to avoid SSH/VPN/port forwarding;
• you need quick on-call access.

Be cautious when:

• company policy forbids self-managed tunnels or remote access tools;
• you require full source/auditability now;
• you need high-quality remote desktop for video or games;
• production access needs enterprise controls;
• paired client devices are not under your control;
• you need offline access but are not on the same LAN.

FAQ

What is 9Remote?

9Remote is a remote access tool for controlling a Mac/Linux/Windows machine’s terminal, desktop and file explorer from a phone or browser, using QR pairing and automatic Cloudflare tunnel setup.²²⁷

Is 9Remote open source?

According to the GitHub README, the source code is not open-source yet and the current license is Proprietary; the npm package is free during development, and an MIT release is planned after a community milestone.⁵ The website says “Open source · MIT License,” but this article prioritizes the repository status because it contains the explicit license section.⁶

Do I need port forwarding?

No. The README says 9Remote uses Cloudflare Quick Tunnel as an outbound-only connection, working behind NAT, corporate firewalls, mobile hotspots and VPNs.²⁸

Can I use Claude Code or Codex from my phone?

Yes. 9Remote does not run AI on the phone; it lets you control the host terminal where Claude Code, Codex CLI, Cursor or OpenClaw is running.³

What is the default port?

The docs say 9Remote starts a local server on port 2208, and the README says 9remote ui opens the browser dashboard at localhost:2208.¹⁰²⁹

Is 9Remote secure?

The README says 9Remote uses Pair Device approval, 30-minute one-time QR keys, outbound-only Cloudflare tunnel and does not collect terminal output, files or screen data.²⁴ Still, because this is a remote access tool, you need device management, host-user permissions and internal policy controls.

Conclusion

decolua/9remote is a developer-oriented remote workspace for people who want to code from anywhere. Its strength is combining terminal, remote desktop, file explorer, code editor, Git integration, local sites proxy and AI coding workflows in a phone/browser-friendly interface.

For beginners, the path is simple: npm install -g 9remote, run 9remote, scan QR and open the terminal. For AI coding users, 9Remote is useful because Claude Code, Codex or Cursor can run on the dev machine while the phone acts as the control surface. For teams, treat it as a sensitive remote-access tool: define device-pairing policy, revoke lost devices, manage host permissions, and review tunnel usage before using it on production or confidential machines.

References

Footnotes

1. GitHub Open Graph preview image for decolua/9remote. https://opengraph.githubassets.com/9remote-guide/decolua/9remote ↩

2. 9Remote README, project overview. https://raw.githubusercontent.com/decolua/9remote/main/README.md ↩ ↩²

3. 9Remote README, AI coding tools FAQ. https://raw.githubusercontent.com/decolua/9remote/main/README.md ↩ ↩² ↩³

4. 9Remote README, “Why 9Remote?” https://raw.githubusercontent.com/decolua/9remote/main/README.md ↩

5. 9Remote README, License and development status. https://raw.githubusercontent.com/decolua/9remote/main/README.md ↩ ↩² ↩³ ↩⁴

6. 9Remote official website, footer/CTA text mentioning “Open source · MIT License.” https://9remote.cc/ ↩ ↩² ↩³

7. GitHub. decolua/9remote. https://github.com/decolua/9remote ↩

8. 9Remote README, Key Features. https://raw.githubusercontent.com/decolua/9remote/main/README.md ↩

9. 9Remote Docs, Getting Started requirements and setup. https://docs.9remote.cc/getting-started ↩

10. 9Remote Docs, Start Server. https://docs.9remote.cc/getting-started ↩ ↩²

11. 9Remote Docs, Connect section. https://docs.9remote.cc/getting-started ↩

12. 9Remote README, First Run & QR Login. https://raw.githubusercontent.com/decolua/9remote/main/README.md ↩

13. 9Remote Docs, Terminal. https://docs.9remote.cc/features/terminal ↩

14. 9Remote Docs, Terminal tips about tmux/screen. https://docs.9remote.cc/features/terminal ↩

15. 9Remote Docs, Remote Desktop. https://docs.9remote.cc/features/remote-desktop ↩

16. 9Remote Docs, Remote Desktop limitations. https://docs.9remote.cc/features/remote-desktop ↩ ↩²

17. 9Remote Docs, File Explorer. https://docs.9remote.cc/features/file-explorer ↩

18. 9Remote Docs, File Explorer limitations. https://docs.9remote.cc/features/file-explorer ↩ ↩²

19. 9Remote README, Local Sites Proxy. https://raw.githubusercontent.com/decolua/9remote/main/README.md ↩

20. 9Remote README, comparison table. https://raw.githubusercontent.com/decolua/9remote/main/README.md ↩

21. 9Remote README, Tech Stack. https://raw.githubusercontent.com/decolua/9remote/main/README.md ↩

22. 9Remote README, LocalFirstAdapter / LAN note. https://raw.githubusercontent.com/decolua/9remote/main/README.md ↩

23. 9Remote README, supported platforms. https://raw.githubusercontent.com/decolua/9remote/main/README.md ↩

24. 9Remote README, security FAQ. https://raw.githubusercontent.com/decolua/9remote/main/README.md ↩ ↩²

25. 9Remote README, Remote Desktop Setup on macOS. https://raw.githubusercontent.com/decolua/9remote/main/README.md ↩

26. 9Remote README, Troubleshooting. https://raw.githubusercontent.com/decolua/9remote/main/README.md ↩

27. 9Remote Docs, Introduction. https://docs.9remote.cc/ ↩

28. 9Remote README, Cloudflare Quick Tunnel / no port forwarding FAQ. https://raw.githubusercontent.com/decolua/9remote/main/README.md ↩

29. 9Remote README, CLI commands. https://raw.githubusercontent.com/decolua/9remote/main/README.md ↩