Skip to Content
AgentsConfiguration

Agent Configuration

Every field on an agent can be edited at any time. Changes take effect on the next message — existing threads are not recomputed.

Instructions (system prompt)

The instructions field is the system prompt prepended to every conversation. It defines the agent’s role, tone, and constraints.

Tips for effective instructions:

  • Be specific about the agent’s domain and the audience
  • Tell it which tools (and MCP servers) to prefer for which tasks
  • List formatting rules, e.g. “always cite the HubSpot contact ID”
  • Say what to do when a tool fails or data is missing — otherwise the LLM will guess

Example:

You are a CRM assistant for the sales team. Use the HubSpot MCP tools to look up
contacts, deals, and companies.

When reporting on a contact, always include: email, company, deal stage, and the
last-activity date. Format monetary values with currency symbols. If a record
cannot be found, say so plainly rather than guessing.

Avatar

Agents have a two-part avatar:

  • Emoji — picked via the emoji picker in the agent editor
  • Color — a hex color used as the badge background in the sidebar and chat header

Description

A short description shown on the agent card in the Agents list. Keep it to one sentence — users pick agents by skimming this.

MCP server bindings

After the agent exists, bind one or more workspace MCP servers from the agent’s configuration page:

  1. Click Add MCP Server
  2. Pick a server from the workspace catalog
  3. auxilia fetches the server’s tools and adds them to the binding

Each binding carries:

  • Tools — the list discovered at bind time, each one with a status (always allow, needs approval, disabled). See Tool Settings.
  • Sync tools — re-fetches the tool list from the MCP server. Use this when the server publishes new tools or changes descriptions.

Code execution (sandbox)

Toggle Code execution on the agent page to give the agent a Linux sandbox with shell, file, and search tools. See Sandbox for the full toolset and security model.

Subagents

Admins can attach subagents — specialized agents that the coordinator agent can call as tools. See Subagents.

Archiving and deleting

Agents can be archived (hidden from the default list but preserved with their threads) or deleted outright. Deleting an agent removes:

  • The agent config
  • All MCP server bindings for that agent
  • All subagent links to or from it
  • All threads and checkpoints associated with it

Archived agents remain queryable; deleted agents don’t.

OverviewPermissions