Skip to content

Keep Codex user questions answerable - #4044

Open
maheen-ejaz wants to merge 2 commits into
get-bb:mainfrom
maheen-ejaz:codex/askuserquestion-persistence
Open

maheen-ejaz wants to merge 2 commits into
get-bb:mainfrom
maheen-ejaz:codex/askuserquestion-persistence

Conversation

@maheen-ejaz

@maheen-ejaz maheen-ejaz commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

Human comments

What was wrong

Codex app-server item/tool/requestUserInput was not recognized by the Codex provider bridge, so Codex was forced onto the fallback plugin path. The durable pending-interaction lifecycle already supports thread-scoped questions, but native Codex requests could not reach it and stale submissions had no clear recovery action.

What changed

  • Added Codex app-server user-input request decoding and response encoding, including option/free-text answers and secret-input rejection.
  • Marked the Codex provider as native-question capable so the fallback tool is withheld for Codex.
  • Added a five-minute fake-timer persistence regression and provider re-registration coverage.
  • Added stale-question UI recovery that refreshes pending-interaction state.
  • Added adapter, provider-gating, server lifecycle, and UI regression tests.

No daemon wire protocol fields changed.

How you verified

  • Focused provider, plugin, server, agent-runtime, and app tests passed.
  • Affected typechecks passed for @bb/server, @bb/app, bb-plugin-ask-user-question, and bb-plugin-provider-codex.
  • Formatting and git diff --check passed.
  • The repository has no check:pr script.
  • The source app launched successfully in an isolated dev instance; live pending-card driving was not completed because the synthetic CLI fixture did not persist into that isolated store.

Fixes #

AGENT GENERATED

@maheen-ejaz
maheen-ejaz force-pushed the codex/askuserquestion-persistence branch from 5174967 to db87310 Compare September 22, 2026 02:45

This branch has not been deployed

No deployments
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