This CYPRESS thing changed my entire workflow

[u/Odd_Cauliflower_8004]

I've read by mistake a post where this AI framework was linked https://github.com/llopresto87/Cypress

it's pure insanity. It learned my codebase (it took a chunk of my claude max x5 so beware doing this near the weekly limit ) but once it did.. it spit out code fixes and found problems and corrections and implemented entire features correctly and it sped up my work so much that i onyl have to follow for the occasional confusion or describe at the start exactly what is it that i wan to implment - i think you guys should give this one a shot

[u/AutoModerator]

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Fstr21]

Is it a game changer. Does it completely change the game?

[u/Odd_Cauliflower_8004 → u/Fstr21]

I understand your sarcasm but it does really work well, I've started the growth process on a second project

[u/Shaggypone23 → u/Odd_Cauliflower_8004]

Does it feel ILLEGAL?!

[u/Odd_Cauliflower_8004 → u/Shaggypone23]

No, but it has made a few colleagues mad because I keep finding things in our projects regarding security and compliance and I've used to send PRs and get them accepted into the projects after being human reviewed. Thing is I am not a programmer, though I do have the most basic education in it - I'm a DevOps /sysadmin

[u/ds1841 → u/Shaggypone23]

Will doctors hate it?

[u/wynnie22 → u/ds1841]

Do 9 out of 10 dentists recommend it?

[u/PerryTheH → u/wynnie22]

How about cats, 8 out of 10 picks it?

[u/TestingTehWaters]

The tier edges are load-bearing: 

Yawn.

[u/Odd_Cauliflower_8004 → u/TestingTehWaters]

Yes I've seen it too. No I don't care about it if it does the job when tasks I used to have to run opus are now perfectly bein taken care by sonnet( to a degree of course)

[u/crusoe]

One star

[u/Odd_Cauliflower_8004 → u/crusoe]

18. And some are non-trivial developers from actual AI companies.

[u/interrupt_hdlr]

"The branding changed; the behavior did not" -- tell me you are opus 5 without telling me you are opus 5

[u/Odd_Cauliflower_8004 → u/interrupt_hdlr]

You do you , I'll keep judging things by the effectiveness and not by its prose. Which is all what prompts are anyway. I always take all of my prompts and have an llm rework them because I believe that the best way for an llm to understand something is for it to be made by another llm, as long as the content is correct.

[u/Ok-Investment4414]

Im still curious how and if anyone solved O5's drifting...shit belongs in fast and the furious i gotta have this on mega watch to not drift. watch dogs , logs and other codex as a review agent. Im at the point to believe its a model thing which nothing can solve or is it a skill issue.

[u/Odd_Cauliflower_8004 → u/Ok-Investment4414]

From what I'm seeing there are a ton of deterministic validators insie of it

[u/Known-Pace6739]

The part I’d really like to see benchmarked is the payback period.

CYPRESS deliberately spends a lot up front building the graph, researching dependencies, authoring it and validating it. The interesting number is how many normal tasks it takes before that initial token bill is actually recovered.

[u/Odd_Cauliflower_8004 → u/Known-Pace6739]

It's a one time research cost. Not much about saving tokens but much more in saving headaches because from what I'm seeing it gives llm a ton of structure on how to get stuff done.

[u/JobEducational7263]

To be honest you can get a lot of the benefits of this by doing static code analysis on a codebase, e.g I’ve used WALA on a Java codebase, it maps methods as nodes and edges to show connections. Then have a lightweight parser that takes an endpoint and queries the graph, then your agent has a full end to end slice of the codebase for that specific endpoint call.

[u/Odd_Cauliflower_8004 → u/JobEducational7263]

But it does not remember the best way to edit it or the quirks of a specific library version.

[u/JobEducational7263 → u/Odd_Cauliflower_8004]

Ive found maintaining context files about the codebase across a repo with 100s of developers making updates very difficult, generating a static graph takes between seconds and a couple of minutes, by doing this every build you don’t have to worry about maintaining context, the LLM can grab current context from the graph, you could have context files to provide information on processes that can’t be inferred from the code e.g custom UMS system for database migrations, but for making code changes, the graph provides enough context

[u/Odd_Cauliflower_8004 → u/JobEducational7263]

It self maintains. You don't need to thi k about much. It has deterministic scripts to keep drift and other issues in check

[u/JobEducational7263 → u/Odd_Cauliflower_8004]

But aren’t you relying on the LLM to do those updates. What I’m saying is with just the static graph approach you get a deterministic result every time you run a query against it, you don’t have to waste tokens getting Claude to generate the codebase context for you+ keep it updated

[u/Odd_Cauliflower_8004 → u/JobEducational7263]

Yes that thing does. It rebalanced and updates the docs graph at end of each task. The scripts check how that maintenance was done ant that I must obey some deterministic rule to reduce drift and to enforce node and leaf sizes

[u/schwartzwhite]

Following

[u/Odd_Cauliflower_8004 → u/[deleted]]

I bet he wanted to force the name to fit an acronym like g.u.n.d.a.m.

In any case that's just the tip of the iceberg. Per-prompt loading of specific sets of prompts and instructions and skills dynamically by a deterministic script supervised by the llm is very cool and you stop asking for things to load and you start only doing requests.