Resources · Documentation

Documentation

Client & mobile

The same server that runs your agents serves the client. Open it in a browser, install it as a PWA, or connect from another device.

On this page

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

Use the server switcher in the client and enter the server URL. If authentication is enabled, the client asks for its token.

Common setups:

Network Example
Same machine http://localhost:8742
Local network http://192.168.1.20:8742
Tailscale or VPN The machine name, Tailscale IP, or HTTPS address you configured
Public internet A TLS-protected address with authentication enabled

Browsers treat localhost as secure, but another device normally needs HTTPS before the service worker and PWA installation are available. Plain HTTP on a private LAN can still open the web client.

Do not expose the default unauthenticated server to an untrusted network. Read Security & auth before remote access outside your private network.

What the client includes

Sessions and chat

  • Run unlimited sessions, with up to six visible in board view.
  • Switch models, reasoning variants, and preconfigs per session.
  • Queue messages while an agent is working.
  • Interrupt, fork, revert, and compact conversations.
  • Mention workspace files from the message composer.
  • Use goal mode for evaluator-checked multi-turn work.

Files and changes

Browse the active workspace, preview files with syntax highlighting, inspect Git changes and diffs, and use file autocomplete from chat. Managed worktrees can be selected without leaving the workspace.

Terminals

Open persistent PTY terminals in multiple tabs. Terminal state belongs to the workspace rather than one chat, so closing a conversation does not discard the shell session.

Configuration

The client manages:

  • Provider credentials and supported OAuth accounts
  • Providers, models, and reasoning variants
  • Preconfigs, prompts, tools, and subagent rules
  • Workspace capabilities and tool grants
  • Status and connection controls for MCP servers configured in the workspace file
  • Server connections

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 a preconfig needs. The extension’s data handling is covered by the privacy policy.

Spotted something wrong or missing? Open an issue ↗