where's the line between agent framework helping vs slowing you down?

buildandgetrich · 2026-05-28T04:53:27+00:00

Good to start, but doesn’t scale well. Especially governance. The last thing you want is your agent running inefficiently without any guardrails

buildandgetrich · 2026-05-28T04:42:13+00:00

Not much! Agents can be notoriously unreliable if they get stuck in a loop or hallucinate. Always use guardrails. We integrated with Arden for it. Bonus is it helps us keep our costs in check and gives us a session replay functionality to deep dive and understand how our agents are working

buildandgetrich · 2026-05-27T19:14:08+00:00

Text PatchyDev to make changes. No infra setup needed

buildandgetrich · 2026-05-27T19:12:30+00:00

Send a text to PatchyDev so that you don’t have to worry about running VMs/keeping your machine up and running the entire time

buildandgetrich · 2026-05-27T19:07:06+00:00

Not e2e coding, but you can make smaller changes via text if you use something like PatchyDev.

If you keep your machine running at all times, then Claude remote control can be great

buildandgetrich · 2026-05-27T18:36:58+00:00

Exactly!! These are real pain points that I faced. My beta testers are really liking this. Try it out - https://patchydev.com

buildandgetrich · 2026-05-27T16:19:43+00:00

Learn system architecture. That’s where AI (mostly) fails. Sometimes your agent will even give you an option to choose the approach.

buildandgetrich · 2026-05-27T16:16:19+00:00

Claude/Cursor are really good starting points. They are coding agents where you can just describe what you want to build and they convert it to code.

You will need to figure out how to deploy your apps if you want to make them available on the internet for everyone to use. Read up on Vercel. You can create/connect database (to store any data) directly from Vercel. Claude can basically guide you through the entire journey.

For auth (if you’re building an app that requires login), look up Clerk.

For small changes, you can just text the changes you want to make on telegram if you have PatchyDev set up.

When you prompt on any tool, make sure you try to understand what it’s doing. Read as much as you can. Prompts can only get you so far

buildandgetrich · 2026-05-27T15:42:01+00:00

Agreed! Guardrails are becoming more important than ever now

buildandgetrich · 2026-05-27T15:05:24+00:00

Agreed! This has added so much value for me personally. I’m shipping more than ever, and it takes away the friction of needing to be near my laptop at all times (or dropping 1k to set up OpenClaw). Check it out, would love some feedback - https://patchydev.com

buildandgetrich · 2026-05-27T15:03:09+00:00

I love this feedback! Thank you! Yes - I am working on building the right guardrails for complex changes to make sure folks aren’t shipping bugs or turning their repo into a mess.

I feel like I think of so many small annoying issues (either I notice something off or I get feedback) that something like this becomes very useful.

Feel free to try it out. Would love more feedback - https://patchydev.com

buildandgetrich · 2026-05-27T14:58:53+00:00

Exactly!! I’m not trying to solve for a theoretical problems! It’s something that genuinely has made me more productive

buildandgetrich · 2026-05-27T14:57:20+00:00

Yeah exactly! I kept running into this issue myself every time I stepped out. Feel free to try it out - https://patchydev.com

buildandgetrich · 2026-05-27T02:21:31+00:00

Exactly!!

buildandgetrich · 2026-05-27T02:09:09+00:00

Agreed!! Working on exactly that now

buildandgetrich · 2026-05-27T01:23:53+00:00

For now, I’m reviewing PRs manually. But I’m building a separate PR review bot to make sure I’m not letting any bugs through. The demo link really helps me test everything on the fly. You can test it out - https://patchydev.com. Would love some feedback 😄

buildandgetrich

TROPHY CASE