How it works

Core ideas

• Agent Bee uses your current workspace context to guide suggestions.
• It can propose actions, but Actions mode and explicit approval are required to apply changes.
• Responses can include Sources and Actions for transparency and next steps.

Prompt input basics

• The prompt box shows: Ask Agent Bee anything… (type @ to mention).
• Type @ to reference pages, flows, products, and other resources.
• Use Add image… to attach screenshots or visual context.
• During Bee-guided setup, use the microphone button when it is easier to talk through your launch goal or brand notes.
• You can type and send another message while Bee is responding. The message is queued for the next turn so you can add context without waiting for the current response to finish.
• Use Stop to interrupt the current response. Text already shown remains in the conversation, and you can send a revised request.
• Code blocks and tables in Bee responses include copy controls, so you can copy a single snippet or table without copying the whole message.

Quick actions

Quick actions appear above the prompt and change based on where you are in the app. Use them to launch guided flows like:

• Edit Page Copy (Bee)
• Create Funnel
• Create Email Flow
• Import Brand
• Migrate Page
• Open Plans

Plan and Brand tabs during setup

Bee-guided setup includes a side panel with two review tabs:

• Plan summarizes the outcome, first win, recommended modules, and launch steps before anything is handed to the builder.
• Brand shows website context, logo, preview images, colors, fonts, and business notes when Bee can learn from an existing website.

If Bee is still analyzing brand context, keep refining the chat. The builder handoff stays disabled until the plan and required brand context are ready.

Approvals and safety

When an action changes data, Bee asks for confirmation:

Reply "yes" to approve or "no" to cancel.

If you are not in Actions mode, Bee will prompt you to switch before applying changes.

Support tickets also require approval. When Bee drafts a ticket, review the subject and summary, then confirm before it sends the ticket to support. For existing tickets, Bee can check the current status and latest support reply instead of opening a duplicate ticket.

Website building safeguards

When an approved Bee action rebuilds an existing page, Hiveality first saves the current page body to Version History as Before AI rebuild. If that recovery copy cannot be created, the existing page is left unchanged.

Bee can also apply structured header layouts while keeping the site's existing navigation. Header treatments can adapt to the menu colors and use an inverse logo on dark or image-backed areas when one is available. Approved editing actions can update Embed Code widgets and expand shared brand styles across forms and page layout settings without replacing unrelated page content.

Review generated pages, headers, embeds, and brand changes in the editor before publishing. For recovery options, see

Version History.

Sessions and history

Bee keeps conversations in sessions so you can switch contexts without losing progress. Use Recent Agent Bee chats in the Bee header to return to earlier conversations.

When you send a follow-up, Bee uses the saved session plus your newest message so it can stay focused on the current request after a panel refresh or chat switch. If Bee is doing longer work, the progress label can show what is happening and an approximate wait. After a generated website, funnel, or flow starts, Bee checks unfinished work on the next message before moving on to the new request.