runwayml / runwayml/avatars-sdk-react
Client event tool changes pt-BR custom voice accent/prosody instead of failing clearly
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 22
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
The README says client events are supported on avatars that use a preset voice, and that custom voice avatars do not currently support client events.
However, when creating a realtime session for a custom avatar using a custom pt-BR voice, passing a minimal client_event tool is accepted by the session create flow, but the avatar
voice/accent changes immediately.
Expected:
For custom voice avatars, either:
- reject
client_eventtools clearly at session creation, or - ignore unsupported client-event tools without changing the configured custom voice/accent.
Actual:
The session starts, but the custom Brazilian Portuguese voice changes to a noticeably foreign/non-native accent.
Minimal tool payload:
"tools": [
{
"type": "client_event",
"name": "registrar_evento",
"description": "Use esta ferramenta apenas para registrar no console que a ferramenta client_event foi chamada.",
"parameters": []
}
]
A/B result in runway-characters-meet:
- omitted tools: correct pt-BR custom voice/accent
- minimal client_event tool: accent/prosody changes
- omitted tools again: correct pt-BR custom voice/accent returns
Related issue:
https://github.com/runwayml/runway-characters-meet/issues/2
Contributor 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.
Research direction
Start with the README's statement about client events and preset versus custom voices, then reproduce the A/B behavior using the minimal client_event payload during realtime session creation. Trace the session-create flow and any client-event validation or forwarding it exposes. Done means unsupported tools are clearly rejected or ignored without changing the configured custom pt-BR voice and accent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100