Skip to main content

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.

A computer is a machine that runs your code. Every space has at least one, and the AI uses them for shell commands, file operations, terminal sessions, and browser automation.

​
Computer types

TypeCapabilitiesUse for
Cloud machineShell, terminal, filesCoding, scripts, builds, app dev. Files survive stop and wake.
Cloud browserBrowserScraping, automation, signed-out browsing
Your deviceDesktop, terminal, browser (when online)Your computer running Kazzle. Built-in browser plus extension support.
ProductionStart, stop, and logs onlyYour 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. It boots the computer.
  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 enforced by the system:
  • Database clients (psql, pg) are never installed. The AI uses the database tool instead.
  • File paths are scoped to the workspace.
  • Destructive patterns are caught by 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.