Skip to content

feat(control): expose native terminal draft uncertainty before prompt entry #800

Description

@Juliusolsson05

In a Codex native terminal, the accessibility Terminal input initially reported no value. After paste it reported the intended status question, but the committed prompt began theWhat do we have left... instead of What do we have left.... This used computer-use paste and Return, not ac_agents_prompt.

The prefix source is unconfirmed: pre-existing native draft or concurrent input are possibilities. The operator failed to reliably establish the full provider draft before pasting. The xterm input accessibility value is not necessarily the complete TUI composer.

Expected/acceptance: expose native draft state where reliable, otherwise report unknown distinctly from empty; prefer typed prompt delivery and preserve/reject occupied provider drafts; document the boundary between app-owned drafts and terminal input transport; validate using a harmless pre-existing draft and the actual committed prompt.

Impact: unnoticed draft text changes the submitted question. This is an observability/workflow gap, not a proven MCP prompt-corruption bug. Related Claude protections: #683, #679.

Environment: macOS, development Electron, two Agent Code windows, external MCP plus computer use, observed 2026-09-05. Exact running build revision was not verified. Refs #793, #795.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions