Skip to content

Fix Pi extension-triggered turn completion - #1663

Open
ryanbbrown wants to merge 1 commit into
get-bb:mainfrom
ryanbbrown:bb/fix-bb-pi-thread-state-thr_hxj33r528u
Open

Fix Pi extension-triggered turn completion#1663
ryanbbrown wants to merge 1 commit into
get-bb:mainfrom
ryanbbrown:bb/fix-bb-pi-thread-state-thr_hxj33r528u

Conversation

@ryanbbrown

@ryanbbrown ryanbbrown commented Aug 15, 2026

Copy link
Copy Markdown
Contributor

Fixes #1633.

Summary

  • accept string content in Pi conversation messages, as allowed by AgentMessage
  • complete extension-triggered turns when agent_end contains a custom message with string content
  • cover the pi-processes notification shape with a regression test

Root cause

The Pi event translator accepted only content-block arrays in agent_end.messages. Pi extensions can also send user or custom messages with string content. Schema validation rejected the complete event, emitted provider/unhandled, and prevented turn/completed for extension-triggered turns.

Validation

  • pnpm exec turbo run test --filter=@bb/agent-runtime --force
    • 29 test files passed
    • 314 tests passed
  • pnpm exec turbo run typecheck --filter=@bb/agent-runtime
  • git diff --check
  • independent review found no blockers

AGENT GENERATED: by GPT-5.6 Sol

@ryanbbrown
ryanbbrown force-pushed the bb/fix-bb-pi-thread-state-thr_hxj33r528u branch from 67f08fa to 79c6d09 Compare August 17, 2026 23:39
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.

Pi extension-triggered turn stays working after agent_end

1 participant