r/OnlyAICoding

Hi all, I am a law student trying to build an app with no coding knowledge. I want to ask which AI subscriptions give the best value for money's worth?

Thanks all!

edit: surprised how much responses I got. I love that the vibe coding community is so willing to help. we don't have the same supportive environment in the legal industry, especially among law students as they tend to be quite competitive.

edit 2: for context, I want to build an language learning app, I myself struggle with learning chinese so I want to build the app for myself to learn chinese through flashcards that have key financial and legal terminology derived from FT, Economist, Bloomberg articles. I want to build a solution to my own language learning problems but using AI. can you integrate AI into the app to create a customised language learning app?

What are your opinions on price, features, and effectiveness for the three. Cursor is interesting because you can use any model - I understand this.

I've noticed that AI coding agents (Claude Code, Cursor, Codex, etc.) are quite good at local tasks, but they often struggle when a feature involves multiple parts of a project — frontend, backend, shared libraries, and so on.

I ran a small test to look into this.

Test Setup:

• Same starting monorepo
• Same prompt: “Implement a minimal login feature for this project.”
• Two versions:
  • Plain monorepo (no extra context)
  • Workspace with a structured context bundle (manifest + guidance files)

Results:

• Plain version: ~4m48s. Backend API worked, but browser login failed.
• With context bundle: ~7m16s. Full flow worked — browser login, session persistence, and logout all succeeded.

Splitting the bundle showed:

• The manifest helped the agent understand the project structure.
• The guidance files (AGENTS.md / CLAUDE.md) helped with execution and verification.

My friend and I originally built this system for our own internal use because we kept hitting this exact problem. We're now exploring whether it can help others too.

Has anyone else experienced similar issues when working with multiple coding agents across a monorepo? What solutions have worked for you?

Would appreciate any thoughts or similar experiences.

I genuinely cannot figure out whether what I’m doing is right or wrong anymore.

So basically, around a year ago I joined a new company. I reviewed a large part of the Android project and after that I implemented around 4–5 major features myself with a lot of research and reviews involved.

But then the AI boom started, and for the last month I’ve been heavily using tools like Codex.

Today in a meeting someone asked me how I implemented one of the recent features, and honestly I could barely explain it properly. The reason is that AI mostly wrote it. At the time I was working on it, I did understand the logic and flow, but when you write code yourself manually, things stay in your memory much more strongly.

With AI-assisted coding, I feel like you forget things much faster, and you slowly become dependent on AI even for very small things.

Now whenever I implement a new feature, I feel guilty. I keep thinking:
“I didn’t really implement this feature… AI did.”

At this point, around 80% of my time is AI-assisted coding, and the remaining 20% is me researching how to improve AI workflows and prompting skills.

Before this AI wave, developers used to spend most of their time researching architecture, standards, and engineering practices. Now it feels like people are focusing more on AI tooling skills instead.

Is this actually okay?
Are other developers experiencing the same thing?

Hi,

I'm on Pro plan, sometimes while coding I suddenly get the error that I'm on 2h cooldown.

I use it mostly in terminal, and there is an option to stop for now and continue later, don't remember exactly.

But when I select it, when the cooldown passes, it doesn't do what it was supposed to do.

Sometimes when I tell it "continue what you were supposed to do before we hit the limit", it will do something completely different.

So my question is basically what's the best way to "resume"?

Thanks!

Viele von euch kennen das wahrscheinlich: Irgendwann kommt man in ein Alter, in dem man sich ernsthaft damit beschäftigt, vielleicht doch eine Immobilie zu kaufen.

Ich merke gerade selbst, dass das gar nicht so leicht ist. Man schaut sich Wohnungen und Häuser an, macht Notizen, vergleicht Lage, Zustand, Preis, Bauchgefühl, Dealbreaker und am Ende verliert man trotzdem schnell den Überblick.

