The easiest way to understand Redock is to connect it to a real machine you already use for development. Start with the least surprising path: your iPhone or iPad and your Mac on the same Wi-Fi. That first connection teaches you almost everything important: how Redock reaches a host, how the terminal behaves on a phone, how Projects and Actions reduce repeated typing, and why tmux matters once the phone is no longer a stable desktop connection.
The short answer: enable SSH on the machine that already has your repository and tools, connect Redock to it, save the project directory, add a few common Actions, then turn on tmux for recoverable work. Claude Code, Codex, OpenCode, Git, Node, Python, Rust, package managers, and your build tools should already exist on that remote machine. Redock gives you the mobile workbench around that environment.
Start on the same network
On macOS, turn on Remote Login in System Settings. That enables the standard SSH server. Then add a Host in Redock. If local discovery finds your Mac, use the prefilled address and port. If not, enter the Mac LAN address, usually something like 192.168.x.x, with port 22.
For the first test, password authentication is fine. Once the connection works, switch to an SSH key for long-term use. A key-based setup is easier to maintain across daily sessions, and it removes the habit of typing account passwords into a small mobile keyboard.
Before you debug anything else, confirm these basics:
- The Mac and iPhone are on the same Wi-Fi.
- Remote Login is enabled for the correct user.
- The Host value is an IP address or hostname that the phone can reach.
- The Port value is
22unless you intentionally changed SSH. - The Username is the macOS account name, not the display name.
If same-Wi-Fi SSH does not work, remote access over Tailscale or ngrok will not magically fix the setup. Get the simple path working first.
Create the first useful Project
After the terminal opens, move into a project directory and run the tools already installed on that remote host:
cd ~/Projects/your-project
git status
codex
This is the point where Redock becomes more than a saved SSH connection. Save the project directory as a Project so you do not have to reconstruct the working context each time. A good first Project usually includes:
- A Host, such as
Home MacorVPS Prod. - A working directory, such as
~/Projects/redock. - A few snippets for Git, tmux, package scripts, or agent commands.
- One Action for starting the agent.
- One Action for running the most common verification command.
The goal is simple: when you open Redock from the couch, a train, or a short break, you should not spend the first minute remembering paths and command names. You should land close to the work.
Add Actions for the commands you repeat
Actions are worth creating for anything you run often or anything that is annoying to type on a phone. Start small. You do not need to model the whole development lifecycle on day one.
Useful first Actions include:
| Action | Example command | Recommended mode |
|---|---|---|
| Start agent | codex or claude --resume |
Terminal Interactive |
| Check Git | git status --short |
Quick Task |
| Run tests | npm test or pnpm test |
Quick Task or Background Long Task |
| Watch logs | tail -f logs/app.log |
Terminal Interactive |
| Build app | npm run build |
Background Long Task |
Use Terminal Interactive when the command expects conversation or continuous input. AI coding agents usually belong here. Use Quick Task when the command runs once and produces output you want to inspect later. Use Background Long Task when the command may continue after the phone disconnects.
This run-mode distinction is one of the biggest practical differences between a mobile workbench and a raw shell session. On a laptop, you can improvise. On a phone, explicit entry points save attention.
Enable tmux for recovery
If the remote machine has tmux, enable Redock tmux in the Host settings. Redock then exposes session entry points for creating, attaching, and resuming work without making every mobile session start with tmux new or tmux attach.
That matters on mobile. Networks change, apps go into the background, and long agent runs can take time. tmux lets the remote session keep going after the phone disconnects.
A practical tmux layout is:
- One pane for Claude Code, Codex, OpenCode, or your shell.
- One pane for tests, logs, or Git diff.
- A recoverable session name tied to the Project or task.
- Background Actions for builds, migrations, or long verification steps.
The remote host must have tmux installed. Redock does not install tmux for you, but once tmux exists on the host, Redock can make it part of the mobile flow.
Make the setup portable
Once same-Wi-Fi SSH works, choose a stable remote access method.
Tailscale is the best daily default for many developers because it puts your phone and development machines on a private network without exposing SSH directly to the public internet. Use the Tailscale IP or MagicDNS name as the Host in Redock.
ngrok TCP is useful for temporary access to a machine without a public IP. Treat it as a public entry point: use strong authentication, stop the tunnel when you are done, and avoid using it as your permanent production path unless you understand the security model.
A VPS or public host works well when you control SSH hardening, users, keys, and firewall rules. This is often the cleanest setup for server-side projects, personal automation, long-running services, or a dedicated development box.
What to configure after the first connection
After the first successful session, do not immediately add dozens of commands. Add only the pieces that remove real mobile friction:
- Save common working directories you use often.
- Save agent launch commands, tests, builds, deploy checks, and log commands.
- Use staged input for longer prompts before sending them to the terminal.
- Try speech input for paragraphs of agent instructions, then review the transcript before sending.
- Enable tmux so long work does not depend on the phone staying connected.
- Keep LAN, Tailscale, and ngrok entries as separate Hosts instead of editing one Host back and forth.
When those pieces are in place, Redock stops feeling like a remote access utility and starts acting like a mobile workbench for your actual development cycle.
Quick answer
To set up Redock for mobile AI coding, first enable SSH on your Mac, VPS, or development server. Connect from Redock on the same Wi-Fi, save the working directory as a Project, add Actions for the agent and verification commands, then enable tmux on the Host for recoverable sessions. After the local setup works, use Tailscale for daily remote access or ngrok TCP for temporary access.