ci/woodpecker/pr/codex Pipeline was successful
ci/woodpecker/pr/compact-editor-chrome Pipeline was successful
ci/woodpecker/pr/notifications Pipeline was successful
ci/woodpecker/pr/progress Pipeline was successful
ci/woodpecker/pr/title-status Pipeline was successful
ci/woodpecker/pr/tool-rendering Pipeline was successful
ci/woodpecker/pr/web-fetch Pipeline was successful
ci/woodpecker/pr/web-search-codex Pipeline was successful
ci/woodpecker/pr/welcome Pipeline was successful
ci/woodpecker/push/codex Pipeline was successful
ci/woodpecker/push/compact-editor-chrome Pipeline was successful
ci/woodpecker/push/notifications Pipeline was successful
ci/woodpecker/push/progress Pipeline was successful
ci/woodpecker/push/title-status Pipeline was successful
ci/woodpecker/push/tool-rendering Pipeline was successful
ci/woodpecker/push/web-fetch Pipeline was successful
ci/woodpecker/push/web-search-codex Pipeline was successful
ci/woodpecker/push/welcome Pipeline was successful
28 lines
491 B
Markdown
28 lines
491 B
Markdown
# tool rendering
|
|
|
|
this gives Pi's built-in `bash`, `read`, `grep`, `ls`, `find`, `write`, and `edit` tools consistent, pretty and minimal rendering in the terminal.
|
|
|
|
## why
|
|
|
|
because
|
|
|
|
## how to install
|
|
|
|
```sh
|
|
pi install npm:@eleith-pi/tool-rendering
|
|
```
|
|
|
|
## how to use
|
|
|
|
make a tool call and be impressed.
|
|
|
|
use `/eleith:tool-rendering toggle` to be unimpressed.
|
|
|
|
## how to configure
|
|
|
|
update `~/.pi/agent/extensions/eleith.json` with the following:
|
|
|
|
```json
|
|
{ "commandPrefix": "personal" }
|
|
```
|