FAQ

Code vs Office

Code Office
Goal Engineering in a repo/workspace DOCX/XLSX/PPTX deliverables
Shell Yes (when enabled) No
Terminal Yes No
Browser Yes (desktop) Usually unused
Typical output Edited source Files under deliverables/

Switch task type before starting a new session. See Task types, Code mode, and Office overview.

Agent says browser_host_missing

The built-in browser exists only on Windows desktop. Open sidebar Browser (or Ctrl+Shift+B) before browser_* tools. TUI/CLI have no host. See Built-in Browser.

Night queue vs scheduled tasks?

See Night queue and Scheduled tasks.

What is Agent health?

Sidebar Agent health is a read-only local tool/harness telemetry report — same source as zagens doctor --tools. See Agent health.

Runtime not connected / docs API 500

The website docs API needs frontend and backend. From the zagens_website repo root, run npm run dev. Frontend-only fails.

In the desktop app, check sidebar connection — the runtime sidecar must be on localhost.

SmartScreen and unsigned installers {#smartscreen}

Builds are not Authenticode-signed yet. Tip: download the zip → Properties → Unblock → extract and install.

See SmartScreen install help.

Windows sandbox (v0.7.4+)

Can the agent access the whole PC?
On Windows, exec_shell can run under an OS sandbox (restricted token + ACL + WFP). Prefer the sidebar Sandbox wizard in Elevated mode with workspace-write and tool approval. See Windows sandbox.

Elevated vs Unelevated?
Elevated needs a one-time UAC setup (off-workspace write protection, profile read isolation, WFP egress). Unelevated needs no admin — workspace write isolation only; cannot isolate profile reads like .ssh.

Same sandbox on Linux?
Linux is currently degraded. macOS uses Seatbelt.

CLI vs desktop

Windows-only desktop? Use zagens-tui and/or headless zagens on macOS/Linux — all share Kernel V3 and ~/.zagens/config.toml. See Terminal TUI, Headless CLI, and Install.

Updates

In-app updates read CDN latest.json. See In-app updates and the download page. These docs target product line v0.8.9.

Where is my API key stored?

Keys stay on your machine. Zagens defaults to ~/.zagens/config.toml; migrations from deepseek-tui may still read ~/.deepseek/config.toml. Multi-provider setup: Settings → Models. See Privacy summary and the Privacy policy.

Workspace & deliverables

Support

Email didclawapp@gmail.com.