Google appears to be preparing to expand Pixel 10’s Magic Cue by adding Google Tasks and Google Wallet as data sources, according to recent reports on January 19, 2026. The change was spotted in a developer-enabled screenshot and is not yet a public rollout, but it suggests Google is testing broader app access for contextual prompts. Magic Cue was introduced to surface relevant information from apps during phone calls and conversations, and these additions could let it surface tickets, reservations and to‑do items more often. Users should expect this to remain experimental until Google announces an official update.
Key Takeaways
- New evidence indicates Google Tasks and Google Wallet appear in Magic Cue’s list of supported apps in a developer-enabled screenshot reported on January 19, 2026.
- Existing Magic Cue sources since the Pixel 10 launch include Pixel Screenshots, Gmail, Messages, Keep Notes, Contacts and Calendar.
- These new options were manually enabled in the screenshot and are not part of a confirmed public rollout.
- Nearly 70% of 9to5Google readers said Magic Cue “hardly appears” on their Pixel 10 devices, highlighting inconsistent behavior in the field.
- If Wallet is integrated, Magic Cue could surface boarding passes, event tickets and payment receipts contextually during calls or chats.
- Tasks integration could let Magic Cue surface action items and reminders when they’re relevant to a conversation or call.
- Expansion raises questions about privacy controls, on-device processing and how Google will limit scope to avoid overreach.
Background
Magic Cue launched with the Pixel 10 as an on-device, context-aware assistant feature intended to pull relevant data from multiple apps and surface it when useful. At announcement, Google showcased scenarios such as showing flight details during a customer-service call or a restaurant reservation while chatting, aiming to reduce friction in common conversational moments. In practice, however, many Pixel 10 owners report the feature rarely appears, often delivering only sporadic suggestions inside Gboard rather than the richer contextual cards Google demonstrated.
The Pixel 10 itself shipped last year with several AI-driven features, and Magic Cue was positioned as a differentiator for contextual help without needing manual searching. Early adoption has been mixed: Google has issued incremental improvements, but third-party and in-house app integrations determine how often Magic Cue can find relevant content. Because Magic Cue’s utility depends on the set of apps it can read, adding high-value sources like Wallet and Tasks would materially broaden scenarios where the feature can help.
Main Event
On January 19, 2026, reporting by Android Authority (citing developer Kieron Quinn) surfaced a screenshot that included Google Wallet and Google Tasks in Magic Cue’s supported-apps list. The image suggests those options exist in settings on at least one device when toggled manually by a developer or tester. 9to5Google reported the finding and contrasted it with the Pixel 10’s current supported-app roster: Pixel Screenshots, Gmail, Messages, Keep Notes, Contacts and Calendar.
Importantly, the appearance of Wallet and Tasks in the screenshot does not mean Google has deployed the feature widely. The items were enabled manually; Android Authority and 9to5Google both note the controls are not present for ordinary users and there has been no official announcement from Google. Nevertheless, the presence of these toggles in a system menu is a common signal that engineers are preparing server-side or client-side support behind the scenes.
Observers point to obvious use cases: Wallet can store plane tickets, train passes, event tickets and loyalty cards, while Tasks contains user-created to‑dos and reminders. If Magic Cue gains access to those data streams, it could bring boarding-pass info up during travel-related calls or display a task checklist when discussing project next steps. For now, though, real-world behavior remains inconsistent and Google has not confirmed timing or scope.
Analysis & Implications
Technically, integrating Wallet and Tasks into Magic Cue expands the pool of structured data Magic Cue can index, increasing the likelihood it can match context to useful items. Wallet stores time- and location-relevant artifacts (for example, boarding passes with flight numbers and times), which are high-value triggers for contextual prompts. Tasks, though smaller in data volume, offers explicit action items that map naturally to conversational triggers like “when can you do this?” or “what’s left to do?”.
Privacy and permission surfaces will be central. Users expect Wallet contents to be handled carefully because it holds sensitive financial and travel data. Google has emphasized on-device processing for many Pixel AI features in the past; whether Magic Cue will process Wallet and Tasks entirely on-device, or send metadata to cloud models, will affect user acceptance and regulatory scrutiny. Clear, granular permissions and transparent indicators when Magic Cue uses these sources would help mitigate concerns.
From a product perspective, broader app support would improve perceived reliability if implemented well, addressing complaints that Magic Cue is too elusive. However, expanding sources also raises false-positive risk—surfacing irrelevant items at inopportune moments could worsen the user experience. Google will need to refine triggers, confidence thresholds and UI affordances so prompts are helpful rather than distracting.
Comparison & Data
| Type | Currently Supported | Newly Reported (Developer-enabled) |
|---|---|---|
| Mail & Messaging | Gmail, Messages | — |
| Notes & Tasks | Keep Notes | Google Tasks |
| Scheduling | Calendar, Contacts | — |
| Payments & Travel | — | Google Wallet |
| Device Content | Pixel Screenshots | — |
The table shows the existing app set since Pixel 10’s launch and the two items observed in the developer-enabled screenshot. Adding Wallet brings travel and ticketing artifacts into scope; Tasks brings explicit user-managed action items. Together, they would increase the variety of triggerable moments for Magic Cue, but only if Google finalizes reliability, permissions, and privacy safeguards before a public release.
Reactions & Quotes
“Magic Cue ‘hardly appears’ on their Pixel 10,”
9to5Google reader poll
The 9to5Google reader poll—cited in coverage of the developer screenshot—captures user frustration with inconsistent Magic Cue behavior. That sentiment helps explain why wider app support alone won’t satisfy users unless visibility and reliability improve.
“Google Wallet and Google Tasks showed up in the supported apps list in a screenshot shared by a developer,”
Android Authority (reporting on Kieron Quinn)
Android Authority’s write-up (which cites developer Kieron Quinn) is the primary basis for the claim that Wallet and Tasks options exist in a settings list when toggled by a developer, underscoring that the finding is reproducible but not yet public.
Unconfirmed
- Whether Google plans a staged public rollout of Wallet and Tasks support, and on what timeline, remains unconfirmed.
- It is not yet confirmed whether Magic Cue will process Wallet and Tasks data entirely on-device or involve cloud-based models for matching and ranking.
- There is no official statement from Google about UI changes or new permissions prompts tied to these integrations.
Bottom Line
The developer-enabled screenshot is an early but meaningful signal that Google is preparing for broader Magic Cue integrations on Pixel 10, notably adding Google Wallet and Google Tasks to the candidate app list. If implemented thoughtfully, these additions could make Magic Cue more helpful by surfacing travel documents and to‑dos at the right moment, addressing some current gaps in usefulness.
However, the screenshot does not mean a public rollout is imminent. Google must balance usefulness with privacy controls, transparency and reliability before the feature can meet user expectations. For Pixel 10 owners, the sensible approach is cautious optimism: the capability looks promising, but confirmation and careful deployment will be the real test.