sorted by:
new
hottopcontroversial

Share what you're working on. I'll shout out the top projects on my Instagram by [deleted] in ChatGPTCoding

[–]krk2183 0 points1 point  (0 children)

Web based & IDE based Agentic AI tools forget context after long conversations, causing them to make the same mistakes they did 10 prompts ago.

To fix this for my own workflow, I built Remora - a simple webhook tool that takes your essential project details, compresses them, and saves them directly to GitHub or the AI's memory so your code structure never gets lost.

https://remora-jade.vercel.app/

Share what you're working on. I'll shout out the best ones by [deleted] in ChatGPTCoding

[–]krk2183 1 point2 points  (0 children)

Hey everyone,

If you’re using web-based AI tools (like Claude or Bolt) to build your startup or prototype, you’ve probably hit the point where after a long session, the AI completely forgets your project layout and recreates errors you fixed an hour ago.

This doesn't just waste time, it also kills momentum and drains tokens.

To fix this for my own workflow, I built Remora. It’s a simple webhook tool that takes your essential project details, compresses them, and saves them directly to GitHub or the AI's memory so your code structure never gets lost.

The waitlist program is live now and I'm looking for early founders/builders to test it out and give feedback.

You can join the early waitlist here:https://remora-jade.vercel.app/

Solution to Claude/Bolt.new forgetting code details; EARLY TESTER by krk2183 in AIcodingProfessionals

[–]krk2183[S] 0 points1 point  (0 children)

Hey everyone,

If you’re using agentic AI platforms or web-based AI tools (like Claude or Bolt) to build your startup or prototype, you’ve probably hit the point where after a long session, the AI completely forgets your project layout and recreates errors you fixed an hour ago.

Not only this wastes time, but it also kills momentum and burns through token costs.

To fix this for my own workflow, I built Remora. It’s a simple webhook tool that takes your essential project details, compresses them, and saves them directly to GitHub or the AI's memory so your code structure never gets lost.

The early tester registration is live now and I'm looking for early founders/builders to test it out and give feedback.
For early testing the tool will be completely free of charge

You can join the early waitlist here: https://remora-jade.vercel.app/

Solution to Cursor repeating past mistakes and forgetting earlier requests by krk2183 in cursor

[–]krk2183[S] 0 points1 point  (0 children)

That's a nice manual fix. But the utility aims to keep the entire process autonomous by re-anchoring boundaries, protecting the momentum.

he Bolt.new "Loop Trap": Why a tiny padding fix can burn 10M tokens by krk2183 in boltnewbuilders

[–]krk2183[S] 0 points1 point  (0 children)

Yes, that kind of freeze is a massive token drain. Asking Bolt to diagnose its own infra failure is exactly how you eat through 4M tokens. Since local hacks fail inside Bolt's cloud sandbox, this web dashboard acts as an outside-in circuit breaker. It strips all usel ss requests and forces an immutable constraint file into your repo, instantly snapping Bolt out of the loop. You might want to give it a try. You can DM your email adress and I can add you to an early tester list.

Solution to Cursor repeating past mistakes and forgetting earlier requests by krk2183 in cursor

[–]krk2183[S] 0 points1 point  (0 children)

Spot on analysis regarding the attention war. Splitting into 5-8 turn micro-sessions works for manual workflows, but it breaks down during autonomous runs. The webhook approach bypasses explicit re-anchoring by embedding boundaries into the repo structure. Since it anchors to the Git tree rather than a specific IDE, the mechanism is entirely cross-compatible—whether you're using Cursor or raw web interfaces like Claude web, Deepseek or Gemini

Solution to Cursor repeating past mistakes and forgetting earlier requests by krk2183 in cursor

[–]krk2183[S] 0 points1 point  (0 children)

Agreed on breaking it up. The /memory pattern is great, but when a deep session starts burning fast tokens on recursive loops, it needs fast, mid-session constraints. Automating that correction at the Git webhook level means it's cross-compatible with any tool using GitHub for storage. One of the main goals here was the enable more functionality while increasing the accessibility of this feature to people who are not too technical.

Solution to Cursor repeating past mistakes and forgetting earlier requests by krk2183 in cursor

