Jadpo is experimental and not ready for production. These docs follow the compiler's main branch as of 5 Nov 2026. What's built · Install 0.3.0
jadpo
ReferenceErrors

ErrorsTools · rule

cli.completions_arguments

On this page

A jadpo completions command names no shell, or one Jadpo writes no completions for.

Area 14, Tools; not declinable; the next step is usually the agent's.

Why Jadpo refuses it

Each shell reads its own kind of completion script, and Jadpo writes them for zsh, bash and fish. A script for the wrong shell would be read as broken code, so it prints none.

What it looks like

The shell is one Jadpo doesn't complete:

shell
jadpo completions powershell
jadpo completions

error powershell isn't a shell jadpo completes

reason
Jadpo writes completion scripts for zsh, bash and fish.
next
Use zsh, bash or fish (agent)
rule
cli.completions_arguments
help
https://jadpo.dev/docs/errors/cli.completions_arguments

(agent) at the end of the next: line means your coding agent can make the fix itself.

With no shell, it asks for one:

shell
jadpo completions
jadpo completions

error jadpo completions needs a shell

reason
Each shell gets its own script: zsh, bash or fish.
next
Add the shell, for example jadpo completions zsh (agent)
rule
cli.completions_arguments
help
https://jadpo.dev/docs/errors/cli.completions_arguments

How to fix it

If your shell is zsh, bash or fish, name it:

shell
jadpo completions zsh > ~/.zfunc/_jadpo

The script completes commands, flags and their values after Tab.

Markdown for agents: /docs/errors/cli.completions_arguments.md.Built from Jadpo main at aee2e8f.