Troubleshooting

Quick checks

Confirm you're logged in

harumi whoami

If this errors, run harumi login (or harumi login --signup for a brand-new email).

Confirm the directory is bound

run, outputs, datasources, and schedules need a project. Either run from a directory containing .harumi/config.json (written by harumi init) or pass --project <PROJECT_ID>.

Confirm the VPN is up for git operations

git.dev.harumi.io is internal. harumi init, harumi projects create, and any run that pushes code fail without the VPN.

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` (once the git backend is live) while on the VPN
Git push hangs or times out	VPN down	Connect to the Harumi VPN and retry
"not yet available" / no-op on `schedules` or `projects create`	Assumed endpoint not shipped	Expected during the git-first migration — see below
`You belong to multiple organizations`	Org not set	`harumi config set-org <ORG_ID>` or pass `--org` per command

Assumed endpoints

Some commands are wired to an API contract that's still landing on the backend as part of the git-first migration:

harumi projects create — POST /projects is live, but repo provisioning on create is assumed. If the backend doesn't return repo metadata, the command errors clearly rather than binding you to an unusable project.
harumi schedules ... — the pivot re-keys schedules from notebook_id to project_id. Until that lands, these commands no-op with an explicit error.

These are expected, not bugs

A clear "not yet available" message means the CLI is ready and waiting on the backend route — not that your setup is broken. Everything else (auth, init, run, outputs, datasources) uses live endpoints today.

Resetting local state

If credentials or config get into a bad state, they're plain files under ~/.harumi (or $HARUMI_HOME if set):

harumi logout            # clears ~/.harumi/credentials.json
cat ~/.harumi/config.json

Deleting ~/.harumi/config.json resets api_url, git_url, and org_id to defaults; the per-project binding lives separately in <project>/.harumi/config.json.