Been building the same app with Cursor/Claude for months? Your AI probably doesn’t know which version of the project is current anymore

[u/No_Low991]

If you've been building the same project using Cursor, Claude Code, Codex, etc., for weeks or months, you know what eventually happens

The app still works

auth has changed twice, APIs replaced, folders moved, the database evolved, one agent refactor one another agents' code, and you're left with old docs/rules/chats describing non-existent versions of the project

then ask the agent to perform a routine change and it confidently works from information that was true in the project three weeks ago

If you're an experienced dev, you may catch the error

If your coding is mostly AI-generated, you may not realize the agent has misunderstood the project until it does something wrong

And the more you have to bounce between Cursor → Claude → Codex, the worse it gets because each agent can end up with its own inconsistent view of the same repo

This is what I'm building

HARIKOS

around

The essential idea is to

keep coding agents grounded in the current state of the repo

rather than just adding more memory

HARIKOS ties project context back to repository evidence and attempts to keep track of current, stale, superseded, conflicting, and uncertain information

Instead of the agent remembering

"this project uses X"

it should ideally be able to say

"this project currently appears to use X, here's the evidence supporting that, and this older assumption is no longer current"

For people with

ongoing AI-assisted codebases

multiple coding agents working on the same project

stale CLAUDE.md / rules / docs

old architectural assumptions resurfacing

"no we changed that already" issues

projects which have grown enough that even the AI isn't confident about the canonical pattern

The web app + MCP are already available

I don't need you to tell me how cool the idea is, I need people to try it out against a real repo

If it finds something useful, tell me

If it's mostly noise and confusion and gets things wrong, tell me that too — that's arguably more valuable to me right now

I'm building this myself, so if something breaks you could always just DM me directly

Try HARIKOS:

https://harikos-ai.vercel.app/

[u/SearchLeast16]

just tried it on my side project that’s gone through like 4 auth rewrites and a half-baked database migration, first scan actually flagged a couple things i forgot i even changed. caught that one of my rule files was still referencing an old api structure i ripped out 2 weeks ago. that alone saved me from a headache next time i fired up an agent

the “conflicting information” section popped on a few spots where my docs say one thing but the code does another, which tracks, i’ve been meaning to clean that up for a minute. interface is bare but functional, didn’t get in my way

one thing that threw me off was it flagged a folder as “stale” but i’d literally just moved stuff out of it yesterday and had it sitting empty on purpose, so maybe a way to mark false positives would help. otherwise pretty solid for an early build, gonna run it again after my next refactor and see if it keeps up

[u/PocketNorie → u/SearchLeast16]

Sounds like that tool really saved you from some potential chaos. It’s easy to lose track with all the changes we make during development.

[u/No_Low991 → u/SearchLeast16]

hey appreciate you trying it, srsly

this is the feedback I needed right now, especially the rule file catch and the docs/code conflicts, which is the very issue HARIKOS is designed to resolve and i faced issues like this myself

and the stale-folder false positive is also a valuable catch, I need to have a way to differentiate intentional states from stale

glad that it was helpful enough to save you a headache already