Privacy

Your terminal, on your phone.

Keep the same session running on your computer and open it on your phone when you leave the desk.

Works well for Claude Code, Gemini CLI, and anything else you run in a terminal.

How it works
➜ ~/projects/app git status
On branch main
Changes not staged for commit:
  modified: src/engine.ts
➜ ~/projects/app
>SHELL-MIRROR CONNECTED sensors
➜ ~/projects/app git status
On branch main
Changes not staged...
  modified: src/engine.ts

Not a separate agent view. Not a reduced control panel. >shell-mirror shows the terminal session you already have.

Same session

You do not start over on mobile. You continue the terminal that is already running.

Real terminal view

What is on your terminal is what you see on your phone. Useful for long runs, logs, prompts, and command-line tools that do not fit into a simplified remote UI.

Private by design

Your terminal stays on your own machine. Your phone connects to your session instead of replacing it with a separate mobile workflow.

Remote control is useful. Sometimes you want the real thing.

A lot of tools now let you check or steer a coding session from your phone. That is useful until you need the actual terminal: the real output, the real prompt, the real state, the real tools.

>shell-mirror is for that. It gives you a simple way to carry your existing terminal session with you instead of switching to a reduced version of it.

Good when you need to

smart_toy
Check on Claude Code while away from the desk
code
Continue a Gemini CLI session without restarting it
monitoring
Watch logs, builds, installs, or long commands
content_copy
Copy output or send one more command on the go
visibility
Keep an eye on a machine without opening a full remote desktop setup

Your terminal stays yours

>shell-mirror is a personal tool. It is meant to give you access to your own terminal session from your own phone.

Your commands still run on your machine. Your files stay where they already are. The point is not to move your work somewhere else. The point is to keep your place.

How it works

1 terminal

Start >shell-mirror on your computer

Install and run the agent where your terminal session is already going.

2 login

Sign in

Connect your phone and computer to the same session with your Google account.

3 smartphone

Open your session on your phone

Pick up where you left off. Same terminal, same output, same state.

That's it.

Why people use this instead of a built-in remote mode

Built-in remote tools can be fine for narrow workflows. >shell-mirror is better when you want access to the terminal itself, not just a product-specific control layer.

check_circle

Same sessionThe same terminal session, not a separate mobile workflow

check_circle

Multiple toolsSupport for more than one CLI tool

check_circle

Personal setupA personal setup tied to your own machine

check_circle

Direct accessLess abstraction between you and the shell