Summary
When a routine is triggered manually via the Routines tab Run button, the routine's agent output is delivered to a seemingly arbitrary existing thread rather than a predictable, user-visible location.
Steps to reproduce
- Open the web UI → Chat tab — note the currently open conversation thread
- Navigate to Routines tab
- Click Run on a routine
- Navigate back to Chat tab and check threads
Expected behavior
The routine output should be delivered to either:
- A dedicated routine-output thread that is clearly labelled, OR
- The currently active thread (with context indicating it came from a routine trigger), OR
- A newly created thread named after the routine
Actual behavior
The routine output appears in an unrelated existing thread (whichever was last active at the server level), with no indication that it originated from a manual routine trigger. Users have no reliable way to find the output.
Affected component
src/agent/routine_engine.rs (trigger dispatch), src/agent/session_manager.rs (thread selection for routine output)
Summary
When a routine is triggered manually via the Routines tab Run button, the routine's agent output is delivered to a seemingly arbitrary existing thread rather than a predictable, user-visible location.
Steps to reproduce
Expected behavior
The routine output should be delivered to either:
Actual behavior
The routine output appears in an unrelated existing thread (whichever was last active at the server level), with no indication that it originated from a manual routine trigger. Users have no reliable way to find the output.
Affected component
src/agent/routine_engine.rs(trigger dispatch),src/agent/session_manager.rs(thread selection for routine output)