Skip to content

fix: voice barge-in race condition & guardian inbound greeting#8419

Merged
noanflaherty merged 1 commit into
mainfrom
do/voice-call-bug-fixes
Feb 24, 2026
Merged

fix: voice barge-in race condition & guardian inbound greeting#8419
noanflaherty merged 1 commit into
mainfrom
do/voice-call-bug-fixes

Conversation

@noanflaherty
Copy link
Copy Markdown
Contributor

@noanflaherty noanflaherty commented Feb 24, 2026

Summary

  • Bug feat: initialize Next.js app in /web directory #1 (race condition): When a caller speaks a follow-up before the assistant finishes processing, startRun() would throw "Session is already processing a message" causing the assistant to say "I encountered a technical issue." Now the orchestrator polls briefly (up to 3s) for the previous run to tear down, and the error is treated as an expected abort as defense-in-depth.
  • Bug feat: add platform terraform for GKE deployment #2 (guardian greeting): When the guardian calls the assistant's phone number, the assistant would greet formally ("Hey there, this is Credence calling on behalf of Noa..."). Now the voice call control prompt detects guardian callers and instructs the model to answer casually ("Hey!" / "What's up?").

Original prompt

Bug #1: Race condition — "Session is already processing a message" crashes voice turns

Add retry loop in run-orchestrator.ts before throwing, and recognize the error as expected in call-controller.ts.

Bug #2: Assistant greets the caller on inbound calls from the guardian

Thread isCallerGuardian through buildVoiceCallControlPrompt to differentiate greeting behavior.

🤖 Generated with Claude Code


Open with Devin

- Add retry loop in run-orchestrator before throwing 'Session is already
  processing a message' so barge-in teardown has time to complete
- Treat the processing-race error as an expected abort in call-controller
  to suppress 'technical issue' fallback message to callers
- Differentiate guardian vs unknown caller on inbound calls so the
  assistant answers casually ('Hey!') instead of a formal introduction

Co-Authored-By: Claude <noreply@anthropic.com>
@noanflaherty noanflaherty merged commit 10c6d26 into main Feb 24, 2026
@noanflaherty noanflaherty deleted the do/voice-call-bug-fixes branch February 24, 2026 23:43
Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 4 additional findings.

Open in Devin Review

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d3b1bd945c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread assistant/src/runtime/run-orchestrator.ts
Comment thread assistant/src/calls/call-controller.ts
@noanflaherty
Copy link
Copy Markdown
Contributor Author

Addressed in #8644

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant