Cetas
A coding agent for your terminal, your editor, and your scripts — usable without coding experience; all records and settings stay on your own machine.
One agent, every surface. The terminal, your editor, and a scripted one-shot all compose the same core and the same durable state — so configuration you set once is there wherever you enter.
Start here
- New to coding agents — Reach your first message without writing code: what to prepare, and what every term means.
- Switching from another agent — Four structural differences; when switching is worth it, and when not yet.
- Three surfaces, one core — How the terminal, the editor, and automation compose one agent — and where each ends.
npm install -g @posoco/cetasThe recommended JS terminal requires Node.js 24+. For a terminal without Node.js, choose Native; see installation options. Agents can start from /llms.txt.
New to npm or Node.js? Read the glossary first.
Why Cetas
- Work you can trace. Tickets, dependencies, and a review gate on a local board; what you review is the diff and the test evidence, and your agent can look the provenance up itself.
- The reviewer cannot touch the code. A subagent's tools and permission posture live in its definition file. Research comes back as summaries, never as context debt.
- Middle steps never enter your window. Loops and filters run in a Wasm-sandboxed program; only the result returns to the conversation. Content that was never generated never cost anything.
- Humans and agents read the same docs. Site-wide llms.txt and a .md source for every page — another agent can read it all for you before you install.