Authorization notice. Raw CLI is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Who it is forA team lead whose agent needs a shell tool that behaves differently, such as a stricter wrapper or a team-specific default.
The problemBuilt-in tools are fixed in most harnesses, so custom behavior usually means forking the whole product.
The outcomeA local copy of the bash tool that one agent selects in place of the built-in, with the change kept in a file the team can read.
What you need first
- Node.js 22.13+ on macOS, Linux or Windows 10/11
- Bash for the bash tool (Git Bash on Windows, or PowerShell if Bash is absent)
- A local model served over an OpenAI-compatible endpoint, or a hosted model with an API key
- Comfort editing a strict JSON config file
Steps
- Run
npm install -g @tlelabs/rawif Raw is not installed yet. - Copy the example folder
examples/tools/bash/to~/.config/raw/tools/my_bash/. - Change the manifest
idandnamein the copied folder, then edit itsindex.mjsas needed. - In your agent's
tools.uselist, replacebuiltin/bashwithlocal/my_bash. - Run
raw --agent raw "Run the test suite"and check that the output shows your tool's behavior. (inferred, check the README)
Prompt for your agent
Using the repo lploc94/raw-cli, copy examples/tools/bash/ to ~/.config/raw/tools/<tool-name>/, change its manifest id and name, and select local/<tool-name> in the agent <agent-name>. Expected output: a successful run of one shell command through the forked tool. Verify the run output shows the forked tool name and a status line.
Caveat. The README gives the copy path and the id and name edits, but the exact contents of index.mjs are not described, so the change itself is up to you.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page