Documentation Index
Fetch the complete documentation index at: https://koreai-v2-agent-platform-dev.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Create, configure, and manage Projects in Studio. Projects are the top-level container for agents, tools, knowledge bases, workflows, and deployment configuration on Agent Platform 2.0.
Studio
Studio is the primary web interface for building, testing, deploying, and monitoring AI agents on the Agent Platform 2.0. It provides a unified workspace where teams can manage every phase of the agent lifecycle, from initial design through production operations.
When you sign in, Studio displays the Projects dashboard - a grid of project cards showing all projects in your workspace. Each card displays the project name, description, orchestration pattern badge, agent count, and last-updated timestamp.
From the dashboard, you can:
- Search projects using the search bar at the top of the page.
- Create a new project using the “New Project” option.
- Open a project by clicking any project card, which navigates into that project’s workspace.
Projects
A project is the top-level container in Studio. It groups agents, supervisors, tools, knowledge bases, workflows, integrations, and configuration into a single workspace, and it defines the isolation boundary for deployments, access control, and analytics.
What a Project Contains
Every agent you build belongs to exactly one project. A project holds seven categories of resources and their associated settings.
| Category | Contents |
|---|
| Build | Agents, workflows, and the project overview. |
| Resources | HTTP tools, code sandbox tools, MCP servers, knowledge bases, integrations. |
| Evaluate | Evaluations and experiments. |
| Operate | Sessions, deployments, inbox, alerts, transfer sessions. |
| Insights | Dashboards, analytics, agent performance, quality monitoring, customer insights, feedback, voice analytics, and pipelines. |
| Govern | Guardrails and governance policies. |
| Settings | Members, API keys, models, config variables, Git, runtime config, and more. |
Because the project is the boundary for access control and deployment, resources defined in one project are not visible to another. Moving assets between projects requires the export and import flow.
Before You Begin
Before creating or managing projects, confirm the following.
- Workspace access. You must be signed in to Studio with a user account that belongs to the target workspace.
- Role. Creating projects, managing members, and deleting projects require administrator permissions on the workspace. Developers without admin rights can still build inside a project they have been added to.
- LLM provider (optional). To use AI-guided project creation, a workspace administrator must configure an LLM provider under Admin > Models. If the provider is not configured, the AI Architect panel shows an in-panel banner instead of the wizard.
Accessing the Projects Dashboard
When you sign in, Studio opens the Projects dashboard. This is the entry point for all project management operations.
The dashboard displays a grid of project cards. Each card shows the project name, description, orchestration pattern badge, agent count, and last-updated timestamp.
From the dashboard you can:
- Search existing projects using the search bar in the header.
- Create a new project from the New Project dropdown.
- Open a project by clicking its card, which loads the project workspace.
- Access the three-dot menu on any card to delete that project.
To return to the dashboard from anywhere in Studio, click the product logo in the top-left corner or follow the breadcrumb trail back to Projects.
Creating a Project
Studio supports three creation methods. Choose the one that fits your starting point.
| Method | When to Use It |
|---|
| AI-guided (Architect) | You are new to the platform, or you want the AI Architect to scaffold agents from a described use case. |
| Blank project | You know exactly which orchestration pattern and agents you need, and you want full manual control. |
| From template | A predefined template matches your use case (for example, customer service or IT help desk). |
Method 1: AI-Guided Creation
Use this method when you want the AI Architect to scaffold agents, tools, and project structure from a described use case. It is the recommended starting point for new users.
To create a project with the AI Architect:
- On the Projects dashboard, click New Project > Start with AI Architect.
- Read the Welcome screen and click Next to begin the interview.
- In the Interview phase, answer the Architect’s questions about your use case, target audience, channels, and success criteria.
- In the Upload phase, optionally attach documents that describe your domain — for example, knowledge base content, API specifications, or existing agent scripts. The Architect uses these to inform agent and tool design.
- Wait for the Generating phase to complete. The Architect produces agent definitions, tool configurations, and an initial project structure.
- In the Reveal phase, inspect the generated structure and adjust agent roles, names, or connections as needed.
- In the Review phase, confirm that the configuration is correct.
- Click Create. Studio provisions the project and opens its workspace.
The richer the context you provide during the interview and upload phases, the more accurate the generated agents will be. Upload real documentation rather than summaries where possible.
Method 2: Blank Project
Use this method when you want manual control over every aspect of the project.
To create a blank project:
-
On the Projects dashboard, click New Project > Blank Project.
-
In the creation dialog, enter the following fields.
| Field | Required | Description |
|---|
| Name | Yes | A descriptive project name. Appears on the dashboard card and in breadcrumbs. |
| Description | No | A short summary of the project’s purpose. |
| Orchestration pattern | Yes | The coordination model for agents in this project. See the table below. |
-
Select an orchestration pattern based on your use case. Refer to Choosing an orchestration pattern.
-
Click Create. Studio opens the project workspace with an empty overview.
Method 3: From Template
Use this method to start from a predefined project that already contains agents and resources for a common use case.
To create a project from a template:
- On the Projects dashboard, click New Project > From Template.
- Browse the template catalog and select a template that matches your use case.
- Review the included agents, tools, and orchestration pattern.
- Provide a name and optional description.
- Click Create. Studio clones the template into your workspace as a new project.
Templates come pre-configured with the orchestration pattern and agent roles appropriate for the use case, so you typically only need to edit prompts, tool credentials, and knowledge sources before testing.
Choosing an Orchestration Pattern
The orchestration pattern determines how agents coordinate with each other. It is set at project creation time and pre-configures agent roles and coordination blocks for new agents.
| Pattern | How It Works | Best For |
|---|
| Concierge (recommended) | A single front-facing agent handles the user and delegates to specialist agents behind the scenes. | Customer service, help desk, general-purpose assistants. |
| Router | A triage agent classifies the request and transfers the user directly to the appropriate specialist. | Multi-department support, intent-based routing. |
| Tiered | A triage agent routes to L1 agents, which can escalate to L2 agents. Supports de-escalation back to a lower tier. | Technical support with defined escalation paths. |
| Custom | No predefined structure. Agents can be connected in any topology. | Advanced use cases requiring flexible orchestration. |
Choosing a pattern does not lock you in. It only pre-configures coordination defaults. You can still add, remove, or reconnect agents within a project at any time.
Navigating a Project Workspace
Clicking a project card opens the project workspace. The workspace has three persistent elements: the header bar, the project sidebar, and the main content area.
Project Overview Page
The first page you see inside a project is the Overview. It adapts to the maturity of your project.
| Project State | What You See on the Overview |
|---|
| Empty (no agents) | A get-started prompt guiding you to create your first agent or import existing agents. |
| Building (agents, no deployments) | Metric cards for agent count, session count, and deploy ratio; an agent list; and a resource summary panel. |
| Live (active deployments) | Full metrics for sessions, messages, tokens, cost, and deployments; active deployment list; activity timeline; and quick action cards. |
The Overview also exposes the Import and Export buttons for moving agents between projects. See Exporting and importing projects.
The left sidebar provides hierarchical navigation inside a project. It is organized into three top-level sections, with More expanding into grouped sub-pages.
Build
| Item | Purpose |
|---|
| Overview | Adaptive project home page with metrics, agent list, and quick actions. |
| Agents | Agent list, agent editor, and in-editor testing. |
| Workflows | Workflow builder and execution monitoring. |
Resources
| Item | Purpose |
|---|
| Tools | HTTP tools, code sandbox tools, and MCP servers. |
| Knowledge Bases | Document ingestion, indexing, and search configuration. |
| Integrations | Third-party connector catalog and active connections. |
More (expandable groups)
| Group | Pages |
|---|
| Evaluate | Evaluations, Experiments. |
| Operate | Sessions, Deployments, Inbox, Alerts, Transfer Sessions. |
| Insights | Dashboard, Analytics, Billing and Usage, Agent Performance, Quality Monitor, Customer Insights, Feedback, Voice Analytics, Agent Transfer, Pipelines. |
| Govern | Guardrails, Governance. |
| Settings | Members, API Keys, Models, and more. |
Clicking a group expands it to show child pages and collapses the top-level menu. A back button returns you to the top-level navigation.
The sidebar can be collapsed to an icon-only mode to reclaim horizontal space. It auto-collapses when the agent editor is active.
Project Switcher
The project switcher dropdown sits at the top of the sidebar and lets you move between projects without returning to the dashboard. It shows a scrollable list of all your projects with the current project highlighted.
Command Palette
Press Cmd + K (macOS) or Ctrl + K (Windows/Linux) to open the command palette. The palette provides fuzzy search across:
- Navigation — jump to any page within the current project.
- Agents — open a specific agent by name.
- Actions — reset session, clear events, and other quick commands.
The command palette is the fastest way to navigate large projects. Type a few characters of a page or agent name to filter results instantly.
Monitoring Project Health
The project Overview aggregates the key runtime metrics for the project. Use it as your first stop when checking project health.
| Metric | What It Measures |
|---|
| Agent Count | Total number of agents in the project. |
| Session Count | Conversations processed by the project’s agents. |
| Messages | Total messages exchanged across all sessions. |
| Tokens | LLM token usage across all agents. |
| Estimated Cost | Cost computed from token consumption and configured model pricing. |
| Deployed Ratio | Number of agents with active deployments versus total agents. |
For deeper analysis, use the pages under More > Insights (Dashboard, Analytics, Agent Performance, Quality Monitor, Customer Insights, Feedback, Voice Analytics, Agent Transfer, Pipelines). For operational issues, use the pages under More > Operate (Sessions, Alerts, Inbox).
Exporting and Importing Projects
Export and import let you move agent definitions and configuration between projects or environments. Both actions are available from the project Overview.
Exporting a Project
Export creates a downloadable package containing agent definitions and project configuration. Common reasons to export include:
- Backing up project state before a major change.
- Promoting agents from a development project to a production project.
- Sharing a configuration with a teammate or partner.
To export a project:
- Open the project and navigate to Overview.
- Click Export.
- In the export dialog, confirm the contents and click Download.
Importing Into a Project
Import loads a previously exported package into the current project. The import merges the uploaded agents and configurations with the existing project contents.
To import into a project:
- Open the destination project and navigate to Overview.
- Click Import.
- Select the exported package file.
- Review the summary of agents and resources to be imported.
- Resolve any conflicts (see the note below).
- Confirm the import.
Import does not overwrite existing agents. If the package contains an agent with the same name as one already in the project, the import flags the conflict and asks you to rename or skip the incoming agent before proceeding.
Deleting A Project
Deleting a project removes it and all of its contents permanently.
To delete a project:
- Open the Projects dashboard.
- Click the three-dot menu on the card of the project you want to delete.
- Select Delete.
- In the confirmation dialog, type the project name exactly as shown.
- Click Delete.
Deleting a project permanently removes all agents, tools, knowledge bases, workflows, sessions, and deployment configurations in that project. This action cannot be undone. Export the project first if you need a backup.
Features and Permissions
Some project features depend on workspace configuration or your assigned role. If a feature appears unavailable, check the conditions below.
| Feature | Requirement |
|---|
| AI Architect | An LLM provider must be configured under Admin > Models. Otherwise an in-panel banner is shown. |
| Platform Admin link | Visible only to users with super-admin permissions. |
| Admin pages (Members, Models, Security) | Require workspace administrator permissions. |
| Some Insights pages | Agent Performance, Quality Monitor, and Customer Insights may show a “coming soon” placeholder if not yet enabled for your workspace. |
If you expect access to a feature and do not have it, contact your workspace administrator.