Denoise · Twitter

Consensus from Anthropic, DeepMind, and MalwareTechBlog shows the security frontier has moved beyond prompt injection to complex agent behaviors like tool leakage and sandbox escapes.

Major labs are releasing red-teaming frameworks and disclosures for autonomous agents, focusing on multi-step, orchestration-level vulnerabilities.

• 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.

The pattern is a clear shift from IDE plugins (Copilot) to standalone terminal agents (Claude Code), validated by commentary from @karpathy and adoption reports from @levelsio.

Anthropic's release of Claude Code 1.5, a terminal-native agent, dominates the conversation, with benchmarks and developer adoption stories.

• 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 happening around standardizing agent orchestration. OpenAI's SDK, LangChain's protocol integration, and Vercel's edge runtime are all aiming to become the 'Kubernetes for agents'.

OpenAI, Vercel, and Replit released new infrastructure for deploying and orchestrating multi-worker agents, signaling a race to build the defining platform.

• 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.

While others focus on the agent application layer, Mistral continues to commoditize the data layer, releasing high-quality, open datasets to fuel foundational model development.

Mistral AI released a large, cleaned, 100M-row dataset for web OCR, continuing its strategy of providing open foundational resources.

• Mistral AI@MistralAIrising

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

Simple vector retrieval is no longer sufficient. Voices like @GregKamradt and @mem0ai are pushing for more sophisticated memory layers that distinguish between working and long-term storage.

The conversation is evolving from simple RAG to 'context engineering,' with deep dives into cache invalidation and advanced 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.

The trend is moving beyond chat interfaces to embed silent, autonomous agents for background process automation, as demonstrated by Notion's database updates and Linear's auto-triage.

SaaS platforms like Notion and Linear are embedding autonomous automation directly into their core workflows for tasks like data entry and issue triage.

• 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.

Prompt engineering is maturing into a data-driven discipline. Weights & Biases' large-scale study contrasts with anecdotal advice, showing a move towards rigorous optimization.

The focus is shifting from anecdotal prompt 'tricks' to systematic, large-scale benchmarking of system prompts to find optimal performance.

• 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.

As agent capabilities advance, @jerryjliu0 highlights that the bottleneck is shifting to data quality, specifically filtering synthetic data that appears correct but poisons generalization.

The discussion focuses on the nuanced problem of curating synthetic data for agent training to avoid performance degradation.

• Jerry Liu@jerryjliu0repeated

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