Dashboard

The dashboard shows what Sortie is doing now and what it did before: which issues need a person, which agents run, how each issue moves toward a merged pull request, what finished runs used and cost, and whether Sortie itself is healthy. It is a web application served from inside the Sortie binary at /ui/, on the same port as the JSON API and the Prometheus metrics. It needs nothing else installed and loads nothing from other hosts: no CDN, no web fonts, no external services.

Opening the dashboard

Sortie serves the dashboard whenever its HTTP server runs. The default address is http://127.0.0.1:7678/. Sortie answers / with a temporary redirect (302 Found) to /ui/, so either address opens the dashboard.

A flag overrides the matching server key in WORKFLOW.md, and a change to either needs a restart. See the --port and --host flags and the server extension.

Every screen has its own address, so a link to an issue or to a filtered view can be bookmarked and shared, and the browser’s Back button returns to the previous screen or filter.

An address under /ui/ that names no screen shows “This page does not exist.” with an Open Overview button.

Security

The server refuses a dashboard action that a browser sends from a page on another origin, so a web page you have open cannot press these buttons for you. A reverse proxy must pass on the browser’s Host header unchanged, port included; see cross-origin requests.

Layout

Side rail

The rail lists the screens in groups separated by a divider: Overview, Pipeline, History, and Analytics, then Health, Workflow, and Prices. A Filter field above the list narrows it by name, and Enter opens the first match. The rail also shows the Sortie version, the project the workflow tracks, the status card, and these controls: Commands opens the command palette, Shortcuts opens the shortcut sheet, and Theme opens the theme menu.

Overview carries a count badge while items need attention. The badge is amber, and red while any open item is critical.

The project sits on its own line under the Sortie name. It is the value of tracker.project, such as sortie-ai/sortie for a GitHub tracker or a Jira project key, cut to the width of the rail with the whole value on hover. The line is absent while the workflow sets no project. The same project shows in the browser tab, in the narrow bar, and in the Tracker panel of Workflow, so the tabs of different Sortie instances can be told apart.

Status card

The status card sits above the rail’s controls and links to Overview. A dot and a headline give the one condition that applies, and the first row of the table wins when several apply.

A second line under the headline says how many agents run: “No agents running”, “2 of 4 agents running”, or, when only one agent may run at a time, “Agent running” or “Agent idle”. Acknowledging an item removes it from the count of items that need attention, but the card reads N acknowledged rather than All clear while the item stands. It does not clear Degraded, which follows the failing check itself.

Health banner

While a health check fails, a banner under the top bar names each failing check, the time it began failing, and the error it reported, with an Open Health link on every screen except Health. The checks are the WORKFLOW.md reload, the dispatch preflight, the tracker poll, the database check, and, when a source control provider is configured, the reads from that provider.

Top bar

On screens 768 px wide and up, the top bar shows the date and time, or on an issue page or session view a breadcrumb that leads back to the screen the reader came from. At its right it shows the live indicator and a Search or run a command button that opens the command palette. Clock times throughout the dashboard use the browser’s time zone.

Browser tab

The tab title and icon carry the same condition as the status card. The title reads the condition (“All clear”, “Waiting on a person” for N acknowledged, “Needs attention”, or “Degraded”), a hyphen, the tracked project and another hyphen while the workflow sets one, and “Sortie”, with the attention count in parentheses in front of it while any item needs attention. A tab can read “(2) Needs attention - sortie-ai/sortie - Sortie”. Before the first answer the title is “Sortie”. The icon is the Sortie mark, with a yellow dot for Needs attention and a red dot for Degraded. All clear and N acknowledged carry no dot. While live updates are paused, the title and icon stay as they were.

Narrow screens

Below 768 px the rail gives way to a bar at the top of the page with the Sortie name, the tracked project under it while the workflow sets one, the condition (“All clear”, “N acknowledged”, “Needs attention” with its count, or “Degraded”), and a Menu button that opens the command palette, which reaches every screen. The top bar, with its clock and live indicator, is hidden, and so is the station header of Pipeline. The peek takes the full width. Keyboard shortcuts stay available, including P to pause.

Themes

The theme is System (follows the operating system), Light, or Dark. The Theme menu in the rail foot names the current choice and sets it, the T key moves to the next choice in that order, and the palette has one command per choice. The choice is stored in the browser.

