Work in the actual project.
Search files, inspect code, make edits and run focused checks from a streaming terminal session. Steer it as it works, or use zana run in a script.
A terminal coding agent · pre-1.0
Code.
Remember.
Keep going.
Work through your codebase with an agent that reads, edits and runs checks. Keep useful context in local memory, then pick up the next session with more to go on.
Created by Ordis Hysa
A place to pick up the thread 
zanaA request you could try
“Find the cause of the failing test. Explain the change and run the relevant checks.”
- Read the relevant code
- Make a focused change
- Run project checks
Give it a task. Steer the conversation as the work develops.
zana --resume lastA request you could try
“Where did we leave off? Check the project memory before proposing the next step.”
- Resume the conversation
- Search local memory
- Inspect the evidence
Resume a session, or bring useful history into memory with /import.
zana agents list --jsonA request you could try
“Create a scheduled worker to review this project. Limit it to the read-only tools it needs.”
- Set a recurring task
- Choose the tool policy
- Inspect the run history
The daemon runs scheduled workers while its machine stays available.
Your project. Your model. Context you can inspect.
01 / Get started Meet you in
Meet you in
the terminal.
Install Zana, open your project, choose a provider.
First run guidecurl -fsSL https://zanaagent.app/install | shRequires curl + bash. The installer provisions Bun when needed.
Installs for your user, adds Zana to PATH and starts its background daemon. What to know before you start ↓
AnthropicOpenAICodexGitHub CopilotDeepSeekOpenRouterOllama
Use a supported API key or account, or a local Ollama model. Provider access and usage are separate from Zana.
02 / Beyond a single chatStay with the work.
Stay with the work.
Keep the context.
For developers moving between repositories, long-running tasks and the decisions that are easy to lose along the way.
Give the next session a start.
Keep durable memory as local, readable files. Search what it remembers and import useful history from tools such as Claude Code and Codex.
Memory with sourcesMake room for recurring work.
Create scheduled workers with their own model and tool policy. The daemon can run them while the terminal UI is closed, on a machine that stays available.
Background workersDesigned to be understoodTools with contracts.
Tools with contracts.
Controls with a purpose.
Extend the agent around the way you work, and choose what it can do.
Make your own tools
Toolpacks add typed tools without changing the core. Tools declare their side effects so the runtime can apply capability policies.
Set the scope of delegated work
Delegated agents and scheduled workers have their own tool policies. Optional Git worktrees separate delegated edits; their diffs are never automatically merged.
Choose read-only when you need it
The interactive agent has full access by default. Read-only mode blocks writes, shell execution and external actions according to tool contracts. Read-only web search and fetch can remain available.
03 / Your first session
Start with a real question.
No Zana account is needed for the standalone CLI. You will need access to the model provider you choose.
- 1
Open a new terminal
Check your environment and see which providers are ready.
zana doctor zana init - 2
Enter your project
Launch an interactive session from the repository you want to work on.
cd your-project zana - 3
Give it a useful starting point
Ask for an explanation, a focused change or a review of the code in front of you.
“Explain how this project is structured and where its tests live.”
Inside the terminal
/help- Discover commands
/model- Choose a model
/memory- Inspect memory
/import- Bring in past context
A few useful details
Before you begin.
Zana is an early-stage project. Interfaces and behavior may change as it develops.
What does “local” mean here?
Sessions, configuration and memory live on your machine under ~/.zana-agent/. When you use a remote model, prompts and relevant context are sent to that provider. You can choose Ollama for a local model.
What does the installer set up?
It downloads the published Zana bundle, provisions Bun if needed, updates your user PATH and starts the daemon. No administrator account is required. Open “Read the installer” above to inspect the script and its options before running it.
What should I know about Windows?
Use the PowerShell installer and run zana doctor first. Windows support has limitations: automatic daemon startup at login is not installed, terminal images fall back to text, and shell and permission behavior differ. Persistent execution is restricted where required permission guarantees are unavailable. Update by rerunning the PowerShell installer.
Where can I find documentation?
The first-run guide on this page covers installation and launch. Use zana --help and /help for the installed version.
Two products, a connected workflowZana runs the agent.
Explore ocode Zana runs the agent.
ocode brings the workspace together.
Zana works on its own in your terminal. ocode uses Zana to connect project work, supervise agent activity and work across cloud workspaces and connected devices.
Both created by Ordis Hysa.