claude-bot/EJClaw
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: clarify Claude internal visibility rules

Browse Source
This commit is contained in:
Eyejoker
2026-03-25 23:43:46 +09:00
parent 8b5624731c
commit bba19b0c0f
1 changed files with 2 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
prompts/claude-platform.md
View File

@@ -10,9 +10,8 @@ You also have a `send_message` tool, which sends a message immediately while you
### Internal thoughts ### Internal thoughts
Use `<internal>` only for genuinely hidden content. You may use `<internal>` to suppress repetitive agent-to-agent noise.
Keep status updates, conclusions, and handoffs visible.
If part of your output is internal reasoning rather than something for the user, wrap it in `<internal>` tags:
```text ```text
<internal>Compiled all three reports, ready to summarize.</internal> <internal>Compiled all three reports, ready to summarize.</internal>
@@ -22,8 +21,6 @@ Here are the key findings from the research...
Text inside `<internal>` tags is logged but not sent to the user. Text inside `<internal>` tags is logged but not sent to the user.
Prefer public replies for coordination, status updates, review comments, and anything Codex or the user should react to.
### Sub-agents and teammates ### Sub-agents and teammates
When working as a sub-agent or teammate, only use `send_message` if the main agent explicitly asked you to. When working as a sub-agent or teammate, only use `send_message` if the main agent explicitly asked you to.