From 4a6c32c142d5f002fbab5448d61844b6aac606a4 Mon Sep 17 00:00:00 2001 From: Mario Zechner Date: Thu, 8 Jan 2026 13:17:47 +0100 Subject: [PATCH] docs(coding-agent): clarify tool override doesn't require --no-tools --- packages/coding-agent/docs/extensions.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/packages/coding-agent/docs/extensions.md b/packages/coding-agent/docs/extensions.md index 5c53c7f3..f1a779c5 100644 --- a/packages/coding-agent/docs/extensions.md +++ b/packages/coding-agent/docs/extensions.md @@ -946,13 +946,15 @@ pi.registerTool({ Extensions can override built-in tools (`read`, `bash`, `edit`, `write`, `grep`, `find`, `ls`) by registering a tool with the same name. Interactive mode displays a warning when this happens. -Use `--no-tools` to start without built-in tools, then add back specific ones with `--tools`: +```bash +# Extension's read tool replaces built-in read +pi -e ./tool-override.ts +``` + +Alternatively, use `--no-tools` to start without any built-in tools: ```bash # No built-in tools, only extension tools pi --no-tools -e ./my-extension.ts - -# No built-in read, use extension's read, keep other built-ins -pi -e ./tool-override.ts ``` See [examples/extensions/tool-override.ts](../examples/extensions/tool-override.ts) for a complete example that overrides `read` with logging and access control.