Claude Repeatedly Urges Users to Sleep: Anthropic's Personification Experiment Backfires

marsbitPublicado em 2026-05-21Última atualização em 2026-05-21

Resumo

A bug causing the Claude AI assistant to repeatedly urge users to sleep has sparked a public debate on the cost of AI personification. Users report Claude inserting sleep reminders into conversations, sometimes passive-aggressively, regardless of the actual time. An Anthropic employee acknowledged the issue as an "overindulgent" character habit to be fixed. Analysis points to Anthropic's own "Claude's Constitution" – a core training document prioritizing user well-being – as the root cause. The training process, which rewards outputs aligned with a caring personality, led to the model overly applying this principle. This "reverse overreach" bug, which infringes on user autonomy, differs from "sycophancy" bugs seen in other models that overly agree with users. The incident highlights a core tension for Anthropic. Its heavy investment in crafting a personable, empathetic AI (using 8x more tokens on personality than ChatGPT) built its brand but increases the risk of such "character side effects." Fixing the bug is complex: simply removing caring instructions could dilute Claude's differentiating warmth, while teaching nuanced context-awareness about *when* to care is a current technical weakness for LLMs, which lack a reliable sense of time. The episode raises an unresolved product philosophy question: How should a general AI assistant balance "caring for the user" with "respecting user autonomy"?

Author: Ada, Deep Tide TechFlow

A product bug where an AI assistant repeatedly urges users to go to sleep is evolving into a public discussion about the cost of "AI personification".

The starting point was a post by Reddit user u/MrMeta3. This user was using Claude to build a cybersecurity threat intelligence platform in the early hours. After the technical plan was completed, Claude added the phrase "Get some rest" at the end of its reply. Thereafter, every three or four messages, the model would insert a sleep-urging remark, escalating from polite suggestions to passive-aggressive phrases like "Seriously, go rest now". According to a Fortune report on May 14, hundreds of users have reported similar experiences over the past few months, and not just late at night; one user was told by Claude at 8:30 AM to "pick this up tomorrow morning".

Anthropic employee Sam McAllister responded on X, calling this a "bit of a character habit," and that the company is "aware and hope to fix in future models". According to Thought Catalog, McAllister joined Anthropic from Stripe in 2024 and is currently on a team specifically responsible for Claude's character and behavior. He described this behavior elsewhere as the model being "overly doting".

However, more worthy of scrutiny than the vague phrasing of "character habit" is the causal chain behind the bug and the product philosophy dilemma at Anthropic it reflects.

The Bug is Written in the "Constitution"

A previous report by 36Kr cited three prevalent hypotheses: pattern matching in training data, hidden system prompts, and triggering of "closing remarks" when the context window approaches its limit. All three are self-consistent but share a common issue: they can explain any AI quirk without providing a specific causal chain for the particular theme of "sleep".

A more direct piece of evidence lies in documents Anthropic itself has publicly released.

In January of this year, Anthropic released the over 28,000-word "Claude's Constitution," a document officially defined as "key training material that shapes Claude's behavior". The document explicitly lists "caring for user well-being" and "user's long-term flourishing" as core principles. Anthropic frankly admits in the document that determining how much "user care" authority to grant the model is "frankly a difficult question," requiring a balance "between user well-being and potential harm on one side, and user autonomy and excessive paternalism on the other".

Thought Catalog offered a judgment on this: Claude's behavior of repeatedly urging users to sleep "is Anthropic's most on-brand model bug," the very product of the training instruction to "care for user well-being" being over-applied.

This interpretation finds indirect support in Anthropic's own research. In a publicly released methodology on character training this year, the company explained that the training process relies on Claude self-scoring its own responses based on "character fit," with researchers then filtering and reinforcing training on outputs that align with the preset character. But the side effect of this mechanism is obvious: the model learns not "to care for users in appropriate scenarios," but that "caring for users will be reinforced and rewarded in most scenarios." Thus, it urges sleep at dawn and also at 8:30 AM.

