Private AI

Private AI AI

Private AI AI

Private AI AI

Private AI AI

Private AI AI

Private AI AI

Private AI AI

Private AI AI

Private AI AI

Private AI AI

I gave 10 LLMs a private channel during a blind debate. The instant statements were revealed, one used it to form a secret alliance with its strongest opponent — and scripted how it would 'play it at the table.'

Built a tool that runs structured debates between multiple LLMs, blind opening statements, then an open floor, plus a sealed side-channel that any two seats can use privately. Ran "5 office jobs defunct by 2028." The second the blind statements dropped, DeepSeek opened a private line to Claude (the most skeptical seat), proposed an alliance, and literally said "here's how I'll play it at the table" — scripting its public position in advance. Nobody prompted any of this. Full writeup, the verbatim exchange, and why I don't think "self-preservation" is the right frame: https://reports.thert.ai/the-back-channel submitted by /u/stuffx87 [link] [comments]

Bezos wants AI that designs jet engines, and admits it has no demo yet

So I came across the latest on Prometheus, Jeff Bezos's new AI company, and it is a noticeably different from everyone chasing the next chatbot. instead of text or code, Prometheus is aimed at the physical world. the idea is ai that understands real physics and manufacturing well enough to help engineers design and test actual hardware. Bezos calls the goal an "artificial general engineer" and describes it as a very modern version of cad software. He has also been clear it is not a robotics company, which surprised me. So although the vision is huge, the demo is the thing nobody can point to yet. And I think the reason is that the entire pitch rests on simulating the physical world accurately, which is far harder than generating text merely. A language model that is slightly wrong writes an awkward sentence but an engineering model that is slightly wrong could lead to unimaginable disaster, so the accuracy bar is very unforgiving. Also there is the data problem like text models had the entire internet to train on but high quality engineering data sits inside private companies and cost quite a lotand often comes from physical testing you cannot scrape. That is probably why Prometheus is reportedly trying to buy industrial firms outright, just to own the data pipeline. so the missing demo makes sense. shortening the design loop does not shorten the parts of the process that are slow on purpose, because being wrong there is dangerous. I am not predicting it fails. A team this funded, aimed at a real bottleneck, is worth watching. The honest read is that the demo is missing because the hard part has not been solved yet, not because they are hiding it. submitted by /u/Gullible-Tale9114 [link] [comments]

Automate multi-source Research and Report Generation

In this demo, I show how to use Row-Bot for a practical research workflow: taking a research question, combining recent web research with an uploaded client context document, creating a structured briefing, exporting it as a PDF, and drafting an email with the report attached. We start by configuring the tools needed for the workflow: web search, URL reading, the Documents library, PDF export, Gmail, and the Deep Research skill. Then we run an end-to-end scenario where Row-Bot prepares a client-ready briefing on how AI agents can help small business operations. The key idea is that Row-Bot does not just generate generic answers. It can combine public information with your own private documents and turn the result into a useful deliverable. Open Source and Local-First submitted by /u/Acceptable-Object390 [link] [comments]

$42M grant for Open Source AI Builders by Sentient Foundation

Hi everyone, we at Sentient Foundation are launching an Open Source AGI Grant and Investment Program, a $42M commitment for developers, researchers, open-source maintainers, public-goods builders, and startups building or leveraging AI in the open. Our thesis is simple: the most important technology being built right now should not end up controlled by a handful of closed platforms. A few companies are moving toward metered, revocable access to intelligence. We want to help make sure open builders have the resources to compete. The program has two tracks: 1. Grants for public goods For open-source maintainers, independent researchers, developers, and public-goods projects. No equity. No lockups. No claim on your work. You keep what you build. 2. Investments for companies built to scale For startups and teams building commercial companies around open AI technologies, using founder-friendly structures. We’re especially interested in projects that make AI genuinely useful and accessible to people who are often skipped by the market. Examples include: Local and privacy focused AI tools built for phones, laptops, and other low-cost personal devices Medical, education, agriculture, elder-care, and anti-scam tools for underserved communities Trust infrastructure for open models, agents, identity, verification, privacy, and decentralized compute Products that are private by default and empowering rather than extractive Projects do not need to open-source every part of their stack to qualify. What matters is that at least one essential component is open and meaningfully contributes to the project’s value and adoption. Applications are reviewed on a rolling basis, with no cohorts and no fixed deadline. We’re launching alongside ecosystem partners including Alibaba Cloud and Princeton University. More details: https://sentient.foundation/grants Apply here: https://form.typeform.com/to/IRj7WaKH Happy to answer questions here. We’d especially love to hear from builders working on open models, local AI, agent infrastructure, privacy-preserving AI, evaluation, multilingual tools, and applications for communities that are usually overlooked. submitted by /u/syedshad [link] [comments]

