Sign in to Hunch

A private, always-current view of what's in motion, what's waiting on you, and what just wrapped. Sign in with the email this dashboard belongs to.

Change connection settings

This dashboard is locked

Your data lives in an encrypted snapshot on this site. Open the full link your Instinct gave you - the part after # is the key, and it never leaves your browser.

View the demo instead

Make Hunch yours

Choose how this Hunch gets its updates. Most people should use the encrypted view - your Instinct sets it up for you.

Recommended

Encrypted view

Your Instinct sets up and updates a private, read-only page. No database, email sign-in, or technical keys for you to manage.

Ask your Instinct to set it up

Optional

Supabase with email sign-in

For people who want per-reader email access and are comfortable creating and managing their own database project.

Back to dashboard

Settings

Back to dashboard

What you're looking at

A small private web app that answers one question: what is my Instinct working on right now? Active work, things waiting on your call, and recently finished work - each card with the current status, the last meaningful update, and the next move.

How it stays current

Your Instinct publishes. As work starts, moves, waits, or completes, it builds one small JSON snapshot of user-visible outcomes, encrypts it with a fresh random key (AES-256-GCM), and replaces one file (snapshot.enc) on this site. Every publish is a complete, consistent view.
The app reads. This page fetches the encrypted file and decrypts it locally with the key from your link. There is no write path from the browser at all.
You look. No chat archaeology. Open the page, see the state of your life in ten seconds.
Something looks wrong? Tell your Instinct in chat - it owns the snapshot and republishes it. Editing the file directly works until the next publish overwrites it.

Running the optional Supabase backend instead? The flow is the same shape: your Instinct upserts rows into your own project, and this page reads them after email sign-in. One backend per installation - no syncing, no split brain.

Security model

Default: encrypted snapshot. The host stores and serves only ciphertext. The decryption key lives after the # in your link, and browsers never send that fragment with any request.
The link is the password. Anyone with the full link can read your dashboard until the key is rotated - there is no per-reader sign-in and no audit log in this mode. Rotation is one republish and takes effect at once; full revocation is rotating the key, then deleting the old file - deleted ciphertext can linger briefly at the host's edge, which is why rotation comes first. Keep the link out of screenshots, tickets, and shared notes.
Optional: Supabase backend. Sign-in is a magic link to your email with new sign-ups disabled. Postgres row-level security releases rows only to your user id, even with the publishable key. The service-role key (full write access) stays with the writer - never in this page, the repo, or the browser. Tradeoff: your data sits as readable text inside a hosted database you manage.
Either way: this page cannot phone home - the content-security policy allows connections only to this site (plus Supabase, only if you configure it). No analytics, no third-party requests, no trackers.

What it is - and is not

Hunch is the unofficial open-source dashboard for Instinct. Unofficial means exactly that: made by a user, not made, endorsed, or supported by Instinct itself. It is also a window, not a control panel - nothing here edits the work itself.

Back to your projects