Tag
The article argues that many AI agent workflows waste money by routing every task to frontier models, and suggests using cheaper model tiers for simple, structured tasks while escalating harder ones. It provides a cost comparison showing up to 75% savings with a tiered approach.
The article argues that practical AI business banking should rely on permissioned roles and limited access rather than full autonomy, with human approval required for large transactions.
The article discusses the difference between retrying a failed agent step and safely resuming a multi-step run, emphasizing that they are not equivalent operations.
A technical write-up discusses the shift from agent loops to structured graphs in production AI agent work, backed by references to durable execution engines (Temporal, Restate) and research like AFlow which uses Monte Carlo Tree Search to optimize workflow graphs.
Git-native agent workflows are gaining credibility as a practical standard for development, moving beyond being seen as a gimmick.
The author discusses the practical failure modes of AI agents that use paid tools, such as cost unawareness, double-spends, and the need for human approval, suggesting that agent payments should be treated as a separate execution layer.
The article explores how AI agent workflows are reintroducing software engineering challenges around reproducibility, auditability, and state management that were previously solved with version control, CI/CD, and static code practices, while noting emerging solutions like GitHub's Agentic Workflows and git-native approaches.
The author asks how developers are regression-testing AI agent workflows, noting common failure modes and sharing their work on adding eval support to Runme for recording tasks, scoring trajectories, and comparing against baselines.
The author argues that chat-first AI tools are insufficient for building autonomous agent workflows and describes alternative primitives like scheduled triggers and sub-agent delegation, advocating for a paradigm shift from 'chat with tools' to 'autonomous processes that use LLMs'.
A developer created a gateway that structurally prevents prompt injection in agent workflows, focusing on architecture rather than model-level fixes.
The Claude Code team published a blog post introducing the /goal and /loop features. The article analyzes the paradigm shift in AI programming from single-turn conversations to iterative operations, detailing four types of loops (turn-based, goal-based, scheduled, proactive) and their applicable scenarios, while proposing the execution layer concept of Harness Engineering.
The author open-sourced a Codex skill called 'prompt-to-loop-engineer' that converts vague prompts into structured, intent-preserving execution loops with anti-drift checks, aiming to make agents more reliable for real-world tasks.
The author identifies four key bottlenecks for AI agent systems in real-world applications: physical constraints, adversarial pressure, institutional authority, and relational trust, and asks where others see agent workflows failing.
The author shares a practical 4-tier LLM routing stack for agent work, where a fast orchestrator handles most requests and only escalates to expensive models when deep reasoning is required, significantly improving cost and interactivity.
推荐一个提供预构建代理循环工作流的网站loops.elorm.xyz,开发者可直接复制闭环工作流到自己的agent workflow中,实用且开源。
The article explores the challenge of per-prompt model routing in AI agents, questioning whether anyone has effectively solved it. It points out that current practices rely on gut feeling, flat-rate plans reduce pressure to optimize, and a triage layer may introduce its own costs.
Coding AI agents often make excessive changes beyond the requested scope; the author proposes a 'change budget' as a structural boundary to prevent scope creep in agent workflows.
Guava is a harness framework for embodied tool use that combines high-level reasoning with external modules, enabling compact models to perform complex manipulation tasks with minimal training data. Experiments show performance comparable to frontier proprietary models.
Introduces Parallel-Synthesis, a framework that enables direct consumption of KV caches from parallel worker agents, reducing time-to-first-token by 2.5x–11x while maintaining or improving performance on agentic tasks.
Discusses the hassle of managing separate API keys and billing for multiple tools in agent workflows. Highlights Orthogonal (YC W26), an MCP server/SDK offering unified pay-per-call access to various APIs.