Desktop messages
Read Agent replies and execution history in the desktop app
System requirements
The macOS app requires macOS 13 Ventura or later.
Inputs and focus
Search fields, settings forms, and multiline editors share a consistent input style. Hover subtly changes the background; clicking or entering with the keyboard keeps a clearer focus background visible. Inputs do not draw an outer focus ring that extends beyond panel or scrolling boundaries. Search headers and chat editors show focus on one input container, without a second background on inner fields. Read-only content remains selectable and copyable, disabled fields appear subdued, and validation messages appear beside the field.
Chat drafts are saved automatically on this device after you pause typing. Leaving the input area or switching sessions immediately saves any pending changes. Each session restores its own draft when you return.
Test System One decision models
Open Settings → Models, select JEV or another model in the decision model section, and use Test decision model in its details. A ready-to-run example is prefilled. Edit the content and decision instructions, choose Boolean, Choice, or Score, then select Run test. Choice accepts one distinct option per line (2–255 options); Score requires a minimum and maximum with a range width of 1–9. Update the instructions to match the selected answer type.
The result shows structured answers, any returned probability or option distribution, usage when provided, and elapsed time. Failures appear in the same form so you can correct the input and retry. Tests use the current account and the model's normal billing. Closing the details does not cancel a request already submitted.
City Remote
Open Settings → General → City Remote to enable HTTP access, initially bound to 127.0.0.1:5314. The switch applies immediately; save changes after editing the address or port. The page shows the actual running status, connection URL or startup failure. Copy the running URL into Chrome settings; there is no need to run city on separately.
Create a City Token on the same page, choosing its name, allowed Agents (or explicitly all existing and future Agents), and expiry. The creation dialog offers 30 days, 90 days, no expiry or a custom date. Plaintext is shown once in a separate dialog: copy it into Chrome's access credential and select Done. Existing Tokens can be edited or revoked. CLI city token manages the same records.
HTTP is disabled by default. Enabled settings are restored on Desktop startup. Disabling access, changing listen settings or exiting Desktop disconnects clients. Desktop and CLI retain the single-host model. Loopback is local-only; when binding another address, clients must use the corresponding machine address and network configuration.
Send follow-ups and take over
When you send a Chat message, it is submitted immediately only while the session is idle and the pending list is empty. While a Turn is still running, or while the pending list already holds messages, new input is appended to the end of that list and submitted one at a time as each Turn finishes, without overtaking what is already queued.
Items in the list are local records until they are submitted: you can edit, delete, reorder, or pause them individually. Option/Alt + Command/Ctrl + Enter appends a paused item that never sends automatically; Command/Ctrl + Shift + Enter bypasses the whole list and submits the current input immediately without disturbing other queued messages. A rejected submission stays in the list as paused so you can fix and retry it.
Each Turn is owned by its initiating actor. The same user can send follow-ups. When another actor owns the work, a queued submission is rejected and stays in the pending list as paused rather than being discarded. To take over, stop the current work, wait for it to finish stopping, then send your message. Stop targets the Turn shown in the interface; refresh and retry if it has changed. A rejected submission does not mark existing work as failed.
Previously registered callbacks still deliver the stopped work's original result, never the answer from your new Turn.
Retry a failed Agent response
When the latest visible conversation message is a finished Agent response with a recoverable error, use Retry on the right side of its error card. The button is disabled while the session is busy, waiting, or submitting, while messages are queued, while history is loading, or while a retry submission is pending. Resolve pending questions or approvals before retrying; the session also checks these when accepting the request.
Retry keeps previous outputs and tool results available, the failed card stays in history, and a new Agent attempt is appended without a duplicate visible user message. It continues from the existing context rather than replaying the entire request. Actions already performed may run again; retry does not guarantee that side effects happen only once.
While the retry is being submitted, the button shows a spinner and prevents duplicate clicks. If submission fails, an error appears and you can retry once the button is available again.
Answer questions and approve operations
Pending Agent questions and approvals appear above the chat input in both one-to-one and group chats. The card has a subtle background and rounded corners. Use the left and right arrows to switch between pending items; group items identify the requesting member. Switching pending items or collapsing tool details in a message preserves your input. For multiple questions, use the left and right arrows to revise an answer. Expand the optional note when needed.
Long content scrolls inside the pending area while the chat input stays visible. Successful submissions leave the pending area; failures display an error and preserve your input for retry. Tool details show execution information without repeating approval cards or approval results. Pending interactions are handled above the input, without a separate right-side response panel.
Compact context manually
In an existing one-to-one Session, type / in the composer and select /compact to fold older stable conversation content into a context summary. The original chat history stays available. You can submit this while the session is running. Compaction joins the Session queue and runs in queue order at a maintenance checkpoint. Compaction and prompts share the Session queue's busy state. The session loading indicator remains active until the queue drains, including across consecutive commands. The chat timeline shows progress and the result, including when there is nothing to compact. New conversation drafts do not show this command.
Summary history uses plain text: user and Agent bodies plus tool results, without call arguments, call IDs, protocol states, or JSON wrappers. Structured results use indented key-value text to preserve field meanings. Compaction shares model-visible message conversion with regular conversations, excluding UI data, activity records, and reasoning. Attachments retain references and metadata without reloading binary contents. Nested image data URLs and explicitly named base64 fields in tool results are replaced with media type and size metadata. Sibling page text, paths, and URLs stay available, and the original tool records remain unchanged. It targets roughly the older 65% of stable projected content at the nearest complete-content boundary, while retaining at least 10,000 tokens of original history. Retention takes priority over the ratio. History at or below this amount, or without an eligible complete unit, is not compacted. Retention excludes system instructions, the previous summary, and tool definitions. Each compaction sends the previous summary, each selected history record, and the final summary instructions as separate plain-text messages in one request. Records keep their original order instead of forming one oversized user message; the summary is not repeatedly rewritten in batches. There is no fixed 16k or 64k input cap. Known model windows reserve 4,000 output tokens and 2,048 safety tokens; only the selected history range is reduced if needed. Unknown windows do not introduce an arbitrary input cap. The current model interface has no tokenizer: ASCII text, code, and JSON are estimated at roughly three characters per token, with other characters estimated by code point. Long encoded strings use a higher token-density estimate rather than the ordinary ASCII rate. These are estimates rather than exact token counts. Each summary has a 4,000-token output limit.
The new summary and boundary are saved once after successful generation. Failure leaves the previous summary and boundary unchanged. Transport interruption retries the same request at most once, discarding any unsaved partial summary. HTTP 400 and other request rejections are reported directly rather than assumed to be context-limit errors. Updated Federation services include the upstream status, an available request ID, and a redacted, length-limited response body to help identify the rejection reason.
Window and panels
The Sidebar, main view, and right-hand BayBar share the window. Resizing the window preserves your Sidebar width where space allows, while the main view grows or shrinks first. When space runs short, BayBar narrows and then hides automatically. If the main view still lacks reading space, the Sidebar hides automatically too. At default width and 100% UI scale, it hides below a window width of 860px and returns at 908px. Your Sidebar width and UI scale adjust these thresholds. Closed panels release their full layout width.
Drag the boundary between a panel and the main view to adjust its width; releasing the boundary saves your choice. Temporarily shrinking the window does not overwrite saved widths. Automatically hidden panels return once there is enough space; manually closed panels stay closed. Explicitly opening BayBar or following a file link in a narrow window displays it over the right-hand content area. Resizing the window returns it to the available-space layout.
When the Sidebar is automatically hidden or manually closed, hover over the left window edge or its top toggle for about 150ms to reveal floating navigation. It overlays the main view without changing the main view's position or width. Moving away hides it after about 250ms; related menus, resizing, and keyboard interaction within navigation keep it open. Click the top toggle to pin it open. If space is insufficient, it stays floating until you click outside or press Escape.
Use the top window controls or ⌘/Ctrl+B to toggle the Sidebar and ⌘/Ctrl+L to toggle BayBar. Window resizing and panel dragging follow your movement directly. Panel toggles use a short animation, omitted when reduced motion is enabled.
Session hierarchy
Within each Workspace in the Works sidebar, child Sessions appear directly below their parent and are indented by depth. Root Sessions and siblings are ordered by live status first, then by most recent update. If a parent is outside the current Workspace section, its children remain visible as root Sessions. Pinning moves the entire subtree together, preserving hierarchy and expansion state. Archiving a parent also archives all descendant Sessions. Finish or stop any running or queued work in the subtree before archiving.
Each parent shows up to 3 direct child Sessions by default. A fourth “Show more (N left)” row expands the remaining children; “Collapse child sessions” at the end returns to 3. Each nested parent expands independently. Workspace pagination counts root Sessions, and range selection includes only Sessions currently displayed. If the current or a selected Session falls beyond the third child, the necessary parent lists expand automatically and cannot be collapsed while needed. Switching Sessions or clearing selection restores the previous manual expansion state.
Pin conversations
In the Works sidebar, open a conversation's more menu and choose Pin to top. The root conversation and all its descendants move into a Pinned section above every Workspace, and stays visible when Workspaces are collapsed. Pinned conversations keep their pin order, newest first, and each row shows the Workspace it belongs to. The chat header menu offers the same action as Unpin. Child menus show “Pin parent conversation” or “Unpin parent conversation”; both actions apply to the whole tree. Unpinning returns each Session to its Workspace, and new children automatically follow the root. Pinned trees also show up to 3 direct children per parent by default, with expand and collapse controls. Pinning applies to Works sidebar conversations, including Group conversations.
Share messages and conversations
Shared images and PDFs include the Downcity logo and name at the start of the document, in both preview and saved files.
Open the more menu below a completed Agent reply and choose Share, then Save as image, Save as PDF, or Save as Markdown in the preview to save its full content, including the Agent name and timestamp.
Choose Share from the Chat Session's top-right menu, then Save as image, Save as PDF, or Save as Markdown. Exports read the complete history and preserve the original order of user messages and Agent replies. Reasoning, tool activity, and internal context are excluded. Markdown keeps editable text and attachment links. Images and PDFs preserve code blocks, tables, math, images, and static views of built-in visualizations. Third-party or unavailable visualizations use their published text summary.
Sharing opens a preview with format tabs at the top, a centered preview canvas, and a fixed bottom bar for the content option, copying, and saving. Images scale proportionally to the available width. Long images keep all sections in one continuous scroll.
When sharing a single Agent reply, enable Include previous user message to place the nearest preceding user message above it, including sender, timestamp, text, and attachments. This option is off by default and appears only when a previous user message exists. Changing it updates the preview and content saved in every format. Messages from earlier history are supported without manually loading the chat first. PNG shows the generated image sections, with a Copy image button in the bottom bar that copies the section most visible in the preview to the clipboard without saving a file first. PDF shows the paginated file, and Markdown shows the source to be saved. Click the selected format's Save as… button to open the system save dialog. Cancelling that dialog keeps the preview open; closing the preview releases its prepared content. Resource failures appear in the preview.
Short images use a file save dialog. Long content asks for a directory and creates a new folder containing numbered PNG sections. PDFs paginate automatically and keep selectable text. After saving, you can open the file or image folder directly. Cancelling does not create an export. Image resource failures show an error so you can fix the resource and retry.
Messages and files
Click a workspace file link in a conversation to preview it in the right-hand file panel while keeping the conversation visible. Files in other registered workspaces also open in this panel. Links with a line number jump to that line. Web links open in your default browser.
The file panel and Workspace view select a preview by file type. Markdown renders as a document; local .html and .htm files render as static web pages with relative stylesheets, fonts, and images. Scripts and in-page navigation are disabled. CSV and TSV files display as tables with row and column numbers, preserving quoted separators and line breaks. Tables display up to 1,000 rows and 100 columns. Use Source mode in the file menu to read the complete original text for Markdown, HTML, CSV, or TSV; text links with line numbers open in source mode.
Relative image paths in Markdown files, such as images/chart.svg or ../images/chart.png, resolve from the current document's directory in both BayBar and Workspace previews.
Fenced Markdown code blocks labeled mermaid render as diagrams and adapt their layout to the available width. Diagrams follow the current theme. Copy their source or open the fullscreen view to zoom, pan, fit to the window, and download a PNG with the current theme. Incomplete streaming syntax keeps the last successful diagram visible; if parsing still fails after generation finishes, the source and a retry button appear.
Fenced Markdown code blocks labeled svg render as images that fit the available width, in both BayBar file previews and chat messages. Incomplete streaming content, invalid SVG, or image load failures display the source instead. SVG loads in an isolated image context without executing scripts.
PNG, JPEG, GIF, WebP, SVG, AVIF, APNG, BMP, and ICO files display as images. Switch between fitting the panel and viewing the original size. Images load separately from the text reader. Other binary files show an Open with default app button that opens the file in its associated system application. If opening fails, the reason appears and you can retry. Text previews remain limited to 2 MB; code and configuration files display as source.
Select text in the right-hand BayBar file panel to show a floating Quote button near the selection. Clicking it adds a reference to the current chat input with the workspace, file path, and selected text; source mode also includes the selected line range. The reference preserves the content at the time of quoting and can be saved with the draft or removed before sending. Clearing the selection, scrolling, switching files, or updating the file hides the button. Markdown, table previews, and source mode support text quoting. Switch HTML previews to source mode to quote text; images do not support text selection references.
Agent messages use two columns. The left column stacks the avatar and optional collapse button. The right column shows an info bar with the Agent name and timestamp, followed by the message body and file changes, with spacing between the info bar and body. Message actions such as copy, quote, and fork appear below all content, including the file changes card when present.
Messages with execution history have an arrow button below the avatar in the left column. The button stays visible and gains a subtle background on hover. Its arrow points right when collapsed and down when expanded. Click it to toggle the history, or use the keyboard.
History starts expanded while the Agent is working and collapses when the message finishes. Collapsing hides the history and keeps the final answer fully visible, without a tool summary row. If a message only contains execution history, the arrow remains available to reopen it.
Both actions use the button as a scroll anchor. Once you toggle it manually, that message keeps your choice. Messages without execution history display the answer directly without a collapse button.