build
edits need yes
Clarifies with ask_user when the tree can’t settle a choice. Shell and every file edit need a yes.
Built for understanding what you are building.
Anti vibe-coding approach.
Demo transcript summary: Zeta explores a repository, asks clarifying questions, then implements a small CLI flag with a test. Playback is decorative; install and run zeta locally for the real agent.
Press shifttabto cycle build → plan → ask without leaving the prompt.
edits need yes
Clarifies with ask_user when the tree can’t settle a choice. Shell and every file edit need a yes.
no writes
Search and explain only. No edits, no shell. Switch to Build to apply changes.
approve → build
Explores the tree, then emits a plan. Approve picks a build model and starts implementing.
Shell and file writes ask first. Bash can be allowed for the session; every edit still needs a yes.
All models via BYOK or OAuth - bring your own keys and providers. Configure in /config; switch with /model.
Chat history stays under ~/.zeta. Resume anytime, auto-compact when the window fills.
Bundled playbook for a strict code-quality pass on the current branch - structure first, nits later.
send message
cycle build → plan → ask
insert newline
cancel turn (or quit when idle)
prompt history
scroll transcript
command autocomplete
manage providers & models
switch model
open a previous session
summarize older context
strict review of the current branch
start a new session