Repository navigation
💡 Voice-Steered Agent Execution: Real-Time Conversational Redirection During Multi-Step Workflows #493
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary
Enable users to redirect, pause, skip, or reprioritize agent workflow steps mid-execution through natural voice commands, without waiting for the agent to reach a decision point. The avatar acknowledges each steering command and confirms the adjusted course before proceeding. This addresses the critical control gap between FR21 (plan approval at decision points) and FR37 (barge-in stops playback) where users have no agency during continuous agent execution phases.
Market Signal
ChatGPT Desktop's July 2026 voice mode lets users "start, check, or steer work in other threads" by voice (TechCrunch, 9to5Mac). Google Gemini Live passes spoken instructions to Spark for multi-step jobs (Google Blog). Voice-directed agent steering is becoming table stakes for desktop AI assistants. Meanwhile, 88% of AI agent pilots fail to reach production (IBM, Arcade.dev) — partly because users feel they've lost control during long-running agent tasks.
User Signal
TalkTerm's PRD defines FR21 (approve/modify/reject plans) and FR37 (barge-in stops playback), but neither covers real-time mid-execution steering. Non-technical users — TalkTerm's primary audience — report the highest anxiety during long uninterruptible agent runs. The existing confirm-plan pattern only activates at pre-defined decision points, leaving a control gap during continuous execution phases. This gap is especially acute for the brainstorming workflow (Journey 1) where multi-step agent processing can run for 5+ minutes.
Technical Opportunity
Claude Agent SDK supports session cancellation and resumption with modified context. TalkTerm's event-based IPC architecture provides natural breakpoints in the SDK message stream where steering commands can be injected. The existing voice pipeline (Web Speech API) and barge-in state machine can be extended to recognize steering intents. MVP needs 5-7 predefined commands mapped to SDK operations:
Assessment
Adversarial Review
Strongest objection: Mid-execution steering could leave agent state inconsistent if a tool call is interrupted partway through (e.g., file partially written, API call in-flight).
Rebuttal: Steering commands take effect at the next natural breakpoint in the SDK message stream — after the current tool call completes, not mid-tool-call. The SDK's structured message flow provides these breakpoints inherently. The avatar confirms "I'll finish this step first, then adjust" for transparency. This mirrors how a human assistant handles redirection: complete the current action, then change course.
Suggested Next Step
Spike: Map Claude Agent SDK message stream events to identify natural breakpoints where steering commands can be safely injected. Define the initial voice steering command vocabulary and prototype the intent-to-SDK-operation mapping with the existing barge-in state machine.
All reactions