Skip to content

CLI Errors and Hints

Mel edited this page Nov 10, 2026 · 1 revision

Every error prints its message on stderr and exits 1. Most are followed by a usage line and a try: pointer. Unknown names get a did you mean line when a close match exists.

Message (as printed) Cause What to do
no entry "skills/file-pip"; search first, or list with `stack list` + did you mean: skills/file-pr an id that does not exist use the suggestion, or stack list / stack search
unknown command "lst" + did you mean: list? + see: stack help a mistyped command use the suggestion or stack help
unknown flag --porject + see: stack help status + did you mean --project? a mistyped flag fix the flag; stack help <command> lists them
--file needs a value a flag that takes a value was last on the line give the value
search needs a query (with usage: and try:) a command missing its argument see the usage line
unknown kind "widget"; use one of skill, style, ... a kind that does not exist one of the eight kinds, singular or plural
no such directory: /abs/path --project (or the cwd) does not exist create it, or fix the path
... is not an entry at stack commit <sha> (new entries must be committed to the stack before importing) the entry exists in the working tree but not in the committed HEAD commit the entry in the stack, then import
these files already exist with other content; move them or choose --to: + paths a project file would be overwritten move the file, or use --to
--to works with one id at a time --to with several ids import them one at a time
../outside is outside the project --to points out of the project use a path inside the project
skills/nope is not imported here remove or update for an id that is not in stack.toml check stack status
stack ref "x" not found in <stack> --ref names a rev the stack does not have fetch it into the stack clone, or use an existing rev
no preset "x"; list them with stack preset list unknown preset stack preset list
no remote library "x" unknown name for stack remote ... stack remote list
stack.toml already tracks 2 imports; nothing to do init in a project that already imports nothing to do
invalid file path '' show --file with an empty path pass a path
binary file 'escacs-logo.svg' (557 bytes); use --json for base64 show --file on a file the CLI treats as binary (see CLI Known Issues) use --json, or read the file at stack path <id>
no such file 'nope.txt' in components/dithercn/aurora show <id> --file with a path the entry does not have use stack show <id> to list the files
--port must be 0-65535 serve --port out of range pick a valid port
remote needs an action: list, status or sync stack remote with no action add one
failed components/<lib>: git failed for <url>: ... (remote sync) the library could not be fetched check the URL and the network, then run it again
.gitignore has a half-written escacs block; delete the "# >>> escacs stack" line and run stack gitignore an interrupted edit of the managed block (from the code) delete the start line, run stack gitignore

Import refuses only the import cases above. Near-match suggestions exist for unknown ids, commands, kinds and flags, but an import does not refuse because a file name looks like another file.

See also: CLI Known Issues, CLI Output Modes, CLI Importing.

Clone this wiki locally