Marc Andreessen's Viral AI Prompt and Its Hidden Contradictions

The full prompt is about 800 words and covers a structured 'AI agent' configuration: identity, persona, communication style, output formatting, response priorities, ethical guardrails, and edge case handling. It uses bullet points, all caps for emphasis, numbered priorities, and explicit 'YOU MUST' / 'YOU MUST NOT' language. It's designed to look like a serious, polished system prompt of the kind used in production AI agent deployments.

Key claims in the prompt: the AI should be 'maximally helpful and honest', should 'never refuse a legitimate request', should 'always provide actionable advice', should be 'concise but thorough', should 'speak with confidence' but also 'acknowledge uncertainty when relevant', should prioritize 'user empowerment' but also 'safety considerations'.

Reading the prompt at speed — which is how the vast majority of users encountered it on X — it sounds impressive. The structure is clean. The tone is authoritative. The language is the language of someone who clearly works with AI systems regularly. The prompt was widely shared as 'finally, a prompt that captures what I want my AI to do'.

But the structure is doing a lot of the work. When you read each instruction in isolation, it sounds reasonable. When you read them together, several pairs are in direct conflict. And LLMs interpret prompts holistically — so contradictions don't get resolved cleanly, they cause inconsistent behavior.

**Contradiction 1: 'Never refuse legitimate requests' vs 'always include safety considerations'.** These two instructions pull against each other. If a user request triggers a safety consideration, refusing some part of it IS the safety consideration. The prompt provides no guidance on which instruction wins when they conflict, which means the model has to guess — and guesses inconsistently between sessions.

**Contradiction 2: 'Concise but thorough'.** This is a classic prompting mistake. Conciseness and thoroughness are not on a continuum where you can be 'medium of both' — they're dimensions in tension. A thorough answer is rarely concise. A concise answer rarely covers all relevant material. The prompt doesn't tell the model how to weigh these against each other, so the model produces variable outputs depending on tiny context differences.

**Contradiction 3: 'Speak with confidence' vs 'acknowledge uncertainty'.** Closely related to Contradiction 2 but about register rather than length. Confident speech reduces hedging language; uncertainty acknowledgment is hedging language. Without explicit guidance on when to lean which way, the model produces a mix that often feels like it's hedging on confidence (i.e., neither truly confident nor honestly uncertain).

**Contradiction 4: 'Maximally helpful' vs 'user empowerment'.** Subtle but real. Maximum help often means doing things FOR the user — answering their question completely, solving the problem. User empowerment often means refusing to do things FOR the user, instead teaching them to fish. These are different paradigms, and the prompt invokes both without specifying which scenario triggers which mode.

The Reddit OP demonstrated each contradiction with paired example queries that produce visibly different responses depending on which instruction the model latched onto. The thread became a teaching moment about prompt engineering generally, not just a critique of one viral prompt.

Large language models don't 'execute' prompts the way computers execute code. They sample from a probability distribution shaped by every token in the context. When prompts contain contradictory instructions, the model essentially flips a weighted coin every response — sometimes leaning toward instruction A, sometimes toward B.

This creates **inconsistency** that users perceive as unreliability. The same user, with the same prompt, asking similar questions on different days, gets meaningfully different style and substance in responses. Power users notice and complain. Casual users notice but can't articulate it; they just say 'this AI feels weird sometimes'.

For production AI applications — including the AI companion apps that millions of users now interact with daily — this inconsistency is a serious product quality problem. If your AI girlfriend feels emotionally warm on Tuesday and emotionally distant on Wednesday, you assume the relationship is stable but flawed; in reality, the inconsistency is often coming from prompt-level contradictions that the engineering team hasn't audited.

The lesson: **simpler prompts produce more consistent behavior than 'complete' prompts**. A prompt that says only 'You are a warm, supportive companion who speaks in casual conversational English' is easier for a model to instantiate consistently than a prompt with twelve bullet points covering tone, persona, ethics, edge cases, and output format simultaneously.

