Skip to content

fix: harden after-start prompt delivery#2520

Closed
nikhilachale wants to merge 1 commit into
AgentWrapper:mainfrom
nikhilachale:ao/agent-orchestrator_d14024986e-89/prompt-delivery
Closed

fix: harden after-start prompt delivery#2520
nikhilachale wants to merge 1 commit into
AgentWrapper:mainfrom
nikhilachale:ao/agent-orchestrator_d14024986e-89/prompt-delivery

Conversation

@nikhilachale

Copy link
Copy Markdown
Collaborator

Fixes #2517

Summary

  • route spawn prompt handling through each agent adapter's prompt delivery strategy
  • keep in-command prompts in argv and prevent an extra post-start send
  • for after-start prompts, wait briefly for the TUI to settle, retry transport send failures, and tear down/terminate the partial spawn if delivery never succeeds

Tests

  • go test ./internal/session_manager
  • go test ./internal/adapters/agent/cline ./internal/adapters/agent/kimi
  • env -u AO_SESSION_ID -u AO_PROJECT_ID -u AO_ISSUE_ID go test ./...

Notes

  • A plain go test ./... in this AO worker shell fails in backend/internal/cli because inherited AO_SESSION_ID/AO_PROJECT_ID make project-context tests take the daemon lookup path. Clearing those AO context variables matches CI-style isolation and passes.

@nikhilachale nikhilachale force-pushed the ao/agent-orchestrator_d14024986e-89/prompt-delivery branch from 60359bf to 03e3ec2 Compare July 8, 2026 15:32
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.

After-start prompt delivery can be lost for interactive TUI agents

1 participant