Claude Dashboard 0.0.30

Pre-release. An early build of Claude Dashboard, a Windows tray app that shows at a glance, and tells you by sound, which of your Claude Code sessions need you, which finished unseen, and which are still working.

What's new since 0.0.29

A name on every session

• A row for a session nobody named now shows the title Claude Code generated for it. Until now it showed no name, because Claude Code writes that title only to the session's transcript, never to its hooks. The dashboard now reads it from the transcript. (#161)
• A name you gave the session always wins: a generated title never replaces it, even when Claude Code writes a new one after a rename. (#161)
• The name comes back after a restart of the dashboard, on the session's next event. (#161)
• The dashboard only reads the transcript, never writes it, and reads it only when it changed, from the end. Each such read costs about 5 ms on the dashboard's own thread; no Claude turn waits for it. (#161)

Install or upgrade

Download dsopko.ClaudeDashboard-win-Setup.exe and run it. If you already have 0.0.9 or later, it upgrades in place and keeps your data. Windows shows "Windows protected your PC" because the build is not code-signed yet. Click More info, then Run anyway. It installs for your user only and never asks for administrator rights.

The history setting is the same as in 0.0.21: the dashboard keeps its history for as long as Claude Code keeps its sessions (cleanupPeriodDays in %UserProfile%\.claude\settings.json, 30 days when it is not there).

You need Windows 10 or 11 (64-bit) and Claude Code. Full details are in the README.

Portable: dsopko.ClaudeDashboard-win-Portable.zip. Extract it anywhere and run current\ClaudeDashboard.App.exe. A portable copy does not add itself to Windows startup.

The other files are the update feed for a future in-app updater. You do not need them.

Known limits

• Unsigned, so SmartScreen warns on every download.
• No in-app update yet. To get a new version, download the new Setup.
• If the dashboard crashes, Windows does not restart it until you next sign in.
• Phase 1: the panel, tray, sounds, acknowledgment and the Activity window. Click-to-navigate to a terminal and the rest of the roadmap are still ahead.

Claude Dashboard 0.0.29

Pre-release. An early build of Claude Dashboard, a Windows tray app that shows at a glance, and tells you by sound, which of your Claude Code sessions need you, which finished unseen, and which are still working.

What's new since 0.0.28

The Activity button shows every line

• The toolbar's Activity and the tray's Activity… now always open the full list. Until now the window kept the filter from an earlier Show activity on a row, so it could open days later showing one session only. Only Show activity on a row filters it. (#157)
• The filter bar names the session as its lines do, with its project: Only 457d3a3e, project IdentityTheftLawsuit. (#157)

The usage caption

• The five-hour limit is now labelled Session: Session 95% · Week 64%. It was Current. (#147)
• Hovering the counts in the caption now opens their tooltip, as it does on the row. The window no longer drags from the counts themselves; the rest of the caption still drags. (#142)

Behind the scenes

• The build now checks every link in a code comment. (#19)
• A test no longer fails when another program holds its port. (#155)

Install or upgrade

Download dsopko.ClaudeDashboard-win-Setup.exe and run it. If you already have 0.0.9 or later, it upgrades in place and keeps your data. Windows shows "Windows protected your PC" because the build is not code-signed yet. Click More info, then Run anyway. It installs for your user only and never asks for administrator rights.

The history setting is the same as in 0.0.21: the dashboard keeps its history for as long as Claude Code keeps its sessions (cleanupPeriodDays in %UserProfile%\.claude\settings.json, 30 days when it is not there).

You need Windows 10 or 11 (64-bit) and Claude Code. Full details are in the README.

Portable: dsopko.ClaudeDashboard-win-Portable.zip. Extract it anywhere and run current\ClaudeDashboard.App.exe. A portable copy does not add itself to Windows startup.

The other files are the update feed for a future in-app updater. You do not need them.

Known limits

• Unsigned, so SmartScreen warns on every download.
• No in-app update yet. To get a new version, download the new Setup.
• If the dashboard crashes, Windows does not restart it until you next sign in.
• Phase 1: the panel, tray, sounds, acknowledgment and the Activity window. Click-to-navigate to a terminal and the rest of the roadmap are still ahead.

Claude Dashboard 0.0.28

Pre-release. An early build of Claude Dashboard, a Windows tray app that shows at a glance, and tells you by sound, which of your Claude Code sessions need you, which finished unseen, and which are still working.

What's new since 0.0.27

The usage hover, and a limit used past 100%

• The hover on each usage figure now reads Usage this session · 95% remaining · resets at 9:00 AM, Usage this week · … and Fable usage this week · …. The caption's labels are the same. (#144)
• A limit used past 100% (extra usage turned on) shows how far past it is, in red: -10%, with 10% over in the hover. Until now it stopped at 0%. No one has yet seen what Claude Code sends past a limit, so this is untested against a real reading; at Debug the log file records each reading in full. (#144)

One dashboard per data folder

• A second dashboard that starts on the same data folder from another Windows session now exits and says why in a message box, instead of starting a second copy that fights the first for listening.txt. (#150)
• A dashboard that starts with no port to listen on deletes a listening.txt left by an earlier copy when no dashboard answers on its port, so hooks no longer go to a dead address. (#151)
• A second start in the same session still brings the open window forward, with no box.

A ticked row stays open

• In selection mode a ticked row is never collapsed, in either view, and its group does not go stale or count it as hidden. It collapses when you untick it or leave the mode. (#46)

/state

• Each session now says who owns its next reminder (nudgeBy, Session or Group), and nextNudgeAt carries that owner's time: for a finished member of an orchestration, the group's reminder. (#58)

Known in this build

• Hovering the counts in the caption does not open their tooltip; the same counts on the row do. (#142)

Install or upgrade

Download dsopko.ClaudeDashboard-win-Setup.exe and run it. If you already have 0.0.9 or later, it upgrades in place and keeps your data. Windows shows "Windows protected your PC" because the build is not code-signed yet. Click More info, then Run anyway. It installs for your user only and never asks for administrator rights.

The history setting is the same as in 0.0.21: the dashboard keeps its history for as long as Claude Code keeps its sessions (cleanupPeriodDays in %UserProfile%\.claude\settings.json, 30 days when it is not there).

You need Windows 10 or 11 (64-bit) and Claude Code. Full details are in the README.

Portable: dsopko.ClaudeDashboard-win-Portable.zip. Extract it anywhere and run current\ClaudeDashboard.App.exe. A portable copy does not add itself to Windows startup.

The other files are the update feed for a future in-app updater. You do not need them.

Known limits

• Unsigned, so SmartScreen warns on every download.
• No in-app update yet. To get a new version, download the new Setup.
• If the dashboard crashes, Windows does not restart it until you next sign in.
• Phase 1: the panel, tray, sounds, acknowledgment and the Activity window. Click-to-navigate to a terminal and the rest of the roadmap are still ahead.

Claude Dashboard 0.0.27

Pre-release. An early build of Claude Dashboard, a Windows tray app that shows at a glance, and tells you by sound, which of your Claude Code sessions need you, which finished unseen, and which are still working.

What's new since 0.0.26

The usage shows what is left

• The caption now shows how much of each plan limit is left, not how much is used: Current 95% · Week 60%. The hover says the same, This week · 60% remaining · Resets Wednesday 9:00 AM. The colour is unchanged: green, amber and red at 50 % and 90 % used, so nothing you saw green turns amber. (#144)
• When a limit's reset time passes, the figure shows 100% in green until the next reading arrives, instead of leaving an empty spot. The hover says which reset passed and that the next reset time comes with the next reading (Claude Code's 5-hour span starts at your first use after a reset, so no one knows it before). (#145)
• /state is unchanged: it answers percentUsed as Claude Code sends it, and leaves a limit out once its reset time has passed.

The log file explains a usage post

• At the normal level the log file writes one line when a usage post changes the picture: a limit appears that the previous post did not carry, a limit the previous post carried is missing, or a reading was not kept, with the reason (an older reset time than the one held, no kind, a bad percentage, a ninth kind). A post that only moves a percentage writes nothing. At Debug one line carries each reading in full: kind, percentage, reset time, and kept or not. The token is in no line. (#143)
• Not in this build: a line in the Activity window when a figure resets. It needs a new kind of record, and #143 stays open for it.

Known in this build

• Hovering the counts in the caption does not open their tooltip; the same counts on the row do. (#142)

Install or upgrade

Download dsopko.ClaudeDashboard-win-Setup.exe and run it. If you already have 0.0.9 or later, it upgrades in place and keeps your data. Windows shows "Windows protected your PC" because the build is not code-signed yet. Click More info, then Run anyway. It installs for your user only and never asks for administrator rights.

The history setting is the same as in 0.0.21: the dashboard keeps its history for as long as Claude Code keeps its sessions (cleanupPeriodDays in %UserProfile%\.claude\settings.json, 30 days when it is not there).

You need Windows 10 or 11 (64-bit) and Claude Code. Full details are in the README.

Portable: dsopko.ClaudeDashboard-win-Portable.zip. Extract it anywhere and run current\ClaudeDashboard.App.exe. A portable copy does not add itself to Windows startup.

The other files are the update feed for a future in-app updater. You do not need them.

Known limits

• Unsigned, so SmartScreen warns on every download.
• No in-app update yet. To get a new version, download the new Setup.
• If the dashboard crashes, Windows does not restart it until you next sign in.
• Phase 1: the panel, tray, sounds, acknowledgment and the Activity window. Click-to-navigate to a terminal and the rest of the roadmap are still ahead.

Claude Dashboard 0.0.26

Pre-release. An early build of Claude Dashboard, a Windows tray app that shows at a glance, and tells you by sound, which of your Claude Code sessions need you, which finished unseen, and which are still working.

What's new since 0.0.25

Your plan's usage in the window

• The window's caption now shows the plan's usage to the left of the counts: Current 5% · Week 36%, the 5-hour and the weekly percentage that the usage mod posts at the end of each turn. A third figure, Fable, appears when Claude Code sends a per-model limit; today it sends only the two. Before the first post the caption shows the counts alone, as before.
• Each figure is green below 50 %, amber from 50 to 90, and red above 90. Hover a figure for the full line with the reset time in your local time: Current session · 5% used · Resets at 6:20 AM, This week · 36% used · Resets Wednesday 9:00 AM.
• A narrow window shows the numbers alone (5% · 36%); narrower still, the usage moves to the row under the caption, the same row the counts use, with the usage at the left and the counts at the right. The counts keep their place first: as a window widens past about 545 the counts take their words back before the usage returns to the caption, so the usage can step down to the row for a stretch and come back at about 685.
• The tray light and the tray tooltip do not show the usage.
• The figures are at most one 15-second tick behind the post. /state is unchanged (usage since 0.0.25). (#133)

Known in this build

• Hovering the counts in the caption does not open their tooltip; the same counts on the row do. (#142)

Install or upgrade

Download dsopko.ClaudeDashboard-win-Setup.exe and run it. If you already have 0.0.9 or later, it upgrades in place and keeps your data. Windows shows "Windows protected your PC" because the build is not code-signed yet. Click More info, then Run anyway. It installs for your user only and never asks for administrator rights.

The history setting is the same as in 0.0.21: the dashboard keeps its history for as long as Claude Code keeps its sessions (cleanupPeriodDays in %UserProfile%\.claude\settings.json, 30 days when it is not there).

You need Windows 10 or 11 (64-bit) and Claude Code. Full details are in the README.

Portable: dsopko.ClaudeDashboard-win-Portable.zip. Extract it anywhere and run current\ClaudeDashboard.App.exe. A portable copy does not add itself to Windows startup.

The other files are the update feed for a future in-app updater. You do not need them.

Known limits

• Unsigned, so SmartScreen warns on every download.
• No in-app update yet. To get a new version, download the new Setup.
• If the dashboard crashes, Windows does not restart it until you next sign in.
• Phase 1: the panel, tray, sounds, acknowledgment and the Activity window. Click-to-navigate to a terminal and the rest of the roadmap are still ahead.

Claude Dashboard 0.0.25

Pre-release. An early build of Claude Dashboard, a Windows tray app that shows at a glance, and tells you by sound, which of your Claude Code sessions need you, which finished unseen, and which are still working.

What's new since 0.0.24

An orchestration counts once

• The counts strip at the top of the window, the tray tooltip and the tray light now count a roster (an orchestration of several sessions) as one. While one member works, the strip says 1 working; when every member has been quiet for the settle window, it says 1 unread. Before, it counted the members one by one, so a working orchestration read 2 unread · 1 working. The session total still counts sessions. (#130)
• A roster's finish is now seen at its deadline, about 1.5 seconds after the last member stops. Before, it could wait for the next 15-second tick, so the group heading, its sound and the counts were up to 15 seconds late. (#131)

The plugin carries the usage mod

• At its next start the dashboard writes two more files into its plugin folder, hooks\register.ts and hooks\listening-file.ts, and names the first in hooks.json. The mod runs inside Claude Code at the end of each turn and posts the plan's usage (the 5-hour and the weekly percentage, with the reset time) to the dashboard at /usage. The dashboard keeps the newest reading of each limit and answers it in /state as usage (null before the first post). The window and the tray do not show it yet. (#133)
• The mod needs Claude Code 2.1.287 or later. This is the first build that ships it, and it is the build on which the real Windows session is checked; the lab proof so far is on Linux and in tests.
• A post with the wrong token is refused with 401 and counted in health.refused; a post is never counted as a hook. The token is in no file but listening.txt and is never logged.

Rows and the log file

• A long prompt on a row is cut between characters, never inside one, so an emoji at the cut no longer draws as �. (#21)
• The log file names each value it does not know (an unknown event type, state or task status) one time, up to 100 values, and traces each event at the Debug level.

For developers

• build.ps1 ends with one verdict line, GREEN or NOT GREEN, from three checks: the exit code, no aborted run, and the total equal to the count it listed before the run. It also runs the usage mod's 28 tests (claude plugin validate --strict and claude plugin test); a machine with no claude is NOT GREEN.
• The two settle numbers for a roster (1.5 s to settle, 5 s to undo a wrong mark) are each held by a test. (#34)
• mods/usage/ holds the mod and its tests; the Usage Mod Development Guide and its Execution Plan are in docs/.

Install or upgrade

Download dsopko.ClaudeDashboard-win-Setup.exe and run it. If you already have 0.0.9 or later, it upgrades in place and keeps your data. Windows shows "Windows protected your PC" because the build is not code-signed yet. Click More info, then Run anyway. It installs for your user only and never asks for administrator rights.

The history setting is the same as in 0.0.21: the dashboard keeps its history for as long as Claude Code keeps its sessions (cleanupPeriodDays in %UserProfile%\.claude\settings.json, 30 days when it is not there).

You need Windows 10 or 11 (64-bit) and Claude Code. Full details are in the README.

Portable: dsopko.ClaudeDashboard-win-Portable.zip. Extract it anywhere and run current\ClaudeDashboard.App.exe. A portable copy does not add itself to Windows startup.

The other files are the update feed for a future in-app updater. You do not need them.

Known limits

• Unsigned, so SmartScreen warns on every download.
• No in-app update yet. To get a new version, download the new Setup.
• If the dashboard crashes, Windows does not restart it until you next sign in.
• Phase 1: the panel, tray, sounds, acknowledgment and the Activity window. Click-to-navigate to a terminal and the rest of the roadmap are still ahead.

Claude Dashboard 0.0.24

Pre-release. An early build of Claude Dashboard, a Windows tray app that shows at a glance, and tells you by sound, which of your Claude Code sessions need you, which finished unseen, and which are still working.

What's new since 0.0.23

The history database closes only its own connection

• When the dashboard closes its history database (dashboard.db), it now releases only its own connection. Before, it emptied every database connection in the process, and a connection that was opening at that moment could be destroyed. A dashboard has one database, so this did not affect a normal installation; it caused tests to fail at random. The file is still released when the dashboard quits.

More reliable tests

• Several tests that failed at random are fixed: a port test that matched by chance, and the database tests that the close above could break.
• A test helper that reads the database now reports SQLite's own error, so a future failure names its cause.

Install or upgrade

Download dsopko.ClaudeDashboard-win-Setup.exe and run it. If you already have 0.0.9 or later, it upgrades in place and keeps your data. Windows shows "Windows protected your PC" because the build is not code-signed yet. Click More info, then Run anyway. It installs for your user only and never asks for administrator rights.

The history setting is the same as in 0.0.21: the dashboard keeps its history for as long as Claude Code keeps its sessions (cleanupPeriodDays in %UserProfile%\.claude\settings.json, 30 days when it is not there).

You need Windows 10 or 11 (64-bit) and Claude Code. Full details are in the README.

Portable: dsopko.ClaudeDashboard-win-Portable.zip. Extract it anywhere and run current\ClaudeDashboard.App.exe. A portable copy does not add itself to Windows startup.

The other files are the update feed for a future in-app updater. You do not need them.

Known limits

• Unsigned, so SmartScreen warns on every download.
• No in-app update yet. To get a new version, download the new Setup.
• If the dashboard crashes, Windows does not restart it until you next sign in.
• Phase 1: the panel, tray, sounds, acknowledgment and the Activity window. Click-to-navigate to a terminal and the rest of the roadmap are still ahead.

Claude Dashboard 0.0.23

Pre-release. An early build of Claude Dashboard, a Windows tray app that shows at a glance, and tells you by sound, which of your Claude Code sessions need you, which finished unseen, and which are still working.

What's new since 0.0.22

The log file may hold any text

• The dashboard no longer keeps session names, titles, prompts or answers out of its log file (%LocalAppData%\ClaudeDashboard\logs\). The same text is already in its history database beside it.
• At the normal log level, the log file is the same as before. With logging.minimumLevel set to Debug, each decision line now shows the session's name.
• The token that Claude Code sends with each message is still never written to the log file.

Install or upgrade

Download dsopko.ClaudeDashboard-win-Setup.exe and run it. If you already have 0.0.9 or later, it upgrades in place and keeps your data. Windows shows "Windows protected your PC" because the build is not code-signed yet. Click More info, then Run anyway. It installs for your user only and never asks for administrator rights.

The history setting is the same as in 0.0.21: the dashboard keeps its history for as long as Claude Code keeps its sessions (cleanupPeriodDays in %UserProfile%\.claude\settings.json, 30 days when it is not there).

You need Windows 10 or 11 (64-bit) and Claude Code. Full details are in the README.

Portable: dsopko.ClaudeDashboard-win-Portable.zip. Extract it anywhere and run current\ClaudeDashboard.App.exe. A portable copy does not add itself to Windows startup.

The other files are the update feed for a future in-app updater. You do not need them.

Known limits

• Unsigned, so SmartScreen warns on every download.
• No in-app update yet. To get a new version, download the new Setup.
• If the dashboard crashes, Windows does not restart it until you next sign in.
• Phase 1: the panel, tray, sounds, acknowledgment and the Activity window. Click-to-navigate to a terminal and the rest of the roadmap are still ahead.

Claude Dashboard 0.0.22

Pre-release. An early build of Claude Dashboard, a Windows tray app that shows at a glance, and tells you by sound, which of your Claude Code sessions need you, which finished unseen, and which are still working.

What's new since 0.0.21

History recording comes back by itself

• If the dashboard could not write to its history database (dashboard.db) when it opened it, it showed "History is not being recorded… The dashboard tries again each minute", but the retry never worked: nothing was saved until you restarted the dashboard. Now the retry works. History comes back within a minute after the cause is gone.
• Two things could cause it: the file was marked read-only, or another program (a backup, sync or checking tool) was reading the file at the moment the dashboard opened it.
• A program that reads the file for only a moment no longer costs anything: the dashboard tries again a few times within one second, so no record is lost and no notice shows.

A roster made from finished sessions stays quiet

• When you make a roster from sessions that have already finished and already played their sound, the roster no longer plays "finished" again. A roster plays its sound when a member that was still working finishes.

Every group line in the Activity window names its group

• A "no sound" line about a roster group now shows the group's name, as a line for a sound that played does. For example: "no sound · orchestration · finished, announced before".
• A click on any group line goes to the group's heading in the main window.

More reliable tests

• Two tests that could fail at random, for reasons in the tests and not in the dashboard, are fixed.

Install or upgrade

Download dsopko.ClaudeDashboard-win-Setup.exe and run it. If you already have 0.0.9 or later, it upgrades in place and keeps your data. Windows shows "Windows protected your PC" because the build is not code-signed yet. Click More info, then Run anyway. It installs for your user only and never asks for administrator rights.

The history setting is the same as in 0.0.21: the dashboard keeps its history for as long as Claude Code keeps its sessions (cleanupPeriodDays in %UserProfile%\.claude\settings.json, 30 days when it is not there).

You need Windows 10 or 11 (64-bit) and Claude Code. Full details are in the README.

Portable: dsopko.ClaudeDashboard-win-Portable.zip. Extract it anywhere and run current\ClaudeDashboard.App.exe. A portable copy does not add itself to Windows startup.

The other files are the update feed for a future in-app updater. You do not need them.

Known limits

• Unsigned, so SmartScreen warns on every download.
• No in-app update yet. To get a new version, download the new Setup.
• If the dashboard crashes, Windows does not restart it until you next sign in.
• Phase 1: the panel, tray, sounds, acknowledgment and the Activity window. Click-to-navigate to a terminal and the rest of the roadmap are still ahead.

Claude Dashboard 0.0.21

Pre-release. An early build of Claude Dashboard, a Windows tray app that shows at a glance, and tells you by sound, which of your Claude Code sessions need you, which finished unseen, and which are still working.

⚠ Read this before you update: the history setting changed

The dashboard no longer has a history setting of its own. It now keeps its history for as long as Claude Code keeps its sessions: the cleanupPeriodDays setting in Claude Code's settings file, %UserProfile%\.claude\settings.json. If that setting is not there, Claude Code keeps 30 days, and so does the dashboard.

"history": { "retentionDays": 0 } no longer keeps everything. If you added that line for 0.0.20, the dashboard now ignores it, leaves it in the file, and writes one line in its log to say so.

At its first start, and once a day after that, the dashboard deletes every record in its history database (dashboard.db) that is older than cleanupPeriodDays. A delete cannot be undone. The file holds your prompts and answers.

To keep a long history, do this before you install:

1. Open %UserProfile%\.claude\settings.json (Claude Code's settings, not the dashboard's).
2. Look for "cleanupPeriodDays". If it is there with a large number (for example 3650), you need do nothing.
3. If it is not there, add it, for example "cleanupPeriodDays": 3650, on its own line directly after the first {. This also changes how long Claude Code itself keeps its sessions, which is the point: the two now agree.

The dashboard deletes nothing when it cannot be sure. If Claude Code's settings file cannot be read, is not valid JSON (comments and trailing commas count as not valid), or holds a cleanupPeriodDays that is not a whole number of 1 or more, the dashboard keeps everything and says why in its log.

To be safe, copy dashboard.db to another folder before you update.

What's new since 0.0.20

The Activity window: what the dashboard did, in plain words

• Open it from the tray menu or from the new Activity button on the toolbar.
• It lists what happened since the dashboard started, newest first: a session started, went to work, needs permission, finished, went quiet, ended, or was acknowledged.
• A line with ♪ is a sound that played, and the line under it is what made the sound. A "no sound" line says why: muted, paused, the group owns the sound, announced before, or no sound device.
• Each line shows the session's name and its project. Hover on the project for the full path.
• Click a line (or press Enter) to open that session's row in the main window.
• Show activity, a new action in an open row, lists only that session's lines. Show all brings every line back.
• The window keeps the newest 19,000 to 20,000 lines, in memory only. It does not read the database, and a restart starts it empty.

A speaker sign on the row that made a sound

• For one minute after a sound plays, a small, still speaker sign shows on the row of the session that set it off. In a roster group, it is on the session that finished last. Hover on it to see which sound and when.

The history database

• Each record now holds the session's name, and each decision also holds the session's folder, so the database can be read without looking up session ids. Old records are not filled in. The first start adds the columns in a moment, with no data lost.

More reliable

• Switching between Grouped and Flat no longer causes hundreds of internal binding errors.

Install or upgrade

Download dsopko.ClaudeDashboard-win-Setup.exe and run it. If you already have 0.0.9 or later, it upgrades in place and keeps your data, except the history older than Claude Code's cleanupPeriodDays (see the warning above). Windows shows "Windows protected your PC" because the build is not code-signed yet. Click More info, then Run anyway. It installs for your user only and never asks for administrator rights.

You need Windows 10 or 11 (64-bit) and Claude Code. Full details are in the README.

Portable: dsopko.ClaudeDashboard-win-Portable.zip. Extract it anywhere and run current\ClaudeDashboard.App.exe. A portable copy does not add itself to Windows startup.

The other files are the update feed for a future in-app updater. You do not need them.

Known limits

• Unsigned, so SmartScreen warns on every download.
• No in-app update yet. To get a new version, download the new Setup.
• If the dashboard crashes, Windows does not restart it until you next sign in.
• Phase 1: the panel, tray, sounds, acknowledgment and the Activity window. Click-to-navigate to a terminal and the rest of the roadmap are still ahead.