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.

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	Follow the agent in its live terminal, or read the same session as a chat feed. Terminal, Chat, 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. Since v0.41.0 the desktop confirms the move as soon as the card’s new column is on disk, before it suspends a session, removes a worktree on a Done move, or spawns an agent, so a move whose tail runs long no longer reads as “Move failed” on the phone
Sessions again	Start a task’s session again from its “Session ended” state, in the column it is already in, without moving the card. For a task whose session ended, or that never had one, the column’s automations run as they do on a move, and a second tap while the first is still spawning does nothing, so the column’s message is never typed twice. For a task you paused, a v0.45.0 or later desktop resumes the paused conversation exactly as its own Resume button does, with no automations and no column message. Either way the desktop answers as soon as the start is accepted rather than once the agent is up
Pause and resume	Long-press a task and tap Pause session to stop its agent the way the desktop’s Pause button does, keeping the conversation. The row reads Pausing agent… until the desktop reports the task paused. A paused session’s Terminal shows Resume session where the terminal would be, and the long-press menu offers it too; it continues the paused conversation the way the desktop’s own Resume does. Pause is offered for a task with a running agent outside To Do, and Resume for a paused task outside To Do, Done, and the archive. Both need a v0.45.0 or later desktop, which tells the phone which tasks can pause or resume
Command Terminals	Start a Command Terminal at a project’s root from the Board’s Terminals button, ask it anything, follow it in Terminal, Chat, and Changes, and stop it. Its Changes diff the project folder against the default base branch. Needs Kangentic Mobile 1.1.0 and a v0.46.0 or later desktop; the button stays hidden otherwise
Notifications	Push alerts when a session needs your attention

Under the hood these map to a fixed set of thirteen capabilities granted at pairing: read-stream, read-board, read-diff, send-user-message, move-task, start-session, pause-session, command-terminal, answer-permission-prompt, interactive-terminal, board-tool-read, board-tool-write, and register-push. pause-session, added in v0.45.0, suspends a running session the way the desktop’s Pause button does. command-terminal, added in v0.46.0, starts or stops a Command Terminal. Pairing grants every verb the protocol defines, so a verb added later is granted on the next bridge start with no re-pair.

A phone newer than the desktop it talks to can ask for a verb that desktop does not know. Since v0.42.0 the desktop answers such a request with an unsupported-verb refusal instead of dropping the frame, so the phone can say “update your desktop” rather than time out. The refusal covers verbs added after v0.42.0; a desktop older than that still drops the frame silently.

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.

command-terminal is the one verb whose name reads like a command channel, and it is not one. It starts the project’s own agent CLI, exactly as the desktop’s New terminal does, and the phone names no command, branch, model, or effort. The desktop ends a Command Terminal the moment its agent exits, so there is never a bare shell left to type into, and the phone holds all input to a terminal until the desktop has seen its agent start.

Screens

Agents is the home tab. It lists every session in four sections: Idle, Active, Queued, and Paused. Idle holds the sessions waiting on you, with open prompts first, and Active holds the ones mid-turn. These are the Agent Monitor’s Idle, Active, and Paused groups, except that the phone gives queued sessions a section of their own where the Monitor files them under Paused. Each section collapses on its own, and the filter button in the header opens Show sections, which picks the sections that show and is remembered on the phone. Each card names its project, shows how long a waiting session has waited on you, and draws one mark per board column from To Do to Done, with the task’s current column shown by its icon.
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. While the desktop has not yet sent a session’s terminal, the Terminal shows a blinking cursor, and after three seconds a Waiting for desktop line, rather than a black pane.
Command Terminal is a terminal’s own screen, with the same three surfaces as a session and the desktop’s round Stop in the header. It closes when the terminal ends. The Agents feed lists terminals beside task agents with a Command Terminal pill in place of a task number.
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.
Paired desktop, opened from Settings, shows your desktop and this phone by key fingerprint, with the relay and an Unpair button. A phone pairs with one desktop at a time, and pairing again replaces it.
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.