▍ ONE LIST. THREE INBOXES.
Task Finder pulls what is genuinely assigned to you out of Jira, Gmail and Slack, puts it in one queue, and lets you say yes or no to each item once. What survives becomes a task. Everything else stops asking.
Synced 4m ago
Synced 4m ago
Synced 2h ago
Priya · #platform-oncall
Marcus · DM
Assigned to you · In progress
Assigned to you · To do
Comment by Dana
legal@northwind.example
finance@northwind.example
Everything assigned to you, plus the issues where someone said your name.
Mail that is actually waiting on you, not the eighty newsletters underneath it.
The messages you saved for later and then never looked at again.
01 — REVIEW
Every item gets two buttons: promote it to a task, or dismiss it. A resync never resurrects something you already decided about — the whole point is that the pile shrinks.
Synced 4m ago
Synced 4m ago
Synced 2h ago
Priya · #platform-oncall
Marcus · DM
Assigned to you · In progress
Assigned to you · To do
Comment by Dana
02 — TASKS
Each task keeps a link back to the issue, thread or message it came from, so “what was this again?” is one click rather than a search.
03 — SYNC
Jira and Gmail sync on a schedule in the cloud. Slack is the exception, and the app says so out loud: its credential is a browser session cookie that has no business living on a server, so the desktop app holds it and pushes items up.
Syncs on the server every 15 minutes.
Metadata only — subject, sender, timestamp, read state.
Session cookie stays in the desktop keychain; items are pushed up.
04 — DESKTOP
The desktop app links to the same account with a one-time code, then reads and writes the same list. Sign out of the browser and it keeps going.
Linked to task-finder.bhushan.fun · syncing
05 — WHAT IS STORED
Subject, sender, timestamp, read state, and a link back to the thread. No message bodies. No snippets. Nothing you would mind a database backup containing.
Every connector secret is sealed with AES-256-GCM before it touches the database. Device tokens are stored as hashes, so a dump cannot be replayed.
The Slack credential stays in the desktop keychain. The server only ever sees the list of items the desktop chooses to push.
Right now this deployment accepts exactly one Google account: mine. If you sign in with anything else you will be turned away at the sign-in screen — that is the whole access policy, not an oversight. There is no sign-up, no waitlist, and no billing.
It is a single-user tool that happens to live on the public internet because a cron job has to run somewhere. If you want the same thing, the honest answer is to run your own copy.