Hunch is one page plus a tiny database. About ten minutes, all on free plans. Your credentials below live only in this browser.
Have an AI assistant? The fastest path: send it the Hunch repo and say "set up Hunch for me" - it does everything below with you.
1
Create a free Supabase project at supabase.com (any name, any region).
2
Add your login. In Supabase: Authentication → Sign In / Providers → disable new sign-ups, then Authentication → Users → Add user with your email. Copy the user's UID.
3
Run setup.sql in the SQL editor - paste your UID on the marked line first. It creates the table, locks it to you, and adds demo rows.
4
Point sign-in links here. Authentication → URL Configuration → set Site URL to this app's address.
5
Paste your project URL and publishable anon key below (Project Settings → API). The publishable key is safe in the browser - row-level security is what guards your rows.
6
Hand your assistant the keys. Give it the service-role key and WRITER.md. It writes plain-English updates as work happens. The service key never touches this browser.
A small private web app that answers one question: what is my AI assistant actually 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
The assistant writes. As work starts, moves, waits, or completes, the assistant upserts one plain-English row per outcome into your database, using the service-role key that stays server-side.
The app reads. This page reads those rows through row-level security with a publishable key. 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 assistant in chat - it owns the rows and rewrites them. Editing the database directly works, but its next update may overwrite your edit.
Security model
Sign-in is a magic link to your email. New sign-ups are disabled, so a stranger's email gets rejected.
Postgres row-level security releases rows only to your user id - even with the publishable key, nobody else can read them.
The service-role key (full write access) stays with the writer. It is never in this page, the repo, or the browser.
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.