Denoise · Twitter

The attack surface is shifting from simple prompt injection to complex exploits in the agent orchestration layer, with @AnthropicAI and @GoogleDeepMind leading the public research.

Major labs are publishing formal frameworks and disclosures for red-teaming autonomous agents, focusing on emerging 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 battle for developer workflow is moving from the IDE to the terminal, a pattern identified by @karpathy and instantiated by @AnthropicAI's Claude Code.

The release of terminal-native coding agents by major players signals a fundamental shift in the primary developer interface.

• 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 de facto agent stack is emerging, with @OpenAI defining protocols, and platforms like @vercel and @replit building the managed runtimes.

Conversation centers on SDKs, runtimes, and protocols for orchestrating and deploying stateful, 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.

While the agent narrative dominates, @MistralAI's release indicates a parallel focus on improving foundational vision and data-parsing capabilities.

The only signal in this category is a large-scale open dataset release for web OCR from MistralAI.

• Mistral AI@MistralAIrising

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

Simple vector retrieval is now seen as insufficient; actors like @mem0ai and @GregKamradt are pushing for memory architectures that differentiate working and long-term stores.

The discourse has evolved beyond simple RAG towards 'context engineering' and structured memory systems for agents.

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

Agent-like patterns of task automation are being productized in mainstream workspace tools, parallel to the hardcore developer tool discussion.

Adjacent SaaS tools like Notion and Linear are shipping AI-powered workflow automation and auto-triage features.

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

The practice of prompt engineering is maturing, with @weights_biases advocating for data-driven optimization over the folk wisdom shared by creators like @dotey.

The focus is on moving 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.

This points to an underlying ML infrastructure problem: as agent complexity grows, data quality and filtering, as noted by @jerryjliu0, become critical bottlenecks.

A single tweet from LlamaIndex's co-founder highlights the 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.