Polish the empty-state illustration
Euclis remembers every decision, blocker, and milestone — captured automatically from the places work already happens.
Q3 auth & beta
Let's go with Supabase Auth — custom JWT is a rabbit hole.
Agreed. But realtime won't work until we set the RLS publication on deploy.
Recorded a decision from this coding session: adopt Supabase Auth.
Flagging a blocker — RLS publication is required before the beta ships.
Pulled project context: 6 decisions, 1 open blocker. Everyone's in sync.
Adopt Supabase Auth, drop custom JWT
@lina · Web
Set RLS publication on deploy
Claude Code
Beta launch waits on billing sign-off
#42 · Web
Closed beta live for 12 teams
@aarav · WhatsApp
Auth keeps getting relitigated — worth a spec
dream cycle
The problem
Decisions get buried in chat. New teammates — and new AI sessions — start from zero.
Capture
WhatsApp, Claude, Cursor, the web. Euclis listens where you already work — you write nothing down twice.
Structure
Decisions, blockers, dependencies, milestones — linked, deduped, kept current. Even superseded calls stay answerable.
Shared
Your team and your coding agents pull the same brief. Call get_project_context — everyone's aligned.
Capture only ever sees one moment. So on a schedule, Euclis takes a step back and tends the whole store — the way you'd wish someone would. It merges duplicates, reconciles decisions that contradict, surfaces patterns no single note could see, and files away what's gone stale. Retrieval reads; dreaming maintains.
Consolidate
Near-duplicate decisions merge into one canonical record.
Reconcile
Contradicting decisions get linked — newest wins, history kept.
Surface
Patterns across events become insights no single capture saw.
Prune
Stale, resolved events are archived out of active memory.
Every change is code-validated — nothing is ever deleted, and open work is never touched.
Adopt Supabase Auth, drop custom JWT
Go with Supabase for auth
Stay on custom JWT for now
v1 closed beta shipped
Discussions
Discussions branch into focused threads. Ask an agent to summarize one and it answers from the whole history plus project memory — so a new teammate, or a fresh AI session, is caught up in a minute.
Are we still doing custom JWT for launch? I'm nervous about the timeline.
We said we'd revisit after the SDK spike.
+ 16 earlier repliesNew here — can someone catch me up on where auth actually landed?
Here's where auth stands
summarized 24 messages across 3 threads · 6 decisions from memory
Focused sub-discussions branch off — not one endless channel.
An agent distills any thread from its full history plus project memory.
New teammates — and fresh AI sessions — catch up in a minute, not a week.
The dashboard
The kanban is still here — drag cards, share assets, sketch on the whiteboard. Updates from WhatsApp or an agent land on the same board your team already uses.
#42 so "close 42" in chat just works.5 open · 4 members
Polish the empty-state illustration
Webhook retries with exponential backoff
Realtime board sync: debounce + reconcile
Landing page hero · v3
Team onboarding & invite links
FAQ
Straight answers about project memory, Dreaming, WhatsApp, and how agents pull the same brief.
Email is enough. No card. Phone optional. Capture from the tools you already use — or start on the web alone.
Hobby free forever · Team trial on pricing · no credit card