Operating modes
Different rules for different kinds of pressure.
Product design, engineering, integration, and launch
ModeMind is a life operating system built for real pressure.
The Web Guy turned a personal need into a mobile-first product that coordinates focus, transitions, recovery, planning, private records, push notifications, and AI-assisted control without making the user's life readable to the plugin.
Plugin tools
A focused control surface for ChatGPT and Dot.
Automated checks
Build, behavior, privacy, and rendered-output coverage.
Command expiry
Encrypted remote requests do not wait forever.
The problem behind the product
A normal task list treats every hour like the same person is available for it.
ModeMind grew from the reality that work, parenting, legal strain, health, household maintenance, and emotional recovery do not ask for the same kind of attention. A list can name the obligation without helping someone enter the state needed to face it.
The product changes the starting question from “What task should I do?” to “What mode does my life need me to enter right now?” That decision changes the timer, prompts, boundaries, notification language, and definition of a successful session.
The work behind ModeMind
The product is doing more than running a timer.
Interface decisions, application state, encryption, scheduling, notifications, AI controls, hosting, and launch QA reinforce the same product promise: help the user move one piece forward without creating another burden.
Mode-first product design
Twelve operating states replace the flat task-list model. Each mode has its own timer, recovery rhythm, emotional boundary, prompts, and definition of success.
Front-End HelpMobile-first application flow
The core path is built for a phone in the middle of a real day: choose a mode, name one action, run the session, leave a clean thread, and move on.
React & Static SitesPrivate control architecture
Personal records stay on the device. Cloud controls use encrypted payloads, expire automatically, require local review, and return only generic event receipts.
Security & ReliabilityChatGPT and Dot controls
A Site-hosted MCP server exposes focused tools for modes, sessions, notes, planning, preferences, notifications, vault actions, exports, and local deletion.
API & IntegrationsSchedule-aware transitions
The planner, closing buffer, mode-specific privacy settings, and push system work together to prepare the next state without exposing sensitive detail by default.
Automation & Internal ToolsProduction delivery and review
Custom-domain hosting, Sign in with ChatGPT, responsive QA, accessibility checks, automated tests, metadata, and production diagnostics are treated as one release system.
AI Production OversightStrategies working together
One flow coordinates product, privacy, and infrastructure.
The value comes from how the pieces meet. The interface changes behavior, the schedule creates continuity, the privacy model limits what leaves the device, and the plugin expands control without becoming a new source of surveillance.
- 01
The mental state comes before the task
ModeMind first asks what kind of operating state the moment requires. Only then does it narrow attention to one safe, useful action.
- 02
Transitions carry context forward
Schedules, previous stopping points, closing notes, and notifications reduce the cost of leaving one responsibility and entering another.
- 03
AI proposes; the device decides
ChatGPT and Dot can prepare encrypted actions, but ModeMind keeps approval, destructive confirmations, downloads, and permission prompts on the user's device.
- 04
Privacy settings follow the mode
Sensitive modes can keep lock-screen language generic while lower-risk modes can provide enough detail to help the user prepare at a glance.
- 05
The product is built to leave the desk
The web app is the control center, while the interaction model is being shaped for Pixel devices, watches, and future smart-glasses workflows.
Privacy as product architecture
The integration can help without reading the life it helps organize.
ModeMind keeps personal records useful on the user's device while allowing ChatGPT and Dot to prepare encrypted actions for review. That boundary is built into the control flow rather than left to a paragraph in a policy page.
View security and reliability servicesEncrypted before storage
Private command content is encrypted to the user's device key before it enters cloud storage.
Reviewed before action
Remote requests wait for local approval, and destructive operations require another confirmation.
Generic event receipts
The plugin can confirm queued, applied, or dismissed status without receiving private notes or timeline content.
Automatic expiry
Unreviewed commands expire instead of becoming a permanent remote backlog.
Built for the day, not the desk
Shipping on the web now, shaped for smaller surfaces next.
The browser application is the control center. The same short, glanceable interaction model guides the next device-specific versions without pretending unfinished hardware integrations are already shipped.
Mobile-first web app
Mode choice, planner, sessions, timeline, encrypted controls, push setup, and account state in a responsive PWA.
ChatGPT and Codex plugin
Discoverable tools, resources, prompts, encrypted approval requests, and generic control-event receipts.
Pixel and watch surfaces
Glanceable mode transitions, current-session controls, and brief capture flows designed around small screens.
Smart glasses
Discreet prompts, context restoration, and voice-first capture with interactions kept brief and situational.
Built with the same discipline
Need a product, integration, or difficult web system moved forward?
The Web Guy handles focused front-end builds, APIs, automation, performance, hosting, production review, and the work required to make the parts behave like one product.