Loading and failure states

Before the first answer the page body reads “Loading”. When Sortie does not answer, it reads “Sortie is not answering. The dashboard keeps trying.” A screen that fails to load, which happens in a tab opened before an upgrade, shows “This screen could not be shown.” with Reload and Open Overview buttons.

Overview

Overview answers: does anything need a person right now? The page opens with a headline sentence and a lede, then the blocks below.

The lede under the headline says what else Sortie is doing, for example “Everything else is handled: 2 agents are running and 1 pull request is waiting on CI.”. It counts running agents, pull requests waiting on reactions, scheduled retries, issues between stages, and acknowledged items that wait in Active, and reads “No agents are running.” when there is nothing to count. Under “N acknowledged items wait on a person.” the lede leaves the acknowledged items out, because the headline already counts them.

Needs attention lists the unacknowledged attention items, critical first and then oldest. Each item shows its reason in bold, the issue title and key, why the item exists, what clears it, how long it has existed, and its buttons. A click outside the buttons opens the peek of the item’s issue.

While nothing needs attention, a calm line and a row of tiles take the place of the list, unless a health check fails or the first run is still to come. The calm line reads “Nothing is parked, escalated, stopped or waiting on a person, and Sortie is healthy.” It shows only when no acknowledged item stands either; under “N acknowledged items wait on a person.” the tiles show without it. Each tile links to the screen that explains its figure.

Usage appears while a daily, weekly, or monthly spend ceiling is set or an agent kind has reported a usage limit that has not reset, below Needs attention and above Active. Each part shows only when it has data, and the section is absent when neither does. It holds one card for the budget and one card for each agent kind that reported a limit.

The Budget card appears while a spend ceiling is set. It has one meter for each window that is set, Daily spend, Weekly spend, and Monthly spend, in that order. Each meter reads, for example, “$41.27 of $100.00”. While the spend is a lower bound, the amount is cut and underlined, and its hover reads “Some runs could not be fully priced or measured, so the real cost is higher.” The bar changes color once the spend reaches the ceiling. A line under the meter reads “Resets Friday 27 March, 00:00 UTC”, or “Holding dispatch, resets Friday 27 March, 00:00 UTC” while the window holds dispatch. The windows are UTC days, UTC weeks, which start on Monday at 00:00 UTC, and UTC months, so the reset time is written in UTC, while Ended today and Runs finished today count the day in your browser’s time zone. While several windows have reached their ceiling, dispatch stays held until every one of them clears. When an agent card is also shown, the card carries the note “Estimated at API prices”, because the figures are Sortie’s estimate and not the plan the agent bills against. See how to control agent costs.

An agent card is titled with the agent kind and appears for each kind the workflow can dispatch to, in alphabetical order, once that kind has reported a usage limit. It holds one entry per limit the agent reported, for example “5-hour limit” or “Weekly limit”. An entry reads as a meter when the agent reported an amount, as “7.08 of 1,000 credits”, or a share, as the percentage used, and as the label with a status word, “Under the limit”, “Near the limit”, or “Usage limit reached”, when it reported neither (“Status not reported” when it reported no status either). A line under the entry reads “Resets” with the time in UTC, or “Reset time not reported”. A near or reached limit that has a meter also puts its status word at the start of that line. A limit stops showing once its reset time has passed, and a card whose limits have all reset is hidden. A card shows “Reported” with a time while its newest report is an hour old or older, and so does a single entry whose report is that old and differs from the card’s. The limits are the rate_limits member of GET /api/v1/state. Sortie holds them in memory, so none shows after a restart until the agent reports again.

Active lists every issue Sortie is working on or waiting for, in the order Sortie picked the issues up. Beside the heading it shows the issue count and a tally such as “2 retrying, 1 held”, and a List and Pipeline switch that moves between this block and the Pipeline screen with the filters kept. Lifecycle chips filter the list, and the Rule menu filters by dispatch rule or stage.

A chip shows only while it has issues, and the whole row of chips shows only while more than one lifecycle is present. The Rule menu shows only when the workflow has dispatch rules. It lists the rules, grouped by stage chain, with a count each, and it has a search field. A filter that leaves nothing reads “No active issue matches these filters.” with a Show all button.

