Architecture and features

Runtime

FastAPI serves JSON routes and server-rendered Jinja templates; SQLAlchemy manages SQLite; APScheduler runs retention, backup, reminder, and demo jobs. UI sessions use signed cookies and database credential-state checks. Asynchronous notification dispatch keeps provider requests out of the main task write path. Bootstrap and FullCalendar assets are npm-locked, vendored with license notices, and served locally.

Task features

Task boards and calendar views support active/archived status, tags, searching, task-type filters, sorting, and per-user preferences. Nested subtasks, cloning, administrator views, manager assignment, task following, and in-app notifications remain supported. Closing a parent requires closing descendants or confirming a cascade in the UI.

Recurrence

Post-completion intervals schedule relative to completion; multi-slot daily schedules use configured clock times; fixed-clock schedules follow anchored intervals or supported calendar rules. Examples include 8h, 08:00,15:00,23:00, and Every Tuesday. Internal stored dates are UTC; display uses the configured application timezone. Complex recurring-subtree recovery after an interrupted write still deserves operational restore testing.

Notification capabilities

Browser notifications use server-sent events while the page is connected; this is not offline Web Push. Email supports SMTP and SendGrid. Discord, webhook, generic API, Gotify, and ntfy use configured delivery endpoints subject to the outbound policy. WNS code implements the legacy UWP credential model and requires a compatible Windows client/channel; it is not a modern Windows App SDK integration. No provider is considered live-verified merely because its adapter passed mocked tests.

Compatibility decisions

Bootstrap is updated within 5.3. FullCalendar stays on the latest verified 6.1 patch line rather than silently moving to the breaking v7 API. The scheduler stays within APScheduler 3. Browser assets no longer require a runtime CDN, except the optional FastAPI documentation viewer. The generated route/package reference is checked against source to reduce website drift.

Assistant boundary

Version 00.14.01 adds an experimental, default-off Streamable HTTP MCP server at /mcp, mounted inside the same FastAPI application and lifespan. Per-user OAuth consent and eleven typed tools share task rules with the existing GPT Actions router. No second service or application port is needed.

MCP access is limited by tasks:read, tasks:write, users:read, and tasks:assign. Task reads and writes remain owner-only, including for administrators. Assignment transfers an owned active standalone task to an eligible recipient; it never opens the recipient's other tasks. The private GPT Actions interface keeps its separate integration tokens and eight task operations.

Enabling MCP adds five SQLite tables for OAuth clients, grants, connections, hashed credentials, and audit/retry records. Existing tables are unchanged. Creation and assignment commit retry records with their mutations. The server does not host OpenAI models, expose arbitrary URL fetching, or add administrator/database tools. See ChatGPT integration for setup and limitations.