fix(status): show runtime in CLI sessions

[vincentkoc]

Summary

• Problem: openclaw status showed recent session model/tokens, but omitted the agent runtime/harness that /status already prints.
• Why it matters: operators could not tell from terminal status whether a session was running through PI, Codex, ACP, or a CLI-backed runtime.
• What changed: shared the /status runtime-label resolver, adds runtime labels to status summary rows, and renders a Runtime column in the CLI sessions table.
• What did NOT change (scope boundary): no gateway runtime/service status semantics, no session migration, no runtime selection policy changes.

Change Type (select all)

• Bug fix
• Feature
• Refactor required for the fix
• Docs
• Security hardening
• Chore/infra

Scope (select all touched areas)

• Gateway / orchestration
• Skills / tool execution
• Auth / tokens
• Memory / storage
• Integrations
• API / contracts
• UI / DX
• CI/CD / infra

Linked Issue/PR

• Related #
• This PR fixes a bug or regression

Real behavior proof (required for external PRs)

• Behavior or issue addressed: CLI status sessions now include the same agent runtime/harness label used by /status.
• Real environment tested: OpenClaw repo worktree on macOS; changed gate in Blacksmith Testbox tbx_01kqvpdtpmqnaamcqd7sjb6p26.
• Exact steps or command run after this patch: see Repro + Verification.
• Evidence after fix: targeted tests assert OpenAI Codex and OpenClaw Pi Default runtime rows; changed gate passed in Testbox.
• Observed result after fix: sessions table rows include a Runtime field populated from shared status runtime label logic.
• What was not tested: a live user session status printout with production channel credentials.
• Before evidence: code inspection showed /status used resolveAgentRuntimeLabel while openclaw status session rows only rendered Model and Tokens.

Root Cause (if applicable)

• Root cause: getStatusSummary() collapsed session metadata into SessionStatus without carrying the selected harness/runtime label, so the CLI renderer had no runtime field to print.
• Missing detection / guardrail: session-row tests only covered key/kind/age/model/tokens/cache, not harness/runtime parity with /status.
• Contributing context (if known): /status and CLI status had separate formatting surfaces even though they described the same session runtime concept.

Regression Test Plan (if applicable)

• Coverage level that should have caught this:
  • Unit test
  • Seam / integration test
  • End-to-end test
  • Existing coverage already sufficient
• Target test or file: src/commands/status.summary.test.ts, src/commands/status.summary.runtime.test.ts, src/commands/status.command-sections.test.ts.
• Scenario the test should lock in: status summaries carry runtime labels and CLI session rows render them.
• Why this is the smallest reliable guardrail: the bug was data plumbing/rendering, so summary/runtime and row-format tests cover the exact seam.
• Existing test that already covers this (if any): /status runtime labels already had coverage in src/auto-reply/status.test.ts.
• If no new test is added, why not: N/A.

User-visible / Behavior Changes

openclaw status now shows a Runtime column in recent session rows.

Diagram (if applicable)

Before:
session store -> status summary -> CLI sessions table: Model, Tokens

After:
session store -> shared runtime label -> status summary -> CLI sessions table: Model, Runtime, Tokens

Security Impact (required)

• New permissions/capabilities? (Yes/No) No
• Secrets/tokens handling changed? (Yes/No) No
• New/changed network calls? (Yes/No) No
• Command/tool execution surface changed? (Yes/No) No
• Data access scope changed? (Yes/No) No
• If any Yes, explain risk + mitigation: N/A

Repro + Verification

Environment

• OS: macOS locally; Linux Blacksmith Testbox for changed gate
• Runtime/container: Node 22 / pnpm
• Model/provider: N/A
• Integration/channel (if any): N/A
• Relevant config (redacted): N/A

Steps

1. Inspect /status runtime-label path and CLI status summary/session-row path.
2. Run targeted status tests.
3. Run changed gate in Testbox.

Expected

• openclaw status session rows include the agent runtime/harness label.

Actual

• Fixed: session rows now include Runtime using the shared status runtime label resolver.

Evidence

• Failing test/log before + passing after
• Trace/log snippets
• Screenshot/recording
• Perf numbers (if relevant)

Targeted proof:

pnpm test:serial src/commands/status.summary.runtime.test.ts src/commands/status.summary.test.ts src/commands/status.command-sections.test.ts src/commands/status.command-report-data.test.ts src/auto-reply/status.test.ts -- --reporter=verbose

Passed: 3 Vitest shards, including 18 unit-fast tests, 5 commands tests, and 68 auto-reply tests.

Changed gate:

pnpm testbox:run --id tbx_01kqvpdtpmqnaamcqd7sjb6p26 -- "pnpm check:changed"

Passed: lanes core, coreTests, docs; typecheck/lint/import-cycle/guard checks completed successfully.

