Skip to content

Add option to suppress terminal responses#165

Draft
assimelha wants to merge 1 commit into
coder:mainfrom
codingagentsystem:codex/emit-terminal-responses-option
Draft

Add option to suppress terminal responses#165
assimelha wants to merge 1 commit into
coder:mainfrom
codingagentsystem:codex/emit-terminal-responses-option

Conversation

@assimelha
Copy link
Copy Markdown

Summary

Adds an emitTerminalResponses terminal option that defaults to the current behavior. When enabled, terminal-generated query replies continue to flow through onData. When disabled, writes are still parsed and rendered, but parser-generated replies such as DSR responses are not emitted through the same onData stream as user keyboard input.

Why

Some embedders terminate terminal queries at the PTY boundary or server-side mux layer. In those integrations, renderer-generated replies can race with or duplicate server-side replies, and because they are emitted through onData, they are indistinguishable from user input to the PTY. This option lets those embedders keep onData user-input-only while preserving the existing default behavior for browser-managed PTY integrations.

Validation

  • bun run typecheck
  • bun run fmt
  • bun run lint
  • bun run build:wasm
  • bun test lib/terminal.test.ts
  • git diff --check

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