Messages
Keep the conversation, let the arrangements come together
This is a simulated concept, not a guide to shipped features. Automatic triggers and the cross-app workflows shown here are proposed.
See the current architectureA group chat settles on dinner Friday at 19:00, then shares a restaurant address.
Friends · Friday dinner
Time proposed · 19:00
Location · Shared restaurant address
The next action will appear here
Read the plan
Dinner details are coming together
Ready for your decisionThe conversation is the source; the plan has not been committed.
Concept walkthrough · All content and actions are simulated
Using the application
- 01
Open the conversation as usual. Keep the original messages, reactions, and participants in view.
- 02
Expand the proposed dinner card beside the relevant messages. Check the time, place, people, and what is still uncertain.
- 03
Edit your acknowledgment or the event details. Confirm before sending a message or adding an appointment.
Using the desktop App Card
- 01
A desktop card combines the proposed reply and event; use its source link to return to the exact conversation.
- 02
If the plan changes, update the existing card. Dismiss or defer it while retaining the conversation.
How the context connects
This concept shows proposed connections. The running shell grants access through scoped workspaces and explicitly allowed tools.
Mail & contacts
Relate the same person across accounts without mixing the destination of a reply.
Calendar
Check Friday availability and show conflicts before adding dinner.
Navigation
Resolve the shared address into a route and a later departure card.
What you authorize
The card shows the recipient or group before sending. A rule for one contact never implies permission to speak in another conversation.
When the agent works
A new message or a change to the agreed plan triggers an update. Unsettled suggestions remain proposals.