Find in the scrollback

Cmd+F on macOS, or Ctrl+F on Windows and Linux, opens a search box over the active tab. Every match is highlighted. The current one is filled in the accent colour, with a count such as 3 of 12.

Enter and Shift+Enter, or the arrows, step through matches and wrap at either end. Aa matches case. Esc closes the box. New output is searched as it arrives.

Search a response

An endpoint body is a JSON block under the endpoint pill. An MCP tool result is the same block under the tool pill. A resource whose type is JSON is too, and so is a stream message that is a JSON object or array.

The magnifying glass on that block searches that response. The match is case-insensitive and can sit in a key, a value, or a number of the pretty-printed text. Each hit is marked. The current one is filled, and the block scrolls to keep it on screen. The count reads 1 / 12. No matches means the text is not in this response.

Enter and the down arrow move to the next match. Shift+Enter and the up arrow move to the previous one. They wrap. Esc, or the magnifying glass again, closes the search and clears what you typed. The copy icon beside it copies the pretty-printed JSON.

The block indents valid JSON with two spaces before it searches. Text that did not parse is shown as it arrived, and the search runs over that text.

Interpretation only hides a successful tool result, so that answer has no magnifying glass. A failed tool call still shows the JSON. An endpoint body is always shown.

Export as Markdown

@export, or right-click a tab and choose Export as Markdown…, saves that tab’s scrollback to a .md file. The save dialog starts in Downloads.

Each command and its output become a console block. JSON stays a json block. Model answers stay Markdown. Notices become quotes.

Secret-looking values are masked before anything is written: tokens, keys, and passwords. The file is written with owner-only permissions.

Diagnostic logs

@logs opens recent API, MCP, Entra token, and OpenAI network activity beside the terminal: request start, connection status, completion, and failures. The panel stays open while you use palettes and run commands.

Failure entries include the destination host, a failure category, a short error chain, and whether proxy environment variables are configured. They stay in memory for this app session, up to 500 entries. They omit full URLs, proxy values, headers, and request bodies.