C: The kiste command-line tool
Every C error code: what it means, when it happens and how to fix it.
18 codes. Each one is part of an error answer as code; type is the stable name that scripts branch on. The CLI shows the code at the end of its message, for example (code: C01). Words in braces, such as {name}, are filled in with the actual value.
C01
invalid_arguments · HTTP 0 · CLI exit code 6
{detail}. (code: C01)
When it happens. The command was given an option or value it does not accept.
How to fix it. See kiste help for the correct usage.
Retry. No. Retrying the same request gives the same answer.
C02
confirmation_required · HTTP 0 · CLI exit code 6
This needs a confirmation. (code: C02)
When it happens. A destructive command ran without a terminal to confirm in and without --yes.
How to fix it. Review the target, then repeat the command with --yes.
Retry. No. Retrying the same request gives the same answer.
C03
command_cancelled · HTTP 0 · CLI exit code 1
Cancelled. (code: C03)
When it happens. You declined the confirmation or interrupted the command.
How to fix it. Nothing was changed.
Retry. No. Retrying the same request gives the same answer.
C04
config_unreadable · HTTP 0 · CLI exit code 6
Your kiste settings couldn't be read. (code: C04)
When it happens. The settings or sign-in file of the command-line tool is unreadable or invalid.
How to fix it. Fix or remove the settings file, then try again.
Retry. No. Retrying the same request gives the same answer.
C05
ssh_client_missing · HTTP 0 · CLI exit code 10
This needs the ssh program, which isn't installed. (code: C05)
When it happens. SSH-based commands need the ssh client on this computer.
How to fix it. Install OpenSSH, then try again.
Retry. No. Retrying the same request gives the same answer.
C06
update_unavailable · HTTP 0 · CLI exit code 7
No update is available right now. (code: C06)
When it happens. The update source could not be reached or has no release for this computer.
How to fix it. Try again later.
Retry. No. Retrying the same request gives the same answer.
C07
update_failed · HTTP 0 · CLI exit code 1
The update couldn't be installed. (code: C07)
When it happens. Downloading, verifying or replacing the program failed; the installed version was kept.
How to fix it. Your current version still works. Install the update again with the installer.
Retry. No. Retrying the same request gives the same answer.
C08
remote_command_failed · HTTP 0 · CLI exit code 1
The command failed inside {name}. (code: C08)
When it happens. A command run inside a Kiste reported a failure the tool could not pass through as an exit code.
How to fix it. Check the command's output above.
Retry. No. Retrying the same request gives the same answer.
C09
forward_not_running · HTTP 0 · CLI exit code 4
There is no port forward running for {name}. (code: C09)
When it happens. A background port forward was stopped that is not running.
How to fix it. Start one with kiste forward.
Retry. No. Retrying the same request gives the same answer.
C10
unexpected_response · HTTP 0 · CLI exit code 1
kiste.run sent an answer this version doesn't understand. (code: C10)
When it happens. The answer could not be read, usually because the tool is outdated.
How to fix it. Update the kiste command-line tool, then try again.
Retry. No. Retrying the same request gives the same answer.
C11
usage_error · HTTP 0 · CLI exit code 2
{detail}. (code: C11)
When it happens. The command line could not be parsed: an unknown command or option, or a missing argument.
How to fix it. See kiste help for the commands and their options.
Retry. No. Retrying the same request gives the same answer.
C12
output_mode_unsupported · HTTP 0 · CLI exit code 10
{detail}. (code: C12)
When it happens. The command cannot produce the requested output format (a terminal session in JSON mode, a stream as one JSON document).
How to fix it. Use the form the message names.
Retry. No. Retrying the same request gives the same answer.
C13
provider_not_configured · HTTP 0 · CLI exit code 5
{provider} is not signed in inside {name}. (code: C13)
When it happens. An agent command needs a provider (such as Claude or Codex) that is not authenticated inside the Kiste.
How to fix it. Carry a login with kiste credentials push, or configure the provider's credentials in the Kiste environment.
Retry. No. Retrying the same request gives the same answer.
C14
ssh_command_failed · HTTP 0 · CLI exit code 1
{program} failed: {detail}. (code: C14)
When it happens. The local ssh, scp or rsync program exited with an error (its own exit code is passed through).
How to fix it. If the Kiste was just started, wait a few seconds and try again.
Retry. No. Retrying the same request gives the same answer.
C15
credentials_not_carried · HTTP 0 · CLI exit code 1
Not every credential could be carried ({count}): {names}. (code: C15)
When it happens. Some or all local logins could not be copied into the Kiste.
How to fix it. See the report above for why each one was skipped.
Retry. No. Retrying the same request gives the same answer.
C16
doctor_found_problems · HTTP 0 · CLI exit code 7
Not everything is healthy. (code: C16)
When it happens. kiste doctor found a check that failed (its exit code is 3 when only the sign-in is missing).
How to fix it. See the checks above.
Retry. No. Retrying the same request gives the same answer.
C17
browser_sign_in_failed · HTTP 0 · CLI exit code 3
The browser sign-in didn't complete: {detail}. (code: C17)
When it happens. The sign-in through the browser was denied, could not be verified, or no browser could be opened.
How to fix it. Run kiste login again, or sign in without a browser with kiste login --with-token.
Retry. No. Retrying the same request gives the same answer.
C18
credential_unavailable · HTTP 0 · CLI exit code 6
{credential} can't be carried: {detail}. (code: C18)
When it happens. A local login selected for carrying into a Kiste is missing, empty, too large or not a plain file.
How to fix it. Sign in to it on this computer first, or leave it out.
Retry. No. Retrying the same request gives the same answer.