Influxx Mobile Companion for iOS: Pair, Monitor, and Control Agents
Influxx Mobile is the iOS companion for the Influxx desktop cockpit. Pair your iPhone with a running desktop (or a reachable headless serve runtime), then monitor workspaces, watch agent terminals, chat with agents that still run on the machine, review diffs, stage and commit, open pull requests, and get notified when an agent finishes or needs input — without sitting at the Mac. This guide covers what ships on iOS today: pairing, home and host navigation, sessions, source control, tasks, notifications, and settings, plus honest notes on surfaces that are partial or capability-gated.
What the mobile companion is (and is not)
Influxx Mobile does not replace the desktop app. Agents still execute as CLI sessions on the paired host — worktree-scoped terminals on your Mac (or remote serve runtime). The phone is mission control: status, streaming output, chat chrome for supported agents, review loops, and lightweight git actions over a secure pairing link.
You use mobile when you leave the desk and still need to:
- See which workspaces are working, idle, or waiting for permission
- Read live terminal or native-chat agent output
- Send a follow-up prompt, approve a path, or type into the session
- Annotate diffs, stage files, commit, and start a PR
- Create a new workspace from a task or a prompt while you are away
- Get push alerts when agents complete or need attention
Your phone becomes mission control. Agents keep running tools on your desktop while you are on a café Wi‑Fi, a flight seatback, or the couch.
Before you rely on mobile day-to-day, install and open Influxx desktop (currently documented for macOS Apple Silicon in the product notes), complete basic onboarding there if needed, and keep the machine awake and reachable on a network your phone can reach. Mobile pairing always needs a live desktop runtime or an explicit headless serve path — there is no “cloud agent” substitute on the phone alone.
Install and first launch on iOS
Download Influxx from the App Store (product listing id 6791351351; store URL form apps.apple.com/us/app/influxx/id…). Open the app and complete onboarding when prompted.
Onboarding is a six-step flow aligned with the desktop design language:
1. Set up your profile — claim a name; photo is optional and can wait.
2. Welcome — the “cockpit in your pocket” overview.
3. Work from anywhere — pairs later so you are not blocked mid-setup.
4. Agents that work remotely — chat demo framing: you talk on the phone; tools run on the host.
5. Stay in the loop — enable notifications when agents finish or need attention.
6. Ready — home, then pair a desktop when you are near one.
You can sign in, manage account profile, and later open Status for account management or deletion tools. Settings stay free of plan or pricing marketing copy so account tools remain App Store–safe and practical.
Pair with Influxx desktop
Pairing links the phone to one host profile: endpoint, device token, and host identity. You can pair more than one desktop over time and switch among them from home.
Standard path from the phone:
1. On the Mac, open Influxx desktop.
2. Go to Settings → Mobile (under Set Up in the desktop settings map).
3. Show the pairing QR code (desktop also exposes a copyable link).
4. On the phone, open Pair Desktop from home (or Desktop when unlinked).
5. Scan the QR with the in-app camera, or paste the pairing link/code.
6. Confirm the connection. The app verifies with a status check, then saves the host.
The Pair Desktop sheet states the three steps explicitly: open desktop Settings → Mobile, show the QR, then scan or paste on the phone. Deep links using the influxx pairing scheme can open the confirm flow directly when a code is present.
After a successful pair, home shows a green Desktop status. Tap Desktop when linked if you need to unlink or remove paired desktops from this phone without hunting through host menus.
- Same LAN: Typical home or office setup — phone and Mac on the same Wi‑Fi so the QR endpoint resolves.
- Custom / VPN routes: Desktop Mobile settings can bake a specific network address into the QR (including manual or tailnet-style addresses when configured). Prefer private networks or a VPN mesh for remote machines rather than exposing pairing on the public internet.
- Headless serve: Product CLI notes document
influxx serve … --mobile-pairingstyle runtimes for lab or remote boxes. The phone still needs a reachable pairing offer; remote pairing codes are the intentional path for environments without a full GUI session. - Stale hosts: If a host entry points at an old IP or dead token, remove it from the app and pair again.
- Protocol versions: Mobile and desktop exchange protocol versions. If a combo is genuinely incompatible, the app can hard-block and direct you to update via the App Store (phone too old) or desktop releases (host too old) instead of failing silently.
If pairing fails
Watch the connection log on the confirm/scan screens. Common fixes:
1. Confirm Influxx desktop is running and Settings → Mobile shows an active pairing surface.
2. Confirm the phone can route to the host address encoded in the QR (try the same Wi‑Fi; disable guest isolation; verify VPN if you rely on a tailnet).
3. Retry with a freshly generated QR after changing network interfaces on the Mac.
4. Remove a half-saved host and pair cleanly again.
5. If the app reports a protocol block, update the lagging side (App Store for mobile, desktop release channel for the host).
Initial pairing attempts use a bounded “Connecting…” window so a broken route surfaces as an error with logs instead of spinning forever.
Home: your mobile desk
After pairing, home is the desk you return to. Expect:
- Time-of-day greeting and a search field for workspaces, chats, models, and desktops.
- Top nav: Desktop (link status), Notes, Journey, and P0DZ.
- Bento actions: New workspace (hero), Tasks, and Agents when a host is connected.
- Host list / resume: paired machines and recent worktree activity so you can jump back into a session.
- Notes on home: A global home Notes surface is currently gated off as not launch-ready for a quiet top-level tile. Per-worktree notes still ship from the host/workspace path (see Notes below).
- Journey: Magazine-style product stories and catalog posts you can browse and search — learning surface, not a worktree.
- P0DZ: Dev-server manager parity with the desktop DManage panel when the connected host supports it — start/stop/history style control of project servers from the phone.
Home also surfaces usage-aware account chips when the host reports provider accounts, and can show task-provider logos and agent avatars so you know which CLIs and integrations are live before you dive into a workspace. Connection health classification (connected, warning, unreachable, auth-failed) drives status dots and banners so you know whether to reconnect or re-pair.
Open a host and manage workspaces
Tap into a paired host to open the worktree (workspace) list — the same isolation model as desktop: each workspace is a tracked checkout with its own agents, terminals, and metadata.
From the host list you can:
- See live status (working, active, permission, done, inactive) and terminal counts
- Pin workspaces, group and sort with desktop-synced view settings where available
- Search the list and open a session into a worktree
- Create a new workspace with the FAB / New workspace flow
- Open worktree actions such as Source Control and Agent Session History (history appears when the host advertises the AI Vault capability)
- Remove a host or force reconnect when the link drops
Create a new workspace from the phone
Use New workspace (home bento or host FAB) while connected:
1. Pick a project/repo the host already knows.
2. Choose an agent (or blank terminal) from the mobile agent catalog enabled on that host.
3. Write a prompt / note for the first session.
4. Confirm setup-hook policy when the repo has hooks (inherit, run, or skip — trust prompts appear when needed).
5. Submit — the host creates the worktree and can launch the agent the same way the desktop New Workspace composer does.
Timeouts and SSH-gated repos are enforced on the host side; if creation fails, the modal surfaces the host error rather than inventing a local checkout on the phone.
Sessions: terminals, native chat, and control
Opening a worktree lands you in the session screen — the heart of remote control.
Terminal streaming. Live PTY output streams from the host into a terminal view on the phone. You can type commands, use accessory keys, adjust text scale, and switch among terminals for that worktree. Output survives host reconnect logic; if the link drops, reconnect and resubscribe rather than assuming the agent stopped.
Native chat (default for supported CLIs). For supported agents, sessions open in native chat chrome by default instead of raw TUI, while still driving the same host agent process. You can send messages, attach images where the session supports it, and follow tool activity in a phone-first layout. Per-tab overrides can still prefer terminal view when you need the full TUI.
Composer and follow-ups. Use the command/chat input to send the next instruction while you are away from the keyboard. Dictation can fill the composer when voice is set up (see Voice settings).
Session menu. The header menu opens:
- Files — browse and open workspace files
- Source control — branch status, diffs, and commits
- Agent history — browse and resume sessions when the host supports AI Vault
- Checks — pull request checks when the hosted provider path supports them
- Status awareness: Working / idle / needs-input style states mirror desktop agent status so you know when to intervene.
- Haptics: Light impact feedback on key session actions for confirmation without looking down.
- Links in terminal: Browser settings choose whether OSC/terminal links open in the Influxx browser on the desktop or in the phone’s browser (Safari/Chrome).
- Clipboard: Copy paths, commands, and review text from session and review surfaces.
- Reconnect: Auth-failed and unreachable banners point you at reconnect or re-pair rather than silent empty terminals.
Send a follow-up while an agent is running
1. Open the host → select the active worktree (or resume from home).
2. Confirm the session shows live output or chat activity.
3. Type your follow-up (or hold/toggle dictation to speak).
4. Send — the host delivers into the same agent/terminal session.
5. If the agent is blocked on a trust or permission prompt in the TUI, switch to terminal view if needed so you can answer the raw prompt, then return to chat.
If the agent is not ready (no active terminal, permission wall, or disconnected host), fix connection or open a terminal on desktop first; mobile cannot invent a new PTY without the host runtime.
Diff review and review comments
Mobile includes a dedicated diff review surface for a worktree. Open review from session/source-control flows to walk changed files, filter scope, and leave line-oriented comments.
Review comments participate in the same send-to-agent loop as desktop review notes: unsent comments can be delivered into the agent path; editing a sent comment clears sent state so it becomes unsent again. Use this when you are away from the desk but still want precise “fix this hunk” feedback instead of a vague chat message.
Pull request conversation comments and bot/human filters appear on PR-aware paths when the host’s GitHub (or other hosted) integration is connected — these are host-mediated, not a second GitHub app login living only on the phone.
Source Control hub
Source Control on mobile is a three-tab hub:
- Changes — unstaged/staged counts, file list, stage all / unstage all, commit message (including generation helpers when available), commit, and related git actions on the host
- Pull Request — create/open PR flows for supported hosts; legacy PR deep links redirect into this tab
- Commits — recent commit history for the worktree
Typical mobile ship loop
1. Agent finishes a feature worktree while you are away.
2. Open the session, skim chat/terminal output, then open Source control → Changes.
3. Review diffs (open Review for deeper file-level comments if needed).
4. Stage, write or generate a commit message, commit.
5. Switch to Pull Request and create or open the PR.
6. Watch Checks when the provider supports hosted checks.
7. Return later via Agent history if you need to resume the same thread.
This is intentionally the same cockpit loop as desktop Source Control — phone-shaped chrome, host-backed truth.
Files and notes
Files. The file explorer panel browses the worktree on the host. Open files into a preview route for reading; use this to confirm agent edits without pulling a full IDE onto the phone.
Worktree notes. Notes under a worktree list host-backed markdown from
.influxx/notes/ — the same plan files desktop Sidebar Notes use. You can list notes, create a new note, and open a note in the file preview path. Markdown-first editing on mobile is intentionally lighter than the full desktop rich editor; treat the phone as the place to read plans and kick or continue work, not as a full wiki replacement.
Again: the top-level home Notes desk tab is not treated as a launch-ready global surface today, even though the control may appear disabled until a connected resume worktree exists. Prefer notes from a specific workspace.Tasks and agents feeds
Tasks. The Tasks surface on a host is a full mobile task console for connected task sources (for example GitHub-oriented issue/PR/project rows when the desktop integrations are configured). From tasks you can inspect items, search, and start a workspace from a task with agent selection and naming helpers — the same “start workspace from task” idea as desktop, adapted for touch.
Agents. The host Agents feed is an Activity-lite list of worktrees with live agent activity (status, terminal counts). Use it as a radar view across the machine when you do not remember which branch is still running.
Both require a connected host client; offline, you will see desktop-not-connected style empty states instead of stale inventiveness.
Accounts, usage, and provider context
On a connected host you can open Accounts to see provider account snapshots (for example Claude / OpenAI-style rows the host reports), rate-limit windows, and usage bars. Drill-down sheets explain usage in plain language. Switching active accounts, where supported, is mediated by the desktop host — the phone is the remote control, not a separate API-key vault for every CLI.
Home may also show compact usage chips so you notice a near-limit provider before starting a large mobile session.
Notifications
Notifications are first-class on iOS:
- Enable push during onboarding or later in Settings → Notifications
- Grant system notification permission when prompted; open system settings if denied
- Toggle notification sound and pick among built-in sound options with preview
- Receive alerts when agents finish or need attention (tied to the paired desktop notification pipeline)
Settings map on iOS
Settings is a searchable hub (Account Center–style rows):
- Your account — Desktop: paired Mac status; jump to manage links
- Account: profile, username, display name, photo
- Status: manage account / delete account tools (no in-app pricing copy)
- Join px campus: community Discord
- Terminal: text size scale, autocomplete, accessory shortcuts, auto-restore fit timing for how the terminal resizes on the phone
- Browser: open links in Influxx browser on desktop vs phone browser
- Voice: dictation mode (toggle vs hold) and speech-model setup against the connected host (download or ensure the host model when the app prompts)
- Notifications: push and sounds
- Troubleshooting: connection help and issue filing chrome
- Learn / Privacy / Support: external product notes, privacy, and contact destinations
Voice dictation setup (high level)
1. Pair and connect a desktop that has dictation support enabled.
2. Open Settings → Voice.
3. Ensure the host model is downloaded when the UI offers setup.
4. Choose Toggle or Hold for how the mic control behaves in session.
5. In a session composer, use the mic control to dictate; live partials can appear while you speak, with a final transcript on release/finish depending on mode.
Dictation is host-assisted. If no host is connected, voice settings will not invent on-device magic for remote agents.
Journey and learning content
Journey is a searchable, magazine-style feed of product posts (bundled catalog with refresh). Use it to learn how Notes, agents, and the cockpit fit together when you are not mid-incident. It is intentionally separate from worktree notes and does not require a live agent session.
P0DZ (dev servers)
When available on the connected host, P0DZ mirrors the desktop dev-server manager: snapshot of active servers, launch/history/settings style tabs, start/stop/restart controls, logs, and project-aware rows. Use it when an agent or local app depends on a dev server you need to bounce without walking back to the desk. If the host does not expose the capability, the home tile stays disabled.
Capability gating is a recurring mobile pattern: Agent Session History, Checks, P0DZ, and some PR/GitHub project features only appear when the paired desktop advertises support. That is deliberate — the phone will not navigate to screens that would call missing host methods. If a row is missing compared to a friend’s phone, compare desktop version and enabled integrations first.
What ships vs what is partial
Be explicit so expectations stay accurate:
- Shipped: QR/link pairing; multi-host save; worktree list; new workspace; session terminal stream; native chat default for supported agents; dictation hooks; files; source control hub (changes / PR / commits); diff review comments; tasks; agents feed; notifications; terminal/browser/voice settings; accounts/usage; Journey; troubleshoot; protocol block / force-update paths; App Store distribution for iOS.
- Partial / gated: Home-level Notes surface is not launch-ready as a quiet global tile (per-worktree notes still exist). Agent history and Checks depend on host capabilities. Managed cloud credit runtimes on desktop are a separate product lane — day-to-day mobile control assumes your local CLI agents on a reachable host. Android exists in the product family; this guide does not claim iOS-only exclusivity for every binary.
- Not the phone’s job: Full desktop markdown rich editor parity, Computer Use, embedded multi-tab Chromium design mode, and deep WSL host configuration remain desktop (or host) concerns. Mobile steers; the machine executes.
If it runs in a terminal on the host, you can watch and steer it from iOS — the companion never pretends the agent lives only in the cloud on your phone.
Networking and remote reliability tips
- Keep the Mac awake (or use a serve host that stays up) while you depend on mobile.
- Prefer stable private networking for remote pairing; product notes call out private networks / Tailscale-class meshes for headless servers.
- After network changes, reopen the host or force reconnect; if status stays auth-failed, re-pair.
- When terminal stream looks empty but the agent is running, leave and re-enter the session so the phone resubscribes; confirm the desktop PTY is healthy if both sides look blank.
- Update mobile promptly after desktop releases when prompted — mobile store lag is expected, but hard protocol blocks exist for unsafe skew.
Quick start checklist
1. Install Influxx desktop on the Mac and Influxx Mobile from the App Store.
2. Finish phone onboarding; enable notifications.
3. Desktop: Settings → Mobile → show QR.
4. Phone: Pair Desktop → scan or paste → confirm green Desktop status.
5. Open the host → pick a worktree (or New workspace with a prompt).
6. Watch the session; send a follow-up; open Source control when ready to ship.
7. Optionally enable Voice dictation and customize Terminal text size for outdoor readability.
When that loop works once on your LAN, try the same pair over your preferred remote network path before you travel.
Related Influxx help topics to explore by name in the help center and product notes: Install and first launch for desktop, Agents overview, Worktrees and parallel agents, Source Control and review notes, Dual intelligence (local CLI vs managed credits), CLI headless serve with mobile pairing, Notifications, and Privacy settings. Mobile is one surface of the same cockpit — not a separate product with different agent semantics.
Troubleshooting shortcuts
- Cannot pair: Desktop running? Settings → Mobile visible? Same routable network? Fresh QR? Remove stale host.
- Paired but red/unreachable: Mac asleep, VPN down, IP changed — wake host, fix network, force reconnect or re-pair.
- No agent output: Confirm a live terminal on the worktree; re-enter session; check desktop for hung PTY.
- Cannot commit/PR: Host connected? Correct worktree? Integration auth valid on desktop?
- No notifications: iOS permission, in-app toggle, sound settings, desktop still paired and online.
- Protocol block screen: Update mobile from the App Store or update desktop from your release channel.
- Missing menu items: Feature is capability-gated — update desktop or enable the integration there.
Influxx Mobile for iOS is built to keep you in the loop without giving up the honesty of local CLI agents. Pair once, treat the phone as a remote cockpit, and let the desktop remain the engine room — terminals, keys, worktrees, and git truth stay on the host while you monitor, review, and steer from anywhere you can keep a secure path open.
