Get Started
The two surfaces of the builder, and how to find your way around.
Each agent in the Qore Agent Builder is a dedicated record. What you configure here — instructions, knowledge, tools, triggers, integrations, credentials, security controls — becomes how the agent behaves at runtime, inside whatever application embeds it.
The two surfaces
The Builder Canvas is the visual workspace. It shows the agent's connected knowledge, skills, triggers, and configuration as a diagram, so you can see at a glance how the agent is wired — which connectors are attached, what knowledge it can reach.
The Agent Preview is a chat panel beside it. You can talk to the current draft of the agent immediately after a change, without leaving the builder — which makes it the fastest way to find out whether a configuration change did what you meant.
A header across the top carries the global actions: renaming the agent, managing versions, and launching Try Agent.
Finding the setting you need
The builder's pages are organized by the order you work in, not by the order the settings panel happens to list them.
Define the agent — identity, instructions, behavior, runtime, skills, MCP tools, connectors, knowledge, triggers, secrets
Validate it against scored datasets before anyone depends on it
Ship it into your product, with authentication, domain, PII, and guardrail controls
Watch production behavior and feed what you learn back into Build
If you're looking for one specific screen, the Overview lists every page under its stage.
Common paths
Go live in your product — Agent Integration, Authentication, and Whitelisted Domains
Improve quality before release — Evals, Instructions, Skills & Capabilities, and Guardrails (Beta)
Improve quality after release — Monitoring, Online-Eval, and Reinforcement Learnings
Move an agent between environments — Export Agent, Secrets & Variables, and Runtime & Versioning
Why the configuration matters
What you set here becomes the agent's runtime behavior. Model selection, response format, instructions, connected knowledge, enabled tools, secrets, guardrails — each one directly affects how the agent answers real users.
A clear configuration produces an agent that behaves predictably in production. An incomplete or ambiguous one produces an agent that fails in ways that are hard to debug later, because nothing is technically broken — the agent is doing exactly what an unclear brief told it to. This guide is written to help you make each choice deliberately rather than by default.
New to agents? How an Agent Works walks through building one end to end. For the ideas behind the settings, see Core Concepts.
Last updated