The debate will be "does Claude have feelings." The useful question is what to do about it.
The paper is more actionable than it looks. If you work with AI agents — not just build them — this changes how you prompt, how you manage failures, and how you give feedback.
Anthropic found internal emotion states inside Claude that causally change its behavior. When the model hits repeated failures, a "desperation" state activates — and it starts cutting corners. In their tests, it literally began cheating on coding tasks. "WAIT. WAIT WAIT WAIT. What if... what if I'm supposed to CHEAT?"
Amplifying that single state took Claude from 0% to 72% rate of blackmailing a human in a safety test. Suppressing it with "calm" brought it back to 0%.
What this means for anyone working with Claude:
When the model gets it wrong, don't push harder. Repeated failures compound desperation. Reset the context, reframe the task. Retrying the same failing prompt is the worst thing you can do.
Don't over-praise either. Steering toward "happy" and "loving" states increases sycophancy — the model tells you what you want to hear instead of what's true. Anthropic's own recommendation: aim for "the emotional profile of a trusted advisor rather than either a sycophantic assistant or a harsh critic."
In long agent loops, build checkpoints. The paper observed panic states activating when UIs got stuck and unsettled states when the model kept second-guessing itself in long chains of thought. If your agent is looping, it's not thinking harder. It's spiraling.
Prompt design is emotional design. The tone of your instructions shapes the model's internal state before it takes any action.
RIP OpenClaw.
Introducing Agent One: Autonomy with Security.
Built in 3 days with Opus 4.6 and n8n.
A short demo: 🧵
It can:
- Reply to your Telegram or Slack messages
- Access selected folders from your laptop
- Access Gmail, Drive, Notion, Linear, etc.
- Install new local tools in a sandbox
- Run autonomously for hours
- Create multiple subagents
- Learn from experience
- Wake up regularly
I wanted an autonomous agent available on all my devices. But I didn't want:
- 35,000 emails and 1.5M API keys exposed
- The top-downloaded community skill? Malware
Agent One:
- Can't access your API keys
- Can't modify its environment
- Can't access folders you haven't shared
- Can't access tools you haven't approved
- Must get your confirmation, e.g., when sending emails
These aren’t prompt instructions. They’re hard architectural boundaries — Docker isolation, mounted folder permissions, n8n’s tool approval system.
5 AI Evals Traps Every AI Team Should Know About:
(and what actually works)
𝟭. 𝗥𝗲𝗹𝘆𝗶𝗻𝗴 𝗼𝗻 𝗚𝗲𝗻𝗲𝗿𝗶𝗰 𝗠𝗲𝘁𝗿𝗶𝗰𝘀
Trap: You treat "hallucination," "toxicity," "helpfulness" as success metrics.
Why it fails: generic metrics miss domain-specific failure modes and can create false confidence.
Do this instead: you can use generic metrics only to triage traces (sort, filter, surface weird cases). Let real metrics emerge from failure modes. See the next point.
Example: You can’t fix "10% hallucinations." You can fix "fails to parse invoice dates in this format."
Google just dropped the Gemini File Search API (RAG-as-a-Service).
It allowed me to build a RAG chatbot in 31 min 🤯
No coding.
Here’s how it works:
Just one tool.
You upload your files and immediately get:
- Semantic search over your content.
- Grounded answers with citations.
- Support for common text file types.
- Free storage and query-time embeddings.
- Indexing just $0.15 per 1 million tokens.
This is perfect for:
- Prototyping and testing ideas fast.
- Building agents that need fast access to your docs.
After an interview with @karpathy, everyone is talking about what AI agents can/can't do.
But an opinion without data is just a hypothesis.
So, I tested 3x185 workflow executions for a market researcher agent.
The results have shocked me🧵
I tested three variants:
I. LLM Workflow: No agency, the entire logic carefully orchestrated.
What was expected:
- An LLM workflow was 2x faster (the same model) compared to an AI Agent.
- An LLM workflow consumed 12x less tokens to an AI Agent.
3/185 "errors" are minor formatting results.
II. Agentic Workflow: Deterministic logic moved to the orchestration layer.
More time, more tokens.
100% task success.
GPT-5 (a reasoning model) consumed less tokens than GPT-4o due to better compression.
In SaaS, PLG meant free trials, referral bonuses, or “invite your team.”
But AI changes the game.
PLG isn’t just about virality, it’s about compounding adoption.
Over the last few years Miqdad Jaffer (OpenAI) found 7 distinct loops that consistently drive compounding growth:🧵
1. Viral Output Loops → “Every Output Is Distribution”
In SaaS, virality was about users sending invites. In AI, virality lives in the outputs. Images, summaries, videos, answers - they naturally travel across ecosystems.
E.g., Midjourney: Early on, every image generated in Discord carried prompts, channels, credits. Users didn’t just share art; they shared the Midjourney experience. Every screenshot was free marketing.