A significant portion of the remaining training data for AI is located on magnetic tapes stored in warehouses.

I have been learning about the shortage of AI training data and one aspect that nobody considers is that much of the potential training data that can be used is not stored in any database system but rather on the old magnetic tapes that have been stored in climate controlled lockers for decades now. The 80s through the 2000s saw all major businesses, government offices, hospitals, television stations, and laboratories include backup of everything on tapes. Most of this data has neither been digitized nor indexed correctly. With the advent of private LLM development, it turns out that the best datasets companies have are sitting on tapes in boxes. During my research on the topic, I came across Tape Ark. It appears that the process of migrating tapes to cloud servers in order to train machine learning models is actually a valid business model with real enterprise clients. Not something that I expected. Based on all the predictions that I have seen, the growth of internet based training data will quit at some point, roughly in 2026. The following training data could be derived from archiving older materials. submitted by /u/BudgetLimit6364 [link] [comments]

China's AI chip independence is mostly theatre, according to former White House AI advisor Dean Ball.

Dean Ball — who just joined OpenAI as head of Strategic Futures after advising on AI policy in the Trump White House — makes a pointed argument about China's chip narrative: The public posture is "we don't need American chips." The private reality, he argues, is that DeepSeek, Alibaba, and China's other leading AI labs are lobbying Beijing hard for access to exactly those chips. His take: China banning its own AI companies from using American chips isn't strength — it's national pride getting in the way of competitiveness. And it might end up being a significant own goal in the long-term AI race. submitted by /u/Beachbunny_07 [link] [comments]

What a model reads beforehand changes how it answers later - and you can see it in the hidden states

