mirror of
https://github.com/openclaw/openclaw.git
synced 2026-05-06 05:30:42 +00:00
docs: replace ampersand headings for stable Mintlify anchors
Per docs/CLAUDE.md, Mintlify anchor generation is brittle for headings
that contain em dashes, apostrophes, and ampersands. Normalize 9 H2
headings across docs/date-time.md, docs/pi.md, docs/platforms/{index,
macos, mac/webchat, mac/peekaboo}.md, docs/nodes/{images,audio}.md, and
docs/reference/AGENTS.default.md from `X & Y` to `X and Y` so anchors
do not collapse on entity decoding. Verified no inbound anchor references
to the renamed sections in the docs tree.
This commit is contained in:
@@ -62,7 +62,7 @@ You can override this behavior:
|
||||
[WhatsApp +1555 +30s 2026-01-18T05:19Z] follow-up
|
||||
```
|
||||
|
||||
## System prompt: Current Date & Time
|
||||
## System prompt: current date and time
|
||||
|
||||
If the user timezone is known, the system prompt includes a dedicated
|
||||
**Current Date & Time** section with the **time zone only** (no clock/time format)
|
||||
|
||||
@@ -144,7 +144,7 @@ Note: Binary detection is best-effort across macOS/Linux/Windows; ensure the CLI
|
||||
}
|
||||
```
|
||||
|
||||
## Notes & limits
|
||||
## Notes and limits
|
||||
|
||||
- Provider auth follows the standard model auth order (auth profiles, env vars, `models.providers.*.apiKey`).
|
||||
- Groq setup details: [Groq](/providers/groq).
|
||||
|
||||
@@ -51,7 +51,7 @@ The WhatsApp channel runs via **Baileys Web**. This document captures the curren
|
||||
- If the active primary image model already supports vision natively, OpenClaw skips the `[Image]` summary block and passes the original image to the model instead.
|
||||
- By default only the first matching image/audio/video attachment is processed; set `tools.media.<cap>.attachments` to process multiple attachments.
|
||||
|
||||
## Limits & Errors
|
||||
## Limits and errors
|
||||
|
||||
**Outbound send caps (WhatsApp web send)**
|
||||
|
||||
|
||||
@@ -337,7 +337,7 @@ const compactResult = await compactEmbeddedPiSessionDirect({
|
||||
});
|
||||
```
|
||||
|
||||
## Authentication & Model Resolution
|
||||
## Authentication and model resolution
|
||||
|
||||
### Auth profiles
|
||||
|
||||
@@ -418,7 +418,7 @@ if (cfg?.agents?.defaults?.contextPruning?.mode === "cache-ttl") {
|
||||
}
|
||||
```
|
||||
|
||||
## Streaming & Block Replies
|
||||
## Streaming and block replies
|
||||
|
||||
### Block chunking
|
||||
|
||||
|
||||
@@ -22,7 +22,7 @@ Native companion apps for Windows are also planned; the Gateway is recommended v
|
||||
- Windows: [Windows](/platforms/windows)
|
||||
- Linux: [Linux](/platforms/linux)
|
||||
|
||||
## VPS & hosting
|
||||
## VPS and hosting
|
||||
|
||||
- VPS hub: [VPS hosting](/vps)
|
||||
- Fly.io: [Fly.io](/install/fly)
|
||||
|
||||
@@ -65,7 +65,7 @@ socket path is in use. You can override with:
|
||||
export PEEKABOO_BRIDGE_SOCKET=/path/to/bridge.sock
|
||||
```
|
||||
|
||||
## Security & permissions
|
||||
## Security and permissions
|
||||
|
||||
- The bridge validates **caller code signatures**; an allowlist of TeamIDs is
|
||||
enforced (Peekaboo host TeamID + OpenClaw app TeamID).
|
||||
|
||||
@@ -13,7 +13,7 @@ agent (with a session switcher for other sessions).
|
||||
- **Remote mode**: forwards the Gateway control port over SSH and uses that
|
||||
tunnel as the data plane.
|
||||
|
||||
## Launch & debugging
|
||||
## Launch and debugging
|
||||
|
||||
- Manual: Lobster menu → “Open Chat”.
|
||||
- Auto‑open for testing:
|
||||
|
||||
@@ -162,7 +162,7 @@ If `openclaw doctor` detects state under:
|
||||
|
||||
it will warn and recommend moving back to a local path.
|
||||
|
||||
## Build & dev workflow (native)
|
||||
## Build and dev workflow (native)
|
||||
|
||||
- `cd apps/macos && swift build`
|
||||
- `swift run OpenClaw` (or Xcode)
|
||||
|
||||
@@ -72,7 +72,7 @@ cp docs/reference/AGENTS.default.md ~/.openclaw/workspace/AGENTS.md
|
||||
- Capture: decisions, preferences, constraints, open loops.
|
||||
- Avoid secrets unless explicitly requested.
|
||||
|
||||
## Tools & skills
|
||||
## Tools and skills
|
||||
|
||||
- Tools live in skills; follow each skill’s `SKILL.md` when you need it.
|
||||
- Keep environment-specific notes in `TOOLS.md` (Notes for Skills).
|
||||
|
||||
Reference in New Issue
Block a user