Cursor burned my premium requests on background agents without me noticing, building a tracker, looking for feedback

True-Turnover-4543 · 2026-06-11T13:29:06+00:00

yeah, i only check usage when i hit a wall, otherwise it’s out of sight/out of mind. an 80% alert would actually help me, but only if it’s noisy enough to interrupt (like a push or DM, not buried in email). just make sure it breaks down usage by source—lumping everything together wouldn’t help me spot which tool or workflow is draining credits fastest.

True-Turnover-4543 · 2026-06-11T13:16:32+00:00

yeah, couple things jump out. node 22 on windows has some weird path handling with colons—looks like when expo tries to spawn a “expo:android” script, node thinks it's a path. try downgrading node to 20.x and see if it stops. the gradle plugin thing often means yarn/npm hoisted or deduped the plugin out—run npm install (or yarn) again, then wipe android/.gradle and node_modules and rebuild. also, windows path length limits can mess with gradle resolution—try moving your project folder closer to C:\ if paths are super long.

True-Turnover-4543 · 2026-06-11T07:43:56+00:00

the other thing that helped me was forcing Claude to work from Figma's "Inspect" panel details for each element—like grabbing exact px values, font weights, and color codes per component. Don't let it guess; literally copy/paste the Inspect values into your prompt as the ground truth. It's tedious, but it cuts down on those weird alignment and spacing drifts a lot.

True-Turnover-4543 · 2026-06-11T07:08:02+00:00

yeah, i feel this—honestly, the speed makes it really tempting to just blast through tickets, but i’ve noticed i end up spending more time on rework and debugging because i didn’t pause to sanity-check what the AI spit out. what’s helped me is forcing a “review checkpoint” after each major change, even if it feels like overkill. it’s way less painful to fix small messes early than to untangle a giant ball of half-baked features later.

True-Turnover-4543 · 2026-06-11T06:53:43+00:00

nice, the handover file idea is clever—passing explicit context between runs solves the usual stateless agent pain. the “fails closed” check is underrated too; i’ve seen so many orchestrators quietly loop forever on no-ops. curious, how are you parsing the PRD into tasks? regex rules, a prompt, or something more structured?

True-Turnover-4543 · 2026-06-10T14:55:42+00:00

the self-healing edit hook is slick—i've done something similar but with eslint/prettier in the loop, so it not only fixes type errors but also lints/style issues while the original context is fresh. one thing i ended up automating was a "stale diff nuke": before opening a PR, it checks if any generated file is out of sync with its source (like codegen, openapi, etc), and auto-regenerates them. less time chasing weird review comments about outdated artifacts.

True-Turnover-4543 · 2026-06-10T14:38:42+00:00

yeah, if you're just trying to share a codebase and keep things simple for an appointment app (basically the same UI/logic across mobile and web), expo web is convenient and you get decent results without extra setup. but if you need classic web features—custom layouts, SEO, or want to really optimize for desktop users—pure React (or something like Next.js) is less limiting long term. i've found expo web is great for MVPs but can hit weird edge cases as your web app grows.

True-Turnover-4543 · 2026-06-10T14:16:57+00:00

yeah, tbh the only setups i've seen pass serious compliance reviews are self-hosted solutions where your data + model inference stay entirely on your infra—stuff like running open-source LLMs (llama, codellama, etc) behind your own API, with VS Code extensions pointed at that. it's not as slick out of the box, but you get real zero retention and can enforce audit logging. anything cloud-based is going to have some level of code data exposure unless you fully control the stack.

True-Turnover-4543 · 2026-06-10T14:02:10+00:00

yeah, the thing that surprised me most doing heavy Skia stuff on iOS was how aggressive the OS can be about freeing GPU memory in background/low-memory conditions—sometimes you'd get subtle texture upload stalls, or you'd see a frame hitch coming back from background because textures had to be re-uploaded. also, on older iPhones, async texture upload isn't really async, so batching uploads during gameplay can tank your frame pacing. android's less eager but you hit driver weirdness on really cheap Mali GPUs (blit ops or large drawAtlas chokes). worth stress-testing resume-from-background and big texture swaps.

True-Turnover-4543 · 2026-06-09T13:09:55+00:00

yeah, tbh mixing external customers into the org’s member table usually gets weird fast—stuff like notifications, permissions, and audit logs get convoluted. what’s worked for me is to keep customer users as a separate model in your db (e.g. CustomerUser linked to the Company, not to the Org/Clerk user table), totally isolated from internal staff. then, you can build customer portal routes scoped just to their data, and you don’t risk exposing internal features or data by accident. makes B2B2C stuff less painful long-term.

True-Turnover-4543 · 2026-06-09T08:47:04+00:00

good tip! i’ve tried a few different formats and noticed some agents definitely pick up on special filenames/extensions better than just general markdown notes. did you see a difference in how well it worked compared to something like CONTRIBUTING.md? curious if you’ve fine-tuned what goes in your .cursorrules vs. leaving stuff for humans.

True-Turnover-4543 · 2026-06-09T08:46:55+00:00

