Kangentic Mobile

Kangentic Mobile is a remote control for the agent sessions running in your desktop Kangentic app. Pair your phone once, then check on your agents, read their progress, answer the questions they raise, and review diffs from wherever you are.

Getting the app

Install Kangentic Mobile has the current availability on iOS and Android, and the steps to get it on each.

On the desktop side, the mobile bridge ships in production builds and is off until you turn it on in Settings > Mobile Devices.

What it is for

The desktop app is where you set work up. The phone is where you keep an eye on it. An agent that finishes a turn, hits a permission prompt, or stops with an error can reach you on your phone, and you can answer without going back to your desk.

It is deliberately not a second copy of the desktop app. There is no board editing marathon, no file browser, and no shell.

What you can do from the phone

Area	What you get
Sessions	Read the agent’s transcript as a chat feed, or switch to the raw terminal when you need the full picture. Chat, Terminal, and Changes are three surfaces on one session
Input	Send a message to a running agent, or type directly into the terminal
Prompts	Answer permission prompts and questions the agent raises
Changes	Review file changes with a per-file diff view
Board	See your projects and columns - grouped the way your desktop sidebar groups them - move a task, create or edit one, and browse completed tasks with their transcripts. A move made on the phone reaches an open desktop board immediately, quietly: the card relocates without a toast, because you are the one who moved it
Notifications	Push alerts when a session needs your attention

Under the hood these map to a fixed set of ten capabilities granted at pairing: read-stream, read-board, read-diff, send-user-message, move-task, answer-permission-prompt, interactive-terminal, board-tool-read, board-tool-write, and register-push.

What it deliberately cannot do

There is no shell verb, no file-read verb, and no arbitrary-command verb anywhere in the protocol. This is a design constraint, not a permission you can grant: a paired phone, or anything that manages to impersonate one, still has no way to ask your desktop to run a command or read a file off disk. The phone can talk to agents and move cards. That is the whole surface.

Screens

• Triage home shows the sessions that want your attention first, rather than making you hunt through a board.
• Board lists projects and columns, with a project picker for switching between them.
• Session is the main view. One session, three surfaces, switched from a control at the bottom of the screen: Terminal, Chat, and Changes. Only Chat raises a needs-you dot, and it never switches surfaces on you.
• File diff renders a single file’s changes.
• Task screens cover creating, editing, moving, and completing tasks, plus a paged archive of completed tasks (newest first) whose finished transcripts you can still read.
• Devices lists paired desktops by key fingerprint.
• Settings covers notification categories and the pairing lifecycle.

Dictation

The message composer has a dictation button that turns speech into text using your device’s built-in speech recognition. Audio is not stored or transmitted by Kangentic, though your device’s own speech engine may send audio to its provider to produce the transcript. See the Privacy Policy.

Requirements

• The Kangentic desktop app, running, on a machine you control.
• The companion app on your phone - see Install Kangentic Mobile.
• A one-time pairing between the phone and that desktop.
• A relay both devices can reach, which is either Kangentic’s hosted one or your own.

Next steps

See also:

• Install Kangentic Mobile - get the app on iOS or Android
• Pairing a Phone - the QR and confirmation-code flow
• Push Notifications - the five alert categories
• Security & Encryption - how the link is protected, and what a relay can still see
• Kangentic Relay - the server that carries the link, and how to run your own