Wapps
Learn what a Wapp is, how it's structured, and how it differs from a published App.
A Wapp is a focused, agent-built workspace you create or install in Cheqq. It groups the chat, data, files, and automations needed for one kind of work — a CRM, an inventory tracker, an outreach tool — into a single scoped surface.
What a Wapp can contain
Depending on how it was built, a Wapp can expose:
- A scoped chat for that Wapp's context
- Data collections with configurable fields and layouts
- Files attached to the Wapp
- Instructions — a custom system prompt that shapes how the Wapp's chat behaves, edited from the Instructions tab in the Wapp workspace
- Related automations — workflows scoped to that Wapp
The tabs and controls visible in a given Wapp are the source of truth for what it can actually do — not every Wapp uses every surface.
Collections in depth
A collection's data is shaped by its fields and presented through its layouts:
- Field types — every field type a collection can use and its configuration options
- Field Agents — generate a field's value with AI: text, images, videos, and Deep Match relations
- Layout types — Overview, Grid, Kanban, List, Calendar, record views, dashboards, and saved views
- Relations — linking records between collections, including two-way sync
- Computed fields — lookup, rollup, and formula fields
Creating a Wapp
Select Create new Wapp beside the installed Wapps list. You'll be asked for:
- Wapp name (required) — a live slug preview appears underneath as you type; the slug can't be changed after creation.
- Description (optional) — what the Wapp should do.
Cheqq creates the Wapp and opens its workspace, where you continue refining the structure and behavior in chat.
Installed and custom Wapps
Installed Wapps (including ones from a catalog) appear in the main navigation. Custom Wapps begin from Create new Wapp. If you install a Wapp you didn't author, you get your own install of it — a separate lifecycle from the author's original, so you can uninstall it without affecting anyone else.
Wapp lifecycle
A Wapp you author can be archived (read-only, re-enable with Restore), duplicated (creates an independent copy, useful for forking a catalog Wapp before you customize it), or deleted (soft-deleted, recoverable for a limited window). If you only installed a Wapp someone else authored, your equivalent action is Uninstall — this deactivates it for you and hides its collection data after 30 days, but you're warned first if other workflows still depend on it.
Archived Wapps are read-only
Restore an archived Wapp before making changes — settings and data edits are rejected while it's archived.
Wapps vs. published Apps
A Wapp itself is private to your workspace. Apps are a related but separate feature: a public-facing site bound to a Wapp's collections and workflows, deployed to a generated *.cheqq.site address. See Apps for the audience, permission, and publishing model, and Manage an App for the click-through.
Scoped chat
Chat inside a Wapp is scoped to that Wapp — Cheqq draws on its data, files, and instructions without treating the conversation as a general workspace request.
Continue with Manage a Wapp.