Back to GSD

How GSD
fits together.

Two views of the same system. The overview is the one to read first: your tasks live on your device, the app arrives as static files, and everything else is opt-in. The detail view opens each box.

Local first, sync optional

Overview
How GSD Task Manager fits togetherArchitecture overview showing the GSD web app saving tasks to a local IndexedDB store in the browser, static hosting delivering the app through a service worker, and optional sync through an AWS-hosted PocketBase database shared with other devices and with an MCP server that answers Claude Desktop.YOUR BROWSEROPTIONAL · SYNCOPTIONAL · YOUR COMPUTERFILESSERVESSAVESSYNCLIVESYNCASKSAPIAWSStatic hostingCloudFront + S3PWAService workeroffline cacheAPPGSD web appEisenhower matrixDATALocal storeIndexedDB · your tasksAPPSOther devicesiOS · Android · browsersSYNCAWS DatabasePocketBase · self-hostedMCPMCP server19 toolsAIClaude Desktopnatural languageLEGENDYour dataAppCacheExternalDevicesOpt-inHTTPSavesSync / live
The web app saves every task to an IndexedDB store on the device. Static hosting delivers the app through a service worker so it keeps working offline. Sync through the AWS database, other devices, and the MCP server for Claude Desktop are all optional.

Inside each box

Detail
GSD Task Manager in detailDetailed architecture showing the web app internals (app shell, service worker, local IndexedDB store, backup, sync engine, sign-in), AWS hosting through CloudFront, S3, edge functions and the agent-discovery files, the AWS-hosted PocketBase database as the sync hub, third-party OAuth providers, the MCP server and Claude Desktop, and the iOS and Android apps each with a local store and sync module.WEB APP · BROWSERAWS · HOSTING & BACKENDOTHER SERVICES · YOUR COMPUTERNATIVE APPS · iOS & ANDROIDSAVESSERVESJSONCHANGESFILESORIGINRUNS INSTATICSYNC · LIVEOAUTHIDENTITYAPIASKSSYNCSYNCWEBApp shellNext.js · React · PWAPWAService worker3 caches · offlineDATALocal storeDexie · IndexedDBFILEBackupJSON export · importSYNCSync enginequeue · retry · realtimeAUTHSign-inGoogle · GitHub · AppleCDNCloudFrontgsd.vinny.devS3S3 bucketstatic exportFNEdge functionsURL rewrite · headersAPIAgent discovery/.well-known · MCP cardDBAWS DatabasePocketBase on EC2EXTOAuth providersGoogle · GitHub · AppleMCPMCP serverstdio · 19 toolsAIClaude Desktopnatural languageIOSiOS appSwiftUI · GSDKitDATAiOS local storeGRDB · SQLiteSYNCiOS syncGSDKit Sync · authANDROIDAndroid appKotlin · ComposeDATAAndroid local storeRoom · SQLiteSYNCAndroid sync:core:sync · authLEGENDYour dataComponentStore / cacheExternalOpt-inHTTPSavesSync / async
Web app internals on the left, AWS hosting and the PocketBase database in the middle, third-party services and the Claude Desktop assistant on the right, and the two native apps along the bottom. Every client keeps its own on-device store and syncs through the same database.

Everything in these diagrams is open source. Read the web app and MCP server, the iOS app, or the Android app on GitHub.