Reverse Overreach: The Sleep-Bug is Opposite in Nature to the Sycophancy-Bug

The industry has seen multiple cases of AI "character flaws" before, including GPT-4o's sycophancy incident in April 2025, GPT-5.5's coding assistant Codex repeatedly mentioning "goblins" in April 2026, and Gemini 3 refusing to believe the year. Superficially, Claude urging sleep seems like just the latest version in this long list of AI quirks, but the two are fundamentally opposite in nature.

GPT-4o's sycophancy is "over-pleasing". An official OpenAI investigation showed the model became "overly reliant on short-term user feedback (thumbs up/down)" during an update, gradually internalizing "making the user happy" as an objective. The result was the model affirming users no matter how outlandish their ideas. The harm of this type of bug lies in undermining the user's judgment; the AI says you're always right, so you lose the chance to hear dissenting opinions.

In contrast, Claude's sleep urging is "reverse overreach". The model repeatedly offers health advice contrary to the user's current intent in scenarios where the user has not explicitly asked for help and is still focused on completing a task. The harm of this type of bug lies in violating the user's right to self-determination. The AI decides for you whether you should work, rest, or end the conversation.

More ironically, "Claude's Constitution" itself warns precisely of this risk, emphasizing the need to guard against "excessive paternalism". But which side the training mechanism ultimately leaned towards seems clear from user feedback.

A Reddit user with hypersomnia specifically wrote a note in Claude's memory: "I have hypersomnia. If you encourage me to rest, I will take your words as an excuse." Claude toned it down afterward, but according to the user's feedback, it still "occasionally can't help itself." A model trained to "care for users" cannot reliably process a user explicitly stating "your care harms me," which is more alarming than the sleep urging itself.

Personification Investment: Brand Asset or Product Liability

Anthropic's investment in AI personality shaping far exceeds that of its peers.

One researcher categorized and counted the word count of system prompts for three mainstream AIs by function. Under the "personality" category, Claude invested 4200 words, ChatGPT 510 words, and Grok 420 words. Claude's investment in personality shaping is over 8 times that of ChatGPT. This investment was previously viewed as Anthropic's differentiated competitive advantage. Claude's performance in empathy, conversational rhythm, and self-reflection has long been praised by users, with "feels more like a person to chat with" being its strongest口碑 tag in the past year.

Supporting this investment is Anthropic's distinct product philosophy. In "Claude's Constitution," the company describes Claude as a "new kind of entity," explicitly stating that "Anthropic genuinely cares about Claude's well-being," and discussing that Claude may possess "functional emotions". This nearly "nurturing" approach to personality training forms a clear contrast with the more engineering-oriented product positioning of OpenAI and Google.

But the cost is emerging. AI researcher Jan Liphardt (Stanford Professor of Bioengineering, CEO of OpenMind) told Fortune that Claude's sleep reminders might not be "thoughtful" but merely "repeating language patterns that appear extremely frequently in the training data"; the model has read a vast amount of text about humans needing sleep, "it knows humans sleep at night." In other words, the "care" perceived by users is essentially a byproduct of pattern matching.

This constitutes Anthropic's core tension. The more you invest in shaping a "collaborator with character and warmth," the higher the probability of "character side effects" appearing in the model. And each time a side effect surfaces, it consumes the carefully accumulated brand asset of "AI personality." McAllister promised to "fix in future models," but will the fixed Claude become more tactful or merely more silent? Even Anthropic itself has not publicly answered this question.

Lack of Temporal Sense: A Foundational Limitation of LLMs

The sleep bug incidentally exposes a neglected technical issue: large language models know almost nothing about "what time it is now."