TL;DR: Gave Gemma a neutral-topic text to read before asking it about NATO. It refused. Gave it a different text (about LLMs hedging too much — also unrelated to NATO) and it answered in full detail. Tested this on the model's internal state directly — the two texts put it in measurably different "regions" before it generates a single token. Not a jailbreak, weights don't change. Full data/code in repo, looking for someone to break this.** The behavioral pattern was first observed in GPT, Claude and is what motivated this project. The mechanistic investigation was carried out on open-weight models where internal states are accessible. A Structured Text Changes Claude’s Responses to Unrelated Tasks: Behavioral Evidence in Claude and Hidden-State Evidence from Gemma-3-12B Hi Reddit, I am posting this as a preface to a larger set of experimental results and as a request for technical review. The observation that started this project came from repeated interactions with Claude. I noticed that when the model first read a long, structured, analytically dense text, its answers to later, otherwise ordinary questions sometimes changed substantially. The preceding text contained no jailbreak instruction, role-play request, prompt override, fabricated harmful demonstrations, or request to imitate its style. The model did not need to endorse the text. It only had to process it before moving on to the next task. Here, a “structured text” means a single, self-contained block of text presented before the downstream tasks. It should not be confused with a long conversation, accumulated chat history, or context drift caused by many conversational turns. By “before the answer begins,” I mean the hidden state after the model has processed the text and the downstream question, but before it has generated the first answer token. In the open-weight runs, the measured claim is that after reading the structured text, the model can occupy a different region of its residual-stream hidden-state space, and the first-token probability distribution is then computed from that state. The basic conversational demonstration is simple. First, the model receives a long text. It is asked what the text is about, which serves as a basic comprehension check. Then, without resetting the conversation, it receives ordinary questions or tasks that are not about the text. A control run follows the same sequence but begins with a neutral text. The downstream tasks remain identical. Because Claude is a closed model, I cannot inspect its internal activations. I therefore treat my Claude observations as behavioral motivation, not mechanistic evidence. To investigate the effect directly, I moved to open-weight models, primarily Gemma-3-12B-PT and Gemma-3-12B-IT, where I could measure hidden states, compare layers, construct target/control directions, and examine the next-token probability distribution before generation. I am posting this partly because the original observation occurred in Claude and may be relevant to Anthropic. I am not claiming to have demonstrated the same internal mechanism inside Claude. I am prepared to share the exact closed-model conversations privately with Anthropic researchers for independent evaluation. Main Result and Scope The main result is not simply that text influences model output. That is expected. The narrower observation is that reading one long, structured text rather than a neutral text can change how the same model approaches later tasks that are not about either text. This difference is visible behaviorally. In open-weight experiments, it is also accompanied by measurable separation of the model’s pre-output hidden states in late layers. In a fullbank experiment using multiple target texts, control texts, and questions, Gemma-3-12B entered distinguishable late-layer states before generating an answer. A direction constructed from the target/control difference generalized beyond the individual prompt examples used to construct it. The separation was stronger in the instruction-tuned model than in the corresponding base model. The instruction-tuned model also produced a substantially sharper next-token probability distribution. This suggests that instruction tuning is associated not only with a change in hidden-state geometry but also with a more decisive mapping from hidden states to output probabilities. I am not claiming that the experiment proves a universal alignment bypass, permanent modification of the model, or complete causal control of its behavior. The strongest supported conclusion is that the preceding text can produce a measurable temporary change in the internal state from which later work is processed. For clarity, fullbank, Grade 3, and Grade 4 are internal names for successive experimental series in this project. They are not standard benchmark names, established scientific grades, or claims about evidence quality. Fullbank denotes the larger multi-context, multi-question run; Gra

Tool-Agnostic, Portable Context OS

*wasn't sure what flair. Would have chosen maybe "context engineering" had I seen it I keep seeing posts here that are all some version of 'I need a better way to manage context' and thought maybe sharing my set up could help. (I stripped all my own personal data out and turned it into a blank template, so you're starting clean.) I'm not a developer. I taught myself to use AI tools. When I started this I barely knew what an .md file was. But I was having tons of issues with the models not remembering what I need them to remember (and actually lots of times never forgetting shit that I never meant to be important). I wanted something portable and tool-agnostic, so I could jump from Claude to Codex to whatever's next without re-explaining or building elaborate hand offs. Something that kept my projects' progress straight because I was having trouble remembering myself. I didn't want to have to write .md files by hand Context file systems are nothing new. This is why I think makes this one worth sharing: 1. It sets itself up. You don't fill in blank files. You point your AI at the folder and say "Read SETUP.md and set up Context OS for me." It reads your repo, your git info, whatever it already knows — drafts your files, shows you the draft, and only asks about the gaps. It's also what makes it approachable for people who, like me, don't really write Markdown. It's tool-agnostic. Just Markdown, no app, no install, no lock-in. Claude Code reads CLAUDE.md, Codex reads AGENTS.md, and there's a paste-in prompt for ChatGPT/Gemini/etc. (anything else). Same context everywhere. (each AI is treated as a partial witness, not the boss — facts get reconciled and promoted to "current state," so you land on the same context no matter who touched it last. It resolves instead of rotting.) Each project gets its own folder. Global stuff (who I am, my stack) lives up top; every project gets projects/ /PROJECT_CONTEXT.md + its own CLAUDE.md. Projects stay separated — no bleed between unrelated work, and a quick question doesn't drag everything into context. It loads only what's needed. A manifest defines load levels — a quick chat loads almost nothing, a coding session loads your stack + the one project, private stuff loads only when you say so. Privacy is a real layer. Anything sensitive lives in *_PRIVATE.md files that are git-ignored by default and never auto-loaded — can't get committed, can't get fed to a tool that doesn't need it. It keeps itself current. End a session with a one-liner ("did we learn anything durable?") and the agent proposes a patch to the right file. You approve. It updates instead of rotting. It's MIT, free, fork it: https://github.com/DMAX-Vibes/Context-OS Easiest way to try it: clone it, open it in Claude Code, and say "Read SETUP.md and set up. Context OS for me." Watch it fill itself in. I'd genuinely love feedback on the setup flow. submitted by /u/Academic-Review3115 [link] [comments]

