{
"$type": "site.standard.document",
"bskyPostRef": {
"cid": "bafyreidhd24rczyp4gzotstewdocaiyb2wuomiz7n6s24cnutucns74fvm",
"uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mpd5gpubxai2"
},
"path": "/t/custom-gpt-actions-work-in-text-but-never-execute-in-voice-mode-invalidrecipient-unrecognized-recipient/1385102#post_1",
"publishedAt": "2026-06-28T04:01:25.000Z",
"site": "https://community.openai.com",
"textContent": "Hi,\n\nI’m trying to determine whether this is a known limitation or a bug.\n\nI created a minimal Custom GPT with a single GET Action using the following OpenAPI:\n\n\n openapi: 3.1.0\n info:\n title: Test Voice API\n version: 1.0.0\n servers:\n - url: https://httpbin.org\n paths:\n /get:\n get:\n operationId: testGet\n responses:\n \"200\":\n description: OK\n\n\n\nGPT instructions:\n\n> Whenever the user says “test”, always call the action `testGet`.\n\n## Results\n\n**Text mode**\n\n * Works correctly.\n\n * The Action executes and the HTTP request reaches httpbin.\n\n\n\n\n**Advanced Voice Mode** (Android app and ChatGPT Web using a microphone)\n\n * The Action is never executed.\n\n * The assistant reports a technical issue.\n\n * No HTTP request reaches the server.\n\n\n\n\nAdditional observation:\n\nIf I type **“continue”** immediately after the failed voice interaction, ChatGPT is sometimes able to inspect its previous attempt and reports that it encountered:\n\n**InvalidRecipient**\n**Unrecognized recipient: httpbin_org__jit_plugin**\n\nThis suggests the failure may occur before any HTTP request is sent.\n\nI first observed this with my own FastAPI backend, then reproduced it with the public `httpbin.org` endpoint, so it doesn’t appear to be API-specific.\n\nHas anyone successfully executed Custom GPT Actions from Advanced Voice Mode recently?\n\nIf yes:\n\n * Android / iOS / Web?\n\n * Which model?\n\n * Any specific configuration?\n\n\n\n\nThanks!",
"title": "Custom GPT Actions work in text but never execute in Voice Mode (InvalidRecipient : Unrecognized recipient))"
}