[Requests and ideas] Can you make the agent and the user more able to control session metadata?
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
**Mood:** 😔
**Category:** Requests and ideas
Can you make the agent and the user more able to control session metadata? The metadata is almost always wrong IME.
like just now, I spun up a session to take over a PR from someone else, and it inferred nothing, and later I asked it to associate the session with the PR, and it just couldn't do that
---
| Field | Value |
| --- | --- |
| App version | 1.0.9 |
| OS | macOS 26.5.1 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 16 |
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by reproducing the reported /chat workflow in app version 1.0.9: create a session to take over a PR, then ask to associate it with that PR; done means the agent and user can reliably control session metadata.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- desktop, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100