Each row shows the issue’s mark and status word, the issue title, a second line with the key, the rule (or the stage and its place in the chain, such as “implement, 2 of 3”), and the agent kind, and a time. The time counts down to the due time for a retry and counts up from the start of the current state for every other row. A row of an issue between stages whose hold is recorded adds a line under the second line with the reason, for example “Waiting to confirm the stage move”. A click opens the peek, which carries Sortie’s sentence about the issue.

Not dispatched lists the issues Sortie could start but holds back, below Active and above Ended today. The block shows only while at least one issue is held, and beside its heading it shows the issue count. Each item shows the issue title and key, why Sortie holds the issue back, what releases the hold, and how long ago the hold began, written as a time of day from one hour on. Open issue opens the issue in the tracker in a new tab; a click on the item opens no peek. The reasons are an open blocker with its key and state, blockers Sortie could not read, has not read yet, or got only in part, a full agent slot limit with its usage, no free SSH host, a spend ceiling, an agent provider’s usage limit, and comments Sortie could not yet read for an issue a person released from a park. The HTTP API reference lists every reason with its wording. A spend ceiling and a usage limit each add the time left until the window resets, as in “Usage limit reached for claude-code, resets in 3h 20m”, and release when it passes. A usage limit that stops one model of an agent kind alone names the model, as in “Usage limit reached for sonnet on claude-code”; issues routed to other agents or models keep dispatching. The list is empty after a restart until the first poll tick has run.

A held issue is not in Active, and it adds no attention item, no mark, and nothing to the headline or the lede. A spend ceiling keeps its own item under Needs attention. The Held status word of Active is a different thing: it marks an issue whose attention items are all acknowledged.

Ended today lists the issues that ended today and that Sortie no longer holds, newest ending first, each with its mark, its ending word, such as “Done”, “Review”, or “Merged”, and the time. Beside the heading a tally line lists, for example, 2 issues ended, 23 runs finished, 7 succeeded, 16 failed, and 48.03M tokens, plus stopped and cancelled counts when there are any and an estimated cost, such as “$12.40 estimated”, when a rate source is available. A token total or cost that is a lower bound is cut and underlined, with the hover “Some runs were not measured or not fully counted, so the real figure is higher.” on the tokens and “Some runs could not be fully priced or measured, so the real cost is higher.” on the cost. Without a figure the tally reads “tokens N/A” or “cost N/A” (see N/A), “tokens not recorded”, or “cost unpriced”, whose hover reads “The configured rates leave these runs unpriced.” A History link follows. The tally reads “No run finished today.” when none did, and it is absent before the first run and while run history is unavailable (“Run history is not available.”).

Status word and mark

Active, the lanes of Pipeline, the issue headers of History, and the Issues group of the command palette give each issue one word for where it stands. Every list except the palette draws the same mark beside the word. Ended today uses the ending word of the issue.

Approval replaces Waiting only for a pull request whose review reaction found no comment to answer and whose forge reports that a required approval is still missing. A standing escalation outranks it, and an issue whose pull request has comments to answer reads Waiting. An unacknowledged attention item outranks an acknowledged one, and both outrank the state the issue is in. An ended issue whose ending Sortie did not record reads “Ended” with no mark.

Run outcome words

A finished run carries its own word wherever it is listed: the run cards and chapter lines of the issue page, the So far list of the peek, the head and the Sessions panel of the session view, the status column of History, and the sessions in the command palette. The word is the run’s recorded status: Succeeded (check mark), Failed and CI failed (cross), Needed input, Stopped at a budget, and Usage limit reached (paused circle in the attention color), or Cancelled (no mark).

A run recorded as succeeded reads differently when its agent ended the session by declaring an outcome in the .sortie/status file.

A run with no declared outcome reads Succeeded, and so does a run recorded before Sortie kept declared outcomes. Any recorded status other than succeeded keeps its own word, so a needs-human-review run whose handoff Sortie withheld reads Failed. The Run status filter of History and the figures of Analytics follow the recorded status, so a run that reads Action required still counts as succeeded there.

