Troubleshooting
Common harumi CLI errors and how to resolve them.
Quick checks
Confirm you're logged in
harumi whoamiIf this errors, run harumi login (or harumi login --signup for a brand-new
email).
Confirm the directory is bound
run, runs, outputs, repo, datasources, schedules, and secrets
need a project. Either run from a directory containing .harumi/config.json
(written by harumi init) or pass --project <PROJECT_ID>.
Common errors
| Symptom | Likely cause | Fix |
|---|---|---|
Signups not allowed for otp on login | First login for this email | Retry with harumi login --signup |
Provide --project or run from a directory with a .harumi binding | No project resolved | cd into a bound directory or pass --project <id> |
No Harumi project found. Run harumi init ... on run | Directory isn't bound | harumi init --project <PROJECT_ID> first |
Not a Harumi repo / git remote errors | The harumi remote isn't configured | Re-run harumi init; ensure you're inside a git init-ialized directory |
No Gitea token found on run/init | Git token wasn't provisioned | Re-run harumi login |
<path> is not valid UTF-8 text on repo cat | The file is binary | Re-run with --output <local_path> to save it |
Run ended with status: failed on run --watch | Your code raised or exited non-zero | harumi runs get <RUN_ID> for the captured stdout/stderr/error |
You belong to multiple organizations | Org not set | harumi config set-org <ORG_ID> or pass --org per command |
A new project is missing from projects list, or landed in the wrong workspace | An older CLI ignored the configured organization when creating projects, so they went to your personal workspace | Upgrade the CLI (pipx upgrade harumi), or pass --customer-id <ORG_ID> explicitly. Already-created projects don't move on their own — change their workspace in the web app |
Not a directory: <path> on import | Pointed import at a .zip instead of a folder | Unzip the export first, then run harumi import from inside it |
zsh: command not found: pip | Homebrew's Python only ships pip3, not pip | Use pipx install harumi (recommended), or pip3 install harumi / python3 -m pip install harumi |
error: externally-managed-environment on pip install | PEP 668 blocks pip outside a virtualenv | Use pipx install harumi, or add --user, or install into a venv |
Resetting local state
If your session or config gets into a bad state, they're plain files under
~/.harumi (or $HARUMI_HOME if set):
harumi logout # clears your stored sessionThe per-project binding lives separately in <project>/.harumi/config.json;
delete it to unbind a directory.