# Files & Data Layout: Database

> What lives in MongoDB.

Glider documentation · Reference · Web page: https://cgglider.com/docs/data-layout/database/

Sections of this page: [On disk](https://cgglider.com/docs/data-layout.md) · [Database](https://cgglider.com/docs/data-layout/database.md) · [Page schema](https://cgglider.com/docs/data-layout/schema.md)

| Collection | Holds | Retention |
| --- | --- | --- |
| agentic_conversations | Agent chat history per page, with each run's tool steps. | Kept. |
| artifact_designs | Every design an agent wrote, in full: request, brief, each designer run's prompts and reply, cost, the HTML, imports with their measured snapshots, logic. | Kept; the 20 latest imports per design. |
| agentic_sessions | MCP agent sessions: catalogs read, baseline ids, consent grants. | 24 hours idle. |
| agentic_questions | Agent questions waiting for an answer. | 30 minutes after the agent last waited. |
| functionLogs | Script log lines. | 24 hours, 200 rows per read. |
| page_checkpoints | Page snapshots for revert. | 25 most recent per page. |

The default connection is mongodb://glider:glider@127.0.0.1:27018/glider?authSource=admin — port 27018 so the bundled container does not collide with a local mongod. The database name comes from the URI path, falling back to glider.

The desktop app needs none of this: it ships MongoDB and runs it for itself, listening on a local-only port it picks at launch, with its data in the app-data folder (mongodb/ next to workspace/) and its log in mongod.log beside server.log. Setting MONGODB_URI before starting the app points it at another database instead.

> **Note:** Mongo holds history, not the page itself. With the database down, the editor still loads and saves pages; you lose chat history, the design archive, run logs and checkpoints.