OpenClaw Main Adds Project-Backed Sessions and Editable Chat Queues

OpenClaw has merged a coherent Control UI workflow for people running several repositories and steering busy sessions: registered projects can be selected as the source of a new session, queued messages can be reordered or edited in place, project-file references are easier to distinguish, and machine-created probe sessions are hidden by default.

None of these changes expands model capability. Together they reduce a more mundane production risk: an operator sending the right instruction to the wrong repository, in the wrong queue position, while real chats are buried under health checks.

Availability: these features are merged to main; check the containing build before expecting them in the UI.

Projects become session inputs

PR #121465 lets the new-session Place picker consume projects registered with OpenClaw rather than requiring operators to rediscover or paste a checkout path.

The current Control UI documentation says read-only connections receive project names and IDs, while checkout paths and origin URLs require write scope. Registering a Git checkout is an administrative action. Starting from a project passes the durable project identity through session creation and can supply the source for a managed worktree.

That distinction matters. A friendly project name is not proof of the checkout, remote origin or branch. Operators should verify the resolved path before the first consequential prompt.

Queue edits preserve position and attachments

PR #121682 adds queue reordering from the composer. PR #121692 then lets an operator lift a queued row and its attachments back into the composer with a pencil action or double-click.

The original row remains visible and marked as being edited. Cancelling leaves storage untouched; sending retires the original and inserts the corrected message at its prior queue position. This is safer than delete-and-recreate because the operator can see where the revised instruction will execute.

It is not a transaction across the whole agent run. If the queue advances while another client edits, acceptance tests should prove the final order rather than trusting visual position.

File labels and system-session filtering

PR #121775 renders recognised workspace paths as file-labelled references, with disambiguating suffixes when basenames collide. This is presentation, not a file-access grant; clicking or reading still follows Gateway scope and workspace policy.

PR #121855 classifies machine-created probes from recorded creation provenance and hides them behind a persisted Show system sessions toggle. The implementation does not rely on prompt text alone, which avoids treating a human chat containing words such as “pong” as a probe.

Hidden is not deleted. Incident responders should turn system sessions back on when investigating failed health checks or internal runs.

Rollout checklist

1. register a disposable repository and confirm read-only, write and admin clients receive only the documented project fields;
2. start direct and managed-worktree sessions from the project, then verify the actual checkout before allowing writes;
3. queue three synthetic prompts with distinct attachments, reorder them and prove execution follows the displayed order;
4. edit the middle row, cancel once, then save a correction and verify attachment ownership and queue position survive;
5. repeat one edit from two clients and require a visible conflict or deterministic result;
6. reference two files with the same basename and confirm the UI exposes enough path suffix to tell them apart; and
7. toggle system sessions on during an incident drill and prove hidden probes remain searchable and inspectable.

Bottom line

Registered projects and editable queues make Control UI steering less error-prone. They do not remove the need to verify checkout identity, queue order and attachment custody before a high-impact run starts.