Troubleshooting
The kodeo CLI isn't working
Push refused, signed out, proxies, certificates and keychains — what the CLI's messages mean and how to fix them.
1 min readUpdated 29 Sept 2026
Start with kodeo doctor — it checks your connection, proxy, certificates, clock, keychain, sign-in and version, and says how to fix each one.
- "Push refused … moved on KODEO" — someone changed a file you're pushing. Run
kodeo pull(it merges), then push again. Nothing was changed by the refused push. - Conflict markers (
<<<<<<<) — both sides changed the same lines. Edit the file, remove the markers, thenkodeo push.kodeo pull --oursor--theirsresolves every conflict one way. - "This sign-in has ended" — it was signed out from Settings → Local access, by a password or email change, "This wasn't me", or a Team policy. Run
kodeo login. - "The project is on another branch now" — a teammate switched the project's branch.
kodeo pull --switchfollows it. - Behind a corporate proxy — set
HTTPS_PROXY(andNO_PROXY). If certificates fail, pointNODE_EXTRA_CA_CERTSat your company's CA. - "No keychain found" (Linux containers) — install libsecret's
secret-tool, or pass--insecure-storageonce to accept a private file. - Your clock is off — sign-ins are signed with the time; turn on automatic time sync.
Still have a question about this?
Assist answers from this article — in any language.
Was this helpful?
More in Troubleshooting
Browsers and devicesWhich browsers KODEO supports, what works on phones and tablets, and fixes for the most common browser problems.Solo mode and "ReconnectingWhy the editor says Solo mode or Reconnecting, why your work is safe, and how to get live collaboration back.Getting help — Assist, tickets and response timesHow to reach KODEO support, what KODEO Assist can and can't see, how tickets work, and how long a reply takes.KODEO for VS Code troubleshootingFixes for the extension — Open in VS Code does nothing, the sign-in doesn't come back, "offline (Solo)", read-only, conflicts, and vscode.dev.