Skip to content
Zana Cloud
Sign inRequest access

The workspace for Zana Agent

Agent work.
Under your
control.

Run Zana sessions in cloud workspaces or on paired devices. Choose your providers, follow the activity, and turn a conversation into an agent you can review.

Request access Explore the workflow

Private preview Created by Ordis Hysa

01 / A place to workWorkflow overview

The workspace comes first.

Choose where Zana works. Keep the session in view from Zana Cloud.

Your machine. Your working folder.

Pair a device, share a folder, and select it when starting a session.

Workspace
A folder you share
Provider & model
Your configured connection
Then, start with a concrete request

“Map this repository. Explain the entry points and test commands before changing anything.”

You choose the context. Zana does the work.
One workflow, from context to review
  1. Choose a workspace
  2. Start a session
  3. Follow the work

The working loop

A clear brief.
A visible process.

For developers and teams who want to work with agents in the context of their own projects.

  1. 01

    Give the session context

    Pick a workspace, provider, and model. Ask for an investigation, a code change, or a plan.

  2. 02

    Stay with the work

    Follow messages and tool activity as the session runs. Send a follow-up when the brief changes.

  3. 03

    Make repeat work explicit

    Ask for an agent proposal. Review its instructions, workspace, schedule, and permissions before creating it.

01 / Connected workspaces

The right machine.
The right context.

A repository on your laptop. A working folder on a server. Connect the device and choose which folders to make available in Zana Cloud.

Meet the Zana runtime
From Settings → Devices
  1. 1

    Generate a pairing command

    Sign in to Zana Cloud and create a one-use pairing code. It expires after ten minutes.

  2. 2

    Run it on your device

    The macOS / Linux setup command installs Zana, pairs the device, and registers its background service.

  3. 3

    Choose a shared folder

    Start a session against that workspace. Keep the device online while it works.

Pairing commands are generated for your account. No credentials or install tokens are included in this preview.

02 / From conversation to agent

Describe the job.
Review the remit.

Start with a request in a session. Zana can draft an agent with a mission and a schedule; the proposal waits for you to review and create it.

These examples show how to write a useful brief. Each needs a configured workspace, provider, and access to the relevant files.

A proposal does not start a background agent. You decide when to create it.

Illustrative proposal — no agent is running.

Your instruction

“Map this repository’s entry points, explain how the main modules fit together, and point me to the tests. Read only; don’t change files or run commands.”

Proposed agent · awaiting your review

Find your way into a codebase.

A proposal for repository orientation, with references back to the files it reads.

Workspace
A repository folder you select
Requested output
An entry-point map and a guide to the existing tests
Review permissions and schedule
Access to review
Read-only file access. No shell commands, file edits, commits, or pushes.
When it would run
Manual run. No recurring schedule is proposed.

Before you create it: Choose an accessible repository folder in a cloud workspace or on a paired device, then select an available provider and model.

03 / Provider connections

Your choice of model.
One place to configure it.

Manage provider connections in Zana Cloud and assign access to paired devices. Choose the provider and model for each session.

Bring a supported provider connection. Model availability depends on that connection.

04 / Persistent memory

Keep useful context.
Keep its source, too.

Zana can save and search project knowledge beyond a single conversation. Inspect remembered information and its sources when you need the context behind an answer.

Memory belongs to the runtime and its user or project scope. Pairing does not merge cloud and device memory.

Two products. A shared foundation.

Zana does the work.
Zana Cloud brings it into view.

Both created by Ordis Hysa.
Start in the terminal or bring your workspaces together in the browser.

Zana Agent

The agent harness for your terminal: tools, sessions, memory, and background work.

Explore Zana Agent Zana Cloud

The web workspace for Zana: cloud and device sessions, provider connections, and agent proposals.

Request preview access

Before you start

Can I use Zana without Zana Cloud?

Yes. Zana Agent can run independently from the terminal. Zana Cloud adds a web interface for cloud workspaces, paired devices, and agent sessions.

What do I need to use Zana Cloud?

Access to the private preview, a configured provider connection, and a cloud workspace or paired device. Request access first; existing users can sign in.

How does device access work?

Choose the working folders exposed in Zana Cloud and review each agent’s tool permissions. The run also has the permissions of its device account; selecting a workspace is not an operating-system sandbox.

Private preview

Bring your next project.
Give it a workspace.

Request access to Zana Cloud. Already approved? Sign in to continue.

Request access Sign in