[chaliy]

Requested by Михайло · project thread

What changed

The command word now goes through the same field splitting as arguments. "$@", "${@}", $@, "${arr[@]}", unquoted $cmd and $(...) used as the command expand to several words: the first is the command name, the rest become leading arguments. An expansion that yields no words ("$@" with no params, empty unquoted $x) runs no command and exits 0, unless a command substitution ran, matching bash. Pure literal command names keep the old fast path.

Why

Wrapper functions like g(){ "$@"; } are a common bash idiom and failed outright: the command word was expanded to one string, so g echo hi looked up a command literally named echo hi.

Before / After

$ bashkit -c 'g(){ "$@"; }; g echo hi'
before: bash: echo hi: command not found   (rc=127)
after:  hi

Differential run against real bash on "$@", "${@}", $@, "$@" x, array splat, $c, $(echo echo sub), empty "$@", empty $x, set -- "" a; "$@", "$x" empty, set -- "echo z"; "$@": identical stdout/stderr/status (apart from bashkit's existing "Did you mean" suggestion). Exit status after empty expansion also matches bash now (false; "$@"; echo $? gives 0, z=$(false) $x; echo $? gives 1).

Risk

• Low
• Only non-literal command words take the new path. Glob/brace expansion is still not applied to the command word (unchanged).

Checklist

• Tests added or updated (spec_cases/bash/command-word-expansion.test.sh, 15 cases; 11 fail on main)
• Backward compatibility considered

https://claude.ai/code/session_01TNq48wTz3pUYQGXQEXHnTN

---

Generated by Claude Code

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	bashkit	c40a714	Commit Preview URL Branch Preview URL	Oct 06 2026, 06:49 PM