Cetas has three usage surfaces — terminal, editor, and automation — with two terminal implementations. Cetas JS from npm is the default recommendation; Cetas Native is an optional Go/Bubble Tea terminal over the same MoonBit Cetas/Posoco core.
| Host | Interface | Install / distribution |
|---|---|---|
Terminal · JS (recommended) cetas-js |
Full interactive terminal, JS-only integrations including Board | npm install -g @posoco/cetas |
Terminal · Native (alternative) cetas-native |
Go/Bubble Tea v2 terminal, separate host capabilities | Homebrew (macOS/Linux), Scoop (Windows), or Cetas Release |
Editor · ACP cetas-acp |
ACP server via stdio; usable with Lody and Zed | Separate cetas-acp-* Release asset |
Automation · Run cetas-run |
One task per process | Separate cetas-run-* Release asset |
What is shared
The hosts compose the same core and generally reuse provider settings, credentials and session storage under Cetas home. This does not imply UI parity or portable conversations between hosts.
What differs
- JS is the primary feature-rich TUI, with Pi/Node/Bun integrations and Board workflows not available in Native.
- Native uses a Go terminal and a MoonBit runtime (Unix static bridge, Windows adjacent DLL), and can run without Node.js.
- ACP is a standalone editor integration; clients own presentation and approval UI. You can download it without installing Native.
- Run produces stdout/stderr-friendly one-shot results, and can also be downloaded independently.
- JS and Native may both expose a command named
cetas; the first match onPATHwins.
Cross-host conversation resume is not a supported contract. See Installation for exact platform options.