Manage a Wapp

Install, open, create, publish, and manage focused AI-powered solutions in Cheqq.

Open an installed Wapp

Installed Wapps appear in the main navigation. Select one to open its workspace, which can expose tabs for its overview, data, automations, and other capabilities defined by that Wapp. Chat inside it is scoped to that Wapp.

Create a Wapp

Select Create new Wapp beside the installed Wapps area.

Enter a Wapp name — a slug preview appears below it, and can't be changed later.

Add an optional description of what the Wapp should do.

Select Create Wapp. You land in the new Wapp's workspace and continue refining it in chat.

Test the generated experience and data behavior before relying on it or adding sensitive data.

Wapp settings

Open Settings from the Wapp header (author only — if you only installed the Wapp, you'll see a lighter setup/uninstall view instead). Settings covers:

General — name, read-only slug, description, and the Wapp's visual identity: an icon picker (emoji or a 74-icon catalog with search), an accent color, and a card pattern. Every Wapp starts with a generated identity derived from its name; pick your own or shuffle for a new one.
Browser Access — which domains and actions the Wapp's agent may reach in Companion extension sessions, whether it persists its session, and whether it requires you to be logged in
Lifecycle — Archive/Restore, Duplicate, and Delete

Changes to General fields save automatically as you edit them.

Wapp lifecycle actions

Archive — makes the Wapp read-only; Restore reverses it.
Duplicate — creates an independent copy, useful for forking a catalog Wapp before customizing it. Only available on Wapps you authored.
Delete — removes the Wapp after a confirmation dialog. A deleted Wapp lands in the Trash drawer on the Wapps page and can be restored for 7 days (30 on paid plans); its workflows come back paused.
Uninstall (Wapps you didn't author) — deactivates your install and hides its collection data after 30 days; Cheqq warns you first if other workflows still depend on it.

Update a Wapp you installed from the store

Installing a store template gives you your own copy, so improvements published to the template afterwards don't reach you until you take them. When a newer version is available Cheqq tells you three ways: a dot beside the Wapp in the sidebar, a card at the top of its settings page, and a notification.

Open the Wapp and select Settings.

Read the Update available card. It names the version you're on and the one being offered, and lists any changes to how your data is stored.

Select Update to x.y.z. Cheqq applies the new version and reports which collections it migrated.

What an update keeps

An update is additive wherever it can be. It keeps:

Your records. Nothing is deleted. If the new version changes how a field is stored — renaming it, or switching a "Minutes" number to a Duration — your existing values are converted, and the update card tells you so before you agree to it.
Fields you added yourself. A field you created stays, with its data. If the new version happens to introduce a field of the same name, yours is kept alongside it under a numbered name rather than being replaced.
Your views. Filters, sorts, visible columns and widths survive. New settings the template introduces are filled in only where you hadn't chosen one yourself, and views the new version adds are created alongside yours without changing which view opens by default.
Your Wapp's identity. The name, icon, colour and description you set stay yours — an update never resets them to the template's.
Your automation decisions. An update brings the new version's workflows — their steps, names, and trigger configuration — but never overrides what you decided about them: whether each one is switched on, the Mailhook address people already forward mail to, and the schedule you set. Workflows you wrote yourself are never touched.

New collections, fields and automations from the template are added.

A new version may ask for a new connection

If the incoming version needs an integration you haven't connected, the Wapp moves back to setup until you connect it. Everything already in the Wapp stays where it is.

Publish a Wapp as an App

A Wapp's collections and workflows can be bound to a separate public site — an App — deployed to a generated *.cheqq.site address, with its own audience and permission model. See Apps for how that works and Manage an App for creating, binding, branding, and publishing one.

Undo and redo

Open History from the Wapp header to browse the shared timeline. Every supported committed change—from a person, agent tool, import, chat restore, or other recorded source—becomes an immutable entry.

Undo and Redo move the collaborative history cursor. Keyboard shortcuts work outside editable text fields.
Compare explains structural changes and semantic record differences, including records or fields that were added, changed, deleted, or restored.
Restore creates a new, undoable entry from an older version instead of rewriting the timeline.
Name snapshot pins an existing entry on paid plans. Free workspaces can use ordinary retained history and see the upgrade option when naming.
Trash recovers deleted Wapps (from the Wapps page), collections, and records.

Wapp history includes its settings, structure, views, dashboards, owned instructions and skills, workflow links, and collection records. It does not reverse external effects or alter standalone workflow definitions. Read History and recovery for retention and exact coverage.

Open the Wapp's automation area to inspect workflows scoped to it, or use the Workflows guide for the editor and run controls.