Developers using Claude, Cursor, VS Code, or another AI client can now hand work to the mabl agent through the mabl MCP and check back on it later. Ask your AI client to start a conversation with the mabl agent, send it messages while it works, and read its replies. Your coding agent can ask mabl to build or fix tests, keep working on your code, and pick up the answer when it's ready.
Previously, your AI client could monitor agent sessions in mabl with tools built only for authoring. The new set of tools works with any mabl agent session and replaces seven older authoring-specific tools. Scripts that use those seven tools should update to the newer agent session tools before November 18, 2026, when the older tools are removed. If you call them directly, see Replace the older authoring tools.
These tools are available in workspaces with generative AI features turned on.
Try it out
Ask your AI client something like:
Ask the mabl agent to create a test that checks out with a saved card on staging. Keep coding, and tell me when the test is ready.
Your AI client starts the conversation, then checks back on it. If the mabl agent asks a question, your AI client can answer it or bring it to you.
New tools
| Tool | What it does |
|---|---|
| start_assistant_session | Starts a conversation with the mabl agent, optionally with a first message. |
| send_agent_message | Sends a message to a mabl agent session. If the session had stopped, the message starts it again. |
| get_agent_session | Reads a session's status and the agent's latest reply. |
| list_agent_sessions | Lists agent sessions, including every session in one run. |
| attach_to_agent_session | Points a conversation at a mabl test, a test case, an Xray test, a Jira or Azure Boards issue, or a file. |
None of the tools wait for the agent. send_agent_message returns as soon as the message is queued, and your AI client checks back with get_agent_session.
Your AI client can also reach the authoring agents the mabl agent starts on your behalf, so it can follow a whole run and step in where it's needed.
Replace the older authoring tools
| Older tool | Use instead |
|---|---|
mabl_authoring_status |
get_agent_session |
get_mabl_authoring_steps |
get_agent_session with includeArtifacts
|
mabl_authoring_answer |
send_agent_message |
mabl_authoring_list |
list_agent_sessions with status needs_attention
|
list_authoring_sessions |
list_agent_sessions with testId or branchId
|
mabl_authoring_plan |
Ask the mabl agent through start_assistant_session
|
mabl_authoring_merge |
Ask the mabl agent through start_assistant_session
|
The tools that start work directly aren't changing. mabl_authoring_initiate, mabl_authoring_edit, their flow equivalents, and the failure analysis tools work as before.