Denoise · Twitter

The focus in agent security is shifting from prompt injection to vulnerabilities in the orchestration layer, a concern echoed by @AnthropicAI, @GoogleDeepMind, and @MalwareTechBlog.

Major labs are proactively releasing frameworks and disclosures for securing autonomous agents against complex attacks.

• Anthropic@AnthropicAIrising

  Responsible disclosure on a Claude jailbreak chain we patched last week. Full write-up including our red team timeline.

• Google DeepMind@GoogleDeepMindrising

  New red team framework for prompt injection in autonomous agents. Covers cross-tool leakage, scanner evasion, and sandbox escape patterns.

• MalwareTech@MalwareTechBlogrepeated

  Autonomous agent running pentest flows against a real SaaS. First real-world run: fewer false positives than I expected on the vulnerability surface.

A new developer workflow is consolidating around conversational terminal agents, with @karpathy providing the narrative, @AnthropicAI the tool, and @swyx the initial benchmarks.

The primary developer interface is shifting towards terminal-native agents, led by the launch of Anthropic's Claude Code 1.5.

• Anthropic@AnthropicAIrising

  Claude Code 1.5 is live. Terminal-native coding agent with full Claude Opus reasoning, file-ops sandbox, and session replay.

• Andrej Karpathy@karpathyrising

  The developer-experience shift from IDE to terminal agent is underrated. Coding workflows are about to look nothing like 2024.

• swyx@swyxrising

  Codex vs Claude Code terminal agent benchmarks. Pass@1 diverges more than I expected on the long-context editor tasks.

• DSPy@dspy_airising

  DSPy 3.0: prompt optimization via compile-time search over system prompt variations. Benchmarks inside.

• @levelsio@levelsiorising

  Switched my whole editor setup to Claude Code this week. Shipping faster than when I used Cursor + Copilot.

A convergence is visible as @OpenAI's SDK, @LangChainAI's protocol integrations, and @vercel's edge runtimes all target the agent orchestration layer.

Infrastructure providers are racing to ship primitives for deploying, orchestrating, and hosting multi-worker agents.

• OpenAI@OpenAIrising

  New agent SDK: protocol-level tool calling, deployment harness, and multi-worker orchestration primitives. Docs live.

• LangChain@LangChainAIrising

  MCP protocol integration thread. How to wire existing LangGraph agents into the Anthropic Model Context Protocol server spec.

• Vercel@vercelrising

  Edge runtime for agent workers is live. Spawn durable background agents from any serverless deployment.

• Alex Albert@AlexAlbert__rising

  When your security scanner finds nothing scary on an agent deploy, check the orchestration layer again. That's usually where the jailbreak sneaks through.

• Replit@replitrising

  New agent deployment harness. One command to go from local orchestration to hosted agent worker.

@MistralAI continues its strategy of releasing open artifacts—in this case, data—to empower the broader community to train foundation models.

The only signal today is a major open dataset release from Mistral AI for training web-scale OCR models.

• Mistral AI@MistralAIrising

  Open dataset release: 100M-row web OCR dataset. Cleaned, licensed, ready to train.

The conversation, led by @GregKamradt and @reach_vb, is fragmenting from a monolithic 'RAG' solution towards 'context engineering' and specialized memory layers from startups like @mem0ai.

Developers are hitting the limits of simple RAG in large context windows and are exploring more complex memory architectures.

• Vaibhav Srivastav@reach_vbrising

  Tested the new 10M context memory window end to end. Surprising failure modes around rag retrieval cache invalidation, thread below.

• Greg Kamradt@GregKamradtrising

  RAG is dead, long live context engineering. My framework for when to cache, when to retrieve, and when to just dump memory into the prompt.

• mem0@mem0airising

  Memory layer for agents: differentiating working memory from the subconscious store. Vector index isn't enough anymore.

• LlamaIndex@llamaindexrepeated

  Knowledge graph retrieval walkthrough: when semantic vector search misses, graph hop beats it every time.

Both @NotionHQ and @linear are converging on similar AI-driven automation features, indicating a pattern of embedding quiet, background orchestration into SaaS tools.

Workspace automation tools are shipping AI-powered features for background tasks like issue triage and data entry.

• Notion@NotionHQrising

  Notion workspace automation is out of beta. Auto-fill tables, chained updates across databases, and a new audit log surface.

• Linear@linearrising

  Linear now auto-triages incoming issues. Quiet launch, but already our favorite workspace feature of the year.

• Temporal@temporaliorepeated

  Orchestrating agents with durable workflows: replayable, resumable, and multi-worker by default. Walkthrough from our infra team.

• James Clear@jamesclearrepeated

  The best habit tracker is the one you actually open. Three open-source alternatives worth trying.

A convergence on programmatic prompt optimization is visible, with @weights_biases performing large-scale analysis and frameworks like @dspy_ai automating the search for optimal prompts.

The discussion is shifting from anecdotal prompt tricks to systematic, large-scale benchmarking of system prompts.

• dotey@doteyrising

  Five prompt tricks learned this week from reviewing 200 production prompts. Short thread.

• Weights & Biases@weights_biasesrising

  System prompt benchmarking at scale: we ran 40k variants across 6 frontier models. The efficient frontier is not where you think.

@jerryjliu0's comment reveals that dataset quality, specifically filtering out plausible but harmful synthetic data, remains a key bottleneck for improving agent generalization.

A single tweet highlights the critical but often overlooked challenge of curating high-quality synthetic data for agent training.

• Jerry Liu@jerryjliu0repeated

  Dataset curation for agent training: how we filter synthetic data that looks good but poisons generalization.