Shared tools
Skills every workspace's agent can run, with their own environment variables and named credential profiles.
- Reading time
- 1 min read
How it works
A tool is a script the whole organization shares, a scraper, a query runner, a headless browser,
a research helper. Any workspace's agent, Claude Code, Codex or OpenCode, can run one with
devbench tools run, so a capability written once in one workspace is available in all of them
instead of being re-implemented per box.
Each tool carries a base environment and any number of named credential profiles. A
profile is a set of variables under a name, staging, prod, so the same tool runs against
different environments without a second copy and without pasting keys into a prompt. Secret values
are stored encrypted and are never returned by the API; a run picks a profile with --env, and
one-off values can be added at the call site.
Steps
Open Tools from Automate in the top bar (or the search: Ctrl Ctrl, ⌘ ⌘ on a Mac).
Press New tool, name it, and pick the interpreter.
python3,bash, and so on.Describe what it does in one line.
That description is what an agent reads when deciding whether to use it.
Paste the script.
Add the base environment variables it always needs.
Add credential profiles for the environments it runs against.
Secrets are stored encrypted and never returned.
Save it. Any workspace's agent can now run it.
Commands
The same job from a workspace's box, for people who live in the terminal.
$ devbench tools listThe team's shared tools and skills.$ devbench tools show <name>A tool's info, env vars and profiles.$ devbench tools run <name> --env prod -- <args>Run one under a named credential profile.