The build loop
Agent development works in a loop. Rasa provides you with a harness that allows you to accelerate that loop and if you’re ready for it - run it on autopilot.1. Install Mantle
Mantle ships in therasa-pro package. Install it into a fresh virtual
environment on Python 3.10 to 3.13:
Mantle is currently pre-release, so pin the exact version rather than letting
pip resolve the latest stable one.
2. Create a project
Runrasa init to start the setup wizard. It also connects the coding agents
you pick to the rasa-tools MCP server:
- Asks where to create your project
- Asks which coding agents to set up (Claude Code and Cursor are pre-selected; VS Code and OpenAI Codex are also available), then installs the Mantle skills for them, registers the rasa-tools MCP server, and downloads the Mantle documentation
- Collects your keys and writes them to a
.env - Validates and trains your agent
- Opens the Inspector so you can chat with it immediately
--ides, for
example rasa init --engine mantle --ides claude,vscode. With --no-prompt and
no --ides, Claude Code and Cursor are set up; pass --ides '' to skip
coding-agent setup.
Once it completes, your project looks like this:
memory.yml for cross-skill state, responses.yml for verbatim wording,
references/ for knowledge, and tools/ for tools shared between skills. See
Project structure for the full layout and which
files are required.
3. Set your environment variables
The wizard collects your keys and writes a.env. To change them later, edit it
directly:
.env
DEEPGRAM_API_KEY. Add it yourself if you want to
try voice in step 7, and set the Inspector to use
Deepgram Flux in integrations.yml:
integrations.yml
orchestrator.model_group
in integrations.yml.
4. Connect your coding agent
If you picked your coding agents duringrasa init, their Mantle skills are
already installed, the rasa-tools MCP server is registered, and the full Mantle
documentation is bundled at .rasa/docs/mantle/. Open the project in your coding
agent and it has the context it needs to build and iterate on Mantle skills, plus
the reference to look up anything the skills do not cover.
For an existing project that wasn’t created with rasa init, if you skipped
coding-agent setup, or to add another coding agent (including JetBrains IDEs),
run the setup wizard in the project folder:
5. Build your first skill from a prompt
With the Copilot connected, describe the skill in plain language, or paste in real transcripts of the conversations you want it to handle:1
Describe it or paste transcripts
In your IDE chat, tell the Copilot what you want:Or paste a handful of real support transcripts and ask the Copilot to
turn them into a skill.
2
Let the Copilot scaffold the agent
The Copilot writes the
skill.md, any tools/, and wires up config. Review
the diff before accepting.skills/check_balance/skill.md
Run
rasa train, rasa run, and rasa inspect from the agent project root,
the directory that contains agent.yml and integrations.yml. See
Project structure.rasa train is the validation gate. Before packaging, it checks the whole
project for undeclared memory writes, unknown response names, and malformed
conditions. Treat its errors as authoring feedback and fix them before debugging
conversation behaviour.6. Evaluate with simulations
Rather than scripting every turn, let an LLM simulate a real user and score whether the agent met its goals. Ask the Copilot to generate and run a scenario:7. Talk to your agent
Start your agent and open the Inspector in your browser:- Chat
- Voice
Type a message such as Show me my recent transactions and step through
each turn in the Inspector to see which skill was active, what memory was
set, and which tools ran. Those moments are recorded as tracker events — see
Tracker events.
8. Make it sound right on a call (optional)
Two small changes make the most difference on voice. Greet the caller. In a voice conversation, the caller expects the agent to speak first. The bundled session-start skill stays silent, so replace it with one that greets:skills/builtin_session_start/skill.md
skills/builtin_session_start/responses.yml
model under language_map on the TTS
model group you named from the inspector channel in step 3. Swap
flux-alexis-en for any other Deepgram Flux voice, or adjust the pace with
speed (0.5 to 1.5):
integrations.yml
provider to azure, cartesia, or
rime and add that provider’s API key to .env. See
Speech providers.
Run rasa train after the skill change, restart rasa inspect, and start a new
voice conversation. For more on writing skills that work well out loud, see
Designing for voice.
9. Loop
Feed what you learn back into the prompt: tighten the instructions, add a tool constraint, or add scoped instructions. Re-run the simulations, inspect again over chat and voice, and repeat until the agent behaves the way you need.10. Take it to the phone
When the agent sounds right in the Inspector, connect it to a phone number through your telephony provider. The skills stay the same; you add a voice channel tointegrations.yml. See Connect a phone line.
What’s next
Skills
Understand the building block you just created.
Instructions
Write the prose that drives your skill.
Tools
Give your skill actions it can take.
Progressive Control
Add guarantees where mistakes are expensive.
Voice agents
What Mantle does for you on a call, and what you control.
Build a voice agent
Take a card replacement skill from chat to a voice conversation.