Skip to content

v0.11.0: GPU for 3D, eco without a GPU, tooltips and panels that fit, shorter tower descriptions

Choose a tag to compare

@JamesMoriartyDecripto JamesMoriartyDecripto released this 15 Oct 10:14
· 858 commits to main since this release
798c69b

[0.11.0] - 2026-10-15

Changed

  • The 3D figures of flow-tower export --pdf and flow-tower report use the GPU when there is one (#209): one launcher (src/cli/browser.ts) starts Chromium with GPU flags, reads the WebGL renderer, and falls back to software WebGL (SwiftShader) when the renderer is software, the probe times out, or the GPU launch fails; it prints which one it used. FLOW_TOWER_GL=gpu|software forces the choice. On a laptop with an Intel Iris Xe the dev-squad level-3 export went from 72 s to 16 s.
  • e2e: FLOW_TOWER_E2E_GPU=1 runs the Playwright project with the GPU flags, for machines that have a GPU; CI stays in software (#209).
  • validate warns when a node description is over 400 characters or a layer description over 300: the first sentence says what the node does, details stay in its files. docs/what-goes-where.md and docs/schema.md state the limits; the example towers were shortened to fit (voice-commands, team-hub, command-center, dev-squad; the longest was 1240 characters).

Fixed

  • flow-tower export kills its server and removes its temporary user folder even when the browser launch throws (#209).
  • flow-tower service on a real systemd desktop (#194, found in #181): a systemctl --user stop no longer leaves the unit failed (the server's 130/143 exits are declared as success); service uninstall also clears a failed state, so no not-found failed unit stays listed; service status on a failed unit points to journalctl --user -u flow-tower; service install says when the library is empty (the service cannot start) and names entries gone from disk.
  • The unit's ExecStart names the node on PATH that is the running binary (/usr/bin/node), not the versioned file it resolves to (/usr/bin/node-24), so a Node major upgrade does not break the service; only absolute PATH directories that group and others cannot write are trusted. The loginctl enable-linger hint is shown only outside a graphical session (#194).
  • The 3D figures of the tower document never drew in Google Chrome (the browser, flow-tower export --pdf without Playwright's headless shell, and the e2e suite): Chrome stops animation frames in an off-screen or hidden iframe, so every snapshot timed out and the document never got ready. The snapshot iframe now stays on screen, inert and out of the tab order, under an opaque veil; both are hidden in print (#181).
  • e2e: the referenced-files check skips an optional file per node, so one node's optional entry no longer hides a file another node requires (#181).
  • Library: long project names on the cards are no longer cut to one line with an ellipsis (#211): they wrap, up to 3 lines, and the chips stay on the first line. At 1440 px four example names were cut ("Sales Pipeline: prospect to invoice", "A2A Purchasing Concierge", …); now none is, at any width from 390 to 1920 px.
  • The HUD tooltip always fits inside the window: it measures itself and goes below, above or beside its anchor, so a long node description in the right node list is no longer cut off at the bottom or squeezed into a narrow column.
  • On a remote view of a hub the MIC is hidden, and V says that voice runs on the machine serving the page (open the tower in your own Flow Tower), instead of "this page cannot reach" the server.
  • Hub budget alerts below one cent show their amounts with 4 decimals instead of "$0.00 of $0.00" (#211).
  • The hub's test alert is sent with rule test instead of silent, so a webhook receiver can tell it from a real alert (#211).
  • flow-tower share names a new share after the tower's name: (as a slug) when the folder holds one tower file, so towers kept in folders called tower no longer all share as tower; --name still wins and existing shares keep their name (#211).
  • flow-tower token add and the Admin tab say "replace 127.0.0.1" only when no url is configured: a hub that sets a loopback url on purpose (one host) no longer gets the tailnet hint (#211).
  • flow-tower connect suggests hooks install only when no harness is wired on this machine; otherwise it names the wired ones and points to hooks status (#211).
  • flow-tower guide (and the skill's procedure.md) names the real checkout command instead of a literal node <path>/bin/flow-tower.js (#211).
  • The server no longer prints Node 22's ExperimentalWarning about SQLite when it opens the history DB; every other warning still shows (#211).
  • docs/getting-started.md writes the copy and library commands as node $FT/bin/flow-tower.js … like the rest of the page, so they work without npm link (#211).
  • Hub › Machines shows one row for a sender id that was revoked and added again, instead of two rows with the same data (#211).
  • Without a GPU (software WebGL such as SwiftShader) the 3D view starts in eco quality: post-processing drew a dark rectangle over part of the tower there, and it is the slowest path anyway; a quality set in the URL or in Settings still wins (#211). The automatic pick is not saved as a preference, so a browser that gets a GPU later starts in balanced again.
  • npm run simulate prints where it sends (the URL and why: --url, the running library, or the default port) and says so instead of a stack trace when nothing answers there (#211).
  • The white corner marks of the node list, the layer list, the legend, the validation panel and the shortcuts dialog stay on the panel's frame: these panels now scroll an inner element, so the corners no longer scroll away with the rows.
  • The command-center kit's systemd unit declares SuccessExitStatus=130 143, like the user unit of service install (#194): without it systemctl stop flow-tower left the hub failed. The example towers that map Flow Tower itself (team-hub, voice-commands, command-center, the e2e-sweep sub-tower) and examples/README.md match this release's code.