Bei mir hat das mit einer riesigen Excel-Tapete angefangen. Nach kurzer Zeit war klar: Das ist Murks. Excel ist halt Excel.

Ich habe dann geschaut, ob es schon etwas Passendes gibt. Ein, zwei ähnliche Projekte habe ich gefunden, aber nichts, was für meinen Anwendungsfall wirklich genug konnte. Da ich mittlerweile recht viel mit KI und Vibe-Coding mache, ja, ich weiß, das böse Vibe-Coding, ist daraus gestern dieses Projekt entstanden:

https://github.com/n3roGit/PickHome

PickHome ist ein kleines self-hosted Tool, mit dem man Immobilien verwalten und bewerten kann. Die Grundidee ist recht simpel:

- Immobilien erfassen, die man besichtigt hat oder noch besichtigen will

- Kriterien gewichten

- Dealbreaker definieren

- Bewertungen vergeben

- Rankings erstellen

- mehrere Personen/Familienmitglieder mit unterschiedlichen Prioritäten berücksichtigen

- am Ende einen besseren Gesamtüberblick bekommen

Dazu kommen noch ein paar praktische Dinge wie Notizen, Volltextsuche, Kalender, iCal, Besichtigungstermine, Fotos und Vergleichsansichten.

Das Ganze läuft als Docker-Container. Es ist sicher noch nicht perfekt, nicht vollständig durchgetestet und es wird garantiert noch den einen oder anderen Bug geben. Aktuell kommen aber fast täglich neue Releases, weil mir beim Benutzen immer wieder Sachen auffallen, die man verbessern kann.

Vielleicht ist es für jemanden von euch nützlich, der gerade ebenfalls auf Immobilienjagd ist oder vorhat, sich damit zu beschäftigen.

Feedback ist ausdrücklich willkommen. Wenn ihr Bugs findet oder Ideen habt, gerne ein GitHub-Issue aufmachen oder hier reinschreiben. Vielleicht kann daraus ja etwas entstehen, das mehreren Leuten diesen ziemlich unübersichtlichen Prozess etwas einfacher macht.

What the title says pls

Persistent memory keeps coming up for AI coding agents. One approach I’ve found useful: treating the knowledge layer as a compiled markdown wiki rather than just stuffing more tokens into the context window.

llm-wiki-compiler ingests docs and URLs, then the LLM builds an interlinked markdown structure. Since the output is plain markdown on disk, Claude Code reads it directly. And when you run query --save, the answer gets written back into the wiki as a page — so future queries improve.

It’s not retrieval. It’s compounding. The knowledge base gets richer instead of resetting every session.

Plain markdown, no opaque vector store, fully inspectable.

How are other agent builders solving persistent memory?

I’m working on a website using Codex and it’s my first time working with an AI tool. i wanted to know if Codex is the only tool I would need for this project? I’m just learning about AI tools so if you mention another please explain why!

i really need an ai that can code cheats for me i know something about coding but not much so i just wanna have fun

Hello everyone,

I recently had an idea for a personal AI project and I would really appreciate feedback from more experienced people.

The concept would be to create an AI chatbot "trapped" in a specific historical period, for example, between 1930 and 1933. The goal wouldn't simply be to make the AI ​​speak about the 1930s, but to allow it to respond as if it were living in that era, without knowing about future events.

For example, I would like to ask it questions like:

• "Do you think Europe is heading towards another war?"
• "Is the economic crisis temporary?"
• "In your opinion, what is the future of Germany?"
• "Will technology radically transform our daily lives?"

The AI ​​would respond using only the information, beliefs, fears, newspapers, political ideas, and cultural context available at that time.

What fascinates me is the idea of ​​recreating the uncertainty people experienced, rather than considering history in retrospect.

The problem is, I'm starting from scratch because I have no programming knowledge, let alone AI, even though it interests me. However, I'm really motivated by this project.

Do you have any advice? Where should I begin? How long will it take?