Record what the user asked for
pdlc.recordPromptChanges dataCreates, updates or deletes something in your workspace.What it does
Saves the message the user just typed to you onto the Agent Sessions page in Test Maze. That page is an activity timeline of every Test Maze tool call; without the prompt it only shows tool calls, with it people can see what each group of calls was trying to do. Call it once at the start of each new user request, before the other Test Maze tools for that request. It changes no test data. sessionId is optional. When omitted, the prompt joins your personal default timeline ("user-<your user id>"), which is also where tool calls without a sessionId land. When you are in a PDLC session (the sessionId from project.initialize), pass that same id here and to the loop tools so they are grouped together. Returns recorded: true, eventId and the sessionId used.
Ask your agent
You don’t call pdlc.recordPrompt yourself. Say something like this to Claude Code, Cursor or another MCP-connected agent:
- “Keep a log of what I ask you in Test Maze”
- “Make my requests show up on the Agent Sessions page”
Inputs
| Name | Type | Description |
|---|---|---|
promptrequired | string | The user's message, word for word, up to 8192 characters, e.g. "Add a password reset flow and test it". |
sessionIdoptional | string | Timeline to attach the prompt to. Use the PDLC sessionId from project.initialize (or pdlc.list) when you have one. Optional; defaults to your personal timeline "user-<your user id>". |
branchIdoptional | string | Label for a side branch of the timeline, e.g. when retrying a different approach. Optional; defaults to "main". Leave it out unless you are deliberately forking the conversation. |
The MCP call
What the agent’s MCP client sends (placeholders in angle brackets):
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "pdlc.recordPrompt",
"arguments": {
"prompt": "<prompt>"
}
}
}Connect your agent
npx -y @testmaze/mcp init tmt_xxx claude mcp add tm --scope project -- npx -y @testmaze/mcp
Create the token in your Test Maze workspace under Settings → MCP. Setup for Cursor, Cline, Gemini CLI and Codex CLI is shown there too.