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

Scheduled work with Routines

When Routines are available for your account, Agent Bee can follow a saved brief on a daily, weekly, or monthly schedule. Custom setup stays conversational: Bee proposes the name, timing, and exact work first, then asks for approval before creating the routine.

New routines keep publishing and sending actions in draft-for-review mode. Manage schedules, manual runs, and reports from the On your schedule card on Home. See Routines for the complete guide.

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.

When a planning request could mean either a tracked project in Plans or a simple outline in the conversation, Bee asks which result you want before it continues.

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.

An older approval is not treated as permission forever. When a proposed plan is more than about two days old, Bee asks you to confirm it again and re-reads the current item before applying the change.

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. When you want to continue the existing conversation, Bee prepares the reply first and sends it only after you approve.

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.

While you work in Design, Bee can read and update navigation without rebuilding the entire header. It can also find recent recovery points for the shared header and footer, then restore a published header, footer, or navigation state after you approve the change. Hiveality saves the current shared layout first, so the restore can be reversed if needed.

For an individual page, Bee can list recent Page History revisions and restore one to the draft after you approve it. The current draft is saved first, the restored version is never published automatically, and a version check prevents the restore from replacing newer work that appeared after the review. Bee can also change a row, subrow, or column background—including an approved video background—without rebuilding unrelated page sections.

When live editor refresh is available and enabled for the open Design page, approved Bee edits can appear on the canvas without a manual reload. Hiveality compares the page revision first and pauses the refresh when the editor has unsaved local work or the saved page changed again, so newer work is not silently replaced. Keep the refresh setting off when you prefer to review Bee changes after reloading the page yourself.

Bee can also apply structured header layouts while keeping the site's existing navigation and header behavior, including sticky, overlay, and mobile settings. 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.

Site-wide brand changes also keep pre-change versions. Bee can list recent brand versions and, after you approve it, restore a selected color, typography, button, form, font, or layout setup. A brand restore is immediately visible on pages that inherit those styles, and Hiveality saves the current brand first so the restore can itself be reversed.

After an approved change succeeds, Bee checks the result without repeating the same write merely because a later verification signal is inconclusive. Looking up available tools and other read-only discovery also remains separate from actions that change your data.

If the same approved action is requested more than once at the same moment, Bee shares one execution instead of applying duplicate changes. When an action returns a clear, non-temporary error, Bee also keeps that result instead of repeating the same change until you adjust the request.

Tool failures include the affected operation when it is available. If the same operation fails repeatedly for the same reason, Bee stops before a third identical attempt and explains what needs to change.

For Flow delivery recovery, Bee reads the complete path first, including branches and their shared continuation. It can then start one contact at a reviewed step or re-run one step for a contact already in the Flow. Because an email or text can send immediately, Bee names the exact step and asks for approval before it proceeds.

Bee can also list the people in one Flow by enrollment status or current step, including step totals that help identify where contacts are waiting or failing. When you ask Bee to enroll a group, such as everyone with a tag, it enrolls up to 100 contacts in one approved action instead of one request per person. Contacts already in the Flow are reported as skipped. To enroll future contacts automatically, Bee sets a Flow trigger rather than enrolling people by hand.

When Bee edits one section of a page, it can find that section by its heading, by a widget inside it, or by a sub-heading or line of text within it. Headings that differ only by capitalization resolve to the exact match. Bee also recognizes its own completed actions more reliably, so a change that succeeded is confirmed rather than reported as not run. Before creating or changing a trigger, it reports another live Flow using the same trigger. Removing a complete Flow requires separate confirmation, keeps its enrollment history, and stops its trigger and in-progress contacts.

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.

The open conversation is remembered separately for each website and signed-in user, even if the website address changes. If a remembered conversation no longer belongs to the current website or account, Bee clears that selection and opens an available chat instead of leaving the panel stuck on an access error.

Build progress and other background activity appear in a compact activity card instead of being mixed into Bee's normal replies. Reopening a recent chat keeps that activity separate and restores the conversation in order, including when older messages need to load in more than one batch.

Activity cards can show the current step, progress, and a completed, warning, or failed result. Use View when a finished job has a result to open. Active work refreshes while Bee is open and checks again when you return to the tab or reconnect, so leaving the starting screen does not hide the latest outcome.

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.

Progress and recovery

Bee keeps a working indicator visible for the full turn, including while it is checking context or moving between tools. Longer turns show elapsed time, and

Still working appears when a response pauses between steps so you can tell the request is still active.

If a turn fails, the error stays in the conversation after a reload. Choose

Try again to resend the request from that point; the failed reply is replaced instead of adding repeated copies to the conversation.

Very long turns stop before the service limit so Bee can save the available reply and status instead of disappearing without an outcome.

Image attachments are sent to Bee in a supported image format without changing the original file in File Manager. If an attachment still cannot be read, Bee shows a specific image message so you can attach a JPEG, PNG, WebP, or GIF and try again.

When an image-generation request is rejected by the image service, Bee can prepare one meaningfully different, safer prompt and try once more. If the second attempt is also rejected, Bee stops and asks for a new creative direction instead of repeating the same request.

Avoid repeatedly sending the same failed request. When Bee detects several identical unanswered turns, it pauses the repeated attempt and leaves one clear status reply so you can adjust the request or try again later.

If your sign-in session expires, Bee tries to restore it once before pausing message updates. If sign-in is still required, the panel stops background refreshes and shows Sign in again; the conversation remains saved. After you sign in, message updates resume only after Hiveality confirms that the conversation is available to the current account. If your current account no longer has access to a conversation, choose another chat or reload after access is restored.