Agent-built apps

Start a new session and select Ricky - App builder. Its app and Sheets tools cover the whole job, including previews, production releases, logs, and rollbacks.

Say who uses the app and what they need to finish. For example, "Build a lead review app for the sales team. Let people filter by status, open a company record, edit the next step, and see its owner."

Name the Hivy Sheet that should back the app and which rows people may change. One app binds to one Sheet, and it can read and update rows without changing that Sheet's schema.

If the data lives in Hivy, name the existing Sheet or ask Ricky to make one first. Ricky reads its pages and field types before writing the app, while the Sheet remains available to agents and teammates outside the new interface.

Ricky checks a temporary preview inside its session before sharing it. Open Browser and complete the main task with believable demo data. The preview disappears when the builder session ends.

Keep follow-up work in that session because Ricky can edit the current app instead of reconstructing it. Be literal: "Put overdue items first; add an owner filter and ask for confirmation before deleting a row."

A preview isn't a production app. Ricky needs your explicit approval each time it publishes or republishes. Once you approve, Hivy stores a new version and deploys it; Ricky checks the running app before returning its live URL.

Ricky writes notes for every release, which makes old versions easy to identify. If the release breaks something, ask it to read the production logs and restore the last good version before attempting another fix.

Select Apps in the workspace sidebar. Hivy groups the list by team and lets you search names or descriptions. Open a result in the right panel, or send it to a separate browser tab when you need more room.

App access follows its team. A person must be able to use that team before Hivy lists the app or issues a launch session.