[Dots][Android] Use notification access for proactive cross-app assistance
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 5/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- android
- Domain
- mobile
Research direction
This is a product-level request for proactive cross-app assistance built on Android's NotificationListenerService, with no specific files, tests or entry points named. Its scope spans permissions, notification ingestion, context linking and proactive behaviour, so it needs design decisions from maintainers before any implementation starts. A newcomer would first need an agreed scope and acceptance criteria.
Written by the indexing model from the issue text.
Description
What variant of Codex are you using?
ChatGPT dot in the Android app.
What feature would you like to see?
Please let me give my dot access to Android notifications and use that context to be genuinely proactive across apps.
Muse is the inspiration. In my experience, it has been incredibly helpful, proactively telling me useful things to the point where I've wondered, “When did I connect Muse to all that?” I'd love my dot to have that kind of everyday awareness.
Notifications bring together things happening across my phone: messages, changes to plans, deliveries, reminders, and updates from apps that may never have a dedicated ChatGPT connector. Letting dot understand that stream would make it much better at noticing what matters and helping before I think to ask.
Requested behavior
- Read incoming notification content across the apps I allow, including apps without a dedicated connector.
- Connect those updates with what dot already knows about my plans, conversations, and ongoing tasks.
- Proactively spot commitments, changed circumstances, unanswered requests, and opportunities to help, without needing me to manually forward each notification or set up a rule for every situation.
- Start useful work from that context: investigate a change, prepare a reply, adjust a proposed plan, or continue a follow-up I've already authorized.
- Keep useful context over time so related notifications can become a coherent picture, and let me turn the level of proactivity up or down.
Access should be opt-in through Android's notification-access permission, with controls to choose apps, pause, and revoke it.
Examples of what I'd like dot to do
These are proposed use cases:
- A travel app reports a delay. Dot connects it to my itinerary, checks the knock-on effects, and brings me an updated plan.
- A message notification changes the time or place of a plan. Dot notices a conflict with my calendar and suggests how to resolve it.
- A reply arrives about something dot is already helping with. Dot picks the task back up, does the next useful piece of research, and comes back with a concrete next step.
The goal is broad, ongoing cross-app awareness that leads to useful initiative. Notification summaries could be part of it, but the real value is dot connecting the dots and getting work moving on my behalf.
Additional information
Meta's How We Designed Muse describes background work in response to relevant events, unprompted messages, and proactive suggestions based on the user's goals and observations. That's the experience I'd like dot to build toward.
Android's NotificationListenerService provides callbacks when notifications are posted or removed, making notification events a concrete platform capability to explore for this feature.
- Dominant language
- Rust
- Stars
- 129k
- Forks
- 20.3k
- Avg merge
- 1m
- Merged PRs (30d)
- 998
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openai/codex
-
app bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
app-server documentation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
app bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
openai/codex#55328 · 1 comment ·
Maintainers usually reply within 1 day
-
bug CLI
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
openai/codex#55122 · 2 comments ·
Maintainers usually reply within 1 day
-
Python SDK: CodexClient.close() leaves the app-server's stdout/stderr pipes open (and never waits after kill)Possibly taken @akhil9tiet claimed this 3 days ago. Openapp-server bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
openai/codex#54908 · 2 comments ·
Maintainers usually reply within 1 day
Similar issues
-
engine-rs P3 review-deferral wasm
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
maniator/verticopolis#1154 ·
Maintainers usually reply within 1 day
-
FFMPEG_BIN/FFPROBE_BIN are always overridden, so a working system ffmpeg cannot be usedPossibly taken @Bilker1422 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Stremio/stremio-service#116 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day