Grok Build on Mobile

Grok Build is a terminal TUI, not a native iOS/Android app. On a phone you don’t install a separate “Grok threads” client — you SSH into a machine that already has grok, git, and your HEOS (or other) repo.

Multi-thread works the same as on desktop: /new, /rename, /resume, /dashboard. The phone is the keyboard and screen; the sessions live on the server.

Architecture (one picture)

iPhone / Android
  └── SSH client (Blink, Termius, …)
        └── always-on Mac or VPS
              ├── git clone of HEOS / vault
              ├── grok (authenticated)
              ├── ~/.grok/sessions/…   ← named threads live here
              └── optional: tmux so you can disconnect safely

Resume tomorrow from phone or laptop: same session names, same machine.

Best path (most people)

1. Always-on box with Grok + git Home Mac (left on, reachable) or a cheap VPS — same idea as SSH for AI development and agent machine.
2. SSH app on the phone
   • iPhone: Blink Shell, Termius, Prompt (prefer solid keyboard + multi-session support)
   • Android: Termius, JuiceSSH, ConnectBot, etc.
3. On the server:

   cd /path/to/headless-empire-os   # your vault path
   grok
   # then:
   /new
   /rename Start CEO OS day

4. Auth once if there’s no browser on the box: use Grok’s device-code / headless auth flow (see Grok auth docs / --device-auth), then stay logged in.

Multi-thread on mobile

Full SOP: /grokthreads — CEO OS day hub, satellite threads, vault residue rules.

tmux (strongly recommended)

Start Grok inside tmux (or screen) on the server so the session survives network drops and app switches. Laptop reconnect checklist (Mini + Tailscale): /tmux.

tmux new -s heos
cd ~/path/to/heos && grok
# detach: Ctrl-b then d
# later from phone or Mac:
tmux attach -t heos

Phone battery death ≠ killing your CEO OS day agent mid-run.

What works well on phone vs laptop

Practical split: use mobile for hub + triage; open heavy satellite threads when you’re at a real keyboard.

Hardware & UX tips

• External keyboard if you do this often — soft keyboards fight /, Ctrl, and paste.
• Pick an SSH client that supports multiple tabs and a usable font size for TUI apps.
• Prefer a client that handles fullscreen / alt-screen apps cleanly (Grok’s fullscreen mode).
• Keep secrets on the server (API keys, Grok auth) — don’t copy env files into phone notes apps.
• VPN or Tailscale / similar if the home Mac isn’t public on the internet.

What not to rely on

• Grok or ChatGPT mobile chat apps — different product; no shared HEOS sessions, tools, or ~/.grok/sessions.
• Weak in-browser SSH — often breaks TUI layout and keys.
• Two writers without a plan — phone agent + laptop agent on the same files → git pain (see parallel rules on grokthreads).
• Expecting a Codex-style native sidebar on iOS — won’t happen via SSH; named sessions are the substitute.

Minimal setup checklist

• □ Mac or VPS with grok installed and authenticated
• □ HEOS (or project) repo cloned and pullable
• □ SSH keys from phone → box (or strong password + fail2ban on VPS)
• □ tmux installed; one named session for daily HEOS
• □ Phone SSH app with multi-tab
• □ Habit: /rename every thread (Codex-style names)
• □ Habit: vault writes (NOW / TODAY / projects) before you close the phone

Quick command card (on the server)

tmux attach -t heos   # or: tmux new -s heos
cd ~/heos && grok

/new
/rename Start CEO OS day
/resume
/dashboard            # Ctrl+\ when it works over your client
/home

# later from laptop — same machine, same threads
grok --resume "Start CEO OS day"

Related

In one sentence

Put Grok and HEOS on a Mac or VPS, SSH from the phone, use tmux + named sessions — mobile is a remote keyboard into your multi-thread setup, not a second product.

Living notes

Update with preferred SSH app, Tailscale hostname, and exact HEOS path once the “phone HEOS box” is standardized. Link any internal runbook for device-code auth if the VPS has no browser.