feat(cli): list managed Agent View sessions in qwen sessions ps

.qwen/skills/find-simplifications/SKILL.md

@@ -122,6 +122,7 @@ the issue comment.
 | Several strong candidates in one run                             | File them all; land at most one                            |
 | Report-only territory                                            | File with evidence, marked report-only. Never a PR         |
 | Path or symbol younger than ~90 days                             | Drop **silently** — unwired new feature, not rot           |
+| A young **subsystem** unwired, its wiring PR open and stale      | Not a deletion. Report the stall to that PR stack          |
 | A never-called migrator, validator, guard, or dropped wire-up    | Not cleanup. It may be a defect → `/bugfix` or `/review`   |
 | Any consumer cannot be named                                     | Drop                                                       |
 | Correct but tiny (one dead import, a typo)                       | Reject on the ledger: below both skills' intake bar        |

.qwen/skills/find-simplifications/references/survey.md

@@ -139,6 +139,27 @@ feature someone is still wiring up. (90 days is a heuristic, not a measured
 threshold; widen it for a large subsystem.) Proposing deletion of something
 that landed last week is the fastest way to lose a reviewer for good.
 
+But "young" is not the fact the gate is reaching for — "still being wired
+up" is, and the two come apart. A directory can keep growing for months
+while its consumer never lands, and then every re-run of this survey dates
+it young again and drops it again, which is how a subsystem gets to five
+figures with nothing calling it. So when the gate fires on a **subsystem**
+(not a single symbol), date the wiring rather than the code:
+
+```bash
+# has anything outside it ever referenced it?
+"$RG" -l '<dir>/' --glob '!<dir>/**' packages
+# and are the PRs that would wire it still open?
+gh pr list --repo QwenLM/qwen-code --search '<feature> in:title' --state all
+```
+
+Recent commits inside the directory plus no external reference plus an open,
+stalled wiring PR is **not** a deletion candidate and **not** a drop. It is a
+different finding with a different owner: the wiring stalled. Report it to
+that stack — the merged infrastructure has no entry point — and never as a
+deletion PR. The code is wanted; the review that would connect it is what is
+missing.
+
 **3 — Published-surface escape.** Is the surface reachable from outside the
 repo? SKILL.md § Territory is the authoritative list; keep the two in step.
 Everything under `packages/core/src` is, via that package's `"./src/*"`
@@ -262,13 +283,27 @@ registry entry), not in `packages/core`, and `git log` puts it well past the
 recency gate. Deletion is the component, its test, and its snapshot entry, in
 one commit. This is what a filed candidate should look like.
 
