Results and tools

From the same task, you can inspect more than its conversation: changed code, files, reports, and running processes. This page covers shared result-review surfaces. Use cockpit browser for web operation and App Surface for a connected mobile screen.

Use the right side panel

The right side panel in task details opens supporting information and interactive surfaces without leaving the conversation. It can show diffs, files, the attachment list, the project explorer, HTML Surfaces, the in-app browser, App Surfaces, side terminals, background logs, child tasks, Talk Rooms, and Asks when they are relevant.

The Desktop Ask tab lists every Ask waiting for an answer on this device, not only Asks from the selected task. Open it from its count badge to review, answer, or close an Ask with the same content as the dedicated Ask window. The tab remains available when Ask windows are disabled under Settings → Notifications. See Ask for details.

Check the panel type and target path before acting. Closing the panel does not stop the task or its browser session. The panel remembers its width, and narrow layouts make long content and tables horizontally scrollable.

In the PWA, Task panel in task details provides context-dependent tabs for child tasks, HTML Surface, an image opened from the conversation, diff, Cockpit Browser, App Surface, side terminal, skills, Fleet, Creative Studio artifacts, and Talk Room. On a narrow screen it opens as a bottom sheet with previous and next controls, a horizontally scrolling tab row, and approximately half-height and full-height states. On a wide screen the panel sits beside the chat; a wider layout can also keep the task navigator visible. Changing width or orientation preserves the selected tab, target, drafts, and scroll positions for the task while the presentation switches. Closing the panel unsubscribes the view without terminating its terminal or browser. The attachment list, general files, project explorer, and background logs are not tabs in this PWA panel.

Reopen content from conversation cards

When an agent presents a file, diff, HTML Surface, or browser tab, a presentation card remains in the task conversation on Desktop and the PWA. Choose Open to reopen the matching right-side panel on Desktop or the target in that task's Task panel on the PWA. A newly arrived card does not switch away from the document or panel you are viewing on the PWA. Closing the panel and reopening a card preserves the conversation position and composer draft.

An HTML Surface card opens the saved Surface. File and diff cards read current content rather than a copy made when the card was created. A browser card refers to the same Browser Identity, session, and tab on the same host, not only to its URL. If the target was deleted or closed, belongs to another host, or is unavailable to this task or device, Cockpit reports the error instead of substituting another target.

Review diffs and files

The diff surface shows changes recognized by Git. Review additions, modifications, and deletions by file, and compare the actual scope with the agent's explanation before accepting completion. Untracked temporary files and files outside the project may not appear in the diff.

File preview supports text, images, audio, video, PDFs, and other recognized formats. Its toolbar stays in a separate row above the document and wraps its controls in a narrow panel, so it does not cover the content. After focusing a file body on Desktop or the PWA, Cmd+A / Ctrl+A selects only that file body, excluding the chat, file list, and viewer controls. Inputs, search fields, and the active text editor keep their normal select-all behavior. Selecting text shows a quote action without shifting the preview or losing the selection; use it to add the file path and line range to the task composer. A writable regular text file up to 1 MB can be edited with the pencil button. Changes save automatically, and Cockpit does not provide an undo action, so confirm the path and Git scope first.

When a Markdown link in a Desktop conversation points to a recognized local file target, selecting it opens the preview in the right-side panel. On Windows this supports C:\\... and C:/... drive paths, \\\\server\\share\\... UNC paths, and the corresponding Windows file: URLs. Cockpit checks a drive path before presenting an active link. It does not contact a UNC path merely to render the conversation; the first read occurs only after you select the link, and an unavailable share reports an error in the preview. Unsupported or unsafe destinations render as ordinary text instead of an active link. Previewing never executes the file.

Desktop initially fits an image preview to the panel. Select the image to zoom to 2× around that point, and select it again to return to the fitted view. You can also use Zoom in, Zoom out, and Fit to panel, or press + / =, -, and 0 / Esc while the image is focused. A zoomed image scrolls inside the panel.

Desktop video preview reads the needed ranges from the local file instead of copying the whole file into the renderer, so you can seek in large videos. It plays MP4 and WebM as well as MOV files encoded with H.264 or HEVC. An unsupported format or codec, a moved or deleted file, or a file that is still being written produces a reason and a Show in Finder action. If playback does not advance because the audio output device is unresponsive, Cockpit asks you to check the system sound output.

When Desktop previews an .html or .htm file, Open in the in-app browser opens that local file in a new browser tab for the same task. If the file is being edited, Cockpit saves the current content first and does not open the browser when that save fails. This does not transfer an HTML Surface; it is a way to verify an HTML file from the working directory in a normal browser renderer.

The Desktop project explorer can switch among the folders in the task's project and marks the task's working folder. Drag the edge of the folder list to resize it, or collapse the list to give the file tree more room. The explorer preserves the selected file across refreshes and opens files in preview. Inspect both the selected project folder and file path before sharing anything that could contain secrets.

Find text in a Desktop side panel

Use Find in content or Cmd+F / Ctrl+F in the active file preview, editable text, diff, or HTML Surface. Enter and Shift+Enter move between matches; Esc closes the search. Search applies to that surface's text, not the whole project. Images, video, and text unavailable to the surface are not OCR-searched. Use the browser's own page search for an in-app browser tab.

Distinguish HTML Mode from HTML Surface

HTML Mode is a skill an agent uses to compose an interactive HTML final result. HTML Surface is the product surface that stores that HTML for a task and displays it in the right side panel.

