Meredith Shubel writes that Vercel published `design.md`, a public prompt file that cut agent-generated design failures by 57% across 200+ agent runs, though none of the six tested pages was ship-ready. The system has three layers: a prompt encoding design judgment, a public stylesheet for mechanical layout rules, and an evaluation loop that converts human feedback into deterministic checks. A Slack-based agent (`design-agent`) consolidates weekly feedback from GitHub and Figma into proposed guidance updates.
- The comparison test used Codex with GPT-5.5: 39 failure instances with `design.md` versus 91 without.
- Vercel's first attempt to port its internal "product design" skill to a public prompt failed because subjective design language was interpreted differently by each model.
- Recurring complaint counts are tracked over time; if a fix doesn't reduce its count, the fix is flagged for refinement.
- The comparison test used Codex with GPT-5.5: 39 failure instances with `design.md` versus 91 without.
- Vercel's first attempt to port its internal "product design" skill to a public prompt failed because subjective design language was interpreted differently by each model.
- Recurring complaint counts are tracked over time; if a fix doesn't reduce its count, the fix is flagged for refinement.
Leela Kumili writes about DoorDash's Flux platform, which moved LLM-based coding agent workloads from developer laptops to cloud infrastructure, automating 130,000 engineering tasks in a single month and supporting over 25,000 automated code reviews per week. The platform was built after local execution hit limits on power, uptime, and security, and is organized around four primitives: Firecracker microVM sandboxes, an in-house MCP gateway, YAML-defined playbooks, and multiple invocation surfaces (Slack, GitHub, cron, CLI, conversational interfaces).
- Sandboxes achieve a 95th percentile SLO under 5 seconds for full setup, including microVM start, repo clone, build tool install, and agent harness configuration.
- Playbooks can mix agent-driven steps with deterministic code where predictable execution or validation is required.
- The Agent Gateway enforces scoped permissions and logs all agent activity for auditing and policy enforcement.
- DoorDash switched Slack integration from private channels to public threads so engineers could observe agent executions and see how other teams delegated work.
- Sandboxes achieve a 95th percentile SLO under 5 seconds for full setup, including microVM start, repo clone, build tool install, and agent harness configuration.
- Playbooks can mix agent-driven steps with deterministic code where predictable execution or validation is required.
- The Agent Gateway enforces scoped permissions and logs all agent activity for auditing and policy enforcement.
- DoorDash switched Slack integration from private channels to public threads so engineers could observe agent executions and see how other teams delegated work.
Mashrul Haque writes about using git worktrees to run multiple LLM coding agents in parallel, each on its own branch and isolated directory, eliminating the bottleneck of sequential agent sessions. He demonstrates a 5-agent workflow with Claude Code on a .NET/Blazor project, reporting roughly 5x throughput gains over single-agent sequential work.
- Boris Cherny, Creator and Head of Claude Code at Anthropic, calls worktrees his number one productivity tip and runs 3'' 5 simultaneously
- Claude Code ships a built-in `--worktree` (`-w`) flag that auto-creates an isolated worktree per session
- Boris Cherny, Creator and Head of Claude Code at Anthropic, calls worktrees his number one productivity tip and runs 3'' 5 simultaneously
- Claude Code ships a built-in `--worktree` (`-w`) flag that auto-creates an isolated worktree per session
Ory Team states traditional IAM frameworks (MFA, SSO, fixed API keys, IP whitelisting) are insufficient for autonomous AI agents entering production, as these agents reason, use tools, and execute multi-step workflows without constant human intervention.
The article describes six identity capabilities for securing these agents: verifiable cryptographically-signed agent identities with delegation chains, just-in-time ephemeral credentials, relationship-based access control bound to task intent, machine-speed automated containment via circuit breakers, in-the-loop runtime policy enforcement with configurable human approvals, and a web-scale identity control plane that handles machine-speed throughput and rapid sub-agent lifecycle governance.
- Sponsored post by Ory; Insight Partners (TNS owner) is an investor in both Ory and TNS.
- Ken Buckler (EMA Research Director) is quoted: "most organizations are woefully unprepared" for the security risks of managing agentic identities.
- A comparison table contrasts agents with humans and service accounts across velocity, decision logic, auth mechanics, and access granularity, highlighting that agents need ephemeral delegation and contextual attestation rather than passkeys or static keys.
- The ReBAC example given: "Agent X may read Document Y only if human user Z is the document owner and the active workflow is 'Data Summarization'."
- PKCE and strict token-binding are called out to prevent credential replay outside the agent's intended runtime context.
The article describes six identity capabilities for securing these agents: verifiable cryptographically-signed agent identities with delegation chains, just-in-time ephemeral credentials, relationship-based access control bound to task intent, machine-speed automated containment via circuit breakers, in-the-loop runtime policy enforcement with configurable human approvals, and a web-scale identity control plane that handles machine-speed throughput and rapid sub-agent lifecycle governance.
- Sponsored post by Ory; Insight Partners (TNS owner) is an investor in both Ory and TNS.
- Ken Buckler (EMA Research Director) is quoted: "most organizations are woefully unprepared" for the security risks of managing agentic identities.
- A comparison table contrasts agents with humans and service accounts across velocity, decision logic, auth mechanics, and access granularity, highlighting that agents need ephemeral delegation and contextual attestation rather than passkeys or static keys.
- The ReBAC example given: "Agent X may read Document Y only if human user Z is the document owner and the active workflow is 'Data Summarization'."
- PKCE and strict token-binding are called out to prevent credential replay outside the agent's intended runtime context.
SWE-bench Verified is a human-filtered subset of 500 instances from SWE-bench created in collaboration with OpenAI to provide a reliable evaluation set for coding agents and language models. Human annotators reviewed each instance to ensure problem descriptions are clear, test patches are correct, and tasks are solvable with available information. The Verified leaderboard shows results from a wide variety of AI coding systems, and a Bash Only view isolates language model performance using mini-SWE-agent in a minimal bash environment.
- Human validation ensures clarity, correctness of test patches, and solvability
- Bash-only comparison uses mini-SWE-agent with ReAct loop, no tools or scaffold
- Leaderboard distinguishes mini-SWE-agent LM results from full agent systems via Agent dropdown
- Release 2.x uses tool calling vs 1.x parses actions from output strings, making releases not directly comparable
- Human validation ensures clarity, correctness of test patches, and solvability
- Bash-only comparison uses mini-SWE-agent with ReAct loop, no tools or scaffold
- Leaderboard distinguishes mini-SWE-agent LM results from full agent systems via Agent dropdown
- Release 2.x uses tool calling vs 1.x parses actions from output strings, making releases not directly comparable
Kanwal Mehreen writes that as large language models move from chatbots to coding agents and autonomous workflows, good prompting is no longer enough and specification engineering is emerging as the key skill. It is the practice of defining goals, constraints, expected outputs, edge cases, tests, success criteria and failure modes so AI-assisted work is testable and reviewable. Prompt engineering asks how to ask, while specification engineering defines what done correctly means, a shift closer to product management, testing and research design than traditional prompting.
- A 2024 Requirement-Oriented Prompt Engineering paper found ROPE training improved requirement-writing ability by 20% versus 1% for conventional prompt engineering training.
- OpenAI Structured Outputs, Model Spec and Anthropic Constitution exemplify specification engineering at API and model-behavior levels.
- SWE-bench Verified is a human-validated subset used to evaluate real-world software issue solving with agents.
- Google's 2025 DORA report surveyed nearly 5,000 tech professionals and found AI amplifies existing organizational strengths and weaknesses.
- A 2024 Requirement-Oriented Prompt Engineering paper found ROPE training improved requirement-writing ability by 20% versus 1% for conventional prompt engineering training.
- OpenAI Structured Outputs, Model Spec and Anthropic Constitution exemplify specification engineering at API and model-behavior levels.
- SWE-bench Verified is a human-validated subset used to evaluate real-world software issue solving with agents.
- Google's 2025 DORA report surveyed nearly 5,000 tech professionals and found AI amplifies existing organizational strengths and weaknesses.
OpenSandbox is a general-purpose sandbox platform for AI applications offering multi-language SDKs, unified sandbox APIs and Docker/Kubernetes runtimes for use cases like coding agents, GUI agents, evaluation, code execution and RL training. It provides SDKs, CLI and MCP integration, a sandbox protocol for custom runtimes, built-in environments such as command, filesystem and code interpreter, network ingress/egress controls, credential vault injection and strong isolation via gVisor, Kata Containers and Firecracker.
- Release images published to Docker Hub, GHCR and Alibaba Cloud with Cosign signatures and provenance
- SDKs for Python, Java/Kotlin, TypeScript/JavaScript, C#/.NET and Go
- OpenSSF Best Practices badge and CNCF Landscape listing
- Release images published to Docker Hub, GHCR and Alibaba Cloud with Cosign signatures and provenance
- SDKs for Python, Java/Kotlin, TypeScript/JavaScript, C#/.NET and Go
- OpenSSF Best Practices badge and CNCF Landscape listing
The NOOA framework provides a way to build LLM agents using standard Pythonic object-oriented patterns. By treating agents as objects, developers can map state to typed fields and capabilities to methods where docstrings serve as prompts; specifically, an ellipsis in a method body triggers the runtime for an LLM-driven execution loop.
- Includes separate packages for CLI tools, memory management, and benchmarking.
- Supports various local and hosted models via LiteLLM integration.
- Offers automated tracing with an interactive web viewer for debugging.
- Necessitates OS-level isolation to safely execute LLM-generated code.
- Includes separate packages for CLI tools, memory management, and benchmarking.
- Supports various local and hosted models via LiteLLM integration.
- Offers automated tracing with an interactive web viewer for debugging.
- Necessitates OS-level isolation to safely execute LLM-generated code.
Asif Razzaq writes that NVIDIA Labs has open-sourced NOOA, a model-agnostic Python framework designed to streamline agentic development by consolidating prompt templates, tool schemas, and state into single class structures. By treating LLM-driven actions as standard methods with docstrings serving as prompts, the framework allows developers to build autonomous workflows that can be tested, traced, and version-controlled like ordinary software.
- Achieves 82.2% on SWE-bench Verified while using roughly half the tokens required by existing open harnesses.
- Employs a "pass by reference" mechanism for live Python objects via bounded previews to conserve context window space.
- Features an optional memory subsystem that utilizes SQLite and ACT-R activation ranking for record retrieval.
- Achieves 82.2% on SWE-bench Verified while using roughly half the tokens required by existing open harnesses.
- Employs a "pass by reference" mechanism for live Python objects via bounded previews to conserve context window space.
- Features an optional memory subsystem that utilizes SQLite and ACT-R activation ranking for record retrieval.
MindMux presents brain.md, an open-source toolkit that provides a persistent memory layer for coding agents by storing project knowledge as plain Markdown files within a repository. This system ensures that critical decisions and constraints are durable across different LLM sessions and machines via version control. A zero-dependency CLI manages the reading and writing of these files to maintain data integrity through an append-only timeline.
- Uses Markdown instead of databases like SQLite to facilitate easier diffing in git history.
- Features a "correct by construction" design that prevents malformed edits by making the CLI the exclusive writer.
- Supports integration with several agents including Claude Code, Codex, Cursor, and Pi.
- Uses Markdown instead of databases like SQLite to facilitate easier diffing in git history.
- Features a "correct by construction" design that prevents malformed edits by making the CLI the exclusive writer.
- Supports integration with several agents including Claude Code, Codex, Cursor, and Pi.
