github / github/app

[Requests and ideas] Cross-chat context awareness for quick chats

Open
#1,721 0 comments 1 reaction 0 assignees View on GitHub
Feedback mood:sad os:macos Requests and ideas
Dominant language
No language data
Stars
2.1k
Forks
153
PR merge metrics
No merged PRs in 30d

Description

**Mood:** 😔
**Category:** Requests and ideas

Cross-chat context awareness for quick chats

When I start a new chat session, there's no awareness of previous chats. If I discussed something 8 sessions ago, I have to manually search for that specific chat to bring in the context. This is especially painful for heavy quick chat users.

What I'd love: the agent should be able to reference or recall relevant context from prior chat sessions without me needing to find and re-open them. Not full history replay, just enough awareness that I'm not starting from zero every time.

Right now the workaround is keeping one mega-chat that never ends, which doesn't scale and defeats the purpose of quick chats. Another workaround is manually storing things in the built-in sqlite db, but that's fragile and could get wiped on an update.

This would make the app feel like it actually knows me over time, not just within a single session.

---
| Field | Value |
| --- | --- |
| App version | 1.0.16 |
| OS | macOS 26.5.2 |
| Theme | Noctis Azureus |
| Path | /chat |
| Tenure | Week 6 |

Contributor guide

Open the contributing guide

Research direction

The request concerns the /chat path, but no implementation files, tests, or specific entry points are identified. Start by locating quick-chat session and history handling, then define how relevant prior context should be selected and verified in a new session without manually reopening an earlier chat.

Written by the indexing model from the issue text.

Assessment

Domain
ai, desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.