Creating an agent
There are multiple ways to create an agent:- From a template
- Blank agent
- Anaconda Assistant
- Select Agents from the left-hand navigation.
- Click Create.
- Select a template to create the agent.

The agent’s configuration page opens automatically after creation.
Configuring your agent
The agent configuration page displays all components that define your agent’s behavior. Select an agent’s card from the Agents page to view its configuration.
AI provider
The AI Provider row configures which model powers your agent and how it generates responses. To configure your agent’s AI provider:- Select an AI provider from the Provider dropdown. For more information, see AI providers.
- Select a model from the Model dropdown.
-
Click the settings icon beside the Model dropdown to open the Model Settings dialog and adjust the following configurations as needed:
- Max tokens: The maximum number of tokens the model can generate in a single response. Leave blank to use the model’s maximum output length.
- Output format: Choose between Text (default) and JSON for structured output.
-
Temperature: Controls randomness in responses. Ranges from 0 (most deterministic) to 2 (most creative).
Lower values work well for analytical tasks; higher values suit more creative tasks.
-
Click Done.

Sandbox
The sandbox runs your agent inside a Docker container, isolating it from your local system. The agent cannot access your filesystem or network unless you explicitly configure folder mounts and networking. To configure the sandbox:- Turn on the Sandbox toggle.
- Click the settings icon beside the Sandbox toggle to open the Sandbox Settings dialog and adjust the following configurations as needed.
-
Select a network mode from the Network dropdown:
- Outbound (default): The agent can make outgoing network requests. Agent Studio publishes the container’s port to localhost so you can chat with it.
- Isolated: No network access. The agent cannot reach external services or be reached from the host.
- Host network: The agent shares the host’s network namespace directly.
- (Optional) Set CPUs and Memory limits for the container.
-
(Optional) Add folder mounts to give the agent access to specific directories on your machine. Click Add mount, then configure:
- Host path: The directory on your machine to share with the container. Click the folder icon to browse your file system.
- Sandbox path: The location inside the container where the directory is mounted.
- Permissions: Choose R (Read-only) or RW (Read/write).
- Repeat the previous step to add as many folder mounts as your agent requires.
- Click Done.

Python tools
Python tools are custom functions that your agent can call during a conversation. Tools are organized into Python files, which group related@tool functions. For example, you might create a file called data_tools.py that contains functions for querying a database and formatting results.
Creating a Python tool file
- Click Add beside Python Tools.
- In the Create File dialog, enter a name using letters, numbers, and underscores. The name must start with a letter or underscore.
-
Click Create.
Agent Studio opens your default editor and creates the file with a sample tool function:
- Customize the generated function with your tool’s logic.
-
Save the file.
The file uses the function name as the tool name; argument names and type hints to build the tool’s input schema; and the docstring as the tool’s description.Write a clear docstring that describes what the tool does, what it accepts, and what it returns.
Adding dependencies
If your tools require external packages, open the agent’s project folder and editpixi.toml to add dependencies. Click Open from the agent configuration page to open the folder in your file system or an external editor.
Add packages under the appropriate section:
Tool approval controls
Each Python tool file has an Edit Tool Policy dialog with two security settings:- Default Permissions: Controls the approval behavior for all enabled write tools in the file.
- Write Tools: Lists the individual
@toolfunctions in the file. Turn on the toggle beside each function to enable it as a write tool.
- Click beside the tool file’s name, then click Edit Tool Policy.
-
Under Security, select a Default Permissions setting:
- Always Allow: The agent can call enabled write tools without asking for permission.
- Always Ask: The agent requests approval before calling any enabled write tool.
- Custom: Set a permission for each write tool individually.
-
Under Write Tools, turn on the toggle beside each
@toolfunction you want to enable as a write tool.
Plugins
Plugins are MCP tools and skills for a specific application that are bundled together. Adding a plugin to an agent provides that application’s bundled MCP tools and skills to it for use. Agent Studio ships with the following plugins:- Anaconda: Connect to conda environment and package management capabilities and Anaconda documentation.
- nteract: Work with Jupyter notebooks through MCP, including creating, running, and managing cells and kernels.
- Jupyter: Inspect notebook files, list kernels, connect to notebooks, run notebook workflows, and work with Jupyter context.
- Atlassian: Access Jira and Confluence for ticket management, sprint tracking, and documentation.
- Miro: Create and edit content on Miro boards, including sticky notes, flows, and diagrams.
- Omni Analytics: Query data using natural language through Omni’s governed semantic model.
- Ramp: Enable secure, read-only access to Ramp data for customer-defined logic.
- GitHub: Create and review pull requests, manage issues, trigger and monitor Actions runs, clone repos, and more.
- Web Search: Query the web to return titles, URLs, and text content.
- Click Add on the Plugins row.
- Select a plugin from the available options.
- Click Add to agent.
Skills
Skills give your agent reusable workflows and context for when to use its tools. Before you can enable a skill for an agent, it must be added to Agent Studio. For details on adding skills, see Skills. To enable a skill for your agent:- Click Add on the Skills row.
- Click Add to open the Add Skill dialog.
-
Choose a source and configure the skill:
- GitHub
- Local folder
Add a skill from a public GitHub repository.- Enter the repository Owner and Repository name.
- (Optional) Enter a Skill name to add a specific skill from the repository. Leave this field blank to add all skills in the repository.
- Click Add.

