Client & mobile

Open the built-in client

The production client is embedded in the Prokop binary and served from the same origin as the API and WebSocket endpoint.

prokop start
prokop open

The default address is http://localhost:8742. If you change the server port, the client URL changes with it.

Install the PWA

Prokop is a Progressive Web App. After opening the client:

• Desktop: use the install icon in the browser address bar.
• iPhone or iPad: open the Share menu, then choose Add to Home Screen.
• Android: use the install prompt or Add to Home Screen from the browser menu.

When the service worker can register, the app shell is cached locally. You still need a connection to your Prokop server to run agents and load current data.

Connect another device

The server listens only on its own machine by default. First turn on remote access there, in Settings → Devices → Remote access or with prokop remote on. It can set up Tailscale HTTPS in one click or save addresses for other VPNs, proxies, and tunnels. Then pair the device:

• Open the server’s address on the other device. It asks for approval and shows a four-digit code; approve it on the machine running Prokop.
• Or choose Add Server in the server switcher and paste a pairing link from prokop pair or Settings → Devices → Pair a device, or scan its QR code.

Paired devices stay signed in for 30 days after their last use. Remove any of them in Settings → Devices or with prokop auth revoke.

Browsers treat localhost as secure, but another device normally needs HTTPS before the PWA can be installed or send notifications. Plain HTTP on a private network can still open the client. Read Security & auth before making a server reachable outside your private network.

Several machines

Once two or more machines are saved, the workspace switcher lists the workspaces on every machine, grouped by machine name. Pick one to switch machines and open it in one step. Unreachable machines show their last known workspaces; machines this device is not paired with offer pairing.

A machine can be reached at several addresses, for example LAN at home and Tailscale away. After the first connection, the client learns them and switches automatically when the current one stops answering. An address that answers as a different machine is never used.

While you work on one machine, the client keeps listening to the others. When a session elsewhere needs an approval or an answer, a prompt names the machine and session, and finished runs get a short notice. Open on a prompt, or a row in the Other machines section of the Overview, opens that session as a tab beside this machine’s sessions. You can chat, answer approvals, and stop it as usual while it runs on its own machine.

What the client includes

Sessions and chat

• Open any number of sessions as tabs, and split them right or down to see several at once.
• Pick the runtime, model, effort, and agent per session from one picker, and switch runtime mid-conversation.
• Steer a running agent with a new message, or queue it for after the turn.
• Stop, edit, undo, fork, and compact conversations.
• Type @ to add files to a message as chips. The list starts with your changed files and searches the session’s checkout.
• Read Mermaid diagrams, math, and pages agents show in their replies. File links in replies open the file preview.
• Use goal mode for evaluator-checked multi-turn work.
• See your Claude and Codex plan limits under Usage.
• Chat with several agents in one thread: groups sit in the sidebar under the sessions and open as a tab, with each member’s status in the header and @ to pick who answers. On the phone a group is a tab in the Chat strip next to the sessions.
• Notes from background work (a finished command, a delegated task that finished or needs an answer) show as one muted line under the conversation, not as a message of yours.

Files, Git, and pull requests

Browse the active workspace, preview and edit files, inspect Git changes and diffs, and commit, pull, push, and rebase. In the Explorer, drag a file or folder onto a folder to move it, or pick Move to… from its menu and type the destination; open editors follow a moved file. Branches show history and push and pull status. Managed worktrees can be created and selected without leaving the workspace, and each row shows where its setup stands. Pull requests open beside the workspace selector.

A button next to the workspace switcher lists the other workspaces of the machine. Pick one or more and Open together to land in Overview, in the group that holds exactly those workspaces (created and named after them when there was none), with every session tab you had open carried along. Going back to a workspace keeps its tabs too.

Terminals

Open persistent terminals in multiple tabs. Terminal state belongs to the workspace rather than one chat, so closing a conversation does not discard the shell. Select output and press Add to chat to attach it to the focused session’s message. Drag tabs to reorder them. On phones, a key row adds ^C, Esc, Tab, and arrow keys.

Settings

The client manages:

• Providers, models, and reasoning variants, plus Codex subscription accounts
• Agents: prompts, tools, models, memory, learning, and subagent rules
• Workspace memory, learning, permission mode, and tool grants
• MCP servers, for every workspace or one workspace
• Claude Code and Codex availability, usage, notifications, devices, and remote access

You can still use files and environment variables directly when automation or deployment needs it. See Configuration.

Prokop Browser

Prokop Browser is a Chrome extension that connects browser tabs to your Prokop server. With the corresponding tools enabled, an agent can read visible page content, discover controls, navigate, and interact with pages.

Browser tools are not enabled in every bundled agent. Add only the browser tools an agent needs. The extension’s data handling is covered by the privacy policy.