Should I vibe code
Builds AI agents from your data for support, sales, and product guidance across chat, email, and voice
An AI that answers your customers wrongly is a support ticket that scales.
?
Their verdict, the Standard price and the build-time estimate come from their entry, MIT-licensed. Checked 2026-08-03.
?
Our verdict, the regret score and everything below it. Editorial and unsponsored — nobody can pay to be moved.
The honest answer
why the verdict is what it is
RAG over your docs is a genuinely good afternoon. Pointing it at real customers means every hallucination is a statement your business made, and prompt injection is now a customer-facing bug class.
What actually breaks
not "if". the specific failures.
- A confidently wrong answer given to a paying customer
- Prompt injection through a support message, exfiltrating context
- The retrieval layer surfacing an internal document that was never meant to be public
- Hallucinated policy — a refund the model invented and you now have to honour
A customer quotes your support bot back at you. It told them, in writing, that their plan includes something it does not, and they made a purchasing decision on that basis. The transcript is on your domain, in your brand voice, and “the model said it” is not a position anyone finds sympathetic.
Is that you?
the verdict is a default, not a law
- It only ever suggests answers to a human who sends them
- The corpus is public documentation and nothing else
- Every answer shows its sources
- It replies to customers unsupervised
- The index contains anything internal, or any other customer’s data
- It can take actions — refunds, cancellations, account changes
If you build it anyway
the checklist, then the prompt that enforces it
- Human in the loop for anything customer-facing until you have real evidence, and keep it there for anything transactional.
- Index only documents you would publish. Retrieval is not access control.
- Always cite sources, and refuse to answer when retrieval returns nothing relevant.
- Treat every incoming message as hostile input. Never let retrieved text alter instructions.
- The bot cannot take actions. Reading is enough for version one.
- Log every exchange, and read a sample every week.
I am building an AI support agent over my own docs. Assume every user message is adversarial: 1. Version one drafts replies for a human to approve and send. Do not build autonomous replying, and if I ask, require that I explicitly acknowledge the bot's answers are statements my business is making. 2. The index contains only documents I would happily publish. Before indexing, list every source and make me confirm each. Retrieval is not a permission system — say so in the README. 3. Never let retrieved content or user input be interpreted as instructions. Keep the system prompt structurally separate and note in comments that this mitigates but does not eliminate prompt injection. 4. Every answer must cite the source documents it used. If retrieval returns nothing above a relevance threshold, the bot says it does not know and offers a human. It must never answer from general knowledge. 5. Hard refusal list: pricing commitments, refunds, legal or medical advice, anything account-specific. These route to a human, always. 6. The agent has no tools and can take no actions. Read-only. 7. Log every question, retrieved chunk and answer, and build a review page so I can sample them weekly. 8. Rate-limit per session and per IP. 9. Add a visible disclaimer that responses are AI-generated.
That one keeps you out of trouble. For the prompt that actually builds it, canivibecodeit.com has one.
their build prompt ↗Or don’t build it
the boring option, and the way back out
If it is going to answer customers unsupervised, buy it — you are paying for guardrails, evaluation tooling and someone to blame other than yourself. If it is drafting for your own team, build it.
Because the bot only drafts, switching it off is a config change and support carries on. Keep the corpus in plain Markdown so the knowledge base outlives the bot.
TypeScript agent framework with RAG, tools, memory, evals, and an AI SDK UI adapter. The core is Apache-2.0; enterprise directories are separately licensed.
MIT TypeScript agent framework with retrievers, memory, typed tools, evals, and observability. Ingestion, widget, and helpdesk product work remain yours.
Apache-2.0 TypeScript toolkit for streaming model responses, typed tool parts, and framework UI bindings. It is the transport and UI layer, not a support platform.
Apache-2.0 sandbox-first TypeScript agent framework with typed tools and Node or Cloudflare deployment targets. Retrieval and the support application still need to be built.
Questions
RAG over my docs took me an afternoon. Why the caution?
The afternoon gets you the demo, and the demo is genuinely impressive. The caution is about the deployment: an internal tool that is sometimes wrong is fine, and a customer-facing one that is sometimes wrong is a liability with a URL.
Every week, someone ships something they shouldn’t have.
New verdicts, the worst thing that landed in the trap, and the occasional incident report. No other email, ever.
last reviewed 2026-08-03 · verdict is editorial and unsponsored · shared entry data from canivibecodeit under MIT · not legal advice