You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Action ## Test bash blocks assume node/head/wc on PATH; can fail spuriously in sandboxed runtimes #157
After F2 (PR #155), ## Test blocks in 03-context-generate action files use bash commands like node --check, head -1, find, wc -l directly without absolute paths.
Problem
Some sandboxed runtimes (e.g. constrained AI agent harnesses) do not have /opt/homebrew/bin or other binary paths in PATH. The Test block then fails with command not found even when the artifact is correct.
Proposal
Either:
Document at the top of every Test block that the agent must run with PATH = standard (/usr/bin:/bin:/usr/local/bin:/opt/homebrew/bin)
Or use absolute paths in Test commands (/usr/bin/head, /usr/bin/wc etc.) — less portable
Or wrap each Test in a PATH preamble: PATH=/usr/local/bin:/usr/bin:/bin:/opt/homebrew/bin head ...
Activity
blafourcade commentedon Jun 12, 2026
We are refactoring current context-generate to split it for each case (rules, agents, hooks, commands, skills, plugins, marketplace.