Definition: Custom Bash Commands are user-defined, bash-backed tools that a Taskade AI Agent can call during its agent loop. Introduced in v6.154, they let a builder extend any agent inside Taskade Genesis with a bespoke command that runs against the shared virtual file system and returns structured output.
Why Custom Bash Commands Matter in 2026
Built-in tools cover the common ground. Custom Bash Commands cover everything else. A team that wants an agent to fetch a CSV from an internal endpoint, run a one-line jq transform, or kick off a build script no longer has to fork the agent runtime, they write a bash script, register it as a command, and the agent can call it. That collapses the gap between "the agent can do this" and "the agent can do this for our exact stack", which is what shipping looks like in production.
How Custom Bash Commands Work
- Author the script. Write a bash command and register it on the agent or workspace.
- Declare the interface. Name the command, describe what it does, and list any arguments it takes. The agent uses this to decide when to invoke it.
- Run in the sandbox. Execution happens inside the Taskade bash sandbox with access to the VFS.
- Return structured output. Stdout becomes the tool result; the agent reads it back during the reflect phase of its agent loop.
- Promote into skills. Once an agent has more than three custom commands, they roll into Agent Skills for on-demand loading.
Connection to Taskade
Custom Bash Commands are first-class citizens alongside slash commands and built-in tools. They are how a Space Agent can do real work inside a deployed Genesis app, the agent perceives a request, plans a script call, runs it in the sandbox, and reflects on the output, all without leaving the workspace.