how do i get out of this death loop of Apying all changes

ticket # 401894 - 6 days . no response
ticket # 402232 - 2 days no reponse leavin ai guy
ticket # 402830 - Migration of images to our server has gone into a death loop and applying changes.. applied over 40 times ut still doesnt complete.

whadday i do . Replit says just keep going get replit team to bulk apply but replit support is dead

I can't republish. It says something about a cahced failure. I emailed replit, but really not trying to wait 3-5 days or however long it takes to fix this. Anyone have suggestions? So frusturating, being in the middle of something and just having to completly stop

You spend hours shaping an agent:

• what tools it can touch
• what it should ask before acting
• what counts as risky
• when it should stop and clarify

Eventually it mostly behaves.

Then the surface changes: new runtime, new coding tool, new MCP server, new workflow…

…and suddenly you're re-explaining the same expectations all over again.

Feels like a lot of this stuff currently lives in prompts, habits, and the operator's head instead of surviving across surfaces.

Curious how others are handling this.

Prompts? Policy files? Wrappers/hooks? MCP? Just accepting the drift?

I’ve been building a mobile app where users earn coins from their daily steps and compete on weekly leaderboards.

Main idea is making fitness feel more like a game instead of just another boring step tracker.

Current features:

Step tracking
Coins for walking
Weekly rankings
Gold / Silver / Bronze rewards
Premium subscription features
Social competition system

Tech stack:

Replit
React Native / Expo
RevenueCat
Clerk auth

I’m currently working through the play store publishing process and improving retention/game mechanics.

A few things I’d genuinely love feedback on:

What would make you open an app like this every day?

What features would instantly make you uninstall it?

Trying to build this properly instead of rushing another generic fitness app.

I’ve been vibe coding for about 2 years now. Early on I made every mistake possible — jumping straight into Lovable/Bolt/Cursor with a half-formed idea, watching the AI confidently go in completely the wrong direction, then spending hours iterating trying to fix it.

Over time I figured out how to prompt properly. Now I rarely need more than 2 or 3 iterations to get something solid. The AI builder hasn’t changed — my input has.
The difference is almost entirely in what goes in at the start. Most people skip the thinking and go straight to building. That’s where the wasted time and money happens.

Curious if others have found the same — a few questions:
•How long do you typically spend prompting before you get something usable?
•How many iterations does an average project take?
•What’s the most frustrating part of the process?
•Have you found anything that helps — templates, frameworks, a certain approach?

Not selling anything, genuinely researching the problem. Would love honest answers — especially if your experience is “actually I don’t struggle with this at all.”

Was wiring token tracking into our Governor and ran into something that's been bothering me.

If one LLM reasoning step produces three tool calls, and your observability stack attributes the same token spend to all three events, your downstream analytics are mathematically wrong. Not slightly wrong. Structurally wrong.

Concrete example from a single agent session I ran:

• Naive event-level aggregation: 14,436 prompt tokens
• Attributed correctly at the reasoning-step level: 4,812 prompt tokens
• A 3x overstatement, silently, on one workflow

The fix is straightforward: every reasoning step needs an identity (we use llm_turn_id), and token spend attaches to the step, not to each downstream tool call. Aggregation becomes dedupe-safe by construction.

What's been bothering me more is the second-order implication.

In non-deterministic agent systems, the normal ways we think about correctness start breaking down. One of the things that starts replacing it is cost. Retries cost money. Loops cost money. Reasoning drift costs money. Every operational pathology shows up, eventually, in tokens.

Which means cost stops being just billing telemetry and becomes one of the few accountability surfaces that survives non-determinism. But only if the attribution is structurally correct. Otherwise you're not measuring agent behavior. You're measuring an artifact of how your trace events were aggregated.

Curious whether others are also starting to read cost as a behavioral signal rather than just billing, or if I'm reading too much into a single workflow.We found a 3x token attribution distortion in a single agent workflow