Skip to content

[agent] Steering commands not working -- should be editable and injected at next agent breakpoint #53

@acertainKnight

Description

@acertainKnight

Feature / Bug

The UI should support "steering commands" -- user inputs that get queued and injected at the next natural breakpoint in the agent's processing stream. These commands should be:

  1. Editable by the user after typing them, up until the moment they are actually sent/injected
  2. Injected at the next breakpoint in the agent stream (e.g., between tool calls, between reasoning steps), not requiring the agent to fully finish its current turn

Current behavior

This functionality is not working. It's unclear whether the feature is partially implemented but broken, or not yet implemented.

Expected behavior

  1. While the agent is mid-response (streaming, executing tool calls, etc.), the user can type a steering command in the input field
  2. The command sits in an editable queue -- the user can modify or cancel it before it fires
  3. At the next natural breakpoint in the agent's execution loop, the steering command gets injected as input
  4. The agent processes the steering command and adjusts its behavior accordingly

Use case

This is critical for interactive development and debugging workflows. When the agent is going down the wrong path mid-response (e.g., making unnecessary tool calls, generating a long unwanted output, or misunderstanding the task), the user needs a way to redirect without:

Context

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions