Ecosystem

What Zeta itself brings.

Zeta delivers its own product capabilities on top of the OMP runtime, while publicly stating each upstream source's role. This page lists Zeta's own capabilities first, then the four source projects and credits.

Zeta's own capabilities

On top of the shared runtime, these are developed and maintained by Zeta.

The zeta workspace

Nested-terminal workbench: tabs, a pane tree, page stacks, widget panes, suite self-install and doctor; one unified entry to the whole suite.

Project tracking /tracking

Milestones and key decisions written to .zeta/tracking/, kept across sessions with compaction summaries persisted; off by default, explicitly enabled.

Web workbench & desktop

43 light/dark themes, a trace view, the right-side dock, and the desktop trust-open bridge; one persistent session shared with the CLI.

Experiment measurement

Per-project local experiment tracking: metrics, directions, and baseline commits, stored in SQLite.

TS custom commands & marketplace

arktype / typebox / zod argument validation; commands install, share, and reuse as Bun packages.

IM channels & workspaces

WeChat / Feishu / Telegram bots, workspace aliases and relayed delegation, sessions synced with CLI / desktop.

Remote access security

The gateway binds loopback only; remote.token auth, with CSRF and clickjacking protections.

Local stats dashboard

zetacode stats local observability: sessions, usage, and cost.

Reference projects

The four sources Zeta builds upon.

Oh My Pi Mainline

Runtime, CLI, local tools, and sessions — Zeta's direct upstream. The runtime tree, package layout, and Bun workflow follow OMP conventions so upstream updates stay mergeable.

→

Pi Advanced

Semantic-port source for modern agent behavior: context engineering, extension primitives, provider correctness. Brought in as verifiable semantic ports, never wholesale merges.

→

OMP Web Snapshot

Direct upstream of the standalone web-ui/ snapshot: agent.db, model handling, session SSE, the Windows picker.

→

Pi Web UX source

Semantic-port source for web product and UX: host allowlists, DNS-rebinding protection, CSP, project trust.

→

TTT Editor vendored

Upstream of the terminal editor: Go source and prebuilt binaries vendored wholesale into editor/ (ledger in editor/VENDOR.md); branding, theme, and mouse interaction are maintained by Zeta.

→

TermIDE vendored

Upstream of the terminal IDE: a Rust snapshot vendored into termide/ (termide/VENDOR.md); Zeta maintains the npm surface and branding, and the workbench pane tree builds on its crates.

→

Research references

Studied for semantics only — never merged into the runtime.

DeepSeek Reasonix

Cache behavior research: system-prompt stability, cache diagnostics, cache-aware compaction.

OpenCode

Model metadata, protocol semantics, and cache-handling boundaries — research reference only.

OpenTUI

TUI design and interaction patterns: layout references, key routing, component design.

Credits

Without these projects and maintainers, there is no Zeta.

can1357

Author and maintainer of Oh My Pi — Zeta's runtime and mainline upstream.

mariozechner / earendil-works

Author and maintainer of Pi — the source of Zeta's advanced agent behaviors.

17380936778

Maintainer of the OMP Web snapshot — from which Zeta's web-ui/ was seeded.

agegr

Author of Pi Web — the source of Zeta's web security and reliability patterns.

The distribution promise

Zeta is a downstream distribution of OMP: the runtime tree, package layout, Bun workflow, and internal @linxiraos/* package names follow OMP conventions so upstream updates stay mergeable.

linxira-zeta

The product repository: tracking and integrating OMP upstream; docs and releases live here.

→

Linxira-OS org

The organization home: the distribution and its infrastructure.

→