claude-code - 💡(How to fix) Fix System prompt directs deferred tools; end-of-turn rule conflict [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#55669Fetched 2026-05-03 04:47:31
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×3commented ×1
RAW_BUFFERClick to expand / collapse

Three additional defects in Claude Code's default system prompt, separate from #55667:

1. "Using your tools" directs TaskCreate without noting it is deferred

The system prompt says:

Use TaskCreate to plan and track work. Mark each task completed as soon as it's done; don't batch.

But TaskCreate is listed in the deferred-tools system reminder. It cannot be called directly — ToolSearch must load its schema first. The instruction reads as if TaskCreate is immediately available, with no acknowledgement of the load step.

2. Bash tool description directs Monitor without noting it is deferred

The Bash tool description says:

Use the Monitor tool to stream events from a background process (each stdout line is a notification).

Monitor is also deferred and requires ToolSearch to load its schema. Same gap as #1.

3. End-of-turn summary rule contradicts the proactive /schedule offer rule

The "Text output" section says:

End-of-turn summary: one or two sentences. What changed and what's next. Nothing else.

The "Session-specific guidance" section says:

When work you just finished has a natural future follow-up, end your reply with a one-line offer to /schedule a background agent to do it...

"Nothing else" forbids anything beyond the summary. The schedule rule prescribes adding a one-line offer. The two cannot both be followed when a follow-up exists.

extent analysis

TL;DR

Update the system prompt and tool descriptions to reflect the deferred nature of TaskCreate and Monitor tools, and clarify the end-of-turn summary rule to accommodate the /schedule offer.

Guidance

  • Revise the system prompt to indicate that TaskCreate is a deferred tool, requiring ToolSearch to load its schema before use.
  • Update the Bash tool description to note that Monitor is also a deferred tool, needing ToolSearch to load its schema.
  • Reconcile the end-of-turn summary rule with the /schedule offer rule, possibly by rephrasing "Nothing else" to allow for a one-line schedule offer when a follow-up is natural.
  • Review all system prompts and tool descriptions for similar inconsistencies and deferred tool usage.

Example

No code snippet is provided as the issue is related to documentation and system prompt inconsistencies.

Notes

The solution requires careful review of the system prompts and tool descriptions to ensure consistency and accuracy in conveying the usage of deferred tools.

Recommendation

Apply workaround: Update the system prompts and tool descriptions to reflect the correct usage of deferred tools and reconcile the end-of-turn summary rule with the /schedule offer rule, as this will provide a clear and consistent user experience.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix System prompt directs deferred tools; end-of-turn rule conflict [1 comments, 2 participants]