Conversational Agent Builder
Build an HTTP voice agent through a saved conversation in the dashboard.
Open Agents → Create with AI to describe an agent, refine its configuration, upload knowledge documents, and configure HTTP actions.
Conversations and configuration
The Chat tab asks clarifying questions and updates a draft. Configuration lets you edit identity (role, personality, and tone), instructions (tasks and rules), greeting, language, voice, and HTTP actions independently.
Conversations and configuration changes are saved to the database. The Conversations button reopens previous work; Start over starts a new conversation without deleting the old one. Threads are private to their creator within the active organization. A thread URL cannot be opened by another user or organization.
Failed messages remain visible with a retry action. Repeating an already completed send does not duplicate the conversation. If another tab has changed the draft, reload the saved version before continuing.
Research your business website
Include a public HTTPS business URL in your message, for example:
“Create a support agent for my business at https://example.com.” The builder
uses Gemini URL context and Google Search to research the business, then uses
that evidence to write its identity and instructions. It can also recognize
bare business domains such as example.com.
Enable Search web for a public business lookup without a URL. In that case, the current message is sent for research. Automatic website research sends only the supplied public URLs, not your previous conversation, draft, or documents. Do not include credentials or private links. URLs with credentials, query strings, fragments, custom ports, or non-public hosts are not researched. Common HTTP API endpoint URLs are excluded from automatic website research.
Research sources and an expandable briefing appear beneath the assistant reply and are saved with the conversation. Google Search suggestions are shown when provided. If research fails or has no usable sources, the builder explains the gap and can continue from your description or documents. A research result is not a guarantee that every fact on the site is current; review prices and policies before activation.
Research does not create an indexed knowledge document or give the voice agent live web access, API actions, booking capabilities, or account access. Upload reference documents and configure real HTTP actions for those needs.
HTTP actions and documents
Describe an API or paste its endpoint and request specification into chat. Review the generated HTTP method, URL, description, and request parameters. The builder supports string, number, and boolean parameters. Use the full agent tool editor for credentials and advanced schemas. Never paste credentials into chat.
The builder does not invoke the configured endpoints. Test calls and active agents can invoke them and can change real data.
Upload PDF, Markdown, or text documents from the composer or Configuration. The existing knowledge ingestion pipeline extracts and indexes their content. The builder can see document names and readiness, but does not read their contents to generate configuration. The voice agent retrieves the indexed knowledge during calls.
Uploading knowledge or starting a test creates an HTTP agent in draft status and attaches it to the conversation. Deleting the conversation does not delete this separate agent or its knowledge.
Test and activate
Test opens the browser microphone test using a short-lived, authenticated preview session. Draft agents can be tested without activation. Public API realtime sessions still require an active agent. Runtime usage and account entitlement checks still apply to preview calls.
Activate agent explicitly applies the reviewed configuration and activates the agent, subject to the plan's active-agent limit. The builder will refuse to overwrite an agent that was activated or modified through the normal editor. Continue editing such agents in the regular agent editor.
Webhook agents and client-server code generation are outside this builder.
Conversation retention
Inactive builder threads and their messages expire after 90 days by default.
An administrator can configure this using BUILDER_THREAD_RETENTION_DAYS
(1–3650). Threads can also be deleted from Conversations. Organization exports
include builder threads and messages; organization deletion removes them, and
user erasure removes that user's conversations in the organization.
Deployment
Apply database migrations 0061_agent_builder_threads.sql and
0062_builder_web_research.sql. The API uses the
existing Vertex AI credentials and project/location configuration:
GOOGLE_CLOUD_PROJECTGOOGLE_CLOUD_LOCATION(an EU region in production)- Application Default Credentials or
GOOGLE_OAUTH_ACCESS_TOKEN GEMINI_BUILDER_MODEL(defaults toGEMINI_GENERATION_MODEL, thengemini-2.5-flash)
No MCP server or separate builder worker is required. Run the existing voice runtime to use microphone tests. Deploy the API and voice runtime together so both understand signed draft-preview sessions.
The former /preview/agent-builder prototype URL redirects to the persisted
builder at /agents/build.