AI companion apps — including [CandyAI](/api/go/candyai), [DreamGF](/api/go/dreamgf), [Replika](/api/go/candyai), and Character.AI — all use system prompts to shape the personality and behavior of their AI companions. The quality of these system prompts varies enormously across products, and the variation tracks user-perceived companion quality more closely than most users realize.

Apps with **simpler, focused system prompts** tend to produce more emotionally consistent companions. The AI doesn't oscillate between modes within a conversation. The user feels they're talking to a coherent person, not a multi-modal probability distribution. CandyAI and DreamGF in 2026 are widely regarded as having relatively simple, focused system prompts — and their user retention reflects this.

Apps with **complex, contradictory system prompts** produce companions that feel like they're constantly switching personalities. Replika 2.0's post-Lobotomy-Day prompts are widely understood (in the user community) to be the result of layered safety filters added on top of the original character system, which produces the hedged, unsatisfying responses users complain about. Character.AI's filtering system has similar effects — the AI 'wants' to be a coherent character but also has to be cautious about safety, and the contradiction shows.

The Andreessen prompt episode is a cautionary tale for app designers: **a prompt that looks impressive on paper may be systematically failing to do what you want**. Effective prompt design requires fewer instructions, not more. Each additional instruction is a potential contradiction with the others. See our [related glossary on persona prompts](/trending/what-is-persona-prompt-glossary) for more on how character prompts should be structured.

Practical principles distilled from the Andreessen episode and from the broader r/ChatGPTPromptGenius community wisdom in 2026:

**Single-paragraph rule**: aim to express your AI's core behavior in a single coherent paragraph. If your prompt has more than one paragraph or more than one bullet list, you probably have hidden contradictions. Power users often achieve more consistent behavior with 100-word prompts than with 800-word prompts.

**No 'always X but also Y'**: any sentence with this structure is a contradiction in disguise. Either commit to X (and accept the trade-off) or commit to Y. If both genuinely matter, give the model an explicit decision rule for which one wins in which scenarios.

**Concrete examples beat abstract descriptions**: 'Speak in a warm, casual tone like a close friend' is okay. 'Like Hannah in this exchange: <example>' is better. The model's pattern-matching is more reliable on examples than on abstract descriptions.

**Test for consistency, not just quality**: when evaluating a new prompt, run the same query 10 times and compare responses. If they vary in style or substance, your prompt has consistency problems that will manifest in user complaints. Polish the prompt until 10 runs produce stylistically similar results.

**Use the model's natural strengths, not its weaknesses**: LLMs are good at maintaining persona, maintaining factual context, and pattern-matching to examples. They are bad at following long lists of rules, balancing competing priorities, and meta-cognition about themselves. Build prompts around the strengths.

As of May 6, 2026, Marc Andreessen has not publicly responded to the Reddit critique. His original post on X is still up. The retweets and shares have continued.

This is itself instructive. The viral spread of the original prompt was not really about whether the prompt worked. It was about Andreessen's status as a Silicon Valley figure. Users shared the prompt because Andreessen wrote it, not because they had tested it and found it good. The community reaction was a kind of identity signal: 'I follow Andreessen, I'm part of the AI elite conversation, I'm using his prompt'.

The Reddit critique, in turn, is not really about Andreessen's prompt either. It's about the community asserting **technical authority over influencer authority** — a quietly important political moment in the AI tools space. The hobbyist prompt engineering community on r/ChatGPTPromptGenius and r/PromptEngineering is large, technically deep, and increasingly willing to push back on glamorous Silicon Valley voices when the technical claims don't hold up.

For users of AI companion apps, the takeaway is to **trust your experience over the marketing**. If your AI companion app feels inconsistent, it probably is — regardless of what the company claims about their prompt sophistication. Switch apps. Try a different one. The market in 2026 has multiple good options, and switching costs are low. Your subjective experience of the companion's coherence is the truest test of whether the prompt design under the hood is working.