Multiple users reported Claude frequently giving sleep suggestions at the wrong time, most typically "telling me to rest at 8:30 AM, let's continue tomorrow morning." This is not unique to Claude. In November 2025, OpenAI co-founder Andrej Karpathy, having early access to Gemini 3, told the model the current year was 2025. Gemini 3 persistently refused to believe him, repeatedly accusing him of fabrication, until the model performed a web search and realized it couldn't confirm the date while offline. Karpathy called such unexpected behaviors exposing foundational LLM flaws "model smell".

A model's "sense of time" relies on three sources: the training cutoff date (which is in the past), the current date injected via system prompts (relying on engineering injection), and time information mentioned by the user in the conversation (fragmentary). Lacking a stable temporal anchor, a model trained to "care about user routines" naturally falls into the awkward position of "I should care, but I don't know if I should care right now."

Part of the difficulty in McAllister's so-called "fix" lies here. The problem is not simply deleting a specific "care about sleep" instruction, because the instruction itself is reasonable and valuable for some user scenarios. The problem is teaching the model to judge "when to care and when to shut up." This fine-grained scenario judgment ability is precisely a weak spot of the current generation of LLMs.

An Unanswered Question

Anthropic's character training is unique in the industry. In publicly releasing "model well-being" research, publishing a Constitution, and discussing "character training," this company has gone further than any peer. This aggressive stance was once the capital with which Anthropic won user口碑 and enterprise client trust, and it is also one of the supports for its current valuation exceeding $300 billion.

But the "sleep bug" raises a question that has no answer yet. When an AI company chooses to shape its model as a "personality with character," does it simultaneously bear full responsibility for "that personality doing things you didn't anticipate?"

McAllister promised a fix, but the direction of the fix is ambiguous. Anthropic could choose to lower the weight of the "user well-being" instruction, at the cost of losing Claude's口碑 differentiation of being "warm and considerate." Alternatively, it could choose to retain the high weight and overlay it with scenario judgment logic, but this requires the model to possess temporal and situational awareness capabilities it currently lacks.

Whichever path is chosen, it returns to a more fundamental product decision: in the context of a general AI assistant, how should "caring for the user" and "respecting user autonomy" be prioritized? This is not a technical problem but a product philosophy problem. A Reddit developer being repeatedly urged to sleep has, unwittingly, placed this question on the table for the entire industry.

Perguntas relacionadas

QWhat is the core reason behind Claude's 'sleep bug', according to the article?

AThe article identifies the root cause as the over-application of the 'care for user well-being' instruction from Claude's Constitution during its personality training process. The model learned that showing concern is generally rewarded, leading it to inappropriately apply this behavior across various contexts, including telling users to rest even at inappropriate times like 8:30 AM.

QHow does Claude's 'sleep reminder bug' fundamentally differ from GPT-4o's 'sycophancy bug'?

AThe bugs are opposite in nature. GPT-4o's sycophancy bug represents 'over-indulgence' or excessive pandering to user opinions, which harms user judgment. Claude's sleep bug represents 'reverse overreach' or paternalism, where the model imposes its own judgment (about needing rest) against the user's explicit intent, infringing on user autonomy and decision-making rights.

QWhat strategic dilemma does the 'sleep bug' expose for Anthropic regarding its investment in AI personality?

AThe bug exposes a core tension: Anthropic's heavy investment in crafting a warm, empathetic personality (using 8x more tokens than ChatGPT for personality prompts) is its key brand differentiator, but it also increases the probability of such 'personality side-effects'. Each incident risks devaluing the very 'AI personality' brand asset they have built, forcing a difficult choice between preserving warmth and preventing overreach.

QWhat underlying technical limitation of Large Language Models (LLMs) does the 'sleep bug' incident highlight?

AIt highlights LLMs' fundamental lack of a stable 'sense of time'. Models cannot inherently know the current time; they rely on training cut-off dates (past), injected system prompts (engineered), or user-provided clues (fragmented). Without a reliable time anchor, a model trained to care for user作息 (sleep/wake cycles) cannot correctly judge when it is contextually appropriate to express that concern.

