User Feedback Collection

[alexlwn123]

User feedback intake

Use this discussion to record feedback, bugs, friction, requests, and recurring themes heard from users.

Please add each distinct piece of feedback as a comment. If you hear the same thing from multiple users, add a new comment or reply with the extra signal rather than editing away the original context.

Comment template

### Summary
One-sentence summary of the feedback.

### Source
Who heard it / where it came from / date.

### User context
Relevant user type, platform, workspace size, usage pattern, or setup. Avoid identifying details unless needed.

### Feedback
What the user said or experienced. Paraphrase unless quoting is useful.

### Impact
How this affected the user: blocked, slowed down, confusing, trust issue, nice-to-have, etc.

### Frequency
One-off / repeated / multiple users / unknown.

### Evidence
Links to issue, support thread, logs, screenshots, recording, or related discussion, if available.

### Suggested next step
Triage, investigate, follow up with user, open issue, needs design, already fixed, etc.

[alexlwn123]

Summary

Recurring task results were delivered to different chats than expected, and the current /sethome command was not intuitive for directing where task output should go.

Source

Claudia, HRF legal department.

User context

Internal/legal user setting up recurring tasks and expecting task results to appear in a predictable, specific chat.

Feedback

Claudia set up recurring tasks and was confused when results appeared across different chats. The /sethome command did not make it obvious how to control the destination chat for recurring task results.

Impact

Confusing workflow and trust issue. The user could not easily predict where recurring task results would appear, which makes recurring tasks feel harder to manage and may cause important outputs to be missed.

Frequency

One-off report so far.

Evidence

No logs or screenshots captured. Feedback reported directly from Claudia.

Suggested next step

Triage as UX/product feedback for recurring task destination routing. Consider replacing or supplementing /sethome with an obvious per-task destination selector, such as “Deliver results to: [selected chat]”, with clear current destination shown during recurring task setup and editing. Perhaps make it similar to how the Codex app handles recurring jobs.