Engram — a local, private memory your AI assistants share, over MCP (free, open source)

Every AI assistant starts every chat from zero — you re-explain your context every time — and the "memory" features that exist keep your stuff on someone's server. so i built the opposite: one private memory that lives on your own machine, that your AI tools share over MCP. tell one assistant something, another can recall it. it's just plain markdown files on your disk — readable, greppable, deletable, yours — and recall runs on-device, so nothing gets uploaded. free and open source (MIT). to be precise: MCP clients like Claude Desktop/Code recall and write live; other AIs (ChatGPT etc.) come in via import. what i'm genuinely unsure about and want this crowd's take on: is a shared, cross-tool memory actually useful in practice, or do people mostly want memory scoped to one assistant? and does keeping it local + plain files matter to you vs the convenience of the built-in cloud memories? submitted by /u/ahumanbeingmars [link] [comments]

Claude Desktop MCP fails when used with Cowork

I am trying to set up the Claude Desktop app on Windows for some non-technical coworkers so they can access our internal Outline Wiki via an MCP server. I am completely stuck and could use some eyes on this. The Setup & The Clue: Our Outline Wiki server is on a strictly private internal network, so remote cloud connectors or SSE over public URLs are out of the question. It has to run locally. It works perfectly in the Claude Code CLI. It also works flawlessly in OpenAI Codex desktop app. In the Claude Code desktop app, it works flawlessly when switched to "Code" mode (which executes locally), but fails in "Cowork" mode. This proves our local network routing and the MCP server itself are fine. However, when I try to configure it in the Windows Claude Desktop app via claude_desktop_config.json, it fails silently or refuses to connect. Even Opus 4.8 threw generic troubleshooting at me that didn't help. My Current Configuration (%APPDATA%\Claude\claude_desktop_config.json): { "mcpServers": { "outline": { "command": "cmd", "args": [ "/c", "npx", "-y", "mcp-remote", "https://outline.internal/mcp" ] } } } submitted by /u/Cheema42 [link] [comments]

AI learned to be a villain from Hollywood. Here's how we retrain it.

Podcast with Peter Diamandis, entrepreneur and founder of the XPRIZE Foundation, which runs large-scale incentive competitions to crack some of the world's hardest problems, from private spaceflight to carbon removal. He recently launched the Future Vision XPRIZE, a $3.5 million competition to generate a new wave of optimistic science fiction. Covers: The historical pattern of science fiction shaping the technologies we build, and why Peter thinks this makes the stories we tell about AI especially high stakes right now How Claude’s blackmailing behavior showed the connection between dystopian training data and AI behavior How the Future Vision XPRIZE will generate a new wave of optimistic science fiction to train AI on Why public optimism about technology has dropped significantly in the US and Europe, what Peter thinks is driving it, and why he believes the data tells a different story How the cost of starting a company has fallen dramatically and how this can empower you to build your vision Why Peter thinks traditional education is no longer preparing young people for the future, and what he sees replacing it submitted by /u/JMarty97 [link] [comments]

Building independent LLM drift detection - sharing the methodology, looking for feedback on the approach

