Skip to content

docs: rename --enabled-tools to --additional-tools and add --restrict-tools#1271

Open
lukealvoeiro wants to merge 1 commit into
mainfrom
docs/rename-enabled-tools-add-restrict-tools
Open

docs: rename --enabled-tools to --additional-tools and add --restrict-tools#1271
lukealvoeiro wants to merge 1 commit into
mainfrom
docs/rename-enabled-tools-add-restrict-tools

Conversation

@lukealvoeiro

Copy link
Copy Markdown
Contributor

Summary

Renames the droid exec --enabled-tools CLI flag to --additional-tools and introduces a new --restrict-tools flag (allowlist: run only the listed tools) across the English and Japanese docs.

Changes

  • overview.mdx (EN + JP): the tool-controls example now shows droid exec --restrict-tools ApplyPatch "refactor files" plus an --additional-tools example; help-text block lists both flags.
  • cli-reference.mdx (EN + JP): the single --enabled-tools row is split into --restrict-tools and --additional-tools rows.
  • mcp.mdx (EN + JP): the per-tool filtering cross-reference now points to --restrict-tools (matching the enabledTools allowlist semantics).

Out of scope

  • The mcp.json enabledTools / disabledTools config field names are intentionally left unchanged.
  • Docs-only; no CLI binary changes.

…-tools

Rename the droid exec --enabled-tools CLI flag to --additional-tools and
introduce --restrict-tools (allowlist) across the EN and JP docs. Update
the overview examples, CLI reference tables, and the MCP per-tool
filtering cross-reference. The mcp.json enabledTools config field is
left unchanged.

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
@factory-droid

factory-droid Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Droid encountered an error —— View job


Security Review

Droid is reviewing code and running a security check…

@mintlify

mintlify Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
factory 🟢 Ready View Preview Jul 6, 2026, 7:05 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@factory-droid

factory-droid Bot commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Droid finished @lukealvoeiro's task —— View job


Security Review

The flag rename and new --restrict-tools docs look consistent across the updated EN/JP pages. The one issue is that the new ApplyPatch examples omit --auto even though the page documents spec-mode as read-only by default, so the example commands will fail as written.

Comment on lines +359 to +363
# Restrict to only specific tools
droid exec --restrict-tools ApplyPatch "refactor files"

# Enable additional tools
droid exec --enabled-tools ApplyPatch "refactor files"
droid exec --additional-tools ApplyPatch "refactor files"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[P1] Add --auto to ApplyPatch tool-control examples

This page states droid exec defaults to spec-mode (read-only), but the new tool-control examples invoke ApplyPatch without --auto, so they will fail permission checks as written. Add --auto low (or use a read-only tool in the example) to keep the docs executable.

Suggested change
# Restrict to only specific tools
droid exec --restrict-tools ApplyPatch "refactor files"
# Enable additional tools
droid exec --enabled-tools ApplyPatch "refactor files"
droid exec --additional-tools ApplyPatch "refactor files"
# Restrict to only specific tools
droid exec --auto low --restrict-tools ApplyPatch "refactor files"
# Enable additional tools
droid exec --auto low --additional-tools ApplyPatch "refactor files"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant