The project moves to Supabase Auth and the implementation changes with it.
One persistent project memory.Every coding agent.
HARIKOS keeps Codex, Claude Code, Cursor, and other coding agents grounded in the same project memory and current repository state, across sessions.
PRODUCT WALKTHROUGH
Evidence, current Truth, useful Memory, and task-specific Context stay connected across agent work.
HARIKOS / PROJECT LOOPILLUSTRATIVE STATE
Product workflow shown with illustrative non-customer state.
The walkthrough shows a repository being connected, scanned for evidence, resolved into current Truth, and prepared as task-specific Context for an authorized coding agent.
THE PROBLEMYour repository moved forward.
Your repository moved forward.
Your agents did not.
Sessions end. Documentation drifts. The next agent inherits an incomplete story and repeats work that evidence could have settled.
The next agent begins from an outdated README and a partial handoff.
Current code, previous decisions, and the task at hand remain distinguishable.
HOW HARIKOS WORKSFrom repository signal
From repository signal
to an agent's next move.
Choose a step to follow the information that HARIKOS carries through the project loop.
AUTHORIZED SOURCEILLUSTRATIVE SIGNAL
A bounded repository scan finds relevant change.
HARIKOS reads authorized repository signal without executing project code or treating every file as useful evidence.HARIKOS OUTPUTRelevant sources selected
Repository evidence establishes current state. Memory preserves history. Context only carries what the task needs.
ONE SHARED PROJECT STATEMany agents. Many sessions.
Many agents. Many sessions.
One place to pick up the work.
Your coding agents use HARIKOS to find what happened before and what the repository supports now. Memory and current facts stay distinct.
YOUR CODING AGENTS
Codex
Claude Code
Cursor
MCP agent
Different sessions, one shared source.HARIKOSOne project memory
Memory is kept across sessions. Current claims stay tied to repository evidence.
MemoryCurrent stateTruth + Evidence
YOUR REPOSITORYGitHub project
Selected files are scanned read only. Changes prompt a refresh when verification is needed.
Evidence from the codebasePROJECT STATE / IN MOTIONSee the system resolve.
See the system resolve.
Then watch it stay current.
Two focused views show the same HARIKOS loop: a shared project state formed from connected evidence, and the lifecycle that updates it when the repository changes.
ILLUSTRATIVE SYSTEM VIEW
One state shared across the project.
The layered mesh represents Evidence, Truth, Memory, Context, and agent access staying connected without collapsing into one undifferentiated record.
Explore the product ↗ALIGNING PROJECT STATE
ILLUSTRATIVE PRODUCT MECHANIC
TASK RECEIVEDReplace Clerk with Supabasetask
middleware.ts +18 −9lib/supabase/server.ts +34README.md CURRENT
AUTH / PREVIOUSClerkVERIFIED
→AUTH / CURRENTSupabaseCANDIDATE
THE CONNECTED SYSTEMCurrent fact. Useful history.
Current fact. Useful history.
Relevant context.
Truth, Memory, and Context have different jobs. HARIKOS keeps their boundaries clear while letting them travel together.
TRUTH / CURRENT
Explore Truth ↗What the repository supports now.
Inspectable claims stay connected to source evidence, confidence, and time.
MEMORY / HISTORY
Explore Memory ↗What happened before.
Decisions, failed attempts, and outcomes persist without being promoted to fact.
CONTEXT / TASK
Explore Context ↗What this agent needs next.
A Context Pack selects the smallest useful set of current Truth, constraints, evidence, and relevant Memory.
CHANGE / CONTRADICTION
When sources disagree, the conflict stays visible.
HARIKOS records the competing evidence, tracks the change, and shows why the current project state won.
README.md / PREVIOUS
≠Authentication: ClerkSTALE DOCUMENTATIONmiddleware.ts / CURRENT
RESOLUTION / SUPABASE AUTH VERIFIEDcreateServerClient()CODE EVIDENCE MULTI-AGENT / MCP
One project state, available to every authorized agent.
Connect Codex, Claude, Cursor, or another MCP client through a revocable project-scoped token. Read current state, create task Context, and write back useful outcomes inside the same boundary.
Explore the agent bridge$
Authentication
Supabase Auth
VERIFIED · 99%
Evidence
middleware.ts:18
lib/supabase/server.ts:7
Previous: Clerk · SUPERSEDED
FREE BETAStart with a real project.
Start with a real project.
Keep every agent in context.
HARIKOS is free during beta. Connect real repositories and use the full project loop without a payment method.
3 projects · 5 agents · 30 scans per month
No card requiredHigher limits and advanced workflows are planned. Paid access is not open yet.
Ask to be notified FREE BETA / AVAILABLE NOW
Stop re-explaining your project to every agent.
Give every coding agent one current, evidence-backed understanding.
Using HARIKOS on a real project?
Tell me what it gets wrong. Your feedback shapes the Free Beta.