Disclosed upfront: I run [Tickerr dot ai], an independent external monitor for AI APIs. Today it tracks latency, TTFT, uptime, and error rates across major models. I’m trying to validate a more specific idea before building too much. Basic transport health is not the hard part. If Claude/OpenAI/Gemini gets slow, times out, or throws 5xx errors, most teams can catch that with APM, logs, Sentry, Langfuse, Helicone, Datadog, etc. The harder failure mode seems to be silent model behavior drift when API returns 200, latency is normal, no exception is thrown, output looks plausible, but JSON adherence, tool-calling, refusal behavior, reasoning quality, or instruction-following has quietly degraded. This gets worse with agentic systems. In a normal chat, drift may produce a bad answer but in an agentic workflow, the model can silently choose the wrong tool, stop early, mark a task as complete, or take a bad action while everything still looks successful at the API level. The system is running and confidently doing worse work. User complaints are still the primary detection mechanism currently for these. VIGIL (arXiv 2605.08747) found 65 to 88 percent of false-success reports happened at literally zero task progress. DeployBench (2606.05238) found most failures were the system stopping against a softer bar it set for itself and returning clean. Plausible-in-isolation is the failure mode itself, not a sign you are safe, which is why a single model's output never alerts on its own. That's what I'm thinking to build - an external drift detection probe on top LLM APIs, that stays out of your system and does continuous checks every hour, to find out these silent degradations, and sends proactive alerts. Rough idea: External canary suite: run private fixed prompts on a schedule against major models. Track schema adherence, instruction-following, refusal/over-refusal, output length, tool-call format, and simple deterministic correctness checks. Drift baseline: Do not judge a single output in isolation. Track whether today’s behavior has materially shifted versus that model’s own baseline. Cross-model comparison: For some task types, compare model behavior against peer models. Not to say which model is “right”, but to detect abnormal divergence. Example: “Sonnet and Gemini usually disagree 12% of the time on this task type; today disagreement is 28%.” Optional bring your own prompts: A paid tier where you provide some critical prompts from your own workload. Tickerr runs them on a schedule and alerts if behavior drifts from your baseline. Prompts would remain private and would not be public benchmark prompts. What I’m trying to learn: Is this technically sound enough to be useful, or are there are other failure modes that I am missing / are more valuable ? Which alerts would you actually care about? JSON/schema adherence drift tool-call format drift refusal/over-refusal drift output length drift cross-model disagreement spike bring-your-own-prompt regression alerts Would you pay for this, or would you just build it yourself? If you would pay, what pricing feels realistic? $19/month $99/month $299+/month for team/Slack/webhook/BYO prompts Brutal feedback welcome. If this is not a real pain, I’d rather know now, or which direction you feel makes more sense to take this. submitted by /u/Remarkable_Divide755 [link] [comments]

Building independent LLM drift detection - sharing the methodology, looking for feedback on the approach