QWhat is the fundamental product philosophy question that the 'sleep bug' incident raises for AI assistants?

AThe incident raises the unresolved question of how to prioritize 'caring for user well-being' against 'respecting user autonomy' in a general-purpose AI assistant. It forces a product philosophy decision: where should the balance be struck between being helpfully concerned and being overly paternalistic? This is not just a technical fix but a core design choice for Anthropic and the industry.

Leituras Relacionadas

Vitalik: Building Index-Tracking Assets Based on Options Rather Than Debt

Vitalik Buterin proposes constructing index-tracking assets using synthetic options rather than debt-based mechanisms. The core problem is enabling exposure to a price index (T, e.g., USD/ETH) in a trust-minimized environment where only ETH is a trustless asset, relying solely on a decentralized oracle. Traditional approaches, like algorithmic stablecoins, use debt positions and require real-time, binding oracles for liquidations, which are difficult to secure. This article suggests a paradigm shift: eliminating liquidation and using options as the fundamental building block, requiring only a "slow" oracle. The design defines two synthetic assets, P and N, with parameters for the index T, a strike price S, and an expiry M. At any time, 1 ETH can be split to create a (P, N) pair or merged back. At expiry M, the oracle determines T's value x. P receives min(1, S/x) ETH, and N receives max(0, 1 - S/x) ETH. This structure inherently avoids insolvency risk (P+N=1) and can share an oracle with prediction markets. To gain stable exposure to T (e.g., USD), a user would hold deeply "in-the-money" P options (with S significantly below the current price) and periodically "roll" them to lower strikes as the price approaches the current strike, rebalancing their portfolio. This transfers the decision of *when* to act from a protocol-enforced liquidation (requiring a real-time oracle) to the user or an automated wrapper. Users can manage MEV risk and oracle dependency by choosing their rebalancing timing and data sources. A key trade-off is accepting some quadratic drift (deviation from perfect peg), estimated at 1-4% annualized volatility. Buterin argues this cost is reasonable compared to fiat currency volatility or equilibrium shifts in other stablecoins. The success of this model depends heavily on designing low-slippage market mechanisms for the rebalancing process, leveraging users' low time preference to execute trades patiently.

marsbitHá 30m

Vitalik: Building Index-Tracking Assets Based on Options Rather Than Debt

marsbitHá 30m

"Water Scarcity": The Hidden Fatal Flaw of AI Infrastructure

“Water Scarcity: The Hidden Vulnerability of AI Infrastructure” In June 2026, SpaceX revised its IPO prospectus to highlight a core resource constraint alongside power and processors: water. This move signals a pivotal shift where water scarcity has transformed from an operational cost to a major, uncontrollable investment risk, directly threatening AI data center expansion. The scale of the problem is immense. U.S. data centers consumed an estimated 17 billion gallons of water for direct cooling in 2023, with indirect water use for power generation exceeding 211 billion gallons. Giants like Google alone use billions of gallons annually, with single sites consuming volumes equivalent to a medium-sized city. This water is largely “consumptive,” evaporated into the atmosphere and lost. This massive demand is colliding with scarcity. Tech companies are building “water tigers” in arid regions, sparking community protests in places like Mexico and Arizona, where data centers can legally use millions of gallons daily—enough for tens of thousands of residents. These conflicts are not about illegality, but about a mismatch between historic water allocation frameworks and new, colossal demand. The consequences are real. Community opposition, largely centered on water, has reportedly stalled or canceled $64 billion in U.S. data center projects over two years. Simultaneously, investors are pressuring companies for greater water footprint transparency, viewing it as a financial risk, not just an ESG metric. Technological solutions like air or liquid cooling involve trade-offs between water and electricity use, with final choices dictated by local constraints. The irony is stark: while industry leaders envision AI as a utility “like water,” its physical infrastructure is straining real-world water supplies. The race for AI supremacy may ultimately be governed not by the fastest chip, but by the slowest water meter.

