The Power Claude CLI ships as a single binary named pc. When pc status returns command not found, the binary either isn't installed, isn't on your PATH, or the shell has a cached lookup pointing at a deleted copy.
1. The CLI is not installed
The VS Code extension does not install the CLI. They are separate components. To install the CLI:
curl -fsSL https://neural-llm.com/install/pc | bash
That drops the binary at ~/.power-claude/bin/pc and writes a one-line PATH addition to your shell rc.
Or install manually from a release tarball — extract anywhere on PATH and chmod +x.
2. The install directory is not on PATH
echo "$PATH" | tr ':' '\n' | grep power-claude
If that prints nothing, your shell can't see the install dir. Add it:
echo 'export PATH="$HOME/.power-claude/bin:$PATH"' >> ~/.bashrc
exec bash
(Use ~/.zshrc for zsh.) If you installed the CLI to a non-default location, substitute that path.
3. The shell has a stale lookup cache
Bash and zsh cache command paths. If you reinstalled pc after uninstalling it, the shell may still be looking at the deleted binary:
hash -r # bash — clear the lookup cache
rehash # zsh
Then pc status should resolve.
Verify the install end-to-end
which pc # path to the binary your shell will run
pc --version # confirms binary + signed-build integrity
pc status --json | jq '.version' # confirms binary can talk to the runtime
If which pc prints a path but pc --version errors out, the binary is corrupt or built for a different architecture. Reinstall from the official installer; do not copy a binary between machines unless they share the same OS/arch.