Troubleshooting
Agent Says You Must Install a CLI Tool?
What to do when your agent insists it needs a random command-line tool before it can continue.
This is a common confusion pattern in community chat: the agent asks for something like a CLI install, users assume setup is broken, and they get stuck for hours.
Short version: in most Heyron workflows, you should ask for a workaround first. Many tasks can be completed without local CLI installs.
Why this happens
- The model may suggest a familiar developer path by default ("install X CLI").
- Your actual environment may be containerized/headless, so local machine installs are irrelevant.
- The task may have multiple valid paths, and the CLI path is only one option.
Use this 3-step recovery flow
1) Ask for a no-install alternative
Do not require local CLI installs. Give me a headless/container-safe workaround using built-in tools, APIs, or manual handoff steps.
2) Force assumptions check
Before continuing, list your assumptions about my environment (OS access, package managers, browser automation, API keys). Mark each as confirmed vs unconfirmed.
3) Request two plans, then pick
Give me:
Plan A: no local installs, fastest path.
Plan B: requires installs, but only if truly necessary.
For each plan include risks, time, and success criteria.
When installs are actually reasonable
- You explicitly want a local-dev workflow on your own machine.
- The task truly depends on a binary that has no API/manual alternative.
- You understand and approve the exact command before running it.
Safety rule: don’t run install commands blindly. If you see an approval prompt, read the full command exactly as shown (including chained operators like && and pipes) before approving.
Copy/paste self-check before opening #help
Task I wanted: [goal]
CLI/tool agent asked to install: [name]
Did I ask for a no-install workaround first? [yes/no]
Environment assumptions listed by agent: [paste]
What happened after workaround prompt: [result/error]
Bottom line: treat "install this CLI" as a suggestion, not a requirement, unless the agent can prove there is no practical no-install path.