HTML Surface is not a general-purpose web browser. Use it for agent-created reports, comparisons, and dashboards; use the in-app browser for navigating external sites or operating forms. HTTP and HTTPS links in an HTML Surface open in the external browser, while other URL schemes are ignored.

A Surface containing <meta name="cockpit-scripts" content="isolated"> can run inline JavaScript in an isolated environment on Desktop and the PWA. Use it for operations contained within that Surface, such as calculating from inputs, toggling sections, or updating a chart. Register events with addEventListener or similar APIs; inline event attributes and javascript: URLs remain unavailable. Surfaces without the marker and Display notices never run scripts.

An isolated script cannot access Cockpit, Node, local files, authentication, cookies, or app storage. Network requests, external resources, embedded pages, navigation, downloads, and popups are also blocked. Data reaches the task only when a person genuinely selects a declared action or validated submit control. Script-generated clicks and messages cannot send, and --non-interactive permits local behavior without task messages. Updating, switching, or reopening a Surface starts fresh script state. If a script stops, reopen the Surface or ask the task to fix its HTML. See the HTML reference for the complete limits and Security and data for the data boundary.

From the CLI, cockpit html show --stdin stores HTML and cockpit side-panel html displays it. See the cockpit html reference for the exact contract.

Open an unseen HTML Surface

Desktop and the PWA count HTML Surfaces that have arrived but have not yet rendered in that task's visible HTML panel. A badge appears on the panel opener or HTML Surface tab. If you are already following the latest Surface, Cockpit follows the new one. If you are reviewing history or an older Surface, your view stays in place and a notice offers Open latest. Opening the unseen shortcut jumps to the newest unseen Surface; older unseen items remain marked in History.

A Surface becomes seen only after its content renders in the visible panel. The seen state persists across an app restart. Dismissing the arrival notice does not mark the Surface seen, and switching to another task does not clear its badge.

Review Display notices

cockpit display puts a reminder, progress update, or lightweight status screen in front of the person as a Display notice that does not request a response. Desktop uses a dedicated window; the PWA includes notices with Asks in Inbox. When the originating task still exists, either surface can open that task directly.

Closing a Display notice sends no answer to the agent and resumes no task. When the same task repeats a notice with the same kind, title, and body, Cockpit reuses the open notice. A resend within ten seconds after closing is also treated as the same notice, so an agent does not retry merely because the duplicate was suppressed. Identical content from different tasks remains separate.

The PWA closes a Display notice immediately even while disconnected and sends that dismissal to the host after reconnecting. If the same notice arrives during resynchronization, it does not return to the Inbox.

The CLI can list open notices and close one by ID:

cockpit display list
cockpit display list --task <task-id>
cockpit display close <display-id>

See the cockpit display reference for the exact duplicate key, response fields, and errors.

Continue to a dedicated operating surface

The in-app browser lets a person and agent operate the same real web page. See cockpit browser for page state, meaningful element targeting, and postconditions, and Browser Identity for sign-in isolation.

App Surface attaches a running Android target or iOS Simulator to one task. See App Surface for readiness, attachment, accessibility actions, coordinates, recovery, and safety boundaries.

Use side terminals and background logs

A side terminal is a shell session separate from the task's agent process. Before running a command, confirm the session name, current working directory, and target host. Closing a terminal ends that shell but does not complete the task.

In both PWA terminal views—the task's main Terminal view and a side terminal—the key bar sends Esc, Tab, Enter, and arrow keys directly to the host terminal. Open Modifier keys to send Ctrl+C, Ctrl+X, Ctrl+S, or Shift+Tab. These are terminal input sequences, not browser shortcuts, and have the same effect as typing them at the host: for example, Ctrl+C can interrupt the foreground process. The menu is disabled when the terminal is not writable.

Background logs show output from long-running processes started by an agent. In Antigravity Native UI, when the agent rechecks a background process and returns an interim answer that it is still running and must be awaited, the task remains in progress through the completion notice, later tool calls, and final answer in that same turn. A persistent server that is intentionally left running after the final answer is different: it remains visible after the turn completes with a Running, Completed, Failed, or Stopped state. Visible output alone is not completion. Check the exit code, generated artifact, listening port, test result, or another success condition appropriate to the request.

See the cockpit side-panel reference when controlling panels and terminals from the CLI.

Use context-specific panels

The child tasks panel shows the state and reports of tasks that belong to a parent. See Task management (CLI) for parent-child relationships and reports. The Talk Room panel shows a shared participant conversation. See Talk Rooms for participation, notifications, and mentions.

Skill details show the selected skill's instructions and usage conditions. In the PWA, Skills lists the project and global skills that the host discovered for the task and searches their names and descriptions. A detail view shows the description, argument hint, defining SKILL.md files, agents that use each definition, and the file body. Definitions can be switched when agents use different files. The PWA shows at most the first 256 KiB and cannot edit, delete, install, or insert a skill. A skill does not expand task permissions. Publishing, deletion, and external messaging remain subject to the normal approval boundary.

Complete result review

Use this sequence to avoid treating a displayed result as a completed outcome:

1. Re-read the task objective and acceptance criteria.
2. Review the diff and any generated files outside Git.
3. Check applicable evidence such as tests, builds, screens, or network results.
4. Check for secrets, destructive changes, and external publication.
5. Save or share the required result before completing the task.

See Task list for state, completion, and deletion, Task details for follow-up and resume, and Security and data for data boundaries.