A quieter conversation, and commands that keep running

A quieter conversation

• No labels, less color. Messages drop the “You” and “Assistant” labels. Yours sit on the right in a soft gray bubble, and the reply fills the width. A finished tool call shows only a small chevron; a running one spins and a failed one turns red. A run of tool calls folds to its tool names, with line counts and time beside them.
• Previews peek instead of scroll. A written file, an edit, or a command’s output is a plain gray block that shows a few lines and fades out, with Show all 42 lines and Open file underneath. Showing all grows the block in place, so the page is the only thing that scrolls, on phones too. Command output shows its last lines, where the result or the failure is.
• Details on hover. Model, time, and token counts for a reply, and the copy, pin, fork, edit, and undo buttons, appear under the message when you hover it. Code blocks show their language and Copy on hover, always on a phone.
• Smoother streaming. New words fade in as they arrive instead of typing out letter by letter, and long code blocks recolor only their newest lines. Replies use noticeably less CPU while they stream. With reduced motion on, words appear without the fade.

Commands keep running

Prokop agents now have one shell tool that runs every command in its own process, with your shell (zsh, bash, dash, ksh, or sh). Commands started side by side no longer wait on each other, and a dev server never blocks the next command.

A command still running after the wait, 60 seconds unless the agent asks for more, keeps going in the background. The agent gets the output so far, and when the command finishes, a prompt in the conversation tells it, with the output attached as a terminal chip. The agent can read more output or stop the command, and the full output is kept in a file it can search. Background commands stop when you archive or delete the session, undo or edit a message, or stop the server. Interactive prompts are not supported.

Claude Code background commands no longer hold the session for up to 10 minutes. Claude’s reply completes and the session is free at once; when the command finishes, its result appears as a note followed by Claude’s follow-up reply.

Notifications reach the right device

• A session’s push goes only to the device that controls it. A session nobody controls, such as a scheduled run, still reaches every enabled device.
• Nothing is pushed while you are at any device. The device you are at signals locally instead, with a sound, an unread mark, or the approval itself. A locked screen no longer counts as being there.
• Questions from Claude Code or Prokop now notify like approvals. The setting is now called Approvals and questions.
• On iPhone and iPad, notifications no longer stop silently after a few pushes. If iOS drops the subscription anyway, the app shows a Re-enable button.
• Returning to the app on a phone reconnects within seconds instead of showing a stale screen for up to a minute and a half.

Approvals

• “Allow for this session” allows only what you approved. In Prokop runtime sessions, approving one command or file for the session or workspace used to approve every later use of that tool. An approval now covers the exact command in the same folder, or the exact file. Commands that can only be allowed once can’t be remembered.
• Commands behind a prefix are checked. A command after FOO=1, time, env, nohup, timeout, if/then, ( ), and similar was judged by the prefix, so time rm -rf / ran in Full access without asking. The command itself is now judged.
• Fewer false asks. ROOT=/repo/build; rm -rf "$ROOT" is judged by the value it sets. awk and sed patterns that start with a slash are not paths. A trailing | xargs in a captured value is not critical.
• Approvals wait 30 minutes in Prokop and Claude Code sessions, like Codex, and survive a reconnect.
• Colors match the modes. Asks for secrets and destructive commands show red, since only Full access runs them without asking. Outside-workspace asks stay amber, the color of Extended.

Git and pull requests

• Reading a commit in Branches. A commit opens as a file list with status letters and line counts, and one diff at a time. Move between files with the arrows or j and k. The + beside History starts a new branch at that commit.
• Pull requests on a phone. The checkout picker, refresh, and New PR share one row, and an open pull request gets the full height.
• Merged pull requests say so. The Merge box reads “Merged into main” or “Closed without merging” instead of “Merge status not yet known”.

Fixed

• Mermaid labels are no longer cut off. Diagrams draw in the font they are sized for.
• The right dock no longer floats over the chat on windows narrower than about 1280 px. It is the same resizable card at every size.
• Sounds play on time or not at all, instead of minutes later after your next click.
• A finished session you did not have open plays the finish sound and shows as unread.
• A message sent into a running turn no longer plays the finish sound or marks the chat finished.
• The workspace loads faster. The terminal, file editor, pull requests, and conflict editor load the first time you open them.

Removed

• The separate terminal tool for Prokop agents. The shell tool covers long-running commands, so agents no longer open tabs in your terminal panel. Your own terminals are unchanged.
• Tools loaded from ~/.prokopai/tools or PROKOPAI_TOOLS_PATH, and prokop init --tools-path. Tools come from the binary and from MCP servers. An existing tools folder is left in place and ignored.

Update

Run this on the machine hosting your Prokop server:

prokop update

Approvals saved for a session or workspace before this update no longer apply, so you will be asked once more.