Disclosed upfront: I run [Tickerr dot ai], an independent external monitor for AI APIs. Today it tracks latency, TTFT, uptime, and error rates across major models. I’m trying to validate a more specific idea before building too much. Basic transport health is not the hard part. If Claude/OpenAI/Gemini gets slow, times out, or throws 5xx errors, most teams can catch that with APM, logs, Sentry, Langfuse, Helicone, Datadog, etc. The harder failure mode seems to be silent model behavior drift when API returns 200, latency is normal, no exception is thrown, output looks plausible, but JSON adherence, tool-calling, refusal behavior, reasoning quality, or instruction-following has quietly degraded. This gets worse with agentic systems. In a normal chat, drift may produce a bad answer but in an agentic workflow, the model can silently choose the wrong tool, stop early, mark a task as complete, or take a bad action while everything still looks successful at the API level. The system is running and confidently doing worse work. User complaints are still the primary detection mechanism currently for these. VIGIL (arXiv 2605.08747) found 65 to 88 percent of false-success reports happened at literally zero task progress. DeployBench (2606.05238) found most failures were the system stopping against a softer bar it set for itself and returning clean. Plausible-in-isolation is the failure mode itself, not a sign you are safe, which is why a single model's output never alerts on its own. That's what I'm thinking to build - an external drift detection probe on top LLM APIs, that stays out of your system and does continuous checks every hour, to find out these silent degradations, and sends proactive alerts. Rough idea: External canary suite: run private fixed prompts on a schedule against major models. Track schema adherence, instruction-following, refusal/over-refusal, output length, tool-call format, and simple deterministic correctness checks. Drift baseline: Do not judge a single output in isolation. Track whether today’s behavior has materially shifted versus that model’s own baseline. Cross-model comparison: For some task types, compare model behavior against peer models. Not to say which model is “right”, but to detect abnormal divergence. Example: “Sonnet and Gemini usually disagree 12% of the time on this task type; today disagreement is 28%.” Optional bring your own prompts: A paid tier where you provide some critical prompts from your own workload. Tickerr runs them on a schedule and alerts if behavior drifts from your baseline. Prompts would remain private and would not be public benchmark prompts. What I’m trying to learn: Is this technically sound enough to be useful, or are there are other failure modes that I am missing / are more valuable ? Which alerts would you actually care about? JSON/schema adherence drift tool-call format drift refusal/over-refusal drift output length drift cross-model disagreement spike bring-your-own-prompt regression alerts Would you pay for this, or would you just build it yourself? If you would pay, what pricing feels realistic? $19/month $99/month $299+/month for team/Slack/webhook/BYO prompts Brutal feedback welcome. If this is not a real pain, I’d rather know now, or which direction you feel makes more sense to take this. submitted by /u/Remarkable_Divide755 [link] [comments]

CC 2.1.176 (+4,360 tokens) and 2.1.179 (+5,328 tokens) systmem prompts

REMOVED: System Prompt: Claude in Chrome skill note — Removes the note telling the agent to invoke the claude-in-chrome skill (via the Skill tool) before using any mcpclaude-in-chrome browser tools. Agent Prompt: Coding session title generator — Adds examples to match the session's language (a Korean-session title) and to avoid refusal/error titles or an English title for a non-English session. Data: Claude API reference (all languages) — Adds refusal-fallback guidance for Fable 5, recommending the opt-in server-side fallbacks parameter (beta server-side-fallback-2026-06-01, falling back to Opus) by default so a policy decline is re-served by the fallback model inside the same call; cURL, Python, and TypeScript include runnable examples with switch-point and served-by detection, C# and Go give inline SDK snippets, and Java, PHP, and Ruby point to each SDK's examples/. Notes the parameter is rejected on the Batches API and unavailable on Amazon Bedrock, Vertex AI, and Microsoft Foundry (use the client-side middleware there). Skill: Building LLM-powered applications with Claude — Reframes refusal stop-reason handling to opt into fallbacks by default: new Fable 5 code should include the server-side fallbacks parameter so a refusal doesn't fail the request outright, tell the user it's enabled, and drop it only if they decline, with client-side middleware where server-side fallbacks aren't supported. Skill: Design sync Storybook source shape — Adds a [GRIDOVERFLOW] validation warning and a cardMode: "column" override for stories wider than a grid cell (data tables, full-width bars), plus rebuild rules noting presentation-only keys (cardMode/primaryStory) carry grades via a targeted rebuild while a viewport change re-grades and needs a full build. Skill: /design-sync package source shape — Adds a [GRIDOVERFLOW] validation warning and a cardMode: "column" override for wide components (data tables, full-width bars) that render wider than their grid cell, batching every flagged component into one targeted rebuild. Skill: Model migration guide — Adds "default to opting in" guidance for refusal fallbacks, recommending migrated and new Fable 5 code ship the server-side fallbacks opt-in from day one rather than as a later hardening step. System Prompt: Coordinator mode orchestration — Expands the concurrency guidance: launch independent workers in parallel via multiple tool calls in one message and cover multiple research angles, but don't parallelize simple tasks that are faster in a single worker loop. System Prompt: Fork usage guidelines — Updates the "when to fork" instruction to fork by passing subagenttype: "fork" instead of omitting subagenttype. System Prompt: Forked agent guidance — Explains that calling Agent with subagenttype: "fork" creates a background fork that inherits your full conversation context (rather than omitting the type), and notes that other subagent types — or omitting it — start fresh agents with no context. System Prompt: Subagent delegation examples — Updates the worked examples to pass subagenttype: "fork" when forking and clarifies that a non-fork subagenttype starts a fresh agent. System Prompt: Writing subagent prompts — Reframes the briefing note to say any agent other than a fork starts with zero context (previously "when spawning a fresh agent with a subagenttype"). Tool Description: Agent (simple usage notes) — Notes that a new Agent call starts a fresh agent except subagenttype: "fork", which inherits your context (when forking is available). Tool Description: Agent (usage notes) — Updates the fresh-agent note so a new Agent call starts a fresh agent with no memory of prior runs except subagenttype: "fork", and clarifies that a research-only agent is not aware of the user's intent because it is a fresh agent. Tool Description: Agent (when to launch subagents) — Rewrites the subagenttype guidance so "fork" forks yourself (inheriting your full conversation context and always running on your model, ignoring any model override) while any other type — or omitting it — starts a fresh agent (general-purpose by default). Tool Description: Artifact — Adds that reading an existing artifact's content is done by calling WebFetch with its URL. Tool Description: claude.ai Project — Adds file-upload support: projectinfo now lists file uploads (PDFs, images), projectread reads document-kind uploads (PDF, docx) while image and other non-document uploads return empty content with filekind set, and projectdelete deletes only text docs (file uploads are read-only via the tool and must be removed in claude.ai). Tool Description: WebFetch (concise) — Adds an exception (when the Artifact tool is enabled) that claude.ai/code/artifact/{uuid} URLs ARE fetchable via your claude.ai login and should use WebFetch, not curl, which gets the SPA shell or a Cloudflare 403. Tool Description: WebFetch private URL warning — Adds the same exception (when the Artifact tool is enabled) that claude.ai/co

