> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kazzle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Computers and terminals

> Cloud machines, your local device, and shared terminal sessions.

A computer is a machine that runs your code. A space can have a cloud machine (created on demand, one per space), a cloud browser, and your own device when the Kazzle app is installed. The AI uses them for shell commands, file operations, terminal sessions, and browser automation.

## Computer types

| Type          | Capabilities                             | Use for                                                                |
| ------------- | ---------------------------------------- | ---------------------------------------------------------------------- |
| Cloud machine | Shell, terminal, files                   | Coding, scripts, builds, app dev. Files survive stop and wake.         |
| Cloud browser | Browser                                  | Scraping, automation, signed-out browsing                              |
| Your device   | Desktop, terminal, browser (when online) | Your computer running Kazzle. Built-in browser plus extension support. |
| Production    | Start, stop, and logs only               | Your deployed app. No shell, files, or browser access.                 |

## Cloud machine persistence

Cloud machine files persist across normal stop and wake cycles. Files, installed packages, and tools remain intact. A cloud machine is a persistent development environment, not a throwaway container.

## Lifecycle

1. **Check existing computers.** The AI sees available computers up front.
2. **Create if needed.** The AI creates a cloud machine or cloud browser on demand.
3. **Wake if offline.** Cloud machines can be woken and stopped; cloud browsers and your device are started differently.
4. **Ready.** Once awake, all tools are available.

## Shell commands

The AI runs shell commands for builds, installs, git operations, and scripts. Commands run on the cloud machine's persistent filesystem.

Rules:

* The AI prefers the database tool over shell database clients.
* App and repo file operations are scoped to their workspace.
* Destructive patterns are caught by [tool policies](/security/tool-policies).

## Terminals

Terminals are persistent shell sessions shared between you and the AI. The AI creates them for long-running processes (dev servers, builds, watchers). You can also open them manually.

Both sides see the same terminal in real time:

* The AI runs `npm install`. You see the output.
* You type a command. The AI can read the output.
* The AI starts a dev server. You can interact with it.

When the AI starts an app, the dev server runs in a terminal. You can read its output to check for errors, and the AI watches it to detect build failures.

## Filesystem

For app and repo files, the AI uses scoped file operations that can't escape the workspace root. For raw filesystem access, it uses shell commands.