Conversations models use Memory v1's 8-value channel enum, so a VIDEO address fails to parse and VOICE is accepted on send
Maintainers usually reply within 5 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python, typescript
- Domain
- api
Research direction
Start with src/tac/models/conversation.py and the referenced TypeScript schemas in packages/core/src/types/conversation.ts; compare their channel types with the canonical Conversations enums cited in the issue. First resolve whether the documented EMAIL address is supported or the spec prose is stale. Done when receive/address and send channels match the confirmed definitions and both SDKs accept valid responses while rejecting invalid send channels.
Written by the indexing model from the issue text.
Description
What differs
Both SDKs use a single 8-value channel union for every channel field in the Conversations v2 models. The canonical definition has two channel enums for Conversations, with six and four values, and neither is the union the SDKs use.
Verified against main today (2026-10-08): Python at 2c24bd988c, TypeScript at c34450aa8c. All line citations are for navigation only.
| source | values |
|---|---|
| SDK union (both languages) | VOICE SMS RCS EMAIL WHATSAPP CHAT API SYSTEM |
conversations.v2.channel (receive/address) |
VOICE SMS RCS WHATSAPP CHAT VIDEO |
conversations.v2.send_channel (send) |
SMS RCS WHATSAPP CHAT |
The canonical enums are in twilio/twilio-oai spec/yaml/twilio_conversations_v2.yaml at 141f1201b5, :1997-2005 and :2007-2015.
The SDK union appears to have been taken from Memory v1, not Conversations: spec/yaml/twilio_memory_v1.yaml:3450-3461 declares Participant.channel as exactly those eight values, in exactly that order. That is the mechanism rather than a guess — the order matches member for member.
Sites:
- Python
src/tac/models/conversation.py:83(ParticipantAddress),:270(CommunicationParticipant),:445(ActionParticipantRef) - TypeScript
packages/core/src/types/conversation.ts:9-18(ParticipantAddressTypeSchema), applied at:25,:39,:124(ActionParticipantRefSchema) and:302(ConversationAddressSchema)
Three consequences, one of which breaks reads
-
VIDEOis rejected on the read path.conversations.v2.channelincludesVIDEO; the SDK union does not. A participant carrying aVIDEOaddress makesParticipantResponse(**response.json())raiseValidationErrorin Python and makesListParticipantsResponseSchema.parse(data)throw in TypeScript — solist_participants/listParticipantsfails on a response the API is entitled to send. This is the sharpest one: a caller cannot read the conversation at all, and no caller mistake is involved. -
EMAIL,APIandSYSTEMare accepted client-side where the Conversations definition does not declare them, so a caller who sets one gets a service-side 400 instead of a type error at the point of the mistake. -
The send path accepts receive-only channels.
ActionParticipantRef(conversation.py:445,conversation.ts:124) is thefrom/toof aSEND_MESSAGEaction, where the definition usessend_channel— four values, with the note "VOICE is receive-only and not supported for send operations." The SDKs permitVOICE, plus the three undeclared values.
What the models should declare
Two distinct types rather than one, matching the two canonical enums:
- an address/receive channel —
VOICE SMS RCS WHATSAPP CHAT VIDEO— forParticipantAddress,CommunicationParticipant,ConversationAddress - a send channel —
SMS RCS WHATSAPP CHAT— forActionParticipantRef
If Memory v1's eight-value enum is needed for Memory models, keeping it under its own name would stop it being reused where Conversations' narrower enums apply.
One thing to confirm on your side
The canonical definition is not entirely self-consistent here, so please check this rather than taking the table above as settled. conversations.v2.participant's addresses description still documents an EMAIL address format — "- EMAIL: Email address (such as "[email protected]")", twilio_conversations_v2.yaml:462, and at four further sites — while the channel enum it points at has no EMAIL. So either the enum is missing a value or the prose is stale, and we cannot tell which from outside. If EMAIL is genuinely supported, the fix is in the definition and only VIDEO and the send/receive split apply to the SDKs.
Context, and no urgency implied
Found while building an OpenAPI-driven client generator against the canonical twilio-oai specs and comparing its output with the hand-written SDKs. Filed here rather than in the TypeScript repo because the two track each other and Python looks like the source (your twilio-agent-connect-typescript HEAD is "Synced from Python"); the TypeScript sites are listed above so both can move together. We are not blocked and nothing here needs a response on any timeline.
- Dominant language
- Python
- Stars
- 17
- Forks
- 11
- Avg merge
- 5d 19h
- Merged PRs (30d)
- 6
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from twilio/twilio-agent-connect-python
-
ParticipantResponse.name is required where the API definition marks it nullable, so a nameless participant fails to parsePossibly taken @TheeCoderAhmed claimed this 22 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 86/100
twilio/twilio-agent-connect-python#134 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 50/100
twilio/twilio-agent-connect-python#136 ·
Maintainers usually reply within 5 days
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
twilio/twilio-agent-connect-python#135 ·
Maintainers usually reply within 5 days
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
twilio/twilio-agent-connect-python#101 ·
Maintainers usually reply within 5 days
-
add tac config validationsPossibly taken @rahulsjha claimed this 4 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 45/100
twilio/twilio-agent-connect-python#70 · 1 comment ·
Maintainers usually reply within 5 days
All issues in twilio/twilio-agent-connect-python
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
area:cli area:security enhancement priority:medium size:small
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
RonaldHensbergen/composable-data-stack#1338 ·
Maintainers usually reply within 1 day
-
area:stdlib effort:S impact:med platform:linux type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
automated endpoint-dead needs-curation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
almanac-data/climate-almanac#139 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
UKGovernmentBEIS/inspect_ai#6695 · 1 comment ·
Maintainers usually reply within 1 day