Zuse

Core concepts

Understand how Zuse organizes repositories, chats, sessions, and isolated environments.

Zuse separates the durable unit of work from the agent process doing the work. That distinction makes it possible to change agents, keep parallel tasks isolated, and reconnect without losing the useful history.

The model

Computer
└── Project (repository or folder)
    └── Chat (one durable task and one environment)
        ├── Session tab (provider conversation)
        ├── Session tab
        └── Files, terminal, changes, and PR state
  • A computer runs the Zuse service and owns its local projects and data.
  • A project points to a repository or directory.
  • A chat is the durable task shown in the sidebar.
  • A session is one agent conversation inside a chat, with its own provider and model.
  • An environment is the main checkout or the chat's Git worktree.

See Projects, chats, and sessions for lifecycle details and Local-first data for persistence and security boundaries.

On this page