docs: corrections from open issues (#2, #8, #9)#18
Conversation
- Part 24 (#8): add a version-accuracy banner mapping the semantic approval category model + openclaw flows references to the verified 2026.4.15+ shipping knobs (tools.exec.security/ask, tools.fs.workspaceOnly, tools.profile, openclaw exec-policy show, ocplatform security audit). Mark the per-category approvals JSON as the intended control-plane model, not a guaranteed config key. - SCORECARD Pillar 4: point the semantic-categories item at the verified knobs. - Part 11 (#9): add a Troubleshooting entry for 'sessionKey is not defined' / 'Hook triggered' / 'Extraction failed' — those strings come from a stale, hand-edited, or built-in hook, not this repo's handler.ts. - Part 27 (#2): add a FAQ entry on the post-Anthropic-subscription model strategy (frontier orchestrator + metered API, push volume to cheaper/local workers).
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
|
|
||
| ### Anthropic ended the Claude subscription path — has that changed your model strategy? Do you still run Opus as the orchestrator? | ||
|
|
||
| Yes, the economics changed; the architecture didn't. Anthropic's April 4, 2026 policy change ended the old "Claude Pro/Max covers OpenClaw" route, so Claude is now explicit **paid API / Bedrock / provider-routed** usage with budget caps — not a flat-rate subscription (see the [README hero note](./README.md) and the upgrade table at the top of this part, plus [Part 33](./part33-late-april-2026-field-guide.md)). |
There was a problem hiding this comment.
🟡 Broken cross-reference: "upgrade table at the top of this part" points to Part 27, which has no such table
The new FAQ entry says "see the [README hero note](./README.md) and the upgrade table at the top of this part, plus [Part 33]...". "This part" refers to Part 27 (the current file), but Part 27 has no upgrade/version table at its top — only cause/fix gotcha tables. The "Version Map" table the text intends to reference is in part33-late-april-2026-field-guide.md:8. Readers following this direction will look at the top of Part 27, find no upgrade table, and be confused.
| Yes, the economics changed; the architecture didn't. Anthropic's April 4, 2026 policy change ended the old "Claude Pro/Max covers OpenClaw" route, so Claude is now explicit **paid API / Bedrock / provider-routed** usage with budget caps — not a flat-rate subscription (see the [README hero note](./README.md) and the upgrade table at the top of this part, plus [Part 33](./part33-late-april-2026-field-guide.md)). | |
| Yes, the economics changed; the architecture didn't. Anthropic's April 4, 2026 policy change ended the old "Claude Pro/Max covers OpenClaw" route, so Claude is now explicit **paid API / Bedrock / provider-routed** usage with budget caps — not a flat-rate subscription (see the [README hero note](./README.md) and the Version Map at the top of [Part 33](./part33-late-april-2026-field-guide.md)). |
Was this helpful? React with 👍 or 👎 to provide feedback.
There was a problem hiding this comment.
Good catch — fixed in 7c81a04. Part 27 does have a relevant table (the "May upgrade broke my old workflow" cause/fix table, whose first row covers exactly this Claude-costs-money case), so I pointed "the table at the top of this part" at that anchor and added the #version-map anchor for the Part 33 reference. lychee --offline confirms both fragments resolve.
The FAQ pointed to a nonexistent 'upgrade table at the top of this part'; point to the actual 'May upgrade broke my old workflow' table in Part 27 and the Version Map anchor in Part 33 (per Devin Review on #18).
2 participants
Summary
Addresses three open issues with targeted, conservative documentation fixes — no mass rewrites, uncertainty flagged inline.
openclaw flows/ semantic-approval categories don't exist in 2026.4.15. Theflows→tasksrename was already handled in a prior refresh; this PR closes the remaining gap (theagents.*.approvalssemantic-token config block). Adds a "Version accuracy" banner to the Semantic Approval Categories section that maps the guide's semantic model to the verified shipping knobs the reporter tested (tools.exec.security,tools.exec.ask,tools.fs.workspaceOnly,tools.profile,openclaw exec-policy show,ocplatform security audit), and reframes the per-categoryapprovalsJSON as the intended control-plane model rather than a guaranteed config-file key. SCORECARD Pillar 4 item updated to point at the verified knobs.Extraction failed: sessionKey is not defined. The currenthooks/auto-capture/handler.tsalready definessessionKeyand logs[auto-capture] Triggered:/Error:— notHook triggered:/Extraction failed:. So the reporter is running a stale/hand-edited handler or the built-insession-memoryhook. Added a Troubleshooting section to Part 11 explaining the symptom, the giveaway log strings, and the fix.Type of change
Review checklist
markdownlint-cli2andlychee --offlinelocally (CI will also run these)Notes / flagged items
agents.*.approvalsblock truly never shipped, a follow-up could demote those JSON examples further.Link to Devin session: https://app.devin.ai/sessions/21e86e63e6ed4a7cb88868ac2243d9ef
Requested by: @OnlyTerp