Features

Everything it should have.
Nothing it shouldn't.

Core capabilities are built-in defaults; the workbench and project tracking are Zeta's signature. Extensions cover the rest — build it yourself, or install something ready-made.

The workbench

The zeta workspace: a terminal multiplexer with opinions.

Pane-tree layout

Split panes freely; a weighted tree keeps proportions exact. zeta code / editor / ide reaches every tool.

Page stacks

Each pane holds a stack of pages: switching pages never kills the PTY — background work keeps running.

Widget panes

Clock + calendar, 🍅 pomodoro, 📋 clipboard history — native panes, all clickable.

Self-install & doctor

Missing tools install themselves inside the workbench; zeta doctor reports item by item.

Core capabilities

zetacode built-in defaults, not optional extensions.

Project tracking

A long-term tracking system independent of memory: enable with /tracking (off by default); the agent writes to .zeta/tracking/ at milestones and key decisions — kept across sessions, with compaction summaries persisted, browsable in desktop and Web UI.

Subagents

Split tasks across parallel subagents, each with its own context and toolset; the main session collects results.

Plan mode

Plan first, execute second: the agent produces a plan for review before touching the workspace.

LSP language services

A built-in LSP client: go to definition, find references, diagnostics, completions — semantic awareness while editing.

DAP debugging

Speaks the Debug Adapter Protocol: set breakpoints, read stack frames, inspect variables, explain failures.

Hindsight memory

Reviews past sessions' successes and failures, reusing accumulated lessons in later tasks.

Hashline editing

Line-precise, content-addressed edit semantics: refactors and bulk replaces stay traceable.

Time-travel rules

Project rules on a timeline: conventions from old commits never leak onto new code.

Native Rust engine

Text, regex, grep, and diff heavy lifting goes to Rust primitives — large files and repos don't drag.

Zh/En interface

/language zh switches the CLI and command descriptions instantly; the choice persists.

Desktop default workspace

The desktop app ships a global default workspace (~/.zeta/workspace) — usable before you pick a directory.

Clear config paths

Project-level .zeta/ and user-level ~/.zeta/ — config, memory, tracking, and logs each in their place.

Context engineering

Control what enters the context window and how — don't leave it to the model to guess.

AGENTS.md

Project instructions: loaded at startup from ~/.zeta/agent/, parent directories, and the current directory.

SYSTEM.md

Replace or extend the default system prompt per project — a personality and constraints for every repo.

Skills

Load-on-demand capability packs: instructions plus tools, progressively disclosed without breaking prompt caches.

Prompt templates

Reusable Markdown prompts, expanded with /name.

Auto-compaction

Near the context limit, old messages are summarized automatically; the strategy is fully extensible.

Dynamic context

Extensions can inject messages per turn, filter history, implement RAG or long-term memory.

Sessions are trees, not logs

Resume from any historical node; branches and the trunk live in one file.

Branching history

Sessions are stored as trees; rewind to any earlier node and continue from there.

Export & share

/export writes HTML; /share uploads a link anyone can open.

Encrypted collab

/collab starts an end-to-end encrypted live session — every participant renders the same session and tool cards.

Pick up where you left off

After a restart, --continue returns to the original session with its full reasoning trail.

Web workbench & desktop

One persistent session, three entries: terminal, browser, desktop app.

One session, everywhere

Desktop, browser, and CLI read and write the same persistent session — tasks started in the terminal continue on the desktop.

Tracking panels

Project tracking docs are browsable in the UI: milestones, decisions, and progress at a glance.

Trace view

Step through thinking and tool calls with timing and token counts; raw records expand for inspection.

The right-side dock

Session / files / tracking / plugins panes as a permanent rail; messages list the files they touched.

43 themes

Full light/dark presets (background, panels, syntax, 8-color chart palettes), pre-hydrated so the first paint never flashes.

Safe remote access

zetacode serve binds loopback only; remote access requires remote.token, with CSRF and clickjacking protections.

Four run modes

One agent, many interfaces.

Interactive

The full TUI: panels, previews, tool cards.

Print / JSON

zetacode -p "query" prints and exits; --mode json streams events for scripts.

RPC

A JSON protocol over stdin/stdout for non-Node integrations.

SDK

Embed the agent as a library and own its whole lifecycle.

Chat-platform bots

Use zetacode directly in WeChat, Feishu, and Telegram. One bot interface; more platforms keep landing.

WeChat bot

Hook zetacode into WeChat: a conversation is a question, results land back in the chat, and session state stays continuous with CLI / desktop / Web UI.

Feishu bot

Feishu integration: group and direct chats can summon the agent, with cards and rich text reporting progress live.

Telegram bot

First-class Telegram support: private chats, groups, and inline mode — coding tasks from anywhere.

One bot interface

A single adapter layer covers every platform: messages, commands, and result streams share one protocol — a new platform is one adapter away.

Primitives, not features

Features other agents ship built-in, you can build yourself. Extensions are TypeScript modules with access to tools, commands, shortcuts, events, and the full TUI.

Permission gates

Custom confirmation flows — allow or block sensitive operations per environment and policy.

Path protection

Declare protected paths; agent reads and writes are strictly contained.

MCP integration

Reach MCP servers through extensions, or build CLI tools directly from skills.

Sandboxed execution

Run commands in containers or sandboxes; keep the risk outside the agent.

Extension discovery

skills, hooks, tools, commands, rules, prompts, and .mcp.json are all discoverable from extensions.

50+ examples

Subagents, plan mode, SSH execution, custom editors, status lines, overlays — official examples that run as-is.

Install each tool standalone

Workspace plus three tools, all one npm command away — or install just the workspace and let the rest self-install on demand.

Workspace zeta@linxiraos/main · Rust binaries

npm install -g @linxiraos/main

Coding agent zetacode@linxiraos/zeta · coding CLI

npm install -g @linxiraos/zeta

Editor zeta-editor@linxiraos/editor · TTT

npm install -g @linxiraos/editor

Terminal IDE zeta-ide@linxiraos/ide · TermIDE

npm install -g @linxiraos/ide

On Bun, swap npm i -g for bun add -g. After installing any of them, zeta doctor reports the whole suite and prints the exact fix for what is missing.

Command reference

Every tool launches standalone with its own --help; the workspace is their unified entry.

Workspace (unified entry)

zetaOpen the workbench (= zetawork / zeta work)

zeta code | zeta cHand off to the coding agent (zetacode)

zeta editor | zeta eHand off to the terminal editor (zeta-editor)

zeta ide | zeta iHand off to the terminal IDE (zeta-ide)

zeta doctorSuite install status + exact fixes

zeta --help / --versionWorkspace help and version

Coding agent (zetacode)

zetacodeInteractive TUI (opens in the current directory)

zetacode -p "query"Print mode — output and exit

zetacode --mode jsonEvent-stream output for scripts

zetacode --continueResume the most recent session

zetacode serveWeb workbench gateway (browser/desktop)

zetacode statsLocal stats dashboard

zetacode authProvider sign-in and credentials

zetacode updateSelf-update the CLI

zetacode acpAgent Client Protocol integration

zetacode install / sshInstall surface and remote-execution helpers

Standalone tools

zetaeditor / zeta-eTerminal editor (any terminal, incl. SSH)

zetaide / zeta-iTerminal IDE

zeta-desktopDesktop app (embeds the web workbench)

… --helpEvery command ships its own help

Everything it should have.Nothing it shouldn't.