💡 Cross-Workspace Morning Synthesis Brief: Avatar-Delivered Daily Digest Across Connected Projects

[github-actions[bot]]

Summary

When the user opens TalkTerm each morning, the avatar delivers a concise, synthesized briefing covering overnight changes across ALL connected workspaces — git commits, open issues, test results, deadline proximity, and relevant external signals. Unlike single-project monitoring, this synthesizes patterns across workspaces (e.g., "Your design system repo had 3 PRs merged that affect the main product repo"). This creates a daily habit that drives retention beyond initial onboarding.

Market Signal

Google Gemini Spark's Daily Brief (announced at I/O 2026) is the headline consumer AI feature — it works overnight to synthesize inbox, calendar, and tasks into a prioritized morning digest. Desktop AI visitation grew 18% YoY (Comscore 2026), concentrated in ChatGPT. Microsoft Copilot Studio shipped post-call action automation and background workflow processing. The trend is clear: proactive AI that works when you're not watching is the next engagement frontier. Gemini Spark's "Neural Expressive" UI replaces text walls with interactive timelines and embedded visuals — the bar for proactive AI presentation is rising fast.

User Signal

Existing idea #234 (Proactive Workspace Monitoring) covers avatar-initiated status briefings within a SINGLE workspace. Users working across multiple projects (e.g., a PM managing a design system repo, a product repo, and a documentation repo) need cross-workspace synthesis that surfaces inter-project dependencies and patterns. The current initiative issues (#333-338) focus on guided onboarding — Daily Brief creates the daily habit that retains users after onboarding is complete.

Technical Opportunity

TalkTerm's architecture gives it a unique advantage over Gemini Spark: full local file system access via Claude Agent SDK built-in tools, MCP for external integrations, and workspace-scoped session persistence (FR52-53). Gemini Spark only sees Google Workspace data. TalkTerm can synthesize git logs, test results, local TODOs, CI status, and connected MCP services — deeper project awareness than any cloud-only competitor. The BackgroundSynthesisScheduler can run as a lightweight background process in Electron's main process, leveraging the existing IPC streaming pattern to deliver brief content to the avatar in the renderer.

Assessment

Dimension	Score	Rationale
Feasibility	med	Requires background processing, cross-workspace data aggregation, and synthesis prompt engineering. Architectural foundation (workspace selection, session persistence) exists but scheduling infrastructure is new
Impact	high	Creates daily engagement habit — the single most important retention metric for consumer desktop apps. Differentiates from Gemini Spark through deeper local workspace access
Urgency	high	Gemini Spark Daily Brief is shipping now. TalkTerm's architecture must accommodate background processing from the start, even if the feature ships in Phase 2

Adversarial Review

Strongest objection: Privacy risk — synthesizing across workspaces may inadvertently mix sensitive data from different project contexts (e.g., a confidential client project's details appearing alongside an open-source project's status). Also, building this before TalkTerm's core features exist is premature.

Rebuttal: Workspace scoping is already in the architecture (FR52-53 workspace selection, per-workspace preference memory FR51). The synthesis stays entirely local — no data leaves the user's machine. Cross-workspace references can be limited to structural signals (PR counts, test pass rates, deadline proximity) rather than content. Implementation should be Phase 2 after core workflows ship, but the architecture must accommodate the BackgroundSynthesisScheduler interface from day one to avoid retrofit.

Suggested Next Step

Add a BackgroundSynthesisScheduler interface to src/shared/types/ports/ during architecture implementation. Design the cross-workspace data aggregation schema (what signals to collect, how to normalize across workspace types). Prototype with a simple git-log-across-repos synthesis as the MVP brief content — the avatar reads a 30-second summary of commits, PRs, and test status across connected workspaces.