Denoise · Twitter

A convergence is happening between formal security research from @AnthropicAI and @GoogleDeepMind and practical application by pentesters like @MalwareTechBlog.

Major labs are publishing formal frameworks for agent red-teaming and disclosing agent-specific jailbreak chains.

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

@AnthropicAI's product launch, amplified by @karpathy's commentary, consolidates the narrative that terminal agents will supersede the IDE-plugin model.

Anthropic's release of the terminal-native Claude Code 1.5 agent dominates the conversation, sparking debate on the future of IDEs.

• 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 new 'agent ops' stack is forming, with @OpenAI providing primitives, @LangChainAI ensuring interoperability, and @vercel offering specialized runtimes.

The ecosystem is rapidly building for agents, with OpenAI releasing an SDK and platforms like Vercel and Replit providing deployment targets.

• 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 most of the industry focuses on agent orchestration, @MistralAI continues to execute its distinct strategy of releasing foundational open data artifacts.

A single, high-value open dataset for web OCR was released by MistralAI.

• Mistral AI@MistralAIrising

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

The RAG pattern is fragmenting, with voices like @GregKamradt and tools like @mem0ai pushing for specialized memory layers over simple vector retrieval.

The discourse is evolving from simple RAG to more complex 'context engineering' to support long-running 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.

A convergence is visible between general productivity tools (@NotionHQ, @linear) and specialized agent frameworks (@temporalio), as both tackle workflow orchestration.

Workspace productivity tools like Notion and Linear are shipping agent-like automation features for tasks like 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.

The community is moving from anecdotal advice (@dotey) to data-driven approaches for prompt engineering, exemplified by @weights_biases' large-scale study.

Discussion centers on scaling up system prompt optimization, moving from individual 'tricks' to systematic, large-scale benchmarking.

• 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 highlights a critical bottleneck in the agent development lifecycle: the non-trivial task of dataset filtering to ensure model generalization.

The focus is on the nuanced infrastructure challenge of curating high-quality synthetic data for training agents.

• Jerry Liu@jerryjliu0repeated

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