docs(agent): document the variable tool Permission Mode

[j15z]

Summary

Documents the agent tool Permission Mode shipped in #7538. The Agent block reference now says the control lives in each tool's expanded settings, and explains switching it to a variable such as <start.toolMode>, which must resolve to auto, force, or none or the run stops before the model is called.

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation
• Other: ___________

Testing

• bun run docs:check passes.
• Wording matches the editor (Permission Mode label and its selector/variable switch) and the run behavior verified during QA of feat(agent): allow variable tool permission modes #7538.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

Screenshots/Videos

No screenshots attached.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Sep 15, 2026 1:27am UTC

[greptile-apps]

Confidence Score: 4/5

The documentation is safe to merge, though it should clarify when Permission Mode and the Force option are unavailable.

Findings

1.  Permission Mode availability omitted ▶

Summary

This documentation update explains where to configure an Agent tool’s Permission Mode, describes the Auto, Force, and None options, and documents selecting the mode dynamically through a workflow variable.

• The documented variable syntax and runtime validation behavior match the implementation.
• The availability constraints for the control and Force option are not documented.

_{Reviews (1) · Last reviewed commit: "docs(agent): document the variable tool ..."}