mirror of
https://github.com/getcompanion-ai/co-mono.git
synced 2026-04-15 08:03:39 +00:00
docs(coding-agent): clarify tool override doesn't require --no-tools
This commit is contained in:
parent
e3dd4f21d1
commit
4a6c32c142
1 changed files with 6 additions and 4 deletions
|
|
@ -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.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue