Coding agent

ZCode

Desktop agent workspace with durable goals, parallel subagents, and scheduled tasks.

Status
Active
License
Proprietary
Evidence
Documented, 17 sources
Product record checked
2026-08-02

At a glance

A proprietary desktop agent environment with persistent goal state, independent completion checks, parallel and background subagents, scheduled tasks, scoped approvals, MCP, hooks, remote workspaces, and an integrated browser and review flow.

Good choice if

  • Developers who prefer a visual agent workspace over a terminal-only loop
  • Long-running goals that need explicit lifecycle state, repeated verification, and recovery
  • Scheduled or parallel desktop work combining subagents, MCP, hooks, browser context, and remote environments

Check before choosing

  • No documented headless CLI, CI entry point, or public API was found; scheduled automation still belongs to the desktop product
  • Docker isolation requires an already-running user-provided container, while local and SSH workspaces otherwise execute with the target account's privileges
  • Undo is documented for surfaced file changes, not arbitrary command, network, database, or system side effects
See 2 more considerations
  • Goal verification and trajectory auditing are vendor-described mechanisms, not independent proof of task success
  • Custom self-hosted compatible endpoints are supported, but the reviewed docs do not establish a packaged local-model runtime

Capability support

Documented first-class product support, checked against the sources below.

External tools (MCP)
DocumentedProduct-supported MCP integrationSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Reusable skills
DocumentedProduct-supported reusable skill packagesSource · checked 2026-07-27Support does not establish portability, package quality, safety, or adoption.
Local models
Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.
Agent parallelism
DocumentedDelegated or parallel agent workflowSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Runs without an open UI
Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.
Browser control
DocumentedBuilt-in or product-supported browser controlSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Isolated execution
DocumentedDocumented execution-isolation mechanismSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Undo file changes
DocumentedProduct-supported file or session rollbackSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.

Getting started

Install ZCode 3.5.3, connect a Z.ai plan or compatible API provider, open a local, SSH, or existing Docker workspace, then choose the permission mode before starting tasks or schedules.

Open official documentation

Classification and operating model

Category fit and technical mechanisms are evidence records, not product-quality scores.

Category fit
Qualifies, 4/4 criteria
Operating model
7/7 layers documented
Inspect category criteria and operating mechanismsFirst-party records

Why it qualifies as a coding harness

This confirms category fit, not product quality. Every required criterion links back to first-party evidence.

Qualifies4 of 4 required criteria evidenced
  • Adaptive agent loop

    Documented

    The system repeatedly observes results and chooses the next action instead of following a fixed one-pass graph.

  • Repository tool execution

    Documented

    The system can use tools to inspect and change a repository or its execution environment.

  • Task-aware context management

    Documented

    The runtime assembles, updates, compacts, retrieves, or persists task-relevant context while work proceeds.

  • Model-independent runtime control

    Documented

    Permissions, budgets, interruption, policy, or stop controls operate outside the model's own text generation.

Membership establishes category fit only. It does not score quality, safety, autonomy, model capability, or benchmark performance. · Read the membership rule.

How it works under the hood

Seven mechanisms mapped from first-party records. These labels describe what the harness provides, not how intelligent its model is.

7/7layers documented
  • Execution & isolationManaged isolationDocumented mechanism, not a performance score.
  • Tooling & integrationsExtensible + browserDocumented mechanism, not a performance score.
  • Context & stateManaged contextDocumented mechanism, not a performance score.
  • Lifecycle & recoveryManaged recoveryDocumented mechanism, not a performance score.
  • ObservabilityStructured tracesDocumented mechanism, not a performance score.
  • VerificationWorkflow-gatedDocumented mechanism, not a performance score.
  • Governance & permissionsPolicy controlsDocumented mechanism, not a performance score.

Measured and public context

Configuration-specific measurements and source-native activity stay separate from general product capability.

Inspect code audit, measured configurations, and ecosystem signalsContext, not a product score

Public code audit

No official public repository was located for a code-level audit.

Measured configurations

No benchmark run passes the full metadata admission policy for this harness yet. Missing data is not scored as zero.

Benchmark policy and all runs

First-party evidence

Each capability claim links to the first-party record that supports it.

17 first-party sourcesProduct record checked

Additional first-party sources

17 sources
View 16 more sources

Ecosystem context

OpenRouter apps Discovery signal only; usage rank is not used as a quality or capability score. Observed 2026-07-27.