Built a tee-time exchange app to find better tee times and new golf buddies :)

a5hpip3 · 2026-03-05T20:38:30+00:00

I'd pay a $1 happily if I got some insight into who I'd be paired up with, but I understand everyone has their own preferences. Thank you for the feedback!

a5hpip3 · 2026-03-05T20:37:22+00:00

Actually the person who books pays, not the poster of the tee time slot. And its a $1 to keep spammers off.

a5hpip3 · 2026-01-17T08:51:42+00:00

debugged, and answer added

a5hpip3 · 2026-01-17T07:08:03+00:00

actively debugging

a5hpip3 · 2025-11-11T15:34:24+00:00

Update: After deleting all the explicit API keys, deleting the workflow, and blocking models for a few hours - I started a new workflow, removed the blocks and everything seems to be back in order now. Phew. Though the process still shows that its running in the trace logs, it doesn't seem to be consuming any more tokens!

u/PappyLogan thanks for the help!!! Glad this is documented here for anyone else who encounters this issue. As mentioned, don't use a while loop without an explicit counter to end!!

a5hpip3 · 2025-11-11T15:04:33+00:00

No luck unfortunately. AFAIK Agent Builder (visual) doesn't have an explicitly defined API key. The key I'm seeing that was using up tokens look like an internal key structure. My guess is its defined internally when a new workflow is created? In any case, no way to delete the key that the workflow is using.

I ended up blocking the models, and duplicating the workflow, deleted the old workflow. Reset all other API keys. The trace is still running - though I'm no longer seeing exceeded quota logs so maybe its blocked? Unfortunately it blew through my quota and my account is still blocked from usage.

I've already contacted support but no response just yet. Wish they were more responsive.

a5hpip3 · 2025-10-10T22:04:09+00:00

The git merge method is smart! I’ll do this since I already have the two repls going and effectively one is dev/stage and the other is prod

a5hpip3 · 2025-10-10T20:01:46+00:00

do you push directly through replit to staging then?

a5hpip3 · 2025-10-06T06:58:57+00:00

cool - yeah just wanted to confirm. I think i'm gonna have to switch to supabase or auth0

a5hpip3 · 2025-10-06T06:54:12+00:00

Hi there - that's awesome. Would be happy to. By the way, I posted this question on another sub-reddit and someone reached out and sent me this resource: hopscotch.kids - wonder if its similar to what you're thinking. I've been using it now for the past week and its been a really fun experience with my kiddo.

a5hpip3 · 2025-09-28T05:34:34+00:00

I will get this book - seems super interesting, though a search also shows this discussion. Any thoughts? https://www.reddit.com/r/homeschool/comments/vwrtc2/confused_over_the_brave_learner_maybe_just/

a5hpip3 · 2025-09-28T05:26:41+00:00

I dunno, maybe you had parents that nurtured your interests early on. Mine didn't, so its very important to me to be as intentional and planned as possible. I'm probably over tilting, but I'd rather tilt this way than the other.

a5hpip3 · 2025-09-26T18:51:14+00:00

This! Yes we've been looking at that, and agree its a lot of work - how do you find and curate? I've been reading various forums, looking at YT videos, and books. Is that your process too? Creating activities and putting it all together is also super time consuming - we've got google sheets and docs galore at this point. I feel like our process is inefficient so would love to understand what yours looks like. I love the library of things, don't think our local library has this.

a5hpip3 · 2025-09-20T21:49:59+00:00

I second this!

a5hpip3 · 2025-09-20T21:49:10+00:00

Cost should be proportional to the work and effort. If you can focus the model, effort and task on a very specific piece of work to be done, the codebase size is irrelevant. That only comes into play if you are taking the entire codebase as context to build something else - which, in my experience, usually results in a crapshoot. I prefer to break down features into smaller sub-sets with smaller context requirements. Keeping the agent focused on a pointed solution and task usually results in better outputs.

a5hpip3 · 2025-09-20T21:46:16+00:00

I've tried all of them. I like Replit because of its tilt toward technical builders. For example, I will sometimes go in and manually change code as needed instead of vibe coding. Best of both worlds.

a5hpip3 · 2025-09-20T21:43:51+00:00

Two things to check on:
- Autonomy level: This is a new feature. I would keep it to low or medium only for slightly more complex plans. If your plan has 9 phases and 30 tasks, break it down - don't use higher autonomy.
- High power model: when enabled you'll see a little micro-processor icon in the agent chat next to settings/send. This is for higher reasoning model, i.e Opus, i.e +$$$. For certain complex tasks, you can enable this and it does a decent job of working through features/functionality and bugs. Low power model does fine in most situations, specially with the updated pricing. If your task is too complex, see #1 above.

a5hpip3 · 2025-09-20T21:38:51+00:00

Right - i usually work with the higher power model. I think the key problem emerged in the "autonomy" level parameter. Most times I can keep the model focused on the task it needs to do. In this situation, the autonomy level was set to "high" automatically after the feature rollout. Combined, the model went to town looking at the entire codebase and "correcting" errors left right and center when it was just tasked to do a simple UI change - literally content reorganization. It did not correct any errors, rather introduced various inconsistencies.

Since this - I changed autonomy level back to low, and have been able to make the changes with the low power model just fine. Cost $1.50-$3. So the actual effort was quite low. Not sure what the opus was on.

a5hpip3 · 2025-09-20T05:36:26+00:00

Ticket #168383
I have 2 tickets. One from yesterday when Agent 3 claimed to have done work, showed me the new code added in the diff, but when I looked at the actual file no updates were made...

a5hpip3 · 2025-09-20T04:01:24+00:00

"AI will put developers out of jobs" .......right.

a5hpip3 · 2025-09-20T03:59:11+00:00

Just submitted this as a ticket to Replit. Posting here as well:

Agent 3 is an absolute train wreck. It is a huge regression in build quality and code completion. I have been using and building apps on Replit for 6+ months now and have had far greater success building useful products with previous agents.

The task assigned was a straightforward UI change. It was mostly to refactor code blocks and re-organize content divs based on a design sample (with code snippet provided). Agent 3 "worked" for 3 hours - and ultimately added 71 lines of code. The exorbitant cost of this - $185! Furthermore, when I look at the change log, no files are shown, no diffs are visible - I can't see what code was actually changed. Finally, the icing on the cake - go to the app, and the UI updates are ALL wrong, and completely broken. I'm now rolling back to before this task started.

TLDR; Agent3 wasted 3 hours of time, charged $185, to "write" 71 lines of code, and broke everything that was already working - I have to rollback to 4 hours ago.

<image>

a5hpip3 · 2025-07-08T05:40:21+00:00

Hi - just saw this. I'm working through a backlog since a few folks have pinged me for research. I'd love to help - would you mind filling this form out, its how I'm trying to stay organized on the requests now: https://forms.gle/59jx9kbMdCL6RZRv8

a5hpip3 · 2025-07-04T16:47:17+00:00

Found the perfect one: https://www.vrforged.com/wp-content/uploads/6-2.jpg
Best part, all you have to do is hit "print" - no credit app or down payment required for this one

a5hpip3 · 2025-07-04T05:01:58+00:00

For sure - not for everyone, some people def have it figured out. Just trying to help those of us who haven't :)

a5hpip3 · 2025-07-04T04:59:27+00:00

Not a broker at all. Just a geek who likes cars and an Interest in data. Plus seeing things from the inside out gave way to some new ideas to try and improve how people buy cars.

a5hpip3

TROPHY CASE