The sentence the agent wrote after the status word shows beside the outcome, in curly quotes that mark it as the agent’s own: in the run card on the issue page, in a note under the facts line of the session view, and as the hover on the status cell in History. The other places show the outcome word alone. A run that declared nothing, or wrote no sentence, shows no quotation. The HTTP API serves the same outcome and sentence with each run.

Pipeline

Pipeline answers: where does each issue stand on its way from the tracker to the end of its pull request? It shows the same active issues as Overview, plus the issues that ended today, each as a lane across the stations of the workflow.

A line above the lanes names how many items need attention, links each affected issue, and links Open Overview. The Active header, the lifecycle chips, and the Rule menu work as on Overview, and the chips add Ended today.

The stations are fixed by the configuration, never by an issue, and they read left to right:

A bracket labeled “PR loop” spans the reaction stations. The station header above the lanes writes the count of lanes standing at each station under its name, in the attention color while one of those lanes needs attention. Each lane shows the issue title, key, route, and agent, its status word, and the track with the issue’s mark at its station and the time above it. On an issue in a stage chain, a stage meter under the Agent station shows the stage and its place in the chain, such as “implement 2 of 3”, while the issue stands at the agent. Elsewhere the meter shows how many stages are done.

The heavy line of the track runs on through every reaction station the issue worked in its current pass, not only to the station it stands at. A bot review whose triage command answered handled holds no station: its issue stands at the handoff station (or at Agent when the workflow has no handoff state) until the bot review’s comments change, also after a restart, and the station header counts it there. The issue reads Waiting wherever the status word shows, and Sortie’s sentence reads “The triage command handled the bot review of PR #N, so Sortie starts no session for it”, followed by the time of the next check. The Bot review station counts a handled triage as Sortie having acted. A pull request that waits only on a required approval stands at the Review station, marked with a dashed circle and read as Approval; a workflow without the review_comments reaction never shows this state.

A reaction station that the issue is not standing at reads from what the reaction did during the issue’s current pass. Hovering the station names the reading and, where the reaction counts its work, the count.

A legend under the lanes explains every mark in use. With more than 24 lanes the lanes compress to a dense form without counts or meter captions, and, while no lifecycle chip or rule is chosen, they group by station: one line per station lists the issue keys and expands with Show lanes and Hide lanes. A click on a lane opens the peek.

Issue peek

The peek is a drawer that shows one issue over Overview or Pipeline without leaving the list. It opens from a click on a row or lane, or from Space on the selected row, and it has its own address, so it can be shared. While it is open the list holds still, and the live indicator reads “Holding still while you read”. J and K move the peek to the neighboring issue, and Esc, Space, the Close button, or the browser’s Back button close it. Open page opens the issue page.

An issue Sortie no longer knows reads “Sortie no longer knows” followed by its key. Showing an issue, in the peek or on its page, marks its ending as read.

Issue page

The issue page answers: what happened to this issue, what happens next, and what has it cost? It opens from the peek, from History, from the palette, and from the Overview tiles, and Esc returns to the screen it was opened from.

The page opens with the issue’s tracker state and type, its title, Sortie’s sentence about it, and, for a running issue whose agent has been quiet, a stall notice. Buttons follow: Open live session or Last session, Open issue, and the pull request button. Under them a Pipeline card draws the issue’s lane with the station names, with the stage meter and, at reaction stations, the counts. From 1280 px wide the story sits beside a margin of panels. Below that the margin follows the story.

The story is the issue’s history, newest at the bottom, grouped into chapters.

• Each stage of a chain is a chapter named after its rule, and a stage that ran again reads “again”. Work on the pull request, such as CI fixes and review fixes, forms chapters named “Pull request” with its number. Work outside a stage chain forms chapters named “Work”.
• An issue in a stage chain opens with a summary of the stages done, the current stage with its place, such as “implement (2 of 3)”, and the stages ahead. Its All stages button lists every stage with its time span. A stage that did not hop to the next reads “hop to” the target “not made” with the reason in plain words: the next stage’s label could not be added, or the limit on automatic hops in a row was reached. Elsewhere a hop reads the same way, such as “moved to implement”.
• Every chapter but the current one is folded to one line with its run count, time span, and outcome. Unless the last run made or missed a hop, the outcome is its outcome word with its first letter in lower case, such as “action required”. An acronym keeps its capitals, as in “CI failed”.
• Each run is a card with its number, its outcome word, what started it (“CI fix”, “Retry after an error”, “Continuation”, and so on), its time span and duration, its error when it failed, the sentence its agent wrote with a declared outcome, its turns when it completed any, its tokens, its estimated cost when a rate source is available, and a Session timeline link to the session view. The tokens and cost of a finished run read as in the Tokens and Est. cost columns of History, hovers included. The tokens of a running session read “not measured” until its agent reports usage, and its cost is left out until then. A CI failure that Sortie recorded is not a run card, since no agent ran: it is one line in the story, “CI checks failed”, with its time.
• The current chapter closes on Sortie’s sentence about the issue, timed at the moment the issue ended once it has, and at the current time while it is active. When older runs are not loaded, a line says how many are not listed, and Show older runs loads them.

