Optimize Router Agent Decision-Making and Enhance UI Confirmation Workflows

[presstab]

Overview

This pull request introduces a series of refinements to the message thread architecture, the router agent's decision-making process, and the user interface. The primary goal is to transition from direct manipulation of thread state to a clean, encapsulated API on the MessageThread class. Additionally, this update optimizes routing logic by establishing a clear policy on when to invoke the heavy /code agent versus performing lightweight, localized edits directly. It also introduces user confirmation prompts before launching coding agents and improves clipboard integration across terminal and chat interfaces.

What This Means for Users

• Smarter Agent Routing: The assistant will no longer default to launching a heavy coding agent for simple, single-file edits or basic questions. Instead, it will perform localized edits directly, resulting in faster response times and lower token usage.
• Control Over Coding Agents: Users will now see a clear confirmation prompt before a coding agent is launched, allowing them to approve or cancel the operation.
• Improved Clipboard & Terminal Experience: Copying text from the terminal or chat bubbles is now more reliable. On Linux systems, copied text is automatically synced to the X11 primary selection, enabling standard terminal paste shortcuts like Shift+Insert.

A Closer Look at the Changes

Code Refinements & Thread Encapsulation

• Replaced direct list operations on thread.messages and thread.context with dedicated methods on MessageThread (add_message, add_user_message, clear, and clear_context) to ensure consistent state management and automatic persistence.
• Introduced a robust parse_router_json method in CommandInterpretationAgent to handle LLM responses containing markdown code blocks inside JSON strings, reducing parsing failures.

Router Agent & Input Handler Optimizations

• Updated the router agent's system prompt (select_command.md) with a strict /code selection policy, guiding it to use direct tools (like write_file) for simple edits and reserve /code for complex, multi-file tasks.
• Implemented a router_turn_id tracking mechanism to record user requests once per routing turn, preventing duplicate user messages from cluttering the conversation history during multi-step tool executions.

UI & Confirmation Enhancements

• Generalized the CommandConfirmationWidget into an inline yes/no prompt widget capable of displaying custom titles and questions.
• Added a prompt_for_yes_no interface to UiWrapper and implemented it across CLI and TUI environments to support interactive user confirmations.
• Integrated X11 primary selection support in the terminal output widget to improve clipboard compatibility on Linux.

Testing

• Added comprehensive unit tests in test_message_thread.py and test_router_agent.py to verify thread persistence, idempotent turn recording, and robust JSON parsing.

Generated by JrDev AI using google/gemini-3.5-flash