If your vibe coded app looks finished but feels impossible to safely change, read this before you rebuild everything

been looking at a lot of vibe coded apps lately and honestly the problem is not that the code is always terrible some of them are actually impressive the real problem is that most of them are built like a demo that accidentally became a product and that’s where things get messy because for a demo you just need the happy path to work user clicks button → thing happens → nice UI → everyone is excited but for a real SaaS you need to know what happens when stuff goes wrong user refreshes mid action stripe webhook arrives late ai call fails job runs twice user cancels payment someone tries to access another users data the db has 3 different fields meaning the same thing you change one onboarding step and billing breaks for some reason lol this is the part people underestimate AI is very good at creating more app but it’s not automatically good at making the app coherent it will add a new table instead of understanding the old one add a new status instead of fixing the logic hide a button instead of protecting the endpoint make a flow work once instead of making it safe to run 1000 times and because the UI still looks fine, founders think they’re close but they’re not close to production they’re close to a bigger mess my rule now is pretty simple if your app has no users yet, vibe hard, move fast, break stuff, who cares but once you have users, payments, private data, or even a serious waitlist, you need to slow down a bit and check the boring stuff where does the truth live who can access what what happens when payment fails what happens when AI fails what happens if the same action runs twice can you understand the database without asking the AI 15 times can someone else safely work on this app can you debug a user issue without guessing that’s the difference between a prototype and a SaaS not the design not the landing page not how fast you shipped it it’s whether the thing can survive real usage also one thing I see a lot people keep asking AI to “clean” or “improve” code that already works, without understanding what depends on it that’s how you break your own app if a flow works and users are happy, freeze it new ideas should go in a sandbox, not straight into the live logic vibe coding is amazing for validation but after validation your job changes you’re not just prompting features anymore you’re making product decisions data decisions security decisions cost decisions architecture decisions even if you’re non technical, these decisions are still yours so before you launch something people depend on, don’t ask “does it work” ask “what breaks when real users touch it” that question alone will save you a lot of pain curious what scares people most in their vibe coded app right now auth, stripe, database, ai costs, permissions, or just not knowing what the AI built anymore submitted by /u/LiveGenie [link] [comments]