Your first agent
A short guided path — create an agent, watch it build, try it in a chat session, and read its activity trail.
This page is the short version of the build loop. For every option in depth, see Creating an agent.
Before you start
You need a workspace selected in the sidebar's workspace picker. If you have none, see First login.
Create the agent
Go to Build → Agents and start a new agent. You can begin two ways:
- Describe what it should do — the conversational skill builder turns your goal into a skill (instructions, tools, entry point) that you refine by chatting.
- Start from a skill — pick a ready-made skill from the catalog.
You also pick the provider and model from the set your deployment offers. This choice is create-only — editing the skill later doesn't change the model. The model endpoint and its credentials are managed by the platform; you never paste a model API key into an agent.
The ask box on Home works as a shortcut: type a goal like "create an agent that summarizes support tickets" and the console hands you into this create flow with the goal pre-filled.
Watch the build
When you deploy, the platform builds a container image for the agent and rolls it out into your workspace's namespace. The create screen streams the build progress log live, so you see each stage — and if something fails, the same stream carries the failure diagnostics.
After creation, the agent's detail page shows its live status; a failed build or rollout surfaces a callout with the phase, message, and diagnostics.
Try it
Open the agent from Build → Agents. The Console tab on the agent detail page is where you run it: type a message, and a chat session starts against the deployed agent. Past sessions are listed so you can pick up where you left off.
A separate Build → Playground screen exists for experimenting across the gateway catalog, but it is disabled by default and may not be enabled in your deployment. The agent Console tab is the default way to try an agent.
See what happened
Two places show the trail your run left behind:
- The agent's Activity tab — the agent's runtime audit events, grouped by execution, with a drawer for event details. A Logs tab shows a bounded tail of the agent's container logs, and a Diagnose action produces a cited diagnosis from health, build, events, and logs.
- Build → Activity — the workspace-wide feed: timestamp, event type, message, and actor for everything that happened in the workspace.