The margin holds these panels, each only when it applies.

A failed read of run history shows “Run history could not be read.” above the story. An issue Sortie no longer knows reads “Sortie no longer knows” followed by its key.

Session view

The session view answers: what is this agent doing, or what did it do? It shows one agent session of one issue, live while the session runs and from the stored events once it ends. It opens from a run card, from the Open live session and Last session buttons, from O, and from the palette. Esc returns to the issue page.

The page head shows the issue key and title, the heading “Session N of” the key, and a line of facts: agent kind, model, route, the reaction that started the session when a pull request fix did, the SSH host when one is used, its time span and duration, and its status, such as “Running, turn 3 of 20”, “Succeeded, 4 turns”, or “Action required, 4 turns”, with no turn count while the run completed no turn (see run outcome words). A running session whose agent has sent no event for longer than usual shows a stall notice, and a running session with no stall timeout shows a notice that stall detection is off. A finished session shows a note under the facts line, alarmed only when the run failed. It gives the error when the run recorded one, then the sentence the agent wrote with a declared outcome in curly quotes, then, for the newest session of an issue that has nothing running, the sentence the issue page shows for what happens next. The status in the head is not repeated in the note.

Events is a scrolling pane with one line per event. Every tool call is one line: an icon for its kind (a terminal for a shell command, a file for a read, a file with a pencil for an edit, an open book for a skill, a wrench for any other tool), the call itself, and its duration when the agent reports one. The call reads as follows, with secrets masked.

A line too long for the pane is cut at the pane’s width, and hovering it shows the whole text. A failed call draws its line inside the failed mark.

Two or more consecutive tool calls fold into one line that counts them by kind, in the order the kinds first appear: “3 commands, 2 file reads”, with “file edit” for an edit and “tool call” for every other tool, such as “4 tool calls”. After the counts the line shows the total duration of the calls that report one and, when any call failed, “N failed” in the failed mark. A click expands the line into the calls it holds. A single call between other events is a line of its own, and a skill call is never folded: it stands alone and ends the fold before it, so the skills of a run read in order among the events. A turn that ended reads “Turn N completed” with its tokens and duration. Events the dashboard no longer holds read as a count of events not retained, and a run with none reads “No events retained”. The pane keeps the newest 1,000 events of the run. When a failed turn closes a finished session, its line reads the run’s outcome word with that word’s mark, so a session that stopped at a usage limit shows the paused circle, not a cross. The foot line counts the events.

A live session follows its newest event until the reader scrolls up. Then a Jump to latest button appears, with a count of new events, and the foot line reads “Live” with the time of the last event, and “following new events” while the pane follows. Pausing live updates holds the pane still and the foot line reads “Paused”.

An address that names no session reads “No such session”. The HTTP API describes which events Sortie keeps and for how long.

History

History answers: what finished, how did it end, and what did it use? It lists finished runs grouped by issue, the issue with the newest ending first, 20 issues at a time. Show more issues loads the next 20.

Filters sit above the table, and each is part of the address.

Each issue is a header row and its newest runs beneath it. The header shows the issue’s mark, the issue title linking to the issue page, and a second line with the key, the issue’s status word, its run count, its tokens, its cache reads when it has any, its estimated cost when a rate source is available, and the amounts its agents reported in their own unit, one per unit, such as “7.08 credits”. At the right it shows when the issue ended. The tokens and cost of the header are totals of the issue’s runs: a total that is a lower bound is cut and underlined, a total without a figure reads “tokens N/A”, “cost N/A”, or “cost unpriced”, and a cost that holds an agent-reported US dollar amount carries a hover that gives the exact cost and the share the agent reported, as in “$4.20. $1.10 of it is the amount the agent reported for acme-coder-1, which no price table lists.” Show more runs loads the issue’s earlier runs.