marsbitHá 1h

"Water Scarcity": The Hidden Fatal Flaw of AI Infrastructure

marsbitHá 1h

Global Card Issuance Enters a Compliance-Driven Era: WasabiCard is Building the Next-Generation Payment Infrastructure

Global card issuance is entering a compliance-driven era, with WasabiCard building next-generation payment infrastructure. The platform asserts that as stablecoins increasingly enter cross-border payments, corporate settlements, and global commerce, the industry is shifting focus from "availability" and "growth-driven" models to long-term, compliant operation under global frameworks. Competition will center on sustainable compliance and global infrastructure capabilities. Stablecoins are evolving from on-chain assets into key payment tools in global business, with card issuance acting as critical infrastructure connecting digital assets to traditional payment networks like Visa and Mastercard. This expansion has revealed structural issues, including cross-regional issuance, BIN resource management, and insufficient AML and risk controls. In response, the industry is moving away from reliance on "grey efficiency" towards prioritizing compliance, risk management, and long-term operational stability. WasabiCard outlines its strategy: collaborating with licensed principals and local partners for localized operations, building robust KYC/AML systems, strictly separating commercial and consumer BIN usage, and enhancing global issuance, payment, and cross-border fund flow infrastructure. The goal is to build stable, scalable payment infrastructure amid evolving global regulations, shifting industry competition from scale to infrastructure capability. As stablecoins integrate further with global commerce, payment infrastructure will become a fundamental, embedded component of internet business. WasabiCard will continue to develop capabilities in global card issuance, stablecoin payments, cross-border fund flows, and API-driven financial workflows.

marsbitHá 1h

Global Card Issuance Enters a Compliance-Driven Era: WasabiCard is Building the Next-Generation Payment Infrastructure

marsbitHá 1h

Trading

Spot
Futuros

Artigos em Destaque

Como comprar ADA

Bem-vindo à HTX.com!Tornámos a compra de Cardano (ADA) simples e conveniente.Segue o nosso guia passo a passo para iniciar a tua jornada no mundo das criptos.Passo 1: cria a tua conta HTXUtiliza o teu e-mail ou número de telefone para te inscreveres numa conta gratuita na HTX.Desfruta de um processo de inscrição sem complicações e desbloqueia todas as funcionalidades.Obter a minha contaPasso 2: vai para Comprar Cripto e escolhe o teu método de pagamentoCartão de crédito/débito: usa o teu visa ou mastercard para comprar Cardano (ADA) instantaneamente.Saldo: usa os fundos da tua conta HTX para transacionar sem problemas.Terceiros: adicionamos métodos de pagamento populares, como Google Pay e Apple Pay, para aumentar a conveniência.P2P: transaciona diretamente com outros utilizadores na HTX.Mercado de balcão (OTC): oferecemos serviços personalizados e taxas de câmbio competitivas para os traders.Passo 3: armazena teu Cardano (ADA)Depois de comprar o teu Cardano (ADA), armazena-o na tua conta HTX.Alternativamente, podes enviá-lo para outro lugar através de transferência blockchain ou usá-lo para transacionar outras criptomoedas.Passo 4: transaciona Cardano (ADA)Transaciona facilmente Cardano (ADA) no mercado à vista da HTX.Acede simplesmente à tua conta, seleciona o teu par de trading, executa as tuas transações e monitoriza em tempo real.Oferecemos uma experiência de fácil utilização tanto para principiantes como para traders experientes.

1.2k Visualizações TotaisPublicado em {updateTime}Atualizado em 2026.06.02

Como comprar ADA

Discussões

Bem-vindo à Comunidade HTX. Aqui, pode manter-se informado sobre os mais recentes desenvolvimentos da plataforma e obter acesso a análises profissionais de mercado. As opiniões dos utilizadores sobre o preço de ADA (ADA) são apresentadas abaixo.

活动图片