Zagens

中文 · 日本語 · Português (BR) | English

Long-horizon agent work tends to stall or “claim done” too early. Code and office files often live in separate tools. Local agents need replay, approval, and auditability — not just another chat window.

Zagens is a desktop agent harness built for the DeepSeek V4 ecosystem: tuned for DeepSeek API, reasoning streams, and tool calling out of the box (DeepSeek Pro / Flash by default). One local runtime sidecar for Code and Office workspaces, turn-by-turn session replay, layered completion gates for long tasks, and desktop-native shell (tray, notifications, embedded terminal). Other OpenAI-compatible endpoints remain supported as a fallback.

From the authors: Don’t believe an AI agent can do anything — it has boundaries. What we can do is expand those boundaries.

License: MIT. Runtime lineage: NOTICE.md · third-party/deepseek-tui/. Capabilities below reflect Zagens v0.7.4 — see CHANGELOG.md.

Who Zagens is for

Three things that define Zagens

1. Harness, not a chat shell — Long-horizon code tasks use composable completion gates (operator / model / toolchain layers), not “the model said it’s finished.” Spec: LHT · fixtures: fixtures/harness/.

2. Desktop-native control plane — Tauri 2 UI over a loopback sidecar (zagens-runtime): system tray, notifications, diff panel, session replay, embedded PTY in Code workspaces, HTTP tool approval. Same engine as the headless zagens CLI.

3. Code + Office, one runtime — Code and Office task types share tools and config but use different tool surfaces and prompts; switching types starts a new session for stable model KV (architecture). Office: read_file / write_office (xlsx via Rust; docx/pptx/pdf via bundled Python).

Also shipped: CRAFT multi-agent (sub-agents, fix-loop verdicts, P1 blackboard — notes), lazy symbol index (.zagens/symbols.json), MCP, skills, hooks, scheduled tasks.

Problems we focus on

Shipped today (v0.7.4)

Desktop: multi-session chat (stream/stop/thinking), file tree + previews + diff, PTY terminal (Code), sub-agent panel, tasks/skills UI, MCP + routing rules, usage charts, keyring API key, UI in zh-Hans / en / ja / pt-BR.

Runtime: threads, MCP, skills (~/.zagens/skills), lifecycle hooks, multi-provider routing, vision (describe_image).

Tools (representative): files (read_file, write_file, edit_file, …), git, exec_shell, write_office, optional web_search / fetch_url, memory tools. Full list: crates/runtime-server/src/tools/ · CHANGELOG.md.

Known limits (read before you rely on us)

We prefer honest scope over marketing checklists.

Report security issues via SECURITY.md.

Where we’re headed

Public design specs live under docs/. Directionally:

• Platform parity — macOS/Linux desktop installers; Linux native sandbox (Landlock/bwrap). Windows native sandbox shipped in 0.7.x.
• Trustworthy long tasks — tighter completion gates, harness fixtures, and replay-friendly operator workflows.
• Office workflows — richer scenario coverage without splitting away from the shared runtime.
• Hardening — security and exec-policy improvements tracked in CHANGELOG and SECURITY.md.

Quick start

Pre-built (Windows): GitHub Releases zagens-v0.7.3 — installer zip + CLI. Unblock SmartScreen: SMARTSCREEN.md.

From source:

git clone https://github.com/didclawapp-ai/zagens.git
cd zagens

cargo build -p zagens-cli          # sidecar copied into crates/desktop/binaries/

cd crates/desktop/web-ui && npm install
cd .. && cargo tauri dev

# API key: Zagens Settings, or ~/.zagens/config.toml

Headless CLI (same runtime as desktop):

cargo install zagens-cli --version 0.7.3 --bin zagens --locked

zagens doctor
zagens exec 'summarize src/' --json
zagens exec 'refactor auth module' --auto
zagens serve --http --port 7878

Prebuilt CLI + SHA-256 sidecars: Releases. Config reference: config.example.toml.

Architecture

┌──────────────────────────────────────────────────────────────┐
│                     Zagens (Tauri 2)                         │
│  ┌─────────────────┐  ┌───────────────────────────────────┐  │
│  │   WebView UI    │  │         Rust Shell                │  │
│  │   React / TS    │◄─┤  commands, sidecar supervisor,    │  │
│  └────────┬────────┘  └───────────────┬───────────────────┘  │
│           │ HTTP + SSE                │                       │
│           ▼                           ▼                       │
│  ┌─────────────────────────────────────────────────────────┐  │
│  │     Runtime API (embedded sidecar, loopback HTTP/SSE)    │  │
│  │  /v1/threads, /v1/skills, /v1/symbol-index, ...         │  │
│  └───────────────────────┬─────────────────────────────────┘  │
│                          ▼                                    │
│  ┌─────────────────────────────────────────────────────────┐  │
│  │  Shared crates: agent, core, config, state, tools, mcp   │  │
│  └─────────────────────────────────────────────────────────┘  │
└──────────────────────────────────────────────────────────────┘

Full boundaries: docs/tech/RUNTIME_ARCHITECTURE.md · HTTP contract: docs/tech/API_DESIGN.md.

Security modes (sandbox_mode)

Approval policies (on-request / untrusted / never), per-domain network rules, OS keyring for credentials. Runtime token never enters the WebView.

Development

Prerequisites: Rust 1.88+ (MSRV; CI pins 1.96), Node.js 20 LTS, Python 3.8+, Tauri CLI 2.

See CONTRIBUTING.md and LOCAL_DEV_VERIFY.md.

Windows: pwsh -File scripts/ci/verify-lint.ps1

zagens/
├── crates/desktop/       # Tauri app
├── crates/runtime-server/ # Sidecar HTTP/SSE
├── docs/                 # Public design specs
├── fixtures/harness/     # LHT / Office harness fixtures
└── config.example.toml

License

MIT — Copyright (c) 2024-2026 Zagens Contributors. Additional attribution: NOTICE.md · third-party/deepseek-tui/LICENSE.