Multi-account Google desktop client

Falcon

North star / never-ending improvement

Every Google account. One calm cockpit.

A Windows C++23 desktop system joining a WebView2 client, loopback service, account-scoped SQLite cache, Google OAuth and provider adapters, background scheduling, and restrained mail, calendar, contacts, and Today views.

Every inbox, calendar, and contact in one calm cockpit.
Jump accounts without crossing identities or local checkpoints.
Turn an email into calendar action without tab pinball.

Explore interactive architecture Read the complete manual ↗

Falcon unified inbox, message reader, and daily calendar

Real project view1 / 2

Current truth

A fresh WebView2-enabled build and all four registered CTest lanes complete, but the live Google lane skips without credentials and no live end-to-end acceptance gate is checked. OAuth material must be rotated out of source, and the unauthenticated wildcard-CORS loopback API and backend HTML sanitizer require hardening before distribution.

Pre-release - Windows candidate

System route

Follow the whole machine.

The public tour shows the shape. Members can open every chapter, search the atlas, follow related systems, and download eligible releases.

01Google OAuth + APIs

02provider sync

03account-scoped SQLite

04service + WebView2 shell

18 connected chapters

Every subsystem has a door.

System map

A local normalized layer between Google and the desktop

Google -> normalize -> local desktop

Native shell

A Windows host wraps a local focused client

Win32 -> WebView2 -> local shell

Local API

A loopback service owns state and provider actions

loopback request -> local authority

Runtime profile

Static configuration selects live or sample behavior

config -> admitted runtime mode

Google identity

Browser consent returns through a validated local callback

consent -> callback -> account

Secret boundary

User tokens stay outside SQLite

token -> Credential Manager

Google boundary

Adapters normalize Gmail, Calendar, and People

provider response -> normalized model

Mail workspace

Multiple Gmail accounts remain visible and scannable

many inboxes, visible ownership

Time workspace

Calendar shares the mail context instead of becoming another app

message context <-> scheduled time

People workspace

Official and inferred people remain separate

mail history -> suggestion, not contact

Local cache

SQLite is the normalized runtime store

provider state -> account cache

Background work

Every account and data area gets its own checkpoint

account x area -> checkpoint

Ownership

Account identity survives every normalized record

aggregate without erasing origin

Content boundary

The client strips active mail content and blocks remotes

untrusted HTML -> bounded display

Threat boundary

Several protections exist; local API hardening remains mandatory

loopback is not authentication

Operations

Sync and failure state is visible by account

state + account + correlation

Delivery

Packaging scripts exist, but distribution gates remain open

assemble != admitted release

Evidence boundary

Local verification is broad; live acceptance is still zero

local proof, no live admission

●

Member library

Open the complete Falcon atlas.

Deep explanations, diagrams, cross-links, evidence, release history, and the latest eligible repository archive.

Unlock the manual

Foundation

Creation