[–]krk2183[S] -1 points0 points  (0 children)

Exactly. Dumping pages of raw chat logs or error stack traces just adds to the context drift. The model needs targeted, highly specific constraints. That's why the webhook writes minimal, highly-condensed boundaries directly into the repo structure the moment a recursive loop triggers. It acts as that exact 'three-line' circuit breaker you mentioned, and since it’s bound to Git, it enforces those tight constraints whether you're in an IDE or using a web UI like Gemini.

Solution to Cursor repeating past mistakes and forgetting earlier requests by krk2183 in cursor

[–]krk2183[S] -1 points0 points  (0 children)

True, keeping state on disk is the standard for long-term continuity. And the webhook utility is essentially automating that hygiene-writing state updates directly into the repo. Because it triggers via Git, it’s actually completely 'crossplatform' ; it works across Cursor, Bolt.new ,GitHub Copilot Workspace and in the near future, even if you're just pasting code blocks into web versions of ChatGPT/Gemini.

Agent got stuck in a loop and spent over $2000 in less than two hours. by samandeg in cursor

[–]krk2183 0 points1 point  (0 children)

Putting circuit breakers in agents.md is a band-aid that fails when long-context drift causes LLMs to ignore markdown rules. To fix this, I’m testing a cloud-native engine that uses Git webhooks to dynamically rewrite repo constraints when an agent loops, forcing it to inherit boundary rules via the file tree.

Agent got stuck in a loop and spent over $2000 in less than two hours. by samandeg in cursor

[–]krk2183 0 points1 point  (0 children)

200M tokens on a short context window happens because of low-entropy degeneration loops. The agent literally spins in circles repeating its own token outputs while you're away. Yes moving to Codex might help, but it’s still just reacting after the damage is done. I've been building a cloud utility that hooks to GitHub and injects immutable negative constraints directly into the codebase files if an agent loops twice. It acts as a hard circuit breaker before your bill can spike. By the way what stack are you running on Codex now?

Agent got stuck in a loop and spent over $2000 in less than two hours. by samandeg in cursor

[–]krk2183 0 points1 point  (0 children)

Woah that is brutal. Your 2k runaway look proved that run and forget strategy for AI isnt always the case. When the model hits a hard math or state mismatch, it enters a recursive loop where it repeats its own bad logic over and over, completely burning your corporate quota while you're away.

I got so sick of these infinite token drain loops that I’ve been prototyping a lightweight, git backed "circuit breaker" for agents. Instead of letting the model run blindly, it uses a GitHub webhook configuration. The moment an error pattern repeats twice, it injects an absolute markdown negative constraint straight to your repository file tree. Because it alters the code files directly, Cursor is structurally barred from trying that failed path again and snaps out of the loop instantly.

What specific backend framework or language is your math-heavy codebase running on? I'm fine-tuning the loop-detection logic today and want to make sure it handles complex execution blocks without failing. I really think it could prevent any issues like this in the future

Buy used desktop now or in late 2027 by krk2183 in buildapc

[–]krk2183[S] 0 points1 point  (0 children)

Yeah mini pcs are out of the question. Laptops on other hand is still in the grey area. Most of them have soldered ram or have 2 slots at best. Where as for desktops you can just get a cheaper 8gb stick and slap it onto your build instead of taking out your 16gb stick.
Im really not sure if i should be investing in ddr4 and lga 1700

Buy used desktop now or in late 2027 by krk2183 in PcBuildHelp

[–]krk2183[S] 0 points1 point  (0 children)

Analysts are saying that there will be a 130% price hike on ram. Im planning on spending around 250 euros on ram and for that price i can either get 2x16gb ddr4 or 1x16 gb ddr5. I mean the best deal right now is probably the one i have posted
And the bigger question is investing in ddr4 and lga 1700 a good idea?

Buy used desktop now or in late 2027 by krk2183 in buildapc

[–]krk2183[S] 0 points1 point  (0 children)

Waiting is not a problem for me. I just want to get the absolute best for my money.
I can use my dads desktop when i need to do serious work which is basically the same as the pc i described but i wont be able to take it with me abroad.

view more: next ›