Tag
OpenAI releases GPT-6 Astra, its most capable AI model for advanced reasoning, software engineering, and agent workflows, featuring async tool calling and mid-turn steering with a tiered rollout plan.
Introducing Spark-X2.5-4B and Spark-X2.5-1.7B, compact general-purpose language models with native 1M-token context, strong coding and agent capabilities, and broad hardware compatibility.
The article discusses the challenges of testing AI agent workflows in sandbox environments versus production, highlighting issues like silent failures, state management, and the inadequacy of current testing methods, and seeks community advice on best practices.
This article criticizes the severe stability issues of the GLM-5.3-flash model in production, like silent failures for large requests and workflow disruptions, despite its good performance.
Experiential is an open-source gateway and router for AI agent workflows that enables usage-based optimization of models through a single OpenAI-compatible API.
A discussion proposing that AI agents working with production data should use data branches — letting the agent write to a cloned database and then reviewing the final diff instead of approving each action individually.
A developer asks for practical strategies to make reviewer/critic AI agents catch real flaws and drive coding tasks to completion without human oversight, covering prompting, testing access, and agent separation.
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.