Troubleshooting & FAQ

Terminal compatibility

Q: Does it work in Windows cmd.exe?

A: Windows legacy console (conhost.exe) does not support DEC 2026, has flaky CJK widths, and process.stdin doesn't surface IME composition events. Use Windows Terminal, WezTerm, Alacritty or VS Code terminal instead.

Models & Providers

Q: Does @zlogic.run use its own API?

A: No. @zlogic.run does not provide models and has no cloud API or control plane. All requests go directly to the provider endpoint you configure.

Q: Can I use local models?

A: Yes. Run Ollama, vLLM or any OpenAI-compatible local inference server, then configure it as sdk: openai-compatible (see Providers & Models).

Daemon & connections

Q: Desktop says the daemon token was rejected / to re-pair?

A: The saved device token was revoked, expired (devices live 90 days), or the daemon state was reset. Re-run zlogic daemon --pair on the daemon host and connect again with the new one-time secret — the desktop never retries with a stale secret.

Q: The agent does not see my database connection?

A: Check the connection is Enabled, its environment is not production (production is blocked by design), it lists your workspace under Authorized workspaces, and the card does not show a missing credential.

Privacy

Q: Does @zlogic.run collect usage data?

A: Nothing beyond the desktop app's single anonymous install receipt per launch (random install ID + version + OS, used to count installations — see the privacy & credits page). No telemetry, no analytics, no cookies; the CLI sends nothing.

Q: Where are API keys stored?

A: In your OS keyring (macOS Keychain / Windows Credential Manager / Linux Secret Service), or read from environment variables at runtime. See Key Management.

Q: Can reasoning content leak to the next provider?

A: No. Reasoning is rendered as a local thinking block and is never fed into the next LLM context.

Other

Q: Is @zlogic.run open source?

A: The CLI and the agent runtime are: Apache-2.0 in the zlogic repository, complete enough to build, run and modify. The desktop app, the remote daemon and the closed-source tool packs are shipped as binaries only, and are built on the crates published there. Third-party open-source libraries the product builds on keep their own licenses.

Local history

Q: Does local history (checkpoints) touch my git?

A: No. Snapshots are stored in a shadow object store under the local data directory. Your commits, working tree and .gitignore are never modified.

Q: Why is undo / rollback unavailable?

A: Local history was probably disabled in Settings (or the initial snapshot exceeded the size budget). Turn it on in Settings → Local history; it must be enabled for "what did this turn change" and rollback to work.