- Click Add to Agent.
Files
Files are reference documents that Agent Studio inserts into the agent’s context at the start of each conversation. To add files, drag and drop them into the Files area, or click it to browse your file system. To remove a file, click beside the file name, then click Remove.Maximum file size is 25 MB.
Instructions
The Instructions field defines your agent’s role, tone, and behavioral guidelines. It also controls when and how the agent uses its tools. Click the Instructions field and type directly to add or edit instructions. For guidance on writing effective instructions, see Crafting effective system prompts.Starting and chatting with your agent
Once your agent is configured, you can start it and begin a conversation:- From the agent configuration page, click Start.
- Wait for the agent to finish starting. A notification appears when the agent is ready.
- Click Chat to open a conversation with the agent.
If your agent has MCP tools that require authentication, Agent Studio prompts you to authorize access when you start a chat.
If your message or the agent’s response triggers a safety filter (such as PII detection, secrets detection, or prompt injection protection), Agent Studio blocks the response and displays a “Blocked by safety filter” warning in the chat.
If your message or the agent’s response triggers a safety filter (such as PII detection, secrets detection, or prompt injection protection), Agent Studio blocks the response and displays a “Blocked by safety filter” warning in the chat.
Monitoring agents
Activity
The Agent Activity monitor displays a real-time stream of events from your running agents, including tool calls, model requests, and lifecycle changes. Use it to verify that your agent is behaving as expected or to diagnose unexpected behavior.- From a chat
Usage
The Usage page tracks token consumption and estimated costs across your agent conversations. Estimated costs are calculated from public model pricing tables and stored locally. Click Usage from the left-hand navigation to open the page. Use the time period buttons in the upper-right corner to filter the data:- Today: Usage from the current day.
- 7 Days: Rolling 7-day window.
- 30 Days: Rolling 30-day window.
- All Time: All recorded usage.
- Refresh: Updates the data to include the most recent usage.
- Requests: Total number of model requests sent.
- Tokens In: Total input tokens sent to the model.
- Tokens Out: Total output tokens returned by the model.
- Estimated Cost: Approximate cost based on public pricing for the models used.
Comparing agents and models
To compare responses from multiple agents or models side by side:- Select Chats from the left-hand navigation.
- Click New, then click Compare Chat.
- Select the checkbox beside two to four agents or models to compare.
- Click Start.
- Enter a message. Agent Studio sends it to all selected agents or models simultaneously and displays their responses in side-by-side columns.
Agents or models that require credentials (such as API keys) are unavailable until their provider is configured. See AI providers.
Connecting to your agent
Every running agent exposes connection options for external tools, browser-based chat, and direct HTTP access. Once your agent is running, click Connect from the agent configuration page to open the Connect dialog.MCP server
The MCP Server section connects your agent to external tools that support MCP. Use Quick Setup to configure supported tools automatically, or Custom to copy the connection details manually.- Quick Setup
- Custom
Turn on the toggle beside each tool to register the agent as an MCP server in that tool’s configuration. Supported tools include Claude Desktop, Claude Code, Cursor, OpenCode, and VS Code.
Web chat
Click Open to open a browser-based chat interface for the agent, or Copy URL to share or bookmark the link.Advanced endpoints
Expand Advanced Endpoints to view the agent’s HTTP endpoints for scripting and automation:Opening agent files
Click in the upper-right corner of the agent’s page, then click Open to open your agent’s project folder in your file system or an external editor like VS Code. The folder contains the agent definition (agent.yaml), Python tool modules, skills, and project configuration.
Configure which editors appear in the Open menu from the Settings page.
Multi-agent orchestration
Every running agent in Agent Studio is exposed as an MCP server on your local machine. Any other agent, whether in Agent Studio or in an external tool like Claude Desktop, Cursor, or VS Code, can connect to it and delegate tasks. To connect one agent to another:- Start the target agent.
- Click Connect from the target agent’s configuration page.
- Copy the streamable HTTP URL from the Custom tab in the Connect dialog.
- In the calling agent’s configuration page, click Add on the Plugins row.
- Click Add beside Custom.
- Give the custom MCP a name and paste the target agent’s URL into the URL field.
- Click Add to agent.
Deleting an agent
- Select Agents from the left-hand navigation.
- Click on the agent’s card.
- Select Delete to remove the agent.
Deleting an agent removes its configuration, documents, and tools. This action cannot be undone.
The Anaconda Assistant agent cannot be deleted.
The Anaconda Assistant agent cannot be deleted.