-**2. Everything says dead; `git` says five days old.** `packages/cli/src/agent-view`
-is ~6,000 lines whose entry flag is passed to a spawned process but parsed
-nowhere; every static signal calls it rot. Then:
+**2. Everything says dead; `git` says five days old — and says it again a
+month later.** `packages/cli/src/agent-view` was ~6,000 lines whose entry flag
+is passed to a spawned process but parsed nowhere; every static signal called
+it rot. Then:
 `git log --follow --diff-filter=A --format=%ad --date=short -- packages/cli/src/agent-view
-| tail -1` → `2026-08-01`, five days before HEAD. It is a feature mid-wiring.
-**Drop silently.** Do not file it, do not mention it — a "should we delete
-your new subsystem?" question costs more trust than the finding is worth.
+| tail -1` → `2026-08-01`, five days before HEAD. A feature mid-wiring, so:
+**do not file a deletion.** A "should we delete your new subsystem?" question
+costs more trust than the finding is worth.
+
+What this example originally got wrong was the second half — "do not mention
+it". Measured again on 2026-09-04: **11,004 production lines, still zero
+external references**, up ~8,000 in four weeks. The five merged PRs of its
+stack shipped the supervisor, the PTY workers and the lifecycle; the two that
+would give it an entry point (#7802 commands, #7803 roster TUI) have been
+open since 2026-07-27, the second at +31,699 lines across 104 files and
+conflicting. The recency gate kept firing and the survey kept dropping it, so
+nothing ever said out loud that a five-figure subsystem had no caller.
+
+The deletion verdict was right and stays right. The silence was not: this is
+the stalled-wiring finding above, owed to that PR stack, not to a cleanup
+list.
 
 **3. The naive count is wrong in both directions.**
 `eslint.legacy-filenames.mjs` lists 559 bare basenames. Checking "does a

docs/users/features/commands.md

@@ -707,10 +707,10 @@ These commands are run from the shell as `qwen <subcommand>` before starting an
 
 ### Session Management
 
-| Command              | Description                                 | Usage Examples                                               |
-| -------------------- | ------------------------------------------- | ------------------------------------------------------------ |
-| `qwen sessions list` | List recent conversation sessions           | `qwen sessions list`, `qwen sessions list --json --limit 50` |
-| `qwen sessions ps`   | List interactive sessions running right now | `qwen sessions ps`, `qwen sessions ps --json`                |
+| Command              | Description                         | Usage Examples                                               |
+| -------------------- | ----------------------------------- | ------------------------------------------------------------ |
+| `qwen sessions list` | List recent conversation sessions   | `qwen sessions list`, `qwen sessions list --json --limit 50` |
+| `qwen sessions ps`   | List the sessions running right now | `qwen sessions ps`, `qwen sessions ps --json`                |
 
 #### `qwen sessions list`
 
@@ -752,12 +752,19 @@ qwen sessions list --json | jq .
 
 #### `qwen sessions ps`
 
-Lists the interactive Qwen Code sessions running on this machine right
-now. `sessions list` walks saved transcripts ("what have I worked on");
-this walks the live-process registry ("what is running at this moment").
-Records left behind by a killed session are swept as they are found.
-Headless sessions (`qwen -p`) do not register with the live-process
-registry, so they are not shown.
+Lists the Qwen Code sessions running on this machine right now.
+`sessions list` walks saved transcripts ("what have I worked on"); this
+answers "what is running at this moment".
+
+Two kinds of session are listed. An **interactive** session is one you
+started in a terminal; it registers in the live-process registry, and
+records left behind by a killed session are swept as they are found. A
+**managed** session is an Agent View session owned by a supervisor: it
+writes no registry record, so it used to be invisible here. Managed
+sessions are listed first, because one of them may be waiting for an
+answer.
+
+Headless sessions (`qwen -p`) register nowhere and are not shown.
 
 **Flags:**
 
@@ -767,20 +774,38 @@ registry, so they are not shown.
 
 **Human-readable output (default):**
 
-A table with columns: NAME, PID, AGE, DIRECTORY.
+A table with columns: NAME, PID, AGE, STATE, DIRECTORY.
+
+STATE is `interactive` for a session you started yourself. For a managed
+session it is what that session is actually doing — `needs input`,
+`working`, `ready`, `stopped` or `failed`. PID and AGE print `-` for a
+managed session with no process behind it (one that has exited, or has
+not started its worker yet).
 
 **JSON output (`--json`):**
 
-Outputs JSON Lines on stdout, newest session first. Each line is a JSON
-object with fields:
+Outputs JSON Lines on stdout, managed sessions first. Every line carries
+a `managed` field saying which kind it is.
+
+An interactive session is emitted as its whole registry record, plus
+`managed: false`:
 
 ```
 schemaVersion, pid, procStart, pidNs, sessionId, cwd, name, startedAt,
-qwenVersion
+qwenVersion, managed
+```
+
+A managed session has no such record and is emitted as the row itself:
+
+```
+name, pid, startedAt, cwd, state, sessionId, managed
 ```
 
 Nothing else is written to stdout — an empty listing prints nothing at
-all — so `qwen sessions ps --json | jq .` is safe to script against.
+all — so `qwen sessions ps --json | jq .` is safe to script against. If
+the supervisor's own bookkeeping cannot be read, the interactive half is
+still listed and the reason is reported on stderr, which leaves stdout
+parseable.
 
 JSON output is raw data: field values are emitted exactly as recorded,
 with no terminal sanitization. Treat them as data, and sanitize before
@@ -796,6 +821,12 @@ qwen sessions ps
 # Note: `jq -r` renders the raw recorded value in your terminal (see the
 # raw-data note above); pipe through a sanitizer if the path is untrusted.
 qwen sessions ps --json | jq -r .cwd
+
+# Which background sessions are waiting on me?
+# Note: `jq -r` renders the raw recorded value in your terminal (see the
+# raw-data note above); a session name is session-generated text, so pipe
+# through a sanitizer if it is untrusted.
+qwen sessions ps --json | jq -r 'select(.state == "needs input") | .name'
 ```
 
 ## 6. Messaging Another Running Session

packages/cli/src/agent-view/presentation.ts

@@ -13,6 +13,15 @@ import type {
   AgentViewSessionStateFile,
 } from './protocol.js';
 
+/**
+ * Title shown for a session that has produced nothing to name it by.
+ *
+ * Exported because a caller that cannot afford an unidentifiable row —
+ * a one-line listing, where there is nothing to arrow onto — has to be
+ * able to recognize the placeholder and substitute the session id.
+ */
+export const AGENT_VIEW_UNTITLED_TITLE = 'Untitled session';
+
 export type AgentViewTaskState =
   | 'running'
   | 'waiting'
@@ -326,7 +335,7 @@ function deriveTitle(
     cleanText(rosterEntry?.displayName) ??
     cleanRuntimeSummary(activity?.summary) ??
     cleanText(launch?.initialPrompt) ??
-    'Untitled session'
+    AGENT_VIEW_UNTITLED_TITLE
   );
 }