Skip to main content
Your agent’s behavior comes from a set of documents we call its context: who it is, how it speaks, its rules, the situations it knows how to handle, and the facts about your business. You change them in Agent Studio, or from an AI tool connected over MCP. Either way, a change goes to a draft first and reaches your customers only after it is reviewed and approved.
Editing the context from an AI tool is being enabled per organization. If the tools answer that it isn’t available for you yet, ask your Boom contact.

What the context is made of

The areas are fixed: you change and add to what is inside them, but you can’t create a new area.

When the agent reads each document

Not every document is read on every message:
  • Every turn: usually persona, voice and tone, policies and the core knowledge. A rule that must always hold belongs in one of these.
  • Only when it applies: each procedure is read when a customer’s message matches its trigger (“when a customer asks for a refund”). This keeps the agent focused, but a rule written inside a procedure only applies in that situation.
Agent Studio and the MCP tools show which documents are read every turn and which only when their procedure fires.

Teach your agent a new skill

To make the agent handle something new, add a procedure: a situation, what triggers it, and the steps to follow. Procedures are how you give your agent a new skill.
  1. Describe the situation as something the customer does: “a customer wants to return an order”, not “process returns”.
  2. Write the trigger in your customers’ own words, including what it is not for if another procedure could be confused with it. A vague trigger never fires.
  3. Write the steps as actions the agent takes (“ask for the order number”, “if it was more than 30 days ago, offer store credit”), not goals.
  4. Add a test (below), then send it for review. For now, tests are added from an AI tool connected over MCP.
Ask Agent Studio to add it (“when a customer asks to return an order, …”), or an AI tool connected over MCP (org_context_add_procedure).

Protect a change with a test

A test is a short, invented conversation plus the points the agent’s reply must meet, such as “offers store credit” or “does NOT promise a refund”. When a change is sent for review, your agent’s tests run against it and the reviewer sees the results before approving. That’s how a change that would break an earlier rule gets caught.
  • Add a test for every new procedure and every rule you add or change.
  • Invent the conversation. Never paste a real one or use real names, phone numbers or emails.
  • Test what the reply must do, not its exact words. One situation per test.
Tests are added from an AI tool, with org_context_add_eval; adding them from Agent Studio is coming. Reviewers expect a test with every new procedure.

From draft to live

  1. Change: each edit is saved to your organization’s draft. Nothing your customers see changes yet.
  2. Send for review: in Agent Studio, open the unpublished-changes indicator and choose Send for review; from an AI tool, org_context_publish. Your tests run against the draft.
  3. Approve: a reviewer approves the change, and your agent is rebuilt with it. Agent Studio shows when it’s live.
You can look at or throw away an unsent draft at any time.

From an AI tool (MCP)

Connected over MCP, an AI tool such as Claude can do all of the above: The same rules apply as in Agent Studio. Changing the context takes the Owner or Admin role, and so does reading conversations and the agent’s trace from an AI tool. The Boom skills for Claude include edit-your-agent, which teaches it this whole process.

The Agent

What answers your customers, and how it improves from your corrections.

Use Boom from an AI tool

Connect Claude or another AI tool to your organization.