> ## 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.

# Drive

> Your workspace - apps, connected repositories, files, folders, and mounts in one view.

Drive is where everything in your space lives. If it's in Drive, the AI can access it. If it's not, it can't.

## What shows up in Drive

| Item                 | What it is                                                    |
| -------------------- | ------------------------------------------------------------- |
| App                  | An application the AI built - has its own repo and hosting    |
| Connected repository | A git repository connected to your space (a git-backed mount) |
| Folder               | A standard folder for organizing things                       |
| Files                | Cloud file storage for uploads and standalone files           |
| Mount                | A link to a filesystem outside the space                      |

## Mounts - giving the AI access to your files

By default, the AI works inside the space's cloud computer. If you want it to access files on your machine or elsewhere, you add a mount.

A mount is a pointer to a filesystem. Once mounted, the AI can read and write files there as if they were local.

**Local folders** - mount a folder from your computer. The AI can browse, read, and edit files in it.

**Connected repositories** - connect a git repository and it's cloned onto your cloud computer or connected device, appearing as its own row in Drive.

**Remote filesystems** - SSH-based mounts for accessing remote servers (coming soon).

## Cloud file storage

Files uploaded to Drive (not inside an app or repo) live in the **Files** storage container. They're accessible from any device and persist across sessions.

## Git tracking

Drive tracks git state for connected repositories automatically - current branch, recent commits, uncommitted changes, how far ahead of remote. Apps use a separate keep/publish workflow. Credentials are managed through the [vault](/work/vault), so the AI can push and pull without setup.
