docs: document embedded harness status indicator · openclaw/openclaw@bb63f3c
steipete
·
2026-04-24
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -60,7 +60,8 @@ have transcript history. Use `/new` or `/reset` to opt that conversation into
|
60 | 60 | Codex after changing config. |
61 | 61 | |
62 | 62 | `/status` shows the effective non-PI harness next to `Fast`, for example |
63 | | -`Fast · codex`. The default PI harness is omitted. |
| 63 | +`Fast · codex`. The default PI harness remains `Runner: pi (embedded)` and does |
| 64 | +not add a separate harness badge. |
64 | 65 | |
65 | 66 | ## Requirements |
66 | 67 | |
|
| Original file line number | Diff line number | Diff line change |
|---|
@@ -140,6 +140,16 @@ Choose your preferred auth method and follow the setup steps.
|
140 | 140 | Onboarding no longer imports OAuth material from `~/.codex`. Sign in with browser OAuth (default) or the device-code flow above — OpenClaw manages the resulting credentials in its own agent auth store. |
141 | 141 | </Note> |
142 | 142 | |
| 143 | +### Status indicator |
| 144 | + |
| 145 | +Chat `/status` shows which embedded harness is active for the current |
| 146 | +session. The default PI harness appears as `Runner: pi (embedded)` and does |
| 147 | +not add a separate badge. When the bundled Codex app-server harness is |
| 148 | +selected, `/status` appends the non-PI harness id next to `Fast`, for example |
| 149 | +`Fast · codex`. Existing sessions keep their recorded harness id, so use |
| 150 | +`/new` or `/reset` after changing `embeddedHarness` if you want `/status` to |
| 151 | +reflect a new PI/Codex choice. |
| 152 | + |
143 | 153 | ### Context window cap |
144 | 154 | |
145 | 155 | OpenClaw treats model metadata and the runtime context cap as separate values. |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