With no run on record the screen reads “No run has finished yet.” A filter that matches nothing reads “No finished run matches these filters.” with a Clear filters button. Without run history the screen reads “Run history is not available.”, and a failed read reads “Run history could not be read.”.

Analytics

Analytics answers: how do runs go over time, and where do they spend their effort? A Range control picks Last 24 hours, Last 7 days (the default), Last 30 days, Last 90 days, or All time, and hovering the control gives the start of the range. A range without a run reads “No run finished in this range.” (or “No run has finished yet.” for All time). Warnings about the report, such as a database written before Sortie recorded a figure, appear above the figures.

The summary opens with the success rate, large, and “N of M runs succeeded” under it. Beside it the figures run in one row.

Outcomes is one bar that shows how the runs ended, with a legend and a count for each outcome that has runs: Succeeded, Stopped, Cancelled, and Failed. The bar’s segments carry no tooltip.

When a rate source is available, a Spend chart follows the bar for every range but Last 24 hours. It draws the estimated cost of the runs per UTC day for the 7, 30, and 90 day ranges and per UTC month for All time, one bar per period, oldest first. The first period is the one that holds the start of the range (for All time, the first run), so it can be a partial period. The top of the scale is the smallest 1, 2, or 5 times a power of ten that holds the largest period. A bar is solid while the period’s cost is complete. A period that leaves out runs that are unpriced, have a partial cost, or reported no usage draws a diagonal hatch, and a period whose runs have no cost at all but include such runs draws a thin hatched bar, so it never reads as a period without spend. A period without runs, and a period whose runs spent nothing, draws no bar. Hovering a period names it, gives the time the range starts from on a first period the range cuts short, and says in one sentence what the bar means. Every date and time on the chart is in UTC, whatever your time zone. The periods are those the daily and monthly spend ceilings count, so a bar compares directly with agent.max_daily_cost_usd and agent.max_monthly_cost_usd.

Each stage chain gets a table headed “Chain from” its entry rule, with a row per stage.

The breakdowns follow, each a table sortable by any column header, 20 rows at a time with Show more, and with the sort kept in the address.

Every table but By skill has the columns Runs, Success (Share in By run status), Duration (the median to the 95th percentile), Mean turns, Tokens, and, when a rate source is available, Est. cost and Per run, whose question mark explains that it covers succeeded runs only.

A run that used two models counts in both By model rows, so the rows’ runs can add up to more than the runs of the range. Per run is the cost divided by the group’s succeeded runs that reported usage, and reads “N/A” for a group with no succeeded run. The Tokens, Est. cost, and Per run cells are worded like the summary figures: a lower bound is cut and underlined, and a hover says what the figure leaves out or why it has none.

By skill has the columns Skill, Runs, Calls, and Failed calls. Runs counts the runs that called the skill, once each however often they called it, and the header’s hover says so. Calls counts every call, and Failed calls the calls that ended in a tool error, muted while it is 0. The table starts ordered by Runs, most first, then by skill name, and any column header sorts it. Runs recorded before Sortie kept skill calls have none on record, so while the range holds any, the three counts are lower bounds: each draws a dotted underline, and hovering it reads “At least this many. It leaves out runs Sortie recorded before it kept skill calls.” The warning above the figures also names the missing skill calls for a database written before Sortie recorded them. The same counts are the skill_calls member of the run statistics report.

Health

Health answers: is Sortie itself working? Checks lists one row per check, each with a mark, a sentence about the last result, and the error text when the check failed.

A failing row reads, for example, “3 ticks in a row failed since 14:02; last success at 13:58.” A check that has not run yet reads “Not run yet.” Beside the checks, Poll loop gives the Interval, Last poll, Last good poll, Next poll, and Failures in a row, and Process gives the Version, when Sortie Started, how many Agents run, and when the Config loaded. A Sortie that serves no health data reads “Sortie serves no health checks.”

