Overview¶

✅ Implemented 🧪 Tested

Current state: SQLite persistence with Drizzle/Kysely, 32+ migrations, snapshot storage, and Unix socket configuration are all implemented. See the Status Glossary for chip definitions.

AutoMobile persists state across sessions using SQLite for metadata and the filesystem for larger payloads.

flowchart TB
    subgraph Runtime["Runtime Data"]
        NavGraph["🗺️ Navigation Graph"]
        Sessions["📱 Device Sessions"]
        Config["⚙️ Configuration"]
    end

    subgraph Storage["Persistent Storage"]
        SQLite["🗄️ SQLite
~/.auto-mobile/auto-mobile.db"]
        Snapshots["📸 Snapshots
~/.automobile/snapshots/"]
        Migrations["🔄 Migrations
src/db/migrations/"]
    end

    NavGraph --> SQLite
    Sessions --> SQLite
    Config --> SQLite
    SQLite -.->|"schema updates"| Migrations
    SQLite -.->|"metadata"| Snapshots

    classDef runtime fill:#CC2200,stroke-width:0px,color:white;
    classDef storage fill:#525FE1,stroke-width:0px,color:white;

    class NavGraph,Sessions,Config runtime;
    class SQLite,Snapshots,Migrations storage;

Storage Locations¶

Topics¶

Database Schema¶

The SQLite database stores:

• Navigation graph - Screens, edges, and fingerprints
• Device sessions - Active device connections
• Snapshot metadata - Index of captured snapshots
• Configuration - Feature flags and settings

Migration System¶

Migrations run automatically on server startup:

flowchart LR
    Start["Server Start"] --> Check["Check Schema"];
    Check --> Run["Run Pending
Migrations"];
    Run --> Ready["Ready"];

    classDef step fill:#525FE1,stroke-width:0px,color:white;
    class Start,Check,Run,Ready step;

See Database Migrations for details on adding new migrations.

Snapshot Storage¶

Device snapshots use a hybrid approach:

See Device Snapshots for capture/restore workflows.