Fix thread-session prompt framing and ambiguous desktop controls
- Dominant language
- Rust
- Stars
- 32.7k
- Forks
- 4.3k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 253
Description
Follow-up to review of #6732 and #6909. Thread policy still receives per-channel ownership instructions and initial root turns receive channel-history guidance. Desktop Stop/live model controls address only channelId and can select an arbitrary concurrent thread. Fix scope-derived prompt framing, policy-neutral ownership language, and fail-closed handling/UI guards for ambiguous controls. Preserve channel and DM behavior. Validate with regressions, full package suites, and a live-local relay workflow.
Contributor guide
Research direction
Trace the thread-session prompt construction and the Desktop Stop/live model controls first, focusing on how scope and channelId are selected. Add regressions for thread and root-turn framing, ambiguous-control fail-closed behavior, and preserved channel/DM behavior. Run the full package suites and validate the live-local relay workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100