The kodeo CLI isn't working

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, then kodeo push. kodeo pull --ours or --theirs resolves 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 --switch follows it.
• Behind a corporate proxy — set HTTPS_PROXY (and NO_PROXY). If certificates fail, point NODE_EXTRA_CA_CERTS at your company's CA.
• "No keychain found" (Linux containers) — install libsecret's secret-tool, or pass --insecure-storage once to accept a private file.
• Your clock is off — sign-ins are signed with the time; turn on automatic time sync.

The dashboard or a prompt looks wrong

• Boxes look broken or symbols are question marks — your terminal's font is missing them. Use --ascii (or kodeo config icons ascii). In Windows' old console, Windows Terminal draws everything properly.
• Colours are hard to read — kodeo couldn't tell your terminal's background. Run kodeo config background light (or dark), or pick a theme: kodeo config theme.
• kodeo ui says it needs an interactive terminal — it can't draw in a pipe, under CI, or in plain mode. Use kodeo who, kodeo chat, kodeo inbox or kodeo git status.
• The mouse doesn't scroll in kodeo ui — not every terminal sends mouse events; the keys always work (? lists them).

"Synced by KODEO for VS Code"

kodeo watch found VS Code already syncing this folder and is standing by — one sync engine per folder. Close the folder in VS Code (or let it be) and watch takes over by itself.

No desktop notifications

They're off until you run kodeo config desktop on, and they show only while kodeo watch or kodeo ui is running. On Linux they need notify-send (the libnotify package). KODEO's pause and quiet hours apply, and one already shown by VS Code isn't shown again. kodeo doctor checks them.