Shell Builtins
Prowl's shell (internal/shell/) uses mvdan.cc/sh/v3 for POSIX shell
emulation. Commands can be intercepted before they reach the OS by adding
builtins — functions handled in-process.
How Builtins Work
Builtins live in builtinHandler() in internal/shell/run.go. This is an
interp.ExecHandlerFunc middleware registered in standardHandlers()
before the block handler, so builtins run even for commands that would
otherwise be blocked. The same handler chain is shared by the stateful
Shell type and the stateless Run entrypoint used by the hook runner,
so builtins are available identically in the bash tool and in hooks.
The handler is a switch on args[0]. Each case either handles the command
inline or delegates to a helper function.
Adding a New Builtin
- Add the case to the switch in
builtinHandler() in run.go.
- Get I/O from the handler context, not from
os.Stdin/os.Stdout.
This ensures the builtin works with pipes and redirections:case "mycommand":
hc := interp.HandlerCtx(ctx)
return handleMyCommand(ctx, args, hc.Stdin, hc.Stdout, hc.Stderr)
- Implement the handler in its own file (e.g.,
internal/shell/mycommand.go). The function signature must accept a
context.Context as the first parameter, plus args, stdin, stdout, and
stderr:func handleMyCommand(ctx context.Context, args []string, stdin io.Reader, stdout, stderr io.Writer) error {
// args[0] is the command name ("mycommand"), args[1:] are arguments.
// Write output to stdout, errors to stderr.
// Return nil on success, or interp.ExitStatus(n) for non-zero exit codes.
}
- Poll
ctx in every unbounded loop. Builtins that iterate over
input, emit values in a generator-style loop, or do any other work
that can exceed a few milliseconds MUST check ctx.Err() on each
iteration and return it verbatim when non-nil. Hook timeouts rely on
this: an unbounded builtin that never polls ctx cannot be interrupted
by a hook's timeout_sec, and the hook runner will have to abandon
the goroutine (see internal/hooks/runner.go). Returning ctx.Err()
(not interp.ExitStatus(n)) lets callers distinguish "command exited
non-zero" from "we ran out of time".for _, item := range items {
if err := ctx.Err(); err != nil {
return err
}
// ... process item
}
- Return values: return
nil for success, interp.ExitStatus(n) for
non-zero exit codes, or ctx.Err() on cancellation. Write error
messages to stderr before returning.
- No extra wiring needed —
builtinHandler() is already registered
in standardHandlers().
Existing Builtins
| Command |
File |
Description |
jq |
jq.go |
JSON processor using github.com/itchyny/gojq |
1---2name: shell-builtins3description: Use when creating a new shell builtin command for Prowl (internal/shell/), editing an existing one, or when the user needs to understand how commands are intercepted in Prowl's embedded shell.4---56# Shell Builtins78Prowl's shell (`internal/shell/`) uses `mvdan.cc/sh/v3` for POSIX shell9emulation. Commands can be intercepted before they reach the OS by adding10**builtins** — functions handled in-process.1112## How Builtins Work1314Builtins live in `builtinHandler()` in `internal/shell/run.go`. This is an15`interp.ExecHandlerFunc` middleware registered in `standardHandlers()`16**before** the block handler, so builtins run even for commands that would17otherwise be blocked. The same handler chain is shared by the stateful18`Shell` type and the stateless `Run` entrypoint used by the hook runner,19so builtins are available identically in the `bash` tool and in hooks.2021The handler is a switch on `args[0]`. Each case either handles the command22inline or delegates to a helper function.2324## Adding a New Builtin25261. **Add the case** to the switch in `builtinHandler()` in `run.go`.272. **Get I/O from the handler context**, not from `os.Stdin`/`os.Stdout`.28 This ensures the builtin works with pipes and redirections:29 ```go30 case "mycommand":31 hc := interp.HandlerCtx(ctx)32 return handleMyCommand(ctx, args, hc.Stdin, hc.Stdout, hc.Stderr)33 ```343. **Implement the handler** in its own file (e.g.,35 `internal/shell/mycommand.go`). The function signature must accept a36 `context.Context` as the first parameter, plus args, stdin, stdout, and37 stderr:38 ```go39 func handleMyCommand(ctx context.Context, args []string, stdin io.Reader, stdout, stderr io.Writer) error {40 // args[0] is the command name ("mycommand"), args[1:] are arguments.41 // Write output to stdout, errors to stderr.42 // Return nil on success, or interp.ExitStatus(n) for non-zero exit codes.43 }44 ```454. **Poll `ctx` in every unbounded loop.** Builtins that iterate over46 input, emit values in a generator-style loop, or do any other work47 that can exceed a few milliseconds MUST check `ctx.Err()` on each48 iteration and return it verbatim when non-nil. Hook timeouts rely on49 this: an unbounded builtin that never polls ctx cannot be interrupted50 by a hook's `timeout_sec`, and the hook runner will have to abandon51 the goroutine (see `internal/hooks/runner.go`). Returning `ctx.Err()`52 (not `interp.ExitStatus(n)`) lets callers distinguish "command exited53 non-zero" from "we ran out of time".54 ```go55 for _, item := range items {56 if err := ctx.Err(); err != nil {57 return err58 }59 // ... process item60 }61 ```625. **Return values**: return `nil` for success, `interp.ExitStatus(n)` for63 non-zero exit codes, or `ctx.Err()` on cancellation. Write error64 messages to `stderr` before returning.656. **No extra wiring needed** — `builtinHandler()` is already registered66 in `standardHandlers()`.6768## Existing Builtins6970| Command | File | Description |71|---------|------|-------------|72| `jq` | `jq.go` | JSON processor using `github.com/itchyny/gojq` |