8.6.0 — See what each session runs, and shared apps that show only what you choose

A snapshot as of 8.6.0 (released 2026-10-03). It will go stale as the app moves on — that is expected, and the living reference is the guide each section links to.

New features

See what each session runs, and which worktrees can go

Open More features → Processes (or type Processes in the command palette) (#2871). Nothing to set up.

• The Processes tab lists each session’s folder with the processes running under it: PID, CPU, memory, how long it has run, and the command. Busy and day-old processes are highlighted. End stops one (it is asked first, then sent SIGTERM, and SIGKILL if it is still there a few seconds later). Nothing is ended for you.
• The Worktrees tab lists the managed worktrees of the folders your terminals have run in, each with what keeps it from going — uncommitted files, commits not in the base, a terminal still standing in it. A worktree with none of those gets Remove, which checks everything again before it removes anything. Nothing is removed automatically.

The page reads only while it is open. See Basics.

Shared apps: choose what visitors see

When you ask the agent to build a shared app (a form, a sign-up sheet, a question box), it now asks first whether visitors to the public page should see what people send (#2866, #2873). Four answers, each a different app:

• Nobody sees it — only you read what arrives.
• Only the ones I choose — each record stays hidden until you switch it on in the list at MulmoServer’s /m/{slug}. The new question-box template is this: anyone asks, you publish the questions you answer (#2865).
• Only the totals — visitors see how many chose each answer; names and comments stay with you. The new tally template (#2873).
• Everyone sees everything — a scheduling grid, where seeing every answer is the point.

The preview shows the same rows production does: an unpublished record no longer appears on the public page while you try it (#2863). See Shared apps.

What looks different

• More features has Processes (#2871).
• A build’s work list says when it failed to load, with Try again, instead of showing nothing (#2859).

Under the hood

• Booking templates let a booker cancel where they can reach it (#2869). meeting-room, salon and gym put the cancel on a page that only people on the app’s roster can open, so a customer who booked from the public page could not reach it. New apps: meeting-room and class-seats show “your bookings” with a withdraw button on the public page; salon sends cancellations to the shop; gym says only invited members reach its member page. If you published an app from one of these templates before, nothing in it changes — its records, its URLs and its settings are as they were — but its cancel page is still out of reach for public bookers. To fix it, ask the agent to move the app to the new template’s shape and publish again; until then, tell customers to contact you.
• Public rows no longer carry an id that links them to the same person in another app (#2874, #2875). Rows anybody can read now use a per-app pseudonym as their id; the schedule-poll and tally templates use it.
• The shared-app publisher was updated (@receptron/sharedapp 0.37–0.39): it checks the new “only the ones I choose” declaration, a deadline on a sender’s own cancellation, and refuses a correction that could move a booking’s window (#2860, #2867, #2868).
• A build’s work list refuses a repeated item id (#2859).

Nothing here needs doing, unless you published one of the booking apps above.