Redock FAQ

Claude Code, Codex, OpenCode, Git, tmux, package managers, and project tools run in your development environment. Redock connects over SSH or Mosh and gives you mobile controls for launching, steering, and resuming that work.

Redock stores product configuration such as Hosts, Projects, Actions, terminal snippets, preferences, and related metadata. It also keeps local runtime history such as Runs and recent connection context so Activity can show recent work.

Secrets are stored through Apple Keychain backed stores. SSH passwords, SSH private key material, and speech API keys are not written into the regular app data snapshot. In local mode they stay local to the device; when Pro iCloud sync is enabled, synchronizable iCloud Keychain items can be used for the same Apple account.

When enabled, supported configuration such as Hosts, Projects, Actions, snippets, preferences, and metadata can be saved to your private CloudKit database. Local runtime history such as recent connections and Runs remains device-local and does not sync through CloudKit.

Speech input is optional. Redock records audio, sends it to the speech provider you choose, then puts the transcript into the editable staged input area before you send it to the terminal or agent TUI.

For OpenAI speech transcription, yes. Add the key in My / Speech. Redock stores it in Keychain and uses OpenAI transcription models such as gpt-4o-mini-transcribe, gpt-4o-transcribe, or gpt-4o-transcribe-diarize. Redock does not require Assistant, Realtime, TTS, or fine-tuning setup for speech input.

Choose the Doubao speech provider, enter the Resource ID for the speech recognition service, and enter the APP Key from the Volcengine console. The common default Resource ID is volc.bigasr.auc_turbo. Endpoint IDs such as ep-... are not used for this speech field.

Local Network permission lets Redock discover SSH devices on the same LAN and prefill Host and Port while you are setting up a Mac or server. If you deny it, you can still enter the host address manually.

Yes. A Host can use SSH or Mosh. Mosh still uses SSH for preflight and mosh-server bootstrap, then uses UDP for the interactive shell when available. If Mosh startup cannot complete in a recoverable path, Redock can fall back to a standard SSH shell.

Phones disconnect, switch networks, and go to the background. tmux keeps sessions and long tasks alive on the remote host. Redock gives you entry points to create, attach, and resume tmux sessions without typing tmux commands every time.

Actions are reusable commands or agent entry points. A quick task or background task creates a Run, which records command status, output, timing, and background task metadata. Runs appear in Activity and do not become normal terminal connections unless you open a live tmux session from them.

Start with macOS Remote Login or a reachable SSH server on the same Wi-Fi. After the basic connection works, use Tailscale for a safer daily remote-access path.