Human Verification (required)

• Verified scenarios: runtime labels from persisted harness metadata, summary propagation, CLI row rendering, and existing /status output tests.
• Edge cases checked: empty sessions row keeps blank Runtime; default PI and Codex labels are rendered; ACP/CLI label behavior remains covered by existing /status tests.
• What you did not verify: live production channel session output with real credentials.

Review Conversations

• I replied to or resolved every bot review conversation I addressed in this PR.
• I left unresolved only the conversations that still need reviewer or maintainer judgment.

Compatibility / Migration

• Backward compatible? (Yes/No) Yes
• Config/env changes? (Yes/No) No
• Migration needed? (Yes/No) No
• If yes, exact upgrade steps: N/A

Risks and Mitigations

• Risk: Wider status table could wrap on narrow terminals.
  • Mitigation: uses the existing table renderer and compact labels already used by /status.

[clawsweeper]

Codex review: needs maintainer review before merge.

Summary
The branch adds a CLI status Runtime column/field backed by the shared agent runtime label resolver, updates focused status tests, and adds a changelog entry.

Reproducibility: yes. Current-main source shows openclaw status recent session rows carry Model/Tokens but no Runtime, while the docs and /status runtime-label path already define that runtime distinction.

Real behavior proof
Not applicable: The external-contributor proof gate does not apply to this maintainer-labeled MEMBER PR, though the PR body includes after-fix test and Testbox evidence.

Next step before merge
Draft protected maintainer PR with no discrete repair finding; the next action is ordinary maintainer review, undraft, and merge gating rather than a ClawSweeper repair job.

Security
Cleared: No concrete security or supply-chain concern found; the diff is limited to TypeScript status rendering, tests, and a changelog entry.

Review details

Best possible solution:

Finish normal maintainer review, undraft when ready, and merge the narrow status summary/rendering patch if exact-head checks remain green.

Do we have a high-confidence way to reproduce the issue?

Yes. Current-main source shows openclaw status recent session rows carry Model/Tokens but no Runtime, while the docs and /status runtime-label path already define that runtime distinction.

Is this the best way to solve the issue?

Yes. Reusing the existing runtime-label helper and adding one summary field plus one table column is the narrow maintainable fix without changing runtime selection or session persistence semantics.

What I checked:

• Current main status summary omits runtime: getStatusSummary() builds SessionStatus rows with model/token/cache data but no runtime field for the CLI renderer to consume. (src/commands/status.summary.ts:217, c874c0863ada)
• Current main CLI sessions table has no Runtime column: The status report table columns are Key, Kind, Age, Model, Tokens, and optional Cache; row rendering also omits runtime. (src/commands/status.command-report-data.ts:116, c874c0863ada)
• Docs define runtime as part of session status: The status docs say session status separates Execution: from Runtime: and define runtime as PI, Codex, CLI backend, or ACP backend. Public docs: docs/cli/status.md. (docs/cli/status.md:26, c874c0863ada)
• Shared runtime label helper exists on main: The merged sessions-runtime work added resolveAgentRuntimeLabel(), covering ACP metadata, persisted runtime/harness ids, CLI providers, and the PI fallback. (src/status/agent-runtime-label.ts:18, c874c0863ada)
• PR diff wires runtime into status rows: The PR adds resolveSessionRuntimeLabel, stores runtime on SessionStatus, renders Runtime, and updates focused tests plus the changelog. (src/commands/status.summary.runtime.ts:169, e66fc3e7d7bb)
• Related merged CLI sessions runtime work: Related PR fix(sessions): show runtime in sessions table #78056 is merged on current main and introduced the shared runtime label helper used by this PR's status path. (src/status/agent-runtime-label.ts:1, c874c0863ada)

Likely related people:

• vincentkoc: Authored merged adjacent runtime-visibility work for CLI sessions and Control UI sessions, including the shared status runtime label helper this PR reuses. (role: recent status/runtime visibility maintainer; confidence: high; commits: c874c0863ada, 16454f5c7ae1; files: src/status/agent-runtime-label.ts, src/commands/sessions.ts, ui/src/ui/views/sessions.ts)
• Devin Robison: Local blame at the available history boundary attributes the current CLI status summary/table surfaces to a broad commit that added these files in this checkout history. (role: adjacent CLI status history owner; confidence: low; commits: 91879ac442d1; files: src/commands/status.summary.ts, src/commands/status.command-sections.ts, src/commands/status.command-report-data.ts)

Remaining risk / open question:

• No tests were rerun because this was a read-only review; verification relies on source inspection plus the PR body's reported targeted/Testbox proof.
• The added Runtime column widens the status table, so narrow terminal wrapping remains a small UX risk.

Codex review notes: model gpt-5.5, reasoning high; reviewed against c874c0863ada.