Point the agent at files and terminal output

Type @ in the message box to add a file. Before you type anything else, the list shows the files you changed, since those are usually the ones you mean. Keep typing to search: you don’t need the exact name, so stok finds sessionToken.ts. The file name comes first in each row, with its folder beside it.

The file you pick becomes a chip in your message. Chips stay in the conversation after you send, and clicking one opens the file. In a worktree session, the list shows that worktree’s files, not the main checkout’s.

To show the agent what a command printed, select the text in a terminal and press Add to chat. The output joins your message as a chip, and clicking it shows exactly what was captured.

Chips work the same way in Prokop, Claude Code, and Codex sessions. Copying a sent message gives you plain file paths with the terminal output included.

Pull requests

Pull requests open in under a second. Opening a GitHub pull request used to wait one to two seconds per click. Changed files load at the same time, and opening a file shows its diff right away.
Start pipelines from the Checks list. Checks that are waiting on you have a button: Queue for an Azure DevOps build that hasn’t run or is out of date, Re-run for a failed GitHub Actions job, and Approve and run, Approve, or Reject for a workflow or deployment waiting for your approval. Approvals ask for confirmation first.
Copy review comments to hand to an agent. Copy unresolved on the Activity tab copies every open review thread as one document, sorted by file and line. Paste it into a session and the agent can work through the feedback. Copy all also includes resolved threads and the general conversation.

Files

README previews look like they do on GitHub. Centered headings, badge rows, sized images, and collapsible sections now show in the file preview, and screenshots follow your light or dark theme.

Fixed

Multi-line commands get the right permission check. A command spread over several lines was checked as a single command, so a dangerous second line could slip through. Each line is now checked on its own. A script handed to a program such as Python counts as that program’s input rather than as commands, while a script handed to a shell is still checked. If a command can’t be checked at all, Prokop asks you instead of failing.
Approving a command after a minute no longer fails. Time spent waiting for your approval no longer counts against the command’s own time limit.
Claude Code waits for your answer. When Claude asks a multiple-choice question, it shows as a question card and Claude continues with what you picked.
Deleting a scheduled job deletes its runs, after a confirmation. Runs left behind by earlier deletions show under the job’s name with a Delete runs action.
Sessions started through the API as an agent now show up when that agent searches its past sessions.
Refresh in the file tree now picks up new and deleted files inside open folders such as build output.

Update

Run this on the machine hosting your Prokop server:

prokop update