Workflow

Workflow answers: what configuration is Sortie running? It shows the WORKFLOW.md in effect, under a line that gives the time of the load (“Loaded at 15:34.”). When a newer edit failed to load, the line adds that no new issue starts until it does. A Sortie that serves no configuration reads “Sortie serves no configuration.”

Usage reporting reads “reports tokens”, “reports none”, or “not declared” for each kind. See token_rates and the usage reporting table.

Prices

Prices answers: which rate prices each model, and where does it come from? It shows the rates in force, not a cost: the screen prices no run, and a finished run keeps the cost recorded when it finished. The panels state the price sources, and the Models table states the rates of each model. The screen reads GET /api/v1/prices.

A table panel gives its Status, whether the table is In force (“Yes” or “No”), its Version, and its Models. A downloaded table, which is Downloaded prices and Custom prices for an address, gives Last download and Next download. Custom prices for a file gives Loaded, the time this process first read the file’s current content. Built-in prices gives Version date, the date of its upstream revision, and no timing rows.

A Version shows its first 12 characters, after sha256: for a content digest, and the hover shows the whole value. Custom prices and Downloaded prices show digests, and Built-in prices shows the upstream revision.

Models lists one row per agent kind and model: every pair run history records, and every model the workflow configures, in the top-level agent settings, the dispatch default, or a dispatch rule. A model that only the workflow names has no last use and no runs. Rows keep the order the server serves, the latest use first, until a column is sorted.

Every column sorts, as the Analytics breakdowns do, and the choice is kept in the address. The Search models field above the table narrows the rows, as it is typed, to the models whose name contains the text, ignoring case; Esc or the clear button empties it, and while no row matches the table reads “No model matches this search.” The table scrolls sideways on a screen narrower than its columns.

Before the first answer the screen reads “Loading”. Without run history it reads “Run history is not available.”, and a failed read reads “Prices could not be read.”.

Attention items

An attention item is one thing that needs a person. Sortie derives the items from its own state, so an item exists exactly while its cause does. Each item has a reason, an explanation of why it exists, and a sentence on what clears it.

An item that has a tracker or pull request address gets a button that opens it in a new tab. Items without an issue, the two failing-check items at the end of the table, are not clickable and open no peek. Critical items sort first. Both critical causes are failing health checks, so the status card reads Degraded while the check keeps failing.

Acknowledge tells Sortie that a person has seen the item. The item leaves Needs attention and the count in the rail, the status card, the browser tab, and the headline. An acknowledged item does not disappear from view: the issue stays in Active, read as Held with its mark, and the issue page shows the item with the time it was acknowledged. Sortie stores the acknowledgement, so it survives a restart, and it ends together with its cause. An item that appears for a new cause, such as a second park of the same issue, is a new item and shows as unacknowledged.

Unread markers

The title of each Ended today row that has not been read is bold. Attention items carry no marker. An ending counts as read once its issue is shown in the peek or on its page. Mark everything read (Shift and U, or the palette) marks every ending loaded for today. Read state belongs to the browser, so another browser starts unread.

Actions

These actions change what Sortie does. Each answers with a short message at the bottom of the screen that states the answer Sortie gave, such as “Retry 7 of sortie-ai/sortie#1363 is due now.” When Sortie does not answer, the message reads “Sortie did not answer. Nothing changed.” During shutdown it reads that nothing was queued or acknowledged. The HTTP API documents the routes behind them.

Other commands act on Sortie as a whole: Refresh now and Pause live updates, described under live updates. The A key, Run the item’s action on the shortcut sheet, opens the item’s tracker or pull request address in a new tab, or acknowledges an item that has no address.

Live updates

The dashboard holds a connection to Sortie’s change stream. When Sortie reports a change, the dashboard rereads what the open screen shows. No timer reloads the page. History rereads at most once every 5 seconds and Analytics at most once every 30 seconds, however often changes arrive. Prices is the exception: it reads its route when it opens and when the browser window regains focus, and a change signal never rereads it, so a reload of WORKFLOW.md or a finished download shows after the screen is reopened or the window is focused again. A session view also receives the events of the session it shows over the same connection.

