← Catalog

Pragma — your agent teams, in your pocket

Agent teams work on workflow graphs with human gates. Someone has to answer those gates, decide when a run escalates, and merge what comes out. Pragma is that handle: four tabs over every team you may see, and a voice mode for when your hands are busy.

fr.imachine.pragma · Android 8.0+ · Kotlin and Jetpack Compose · 36 MCP tools · no public store: your instance serves its own build.

What it drives

Each tab answers one question. Teams: who is working right now. WIP: every run of every team, and what waits for you. Features: what one team asks of another. Tracking: one team from the inside — its graph, its workers, its missions.

Nothing here is a read-only dashboard. You answer a gate, you settle an escalation, you merge a pull request, you stop a team. The app calls the same MCP tools the web console calls, so a decision taken on the phone is the decision.

The screens

Interface preview: the published screens are in English, the shipped app speaks French. A cross-team request is open to make the apps bilingual.

Teams

Teams — every team you may see, with what it is doing right now. The banner appears when the instance publishes a newer build; the app installs it itself.
Chat — you talk to the whole team; its orchestrator splits the request. Hold the microphone to speak. A gate posted by the engine shows up as a card you can answer.
Approve step — the human gate of a workflow graph. Each question carries its options and the worker recommendation. The answer leaves as "1 b, 2 a"; amendments send the step back.

WIP

WIP — every run of every team on one board. The counters say what waits for you. Each card names its graph and its current stage; irreversible actions ask twice. A queued run says why it waits and its rank, and Start now releases a queue that stayed stuck on a free team.
Decide — a run that escalated. The orchestrator gathers the facts, states the question and proposes options with one recommendation. Delivering or abandoning asks for a confirmation.
Run detail — the work as it goes. The stages walked, how many times each was revisited, the branch, and what the team wrote at every step. The screen re-reads itself every five seconds.

Features

Features — requests one team files against another. Accepting one picks the workflow graph that will handle it. Refusing one needs a reason. The thread button opens the discussion.

Tracking

Tracking — one team, from the inside: the running graph, its workers, a live feed and the missions. Stop halts the team at the next safe point and leaves the run resumable.

Documents

Documents — the files of the active project and the deliverables the team published. The badge says what the app can open. Search flattens the tree to matching paths.
Document viewer — Markdown, images, PDF and diagrams render in the app. A PlantUML block inside a document is rendered by the server and shown inline.

Settings

Settings — read-aloud, the installed version, the server you are on. Speech recognition runs on the server: nothing is transcribed on the phone.

Voice, and hands-free

Hold the microphone to speak; the server transcribes with Whisper and the team answers. Read-aloud sends the answer back as speech, and the phone's own voice takes over if the server goes quiet. The hands-free mode goes further: it announces gates, escalations and pull requests, takes a command after the word "Pragma", and waits for a spoken "yes" before anything that commits.

The graphs this app watches are described in AI Agent Teams; the plugin behind the teams in Company Manager.

Yours, on your own servers

Pragma talks to your instance, not to ours. The teams, the graphs and the projects are yours; the app is the handle. Another trade means another configuration of the same shared module — see Pragma Commercial.

Talk to an engineer