FAQ & TROUBLESHOOTING
Answers based on the current EveryCli workflow.
01The daemon does not respond+
The daemon runs as a Windows service. Check its status with `sc.exe query EveryCliDaemon`. If it is not running, start it with `sc.exe start EveryCliDaemon`, or run a search with `--no-daemon` to force direct local retrieval.
02Can I work without a connection?+
Yes. EveryCli is local-first. The semantic model runs entirely on your machine; lexical retrieval is always available as a fallback when the daemon is not running.
03Does Sentinel execute the command it suggests?+
No. `everycli plan` only returns a command, risk level, and checks. It never runs a shell command.
04How do I add a command to the corpus?+
Run `everycli add` for the interactive flow. Your entry is saved to `~/.everycli/commands/<namespace>.yaml` and merged with the built-in corpus at search time.
05How do I list or remove my custom commands?+
Use `everycli list` to see all personal corpus entries and `everycli remove <id>` to delete one (the tool prompts for confirmation).
06How do I use the PowerShell helper?+
Source `everycli.ps1` in your session, then use `evc`. The result goes into PSReadLine's editable command buffer; it is not executed automatically.
07How do I install or uninstall the daemon service?+
Run `.\install.ps1` to register the daemon as a Windows service (UAC elevation is handled automatically). Run `.\uninstall.ps1` to remove it.
Still blocked? Open an issue on GitHub with the output of sc.exe query EveryCliDaemon and the command you were trying to run.