Refresh now (R, or the palette) asks Sortie to poll the tracker now, and the message reads “Tracker poll and reconciliation queued.” or says that a poll was already queued. Pause (P, the palette, or the live indicator) holds the screens still, and resuming applies what changed in the meantime. While paused, the title and icon of the tab stay as they were and a session view stops adding events.

The live indicator at the right of the top bar says how fresh the screen is. When several rows apply, the first one wins.

When the version of the running Sortie differs from the version the open tab first saw, a message that stays until dismissed reads “Sortie” and the new version, then “is running. Reload to update the dashboard.”, with a Reload button.

How the screens follow the workflow

The dashboard shows only what the workflow configures. Every row below changes with the matching part of WORKFLOW.md.

How figures are written

Costs are estimates, built from the rates in force (token_rates entries over the price table), and the dashboard says so with the words “estimated”, “est.”, and “Estimated cost”. A finished run keeps the cost recorded when it finished, whatever the rates say now. Token figures leave out cache reads, which the dashboard shows separately where it has them. agent.max_tokens leaves them out too, so the budget meter reads Tokens and counts the same figure. The Cost meter counts them, because the estimated cost prices them. Durations use at most two units (“1h 17m”), and a duration under one second reads “< 1s”. Tokens read as “830K” or “48.03M”, costs read with two decimals below $100 and as whole dollars from $100, amounts in an agent’s own unit read with at most two decimals, and a share strictly between 0 and 100 percent never rounds to either end.

A figure Sortie does not have is never written as zero. A cost above zero and under one cent reads “under $0.01”, so only a cost of zero reads “$0.00”. How Sortie measures a run, and what makes a figure a lower bound, is explained in spend measurement.

Lower bounds and hints

A figure that carries a note is drawn with a dotted underline, and hovering or tapping it opens the note. A figure without a note has no underline and no hover. A figure that is a lower bound always carries a note. Its amount is cut, never rounded up, so the text never exceeds what it bounds: tokens drop the digits past the last one shown (1,699,999 reads “1.69M”), a cost below $100 keeps two decimals, from $100 drops the cents, and under one cent keeps its first non-zero digit ("$0.004"), and an amount in an agent’s own unit keeps at most two decimals. The dashboard writes no “at least” before such a figure; the underline and the note mark it.

Other notes give the provenance of a complete figure: the tokens of a finished run say how Sortie measured it (“Measured from live protocol.”) and give its cache reads, and a cost that holds a US dollar amount the agent reported gives the exact cost and that share ("$4.20. $1.10 of it is the amount the agent reported for acme-coder-1, which no price table lists.").

N/A and its reason

A finished run, or a total of finished runs, with no token figure reads “N/A” for its tokens and its cost. The note gives the reason.

A total whose runs all share one reason carries the note only when that reason is the agent’s own unit; for any other shared reason it reads “N/A” with no note. A running session with no usage yet reads “not measured” instead.

Wording

Keyboard shortcuts and command palette

? opens the shortcut sheet, which lists the keys that act on the current screen. Keys are ignored while the cursor is in a text field and while Ctrl, Alt, or Cmd is held, except for the palette key. Keys that activate a focused button or link keep that job.

Global shortcuts

The go-to sequence is G followed by the letter within 1.2 seconds. Esc closes the peek first. On an issue page it returns to the screen the page was opened from, and on a session view it returns to the issue page.

Overview shortcuts

Pipeline shortcuts

Issue page shortcuts

“The latest session” is the running session when there is one, and otherwise the issue’s newest session. On Overview, A and E act on the selected item, or on the peeked issue’s item while a peek is open.

Command palette

Ctrl K or Cmd K opens the palette from any screen, and so do the Commands button in the rail, the Search or run a command button in the top bar, and the Menu button on narrow screens. It has a search field and lists the commands, each with its key.

Typing narrows the commands and adds the groups below. Issues lists active issues whose key or title contains the text (the first 8), then finished issues from run history that match by key or title (up to 5 more), each with its status word under the name. Sessions lists the live sessions of matching running issues, named “key live session”, and the finished sessions of the issues found, named “key session N” with the route, outcome word, and start time (up to 8 in all). Choosing an issue opens its page, and choosing a session opens its view. A search with no match reads “Nothing matches” and the text, and a failed history lookup reads “Run history could not be read.”