Skip to content

Launches: list every launch Nullius made, in a workspace or not #183

Description

@harenome

Priority

medium. The change is in the web layer: a new page, two routes and a shared table script. The backend gains two small helpers and reads only what it already reads.

Components

  • app/nullius (backend)
  • app/web (routes)
  • templates and static files
  • docs and the site
  • catalogue (benchmarks, agents, capabilities)
  • the standard (ports, kits, relay, runs)
  • CI, workflows and skills

Today

A press of Run in the builder makes a launch: one run record, runs/<name>/run.json, per machine. The Runs page shows only the launches of the open workspace (_launched_here in app/web/runs.py). At start-up, execution.restore() reads every run record but adds only the runs that are still going to a workspace.

If you delete a workspace, its launches stay on disk (the run folders and their copies on the hosts). No page lists them. You cannot open them again, add them to another workspace or delete them from the UI.

Wanted

A Launches page under Manage, after Workspaces. It is a table like the Workspaces page, with one row for each launch that Nullius made from the builder, newest first. Each launch is in the table, in a workspace or not. The rows use the grouping of the Runs page (launches.group), so a launch in shards on several machines is one row in every state, also while its shards prepare or run. There is no row per shard.

Columns:

  • State, first: an icon for each state, in the words of the Runs page (finished, refused)
  • Launch: its title as the Runs page shows it
  • Started
  • Runs (the agents) and Checks (nop and oracle), counted as on the Runs page
  • Shards: one for each machine
  • Machines: this machine or the hosts
  • Size: on this machine
  • Workspaces: each workspace that holds it, or "none"

Actions: Add to workspace…, which asks for a workspace in a dialog and adds the launch's job roots to it. Delete launch, with the dialog and the rules of the Runs page (no Delete while a run is still going). The title opens a workspace that holds the launch, on the Runs page at that launch.

Three buttons above the table: Columns, Filter and Sort by. Filter narrows by State, Machines and Workspaces ("none" gives the launches that no workspace holds). Sort by sorts by Launch, Started, State, Runs, Checks, Shards and Size. The headers have no filter carets; only the sorted column shows an arrow. When the table is wider than the page, it scrolls sideways in its own box, and State and Launch stay at the left. It shows 10, 25, 100 or all rows on a page, and each viewer's choice is remembered.

Jobs that nullius standard run writes from the CLI, and Harbor folders from elsewhere, are not included.

Acceptance

  • The sidebar has Launches after Workspaces, with an icon of its own.
  • Every run record is in the table. One row is one launch, and the shards of a launch on several machines are one row in every state, also before any shard writes its job.
  • A launch that no workspace holds is listed, with "none" in Workspaces.
  • Add to workspace adds the launch's job roots to the chosen workspace. It needs the form token and a local client.
  • Delete launch uses the dialog and route of the Runs page, works with no workspace open, and returns to Launches. What it would take is worked out when the dialog opens, not for every row of the page.
  • A launch that cannot be deleted keeps a greyed Delete that a keyboard can reach and that says why: a run still going, no run record, or a run record that cannot be read.
  • A launch shows the same Runs and Checks on Launches and on the Runs page, a merged launch and a job refused before it started included.
  • The title opens a workspace that holds the launch, on the Runs page at that launch, also when the workspace holds only some of its shards.
  • The table sorts, filters and pages in the browser, with the sort and filter code that the Runs page also uses. Filter and Sort by are menus beside Columns, not header carets, and only the sorted column shows an arrow. The menus work with the keyboard: Escape closes them and gives the focus back, and Tab out of one closes it. The pages are shared table code too, that another table can use.
  • When the table is wider than the page, it scrolls in its own box, and State and Launch stay in place.
  • State is the first column: an icon of its own shape for each state, with the Runs page's word as its accessible name and tooltip. Its header shows nothing and is named State for screen readers. It sorts in the Runs page's state order.
  • The page answers while a run is writing its files.
  • The empty page is one line.

Dependencies and related

Activity

  1. added
    enhancementNew feature or request
    P2Planned: limited in scope, has a way around it, or a missing feature
    on Nov 17, 2026
  2. added theissue type on Nov 17, 2026
  3. added a commit that references this issue on Nov 17, 2026
    fe260f5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Planned: limited in scope, has a way around it, or a missing featureenhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions