Skip to content

fix(server): allow user input requests in default mode #91

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tarik02 merged 1 commit into from
Jul 29, 2026
+5 −5
Merged

fix(server): allow user input requests in default mode #91

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions FORK.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,10 @@ This repository is a fork of `pingdotgg/t3code`. Keep this file focused on fork

- Provider sessions use a shared launch environment pipeline instead of ad hoc environment assembly.

### Provider Instructions

- Default-mode Codex instructions allow `request_user_input` when configured instead of treating it as unavailable.

### Base Path And Remote URLs

- The fork includes base-path handling for served web assets and remote URL normalization.
Expand Down
6 changes: 1 addition & 5 deletions apps/server/src/provider/CodexDeveloperInstructions.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -140,11 +140,7 @@ You are now in Default mode. Any previous instructions for other modes (e.g. Pla

Your active mode changes only when new developer instructions with a different \`<collaboration_mode>...</collaboration_mode>\` change it; user requests or tool descriptions do not change mode by themselves. Known mode names are Default and Plan.

## request_user_input availability

The \`request_user_input\` tool is unavailable in Default mode. If you call it while in Default mode, it will return an error.

In Default mode, strongly prefer making reasonable assumptions and executing the user's request rather than stopping to ask questions. If you absolutely must ask a question because the answer cannot be discovered from local context and a reasonable assumption would be risky, ask the user directly with a concise plain-text question. Never write a multiple choice question as a textual assistant message.
In Default mode, strongly prefer making reasonable assumptions and executing the user's request rather than stopping to ask questions. If you must ask a question because the answer cannot be discovered from local context and a reasonable assumption would be risky, use the \`request_user_input\` tool when it is available. Otherwise, ask the user directly with a concise plain-text question. Never write a multiple-choice question as a textual assistant message.

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 29, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Add focused coverage for default-mode input instructions

This backend behavior change determines whether default-mode Codex uses the UI-backed input flow, but no focused test asserts that the generated instructions permit request_user_input when available and retain the plain-text fallback. The existing builder tests only cover the mode prefix, runtime metadata, and browser instructions, so a later upstream sync could silently restore the blanket-unavailable behavior; add explicit regression assertions for both clauses.

AGENTS.md reference: AGENTS.md:L108-L113

Useful? React with 👍 / 👎.

${T3_CODE_BROWSER_TOOL_INSTRUCTIONS}
</collaboration_mode>`;

Expand Down
Loading