Skip to content

Dashboard dashboard-v0.18.0

Choose a tag to compare

@github-actions github-actions released this 28 Sep 12:10
· 2607 commits to master since this release

Dashboard v0.18.0

Works with Magic Context 0.44.0, including OpenCode 2.

OpenCode 2 sessions and projects are listed (#542)

The dashboard read sessions from OpenCode 1's session table. OpenCode 2 keeps its sessions in session_v2, and a fresh OpenCode 2 store has no session table at all, so no OpenCode 2 session was listed and the Projects page stayed empty. A store converted from OpenCode 1 showed only the sessions from before the upgrade. On an OpenCode 2 store, the Projects page, the Sessions list, session details and the Cache tab's session list and titles now read session_v2.

Logs page reads the OpenCode 2 log

The Logs page read only the OpenCode 1, Pi and OMP logs. It now also reads the OpenCode 2 plugin's log, at opencode2/magic-context/magic-context.log in the temp directory and logs/magic-context.opencode2.log in the storage directory.

OpenCode 2 filter in the Sessions viewer

The Sessions viewer's harness filter now offers OpenCode 2, next to OpenCode, Pi and OMP, and remembers it like the other choices.

Cache tab follows a live OpenCode 2 turn

OpenCode 2 updates a session's time when a prompt is sent and not again during the turn, so the Cache tab saw no change until the next prompt. It now dates an OpenCode 2 session by its newest message as well, so steps appear while the turn runs. If an OpenCode 2 store's session_message table has no time_updated column, the tab still lists its sessions but refreshes them only when a new prompt starts, and says so above the session cards.

The Cache tab's OpenCode 2 filter listed nothing before; it now lists OpenCode 2 sessions, and the OpenCode filter no longer includes them.

Broca runs are shown as run totals

Broca's run index records one usage sum per run, covering every model step in it. The Cache tab compared each run's sum with the previous run's, which showed busts that did not happen and a red 0% for a session's first run. A run total is now labelled RUN TOTAL and shows its own cached share; it is never marked stable or bust, and never compared with another run. A run that did not complete normally names how it ended, for example RUN TOTAL · ERROR. Every Broca session is now listed, not only historian and dreamer sessions.

Broca steps are read live

The Cache tab reads each Broca session's model steps from Broca's write-ahead log files as Broca writes them, including its archived logs, and shows one row per step, compared step against step as for OpenCode. Steps of a run that is still going appear, and a session whose only run is still active is listed. The files are only read, never written. When a session's log can't be read, its runs are shown as run totals.

Broca cache counts that were not reported

When a provider does not report cache reads or cache writes, Broca leaves the count out. The Cache tab showed these as 0; it now shows "not reported" in the list and in the timeline tooltip, and a reported 0 still shows as 0. A row with no reported cache reads shows "No cached tokens reported" instead of a percentage and is left out of the session's cached share. A turn where only some rows reported cache writes shows its total marked "(partial)". The timeline tooltip now also lists cache writes.

Session header and cards in the Cache tab

Above the timeline, the Cache tab shows the selected session's full name and its latest provider and model, with "(+N)" when the loaded rows used more than one model; the tooltip lists them all. For a Broca session it also shows the harness Broca ran it for ("via …") and puts the project root in the tooltip. On OpenCode 2 the model is read from model.id, where OpenCode 2 stores it.

Session cards shorten long names, such as alfonso:consult-<uuid>, and show the full name in a tooltip. A card is shown in a neutral color instead of red when no row in the window read anything from the cache, or when only the session's first run is loaded. A card of Broca run totals counts runs instead of events.

Pi todowrite default in the config editor

When the config does not set todowrite.enabled, the config editor now shows Pi's todowrite tool as off, matching the plugin's new opt-in default. Magic Context 0.44.0 still turns the tool on when the key is unset, so on 0.44.0 set todowrite.enabled to true or false yourself.

Smaller changes

  • A session's first row in the Cache tab is labelled COLD START in blue instead of NEW SESSION, with a tooltip saying nothing was cached yet.
  • Session cards in the Cache tab are slightly wider.