Comparing a32bc9af17..e2fa21ddf7 - ocp - Gitea: Git with a cup of tea

taodeng/ocp

Fork 0

mirror of https://github.com/dtzp555-max/ocp.git synced 2026-07-24 14:35:08 +00:00

Author	SHA1	Message	Date
taodengandClaude <claude-opus-4-8> <noreply@anthropic.com>	e2fa21ddf7	fix(prompt): OCP_LOCAL_TOOLS wrapper no longer hard-codes a tool list (closes #185 ) The positive local-tools wrapper (server.mjs) claimed the model has "full access to the local filesystem, working directory, and shell through your available tools (Bash, Read, Write, Edit, Glob, Grep, etc.)". That over-promises when an operator narrows CLAUDE_ALLOWED_TOOLS (e.g. to Read,Grep): the model is told it has Bash/Write/shell it doesn't hold, then attempts a non-granted tool and gets denied. The default set matches the text, so the primary/OpenClaw path was fine — but the enumeration was a prompt-honesty mismatch (flagged in the #182 fact-check). Reworded to flip the POSTURE only ("you may use your available local tools … do not assume access beyond the tool set provided to you in this session") without enumerating specific tools or asserting shell/write capability. The model learns its real tools from the tool definitions claude is given (--allowedTools), so the enumeration was redundant as well as fragile — now honest under any allowed set. No const reordering / no CONFIG_EPOCH change (still a constant; the epoch-fold test confirms toggling still invalidates the cache with the new text). Test markers updated (selectPromptWrapper unit + the boot-server integration assertion that the positive wrapper reaches the -p spawn). Suite 449/0. Rule 2: OCP-owned prompt composition, no wire change, no cli.js citation. Closes #185 Co-Authored-By: Claude <claude-opus-4-8> <noreply@anthropic.com>	2026-07-23 17:29:24 +10:00

Author

SHA1

Message

Date

taodengandClaude <claude-opus-4-8> <noreply@anthropic.com>

e2fa21ddf7

fix(prompt): OCP_LOCAL_TOOLS wrapper no longer hard-codes a tool list (closes #185 )

The positive local-tools wrapper (server.mjs) claimed the model has "full access
to the local filesystem, working directory, and shell through your available
tools (Bash, Read, Write, Edit, Glob, Grep, etc.)". That over-promises when an
operator narrows CLAUDE_ALLOWED_TOOLS (e.g. to Read,Grep): the model is told it
has Bash/Write/shell it doesn't hold, then attempts a non-granted tool and gets
denied. The default set matches the text, so the primary/OpenClaw path was fine —
but the enumeration was a prompt-honesty mismatch (flagged in the #182 fact-check).

Reworded to flip the POSTURE only ("you may use your available local tools … do
not assume access beyond the tool set provided to you in this session") without
enumerating specific tools or asserting shell/write capability. The model learns
its real tools from the tool definitions claude is given (--allowedTools), so the
enumeration was redundant as well as fragile — now honest under any allowed set.

No const reordering / no CONFIG_EPOCH change (still a constant; the epoch-fold
test confirms toggling still invalidates the cache with the new text). Test
markers updated (selectPromptWrapper unit + the boot-server integration assertion
that the positive wrapper reaches the -p spawn). Suite 449/0.

Rule 2: OCP-owned prompt composition, no wire change, no cli.js citation.

Closes #185

Co-Authored-By: Claude <claude-opus-4-8> <noreply@anthropic.com>

2026-07-23 17:29:24 +10:00

Compare commits

Diff Content Not Available