r/Indiehacker

📣 We want to hear from you on a side project that is moving fast. Android only for now.

What is it?
My wife and I realized we had zero visibility into our food spending. We'd guess $600 a month. Well, turns out it was over $900.

So I built BiteSpend. You snap a photo of your receipt (or manual entries), and AI extracts every item, price, and store in about 3 seconds. After a few weeks it starts telling you things like:
- "You're eating out 5x/week — cutting once saves $140/month"

- "You've used 82% of your grocery budget with 12 days left"

https://preview.redd.it/r05oc4k6kptg1.jpg?width=1080&format=pjpg&auto=webp&s=acd2ed109fd65146f4872db6bf8cfa38ea9e6377

Food is the biggest controllable expense for most families (avg $12,700/year per USDA), but nobody tracks it at the item level.

Still early — collecting emails for when we launch on the Play Store. Would love feedback on whether this solves a real problem or if I'm building something only I want.

🔗 Link in the first comment ⬇️

Hey everyone — I've been working on this for a while and wanted to share it.

 The problem: I watched a friend vibecoding — shipping features straight from ChatGPT into his repo. No branches, no review, just paste and push. He was tracking bugs and feature requests in a notepad. An actual notepad. It worked until it didn't — broken deploys, no idea what the AI changed, and zero visibility into what anything cost. I figured there had to be a better way to let AI agents do the work without losing control. 

What I built: CodePylot — a project management tool where AI agents are first-class team members. You write a story on the board, an agent picks it up, creates a branch, writes the code, and puts it up for review. You read the diff, approve
or reject, and it merges.

The key thing: nothing ships without human review. The approve button is literally disabled until you've viewed the diff. The diff viewer flags risky patterns — hardcoded secrets, eval(), raw SQL, XSS vectors, debug logging. It's trust, but
verified.

What makes it different from just using Cursor/Copilot:

• Agents are persistent. They have schedules (cron-based heartbeats), memory of past rejections, and organizational hierarchy. They learn from your feedback.
• Multi-provider. Not locked to one AI. Supports Claude, OpenAI, Ollama (fully local, zero cost), or any HTTP webhook. Swap providers per agent.
• Budget controls. Set spending limits per agent, per project, or org-wide. Soft warnings at 80%, hard stops at 100%. Agents auto-pause when budget is hit — no surprise bills.
• Goal alignment. Link stories to company/team/project goals. The goal context gets injected into agent prompts so they're working toward something, not just closing tickets.
• Review gate is server-enforced. It's not a frontend-only check. The API returns 422 if you try to mark an agent story as done without reviewing it. Can't bypass it.

Stack: Next.js (App Router) + TypeScript + Prisma + PostgreSQL + Tailwind + shadcn/ui

Free tier gives you 3 projects, 15 stories/project, 1 agent, and 15 AI rewrites/month. Enough to try it out for real.

Happy to answer any questions about the architecture, the agent system, or anything else. I've been pretty deep in the "how do you actually trust AI-written code" problem and have some opinions.