vultr/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-05-06 07:40:44 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: typography hygiene + dup H1 across 5 pages (cli/gateway/help)

Browse Source
This commit is contained in:
Vincent Koc
2026-05-05 22:34:25 -07:00
parent 6febffb6fe
commit e85fd2abcd
5 changed files with 16 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/cli/acp.md
View File

@@ -118,7 +118,7 @@ Permission model (client debug mode):
- `read` auto-approval is scoped to the current working directory (`--cwd` when set).
- ACP only auto-approves narrow readonly classes: scoped `read` calls under the active cwd plus readonly search tools (`search`, `web_search`, `memory_search`). Unknown/non-core tools, out-of-scope reads, exec-capable tools, control-plane tools, mutating tools, and interactive flows always require explicit prompt approval.
- Server-provided `toolCall.kind` is treated as untrusted metadata (not an authorization source).
- This ACP bridge policy is separate from ACPX harness permissions. If you run OpenClaw through the `acpx` backend, `plugins.entries.acpx.config.permissionMode=approve-all` is the break-glass “yolo” switch for that harness session.
- This ACP bridge policy is separate from ACPX harness permissions. If you run OpenClaw through the `acpx` backend, `plugins.entries.acpx.config.permissionMode=approve-all` is the break-glass "yolo" switch for that harness session.
## How to use this
@@ -218,7 +218,7 @@ pull contextual information from an OpenClaw agent without scraping a terminal.
## Zed editor setup
Add a custom ACP agent in `~/.config/zed/settings.json` (or use Zed’s Settings UI):
Add a custom ACP agent in `~/.config/zed/settings.json` (or use Zed's Settings UI):
```json
{
@@ -256,7 +256,7 @@ To target a specific Gateway or agent:
}
```
In Zed, open the Agent panel and select “OpenClaw ACP” to start a thread.
In Zed, open the Agent panel and select "OpenClaw ACP" to start a thread.
## Session mapping

10
docs/cli/status.md
View File

@@ -2,12 +2,10 @@
summary: "CLI reference for `openclaw status` (diagnostics, probes, usage snapshots)"
read_when:
- You want a quick diagnosis of channel health + recent session recipients
- You want a pasteable “all” status for debugging
title: "Status"
- You want a pasteable "all" status for debugging
title: "openclaw status"
---
# `openclaw status`
Diagnostics for channels + sessions.
```bash
@@ -34,8 +32,8 @@ Notes:
- Overview includes update channel + git SHA (for source checkouts).
- Update info surfaces in the Overview; if an update is available, status prints a hint to run `openclaw update` (see [Updating](/install/updating)).
- Read-only status surfaces (`status`, `status --json`, `status --all`) resolve supported SecretRefs for their targeted config paths when possible.
- If a supported channel SecretRef is configured but unavailable in the current command path, status stays read-only and reports degraded output instead of crashing. Human output shows warnings such as “configured token unavailable in this command path”, and JSON output includes `secretDiagnostics`.
- When command-local SecretRef resolution succeeds, status prefers the resolved snapshot and clears transient “secret unavailable” channel markers from the final output.
- If a supported channel SecretRef is configured but unavailable in the current command path, status stays read-only and reports degraded output instead of crashing. Human output shows warnings such as "configured token unavailable in this command path", and JSON output includes `secretDiagnostics`.
- When command-local SecretRef resolution succeeds, status prefers the resolved snapshot and clears transient "secret unavailable" channel markers from the final output.
- `status --all` includes a Secrets overview row and a diagnosis section that summarizes secret diagnostics (truncated for readability) without stopping report generation.
## Related