The intelligence layer meets the workspace. How Journeys becomes the proactive engine that feeds Projects with context, intent, and momentum.
Both products exist because context loss during task-switching is the #1 user pain point.
Journeys is the entry ramp. Projects is the destination. Together they own the full loop.
Sarah, a college student, spent 2 days researching climate policy across 8 tabs. She closed Edge. Next morning, a Journey card appears on her NTP.
One click: "Open as Project" creates a dedicated window with all 8 tabs restored, page summaries pre-loaded as Copilot sources, and AI ready with full context.
Two surfaces, two purposes, zero conflict.
Within a Project window, Journeys can track session-level activity and surface a "session recap" on the Project NTP.
Journeys' page summaries become Projects' automatic sources — zero extra COGS.
Journeys for things you didn't plan. Projects for things you commit to.
| Dimension | ✦ Journeys | 📁 Projects |
|---|---|---|
| When it appears | Proactively — AI decides what to surface | On demand — user creates workspace |
| User intent | "I didn't realize I was working on this" | "I'm deliberately focusing on this" |
| Persistence | Ephemeral (14-day window) | Durable (close and come back) |
| Context source | Browsing history + page summaries | Open tabs + user-added sources |
| NTP surface | Default window NTP (3 card slots) | Project window NTP (home page) |
| Analogy | A smart assistant who remembers what you did | A dedicated desk for your project |
Three tiers of integration — design for all now, build progressively.
Together they create the full loop: AI captures what users were doing, a dedicated workspace lets them finish it, and the intelligence gets smarter with every session.