Features / Apps

Turn Agent work into a surface you can keep using.

Apps give a workflow its own interface, data, and permissions, so the useful result is not trapped in a transcript.

Bottega Apps library showing an installed Bottega Design Canvas marked Ready — Captured in Bottega: an installed App has a durable place in the Apps library and an explicit readiness state.

An App is a durable product surface

Bottega can install static, server-backed, and Base-backed Apps from immutable Git revisions. An App can present a dedicated GUI, structured data, or both, while Chats remain the control surface for asking an Agent to do work.

The first-party examples cover distinct jobs rather than one generic dashboard: Design Canvas, Development Kanban, Expense Tracker, and Fitness Log. Their interfaces differ because each App is shaped around its task.

Interface and data stay connected

A Base-backed App can place its own GUI beside the rows that power it. The user sees a purpose-built surface; the Agent sees explicit tools for reading or changing the underlying records.

Design Canvas renders self-contained HTML directions and can send numbered visual anchors back to Chat.
Development Kanban keeps implementation tasks and review findings as structured records.
Expense Tracker normalizes natural-language expenses into a ledger and analysis views.
Fitness Log records training sets and projects them into a muscle heatmap.

Installation has a real trust boundary

App permissions are declared and confirmed before use. Data access is granted by capability—read, insert, patch, delete, or attachments—for an exact App generation. A GUI does not silently inherit unrestricted access to local files or data.

Reusable Apps can be shared without copying local credentials or private workspace state into the package.