Notesflow

A fast, private to-do list and notes app in the spirit of TickTick. Lists hold tasks and Markdown notes. Everything works offline and is stored on your device; sign in to sync across devices.

Features

Organise

• Smart views: Inbox, Today (with overdue), Tomorrow, Next 7 Days, All, Completed, Won't Do, Trash
• Your own lists, grouped into folders; #tags found automatically in titles and notes
• Search and sort (smart order, due date, priority, title, last edited) in every view

Tasks

• Quick add with shortcuts: Pay rent tomorrow !high #bills
• Priorities, due dates, subtasks with progress, descriptions in Markdown
• Complete, mark Won't Do, duplicate, move to trash and restore

Notes

• Markdown editor with live split preview, formatting toolbar, list continuation, clickable checklists
• Pin, duplicate, export as .md, import .md / .txt files; word count and reading time

Everywhere

• Command palette (Ctrl/⌘+K), / to search, ? for shortcuts, Alt+T new task, Alt+N new note
• Light, dark and system themes; responsive layout; keyboard and screen-reader friendly
• Full JSON backup and restore (older backups still import)
• Public landing page at /, with the app at /app
• Installable PWA (Serwist): works offline, home-screen icon, Today and Inbox shortcuts
• Optional accounts (email + password or Google) with sync across devices; last edit wins per item

Development

npm ci
npm run dev        # http://localhost:3000 (local-only mode, no setup needed)
npm run lint
npm run typecheck
npm test
npm run build

Built with Next.js (App Router), React, TypeScript, Tailwind CSS v4, Zustand, Vitest, Serwist (PWA), Auth.js (next-auth v5), Drizzle ORM and Postgres.

Accounts and sync (optional)

Without configuration the app is local-only. To try accounts and sync locally:

npm run db:dev                       # terminal 1: local Postgres (PGlite), prints a DATABASE_URL
cp .env.example .env.local           # then fill in DATABASE_URL and AUTH_SECRET (openssl rand -base64 32)
npm run dev                          # terminal 2

Deploying on Vercel with Neon

1. Import the repository in Vercel.
2. Add a Neon Postgres database (Vercel → Storage → Neon). It sets DATABASE_URL for you.
3. Add environment variables: AUTH_SECRET (openssl rand -base64 32); for Google sign-in also AUTH_GOOGLE_ID and AUTH_GOOGLE_SECRET (Google Cloud Console → OAuth client; authorised redirect URI https://<your-domain>/api/auth/callback/google).
4. Create the tables once, from your machine, with the production connection string (use Neon's direct, non-pooled string for migrations): npm run db:migrate (it asks for the connection string and hides what you type). Re-run it after pulling any change that adds a file under drizzle/.
5. Deploy. Open the site on your phone and use the browser menu's "Install app" / "Add to Home Screen".

Push reminders when the app is closed (optional)

While Notesflow is open, reminders ring from the app itself. To also ring when it is closed, the server sends Web Push notifications (VAPID) to devices that turned them on in Reminder settings → When Notesflow is closed (signed-in users only; on iPhone and iPad the app must be added to the Home Screen first).

1. Run npm run push:keys and add the four printed values to the Vercel environment variables: VAPID_PUBLIC_KEY, VAPID_PRIVATE_KEY, VAPID_SUBJECT (a mailto: address) and CRON_SECRET. Redeploy.
2. Run npm run db:migrate (adds the push_subscription and push_delivery tables).
3. Create a free job on a scheduler such as cron-job.org that calls https://<your-domain>/api/cron/reminders every minute with the request header Authorization: Bearer <CRON_SECRET>. (Vercel's free cron only runs once a day, which is too slow.)

Each reminder reaches each device once, in that device's time zone and respecting its quiet hours. Devices that unsubscribe or sign out are removed automatically.

Autonomous daily improvements

.github/workflows/daily-improvement.yml runs every day at 09:00 Asia/Kolkata (and on demand from the Actions tab). Claude makes one improvement following CLAUDE.md and the maintainer's ROADMAP.md. Every change must pass the protected-path guard, lint, type check, tests and build before it is published:

• Minor changes (small, low-risk) are committed straight to the default branch.
• Major changes (big features, new dependencies, config, database or auth paths) are opened as a pull request with a summary, rationale, test steps and risks. Nothing is merged until the owner approves it.

Changes are committed in batches of at most 5 files ((1/3), (2/3), …) and pushed together. If nothing worthwhile is found, no commit is made.

One-time setup in Settings → Secrets and variables → Actions:

Kind	Name	Value
Secret	CLAUDE_CODE_OAUTH_TOKEN	Output of claude setup-token (Claude subscription)
Variable	GIT_AUTHOR_EMAIL	The GitHub noreply email that receives commit credit

The workflow never needs DATABASE_URL or any auth secret: the build and tests run without them.