Product guide

Core brings together the things an agent needs to work: a model, instructions, connected capabilities, a place to run, and ways for people to participate. This guide explains those pieces through the console. The Developer docs cover calling Core from your application and embedding its interface.

Choose a starting point

• New to Core: read How Core fits together, then follow Your first agent.
• Already have an agent: use Configure an agent as the inventory of settings, with links to the deeper guides.
• Need a repeatable process: build Your first workflow and explore the step reference.
• Preparing for other people: work through Access and client apps, Publishing, and Runs and conversations.

The smallest useful setup

Start with one environment, one ready model profile, and one agent that takes a message and returns a written answer. Publish it and run it with a simple question. Add tools, knowledge, specialists, and automation when the task needs them.

You do not need to build a workflow to run an agent. A workflow becomes useful when you want to decide the sequence, require a review, route a result, or coordinate several pieces of work.

A running example

The guides use a small request assistant. Its first job is to answer one question. Later, it can classify a request, consult a collection of guidance, and produce a draft response. A workflow can send that draft for review before returning it or passing it to an external system.

Each addition has a specific purpose. Knowledge supplies reference material. A tool looks up or changes something in another system. A skill describes a repeatable procedure. A specialist agent handles a narrower task. A workflow decides which step happens next.

Before using the console

You need access to a Core environment and a role that permits the action you are taking. Check the organization, project, and environment in the console before creating resources. Ask an owner or administrator to set up a model connection if you cannot manage Connections.

This guide describes the current console. Access is by invitation during preview, and available modules depend on your environment. Screens marked as sample data or preview may let you inspect a feature while disabling changes. The interactive marketing demos use sample data and do not create agents in your environment.

Find the integration reference

After you have a published agent or workflow, the SDK quickstart explains how to run it from a server. Embedding in your product explains client sessions and end-user access. Keep those implementation steps alongside the product setup in this guide.