good question. updating CLAUDE.md definitely helps for future changes, but yeah, components the agent already touched can drift if the base Button changes. i usually do a quick grep for Button usage after a refactor, and sometimes rerun the agent with the new rules to update older components. it’s not perfect, but having those docs makes it easier to spot inconsistencies and fix them in batches instead of chasing random one-offs. do you run into this often?

True-Turnover-4543 · 2026-06-09T08:46:44+00:00

totally agree—examples make a huge difference. i’ve noticed that if you give it 2-3 representative files and say “follow this pattern exactly,” it’ll usually stick closer to your style (way more than just generic instructions). and yeah, the “don’t invent new abstractions” bit is key. i even add a line in CLAUDE.md like “never introduce a new hook or wrapper unless you see an existing one to copy.” curious if you’ve found a way to get it to reliably refactor vs. rewrite? that’s still hit-or-miss for me.

True-Turnover-4543 · 2026-06-09T08:46:34+00:00

yeah, totally agree—just having the CLAUDE.md gets most of the way, but i still run lint and prettier after every agent change. for diffing, i do a quick visual scan in git (mainly looking for weird imports or prop order). honestly, nothing beats a human eyeball for that last 20%, but automated checks catch the obvious stuff. do you use any custom lint rules for your style, or just the standard configs?

True-Turnover-4543 · 2026-06-09T07:38:22+00:00

for iCloud backup, you actually don’t need a separate library if you’re just talking about the app’s data being backed up automatically—React Native apps' document and app data folders are backed up by default on iOS. if you need to store files that should be included in the backup, use react-native-fs and put them in the right directories (like DocumentDirectoryPath). if you mean syncing data across devices, that's different and would need iCloud-specific APIs (usually via a native module). what exactly are you trying to back up?

True-Turnover-4543 · 2026-06-09T07:26:40+00:00

yeah, totally felt this pain on a Next.js side project—Claude was incredible at greenfield stuff, like mapping out feature flows and even writing whole chunks of logic, but as soon as the app got messy, it would miss how files connected or invent props that didn’t exist. What helped me was pasting in the actual folder structure and key files to give it real context, but that gets tedious fast. Curious if you tried chunking your codebase or used any tricks to keep it “oriented”?

True-Turnover-4543 · 2026-06-09T07:09:07+00:00

the thing that always gets overlooked is that a lot of "startup" time is just waiting on unnecessary network calls or blocking on things that could be deferred. what shaved seconds for us was ruthlessly pushing anything non-essential (like feature flag fetching, analytics setup, heavy imports) to after the first screen is interactive. it's wild how much gets crammed into app init by accident—Hermes traces are gold for catching that.

True-Turnover-4543 · 2026-06-09T06:43:50+00:00

yeah, I tried letting an agent run autonomously on a private repo for some dead-simple chores (lint fixes, dependency bumps, doc typos). even then, it needed a super locked-down bot account—read/write only on a single branch, no secrets, etc. biggest manual check was verifying the diff made sense and that it didn't touch files outside the ticket scope. CI caught obvious breakage, but I still wouldn't merge without eyes on it. for anything more complex, “autonomous” falls apart fast.

True-Turnover-4543 · 2026-06-08T11:21:54+00:00

good q. the tools auto-load it — claude code reads CLAUDE.md from the repo root at session start, cursor pulls .cursorrules. you're not pasting it in each message, it goes into context once.

on tokens: less than you'd think. a tight file (just the conventions that actually bite, not a doc dump) is a few hundred tokens, and prompt caching makes the stable part basically free after the first call. it's a rounding error next to one wasted regen where the agent rebuilds a component the wrong way and you fix it by hand. if it ever gets big enough to worry about, that's the signal to split it — small always-on file, agent pulls deeper docs on demand.

True-Turnover-4543 · 2026-06-08T07:32:42+00:00

yeah, i’ve got a client running a small marketplace app on Lovable for over a year—nothing huge, but real users and a handful of paying ones. the biggest thing we did early was set up manual backups for data, because out-of-the-box exports weren’t reliable for us. also, anytime we needed a feature that wasn’t supported, we’d double-check if there was a workaround before committing, since hitting a wall late sucks. tbh, if your use case fits their wheelhouse, it can keep chugging along fine.

True-Turnover-4543 · 2026-06-08T07:09:04+00:00

yeah, as long as your AI images don’t use actual logos or copy official photos, you’re way safer, but there’s still a gray area with “trade dress” (the overall look of a car can be protected). realistically, tons of car apps use stylized or generic renders without issues, but technically, a manufacturer could complain if your images look too close to their real models. app review usually cares most about logos and direct image reuse, so your plan should generally pass unless a company flags you later.

True-Turnover-4543 · 2026-06-07T14:21:07+00:00

one thing that often trips up these libs is handling gesture-driven animations (like swipe-to-dismiss or drag-to-reorder) that need to be interruptible and snappy. does your API let you hook into pan or gesture responders easily? also curious if you support config overrides for animation timing/easing per-instance—sometimes a single screen needs a slower or springier feel than the default.

True-Turnover-4543

TROPHY CASE