{"version":"2.1.242","anchor":"agent-backed-mock-responders-are-present-but-switched-off","canonical_anchor":"agent-backed-mock-responders-are-present-but-switched-off","heading":"Agent-backed mock responders are present but switched off","tier":"soon","area":"Plugin Eval","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/agent-backed-mock-responders-are-present-but-switched-off","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Agent-backed mock responders are present but switched off\n\nMocks could be answered by a prompt instead of a fixed body, but that type is rejected.\n\n**What**\n\nMock files can declare a responder that is answered by a prompt rather than a fixed body, with an `abort_when:` condition, but the code path is behind a constant that is false in this build. Any mocks file using `type: agent` fails and is told to use a fixed body for now.\n\n**Details**\n\n- Supporting machinery ships unreachable: `abort_when`, the `tools:` key in `_server.md`, and a heuristic warning that prose about failing the run does not actually abort it.\n\n**Evidence**\n\n`mocks: agent responder unavailable`\n\n- Area: Plugin Eval\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}