# agentic workflows

An AI-driven process in which autonomous agents make decisions, coordinate tasks, and execute complex workflows with minimal human intervention.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Chapter 1: Introduction to AIAutomation

DevFeed: [Chapter 1: Introduction to AIAutomation](<https://devfeed.tech/articles/chapter-1-introduction-to-aiautomation-146464.md>)

Original publisher: [Read original article](<https://linuxhandbook.com/courses/n8n/n8n-intro/>)

Author: Yash Kiran Patil

Published: 2026-11-20T14:20:27Z

Content type: article

Language: en

Sources: [Linux Handbook](<https://devfeed.tech/sources/linux-handbook.md>)

Topics: [workflow automation](<https://devfeed.tech/topics/workflow-automation.md>), [n8n](<https://devfeed.tech/topics/n8n.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-automation](<https://devfeed.tech/tags/ai-automation.md>), [ai-model](<https://devfeed.tech/tags/ai-model.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [apis](<https://devfeed.tech/tags/apis.md>), [automation](<https://devfeed.tech/tags/automation.md>), [backups](<https://devfeed.tech/tags/backups.md>), [code](<https://devfeed.tech/tags/code.md>), [community-edition](<https://devfeed.tech/tags/community-edition.md>), [comparison](<https://devfeed.tech/tags/comparison.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [email](<https://devfeed.tech/tags/email.md>), [introduction](<https://devfeed.tech/tags/introduction.md>), [n8n](<https://devfeed.tech/tags/n8n.md>), [process](<https://devfeed.tech/tags/process.md>), [routine](<https://devfeed.tech/tags/routine.md>), [tasks](<https://devfeed.tech/tags/tasks.md>), [time](<https://devfeed.tech/tags/time.md>), [work](<https://devfeed.tech/tags/work.md>)

### AI overview

AI automation connects AI to repeatable processes to reduce hands-on work. A workflow follows designer-defined steps and conditions; an agent gives the model more freedom to choose tools or actions based on its goal and inputs. Both can include safeguards or human approval. The text recommends workflows for predictable, inspectable tasks and agents when choosing among actions is needed. It introduces n8n, Make, and Zapier, then selects n8n for Linux and open-source examples because it offers a visual editor, integrations, API access, and self-hosting. Its Community edition can be used without a software subscription for permitted personal or internal use, but its Sustainable Use License limits some commercial uses. Self-hosting provides control while making the operator responsible for updates, backups, access control, and availability. Platform features, licensing, and prices may change, so the text advises checking current terms.

### Source excerpt

Today, AI can help with many kinds of work, but routine tasks still take time when they are handled manually. AI automation combines AI with a repeatable process so that some of those tasks can run with less hands-on effort. In this series, we'll learn how to use

## Why AI Agents Leave You More Tired, Not More Rested

DevFeed: [Why AI Agents Leave You More Tired, Not More Rested](<https://devfeed.tech/articles/why-ai-agents-leave-you-more-tired-not-more-rested-146457.md>)

Original publisher: [Read original article](<https://hackernoon.com/why-ai-agents-leave-you-more-tired-not-more-rested?source=rss>)

Author: Dmitry Mishunin

Published: 2026-11-20T12:02:01Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [context window](<https://devfeed.tech/topics/context-window.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [attention](<https://devfeed.tech/tags/attention.md>), [burnout](<https://devfeed.tech/tags/burnout.md>), [compaction](<https://devfeed.tech/tags/compaction.md>), [context-switching](<https://devfeed.tech/tags/context-switching.md>), [context-window](<https://devfeed.tech/tags/context-window.md>), [deep](<https://devfeed.tech/tags/deep.md>), [developer-productivity](<https://devfeed.tech/tags/developer-productivity.md>), [domains](<https://devfeed.tech/tags/domains.md>), [focus](<https://devfeed.tech/tags/focus.md>), [mental-health](<https://devfeed.tech/tags/mental-health.md>), [productivity](<https://devfeed.tech/tags/productivity.md>), [switching](<https://devfeed.tech/tags/switching.md>), [work-life-balance](<https://devfeed.tech/tags/work-life-balance.md>)

### AI overview

The article argues that AI agents can leave people more tired because they expand one person's work across unfamiliar domains, increase task switching, and raise expectations for faster delivery. It cites research on switching costs and attention residue, plus a survey in which 77% of AI-using employees said AI added to their workload; it notes the survey came from Upwork, which sells freelance work. The article compares human recovery to an agent's context compaction: people need sleep and breaks to recover and retain information, but have no instant reset. It recommends focus blocks with genuine breaks, grouping work by domain, attention-restoring activities such as walks, adequate sleep, and deadlines that account for review and decisions. Its central caution is that faster tools can create more work rather than saved time, so sustained use requires recovery.

### Source excerpt

Why working with AI agents drains people by lunch: domain switching, deadlines measured in hours, and the myth of an infinite human context window.

## Apple doesn't need the smartest AI agent. It needs the most trusted one

DevFeed: [Apple doesn't need the smartest AI agent. It needs the most trusted one](<https://devfeed.tech/articles/apple-doesn-t-need-the-smartest-ai-agent-it-needs-the-most-trusted-one-146557.md>)

Original publisher: [Read original article](<https://www.computerworld.com/article/4251496/apple-doesnt-need-the-smartest-ai-agent-it-needs-the-most-trusted-one.html>)

Author: Jonny Evans

Published: 2026-11-20T10:30:00Z

Content type: opinion

Language: en

Sources: [Computerworld](<https://devfeed.tech/sources/computerworld.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [Multi-step AI processes](<https://devfeed.tech/topics/multi-step-ai-processes.md>), [Local AI](<https://devfeed.tech/topics/local-ai.md>), [least privilege](<https://devfeed.tech/topics/least-privilege.md>), [ai security](<https://devfeed.tech/topics/ai-security.md>)

Tags: [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [apple](<https://devfeed.tech/tags/apple.md>), [apple-artificial-intelligence-productivity-software-siri-vendors-and-providers-voice-assistants](<https://devfeed.tech/tags/apple-artificial-intelligence-productivity-software-siri-vendors-and-providers-voice-assistants.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [privacy](<https://devfeed.tech/tags/privacy.md>), [private-cloud-compute](<https://devfeed.tech/tags/private-cloud-compute.md>), [productivity](<https://devfeed.tech/tags/productivity.md>), [productivity-software](<https://devfeed.tech/tags/productivity-software.md>), [siri](<https://devfeed.tech/tags/siri.md>), [siri-ai](<https://devfeed.tech/tags/siri-ai.md>), [storytype-opinion](<https://devfeed.tech/tags/storytype-opinion.md>), [vendors-and-providers](<https://devfeed.tech/tags/vendors-and-providers.md>)

### AI overview

The article argues Apple's advantage in agentic AI could come from trust, integration and distribution rather than having the smartest model. It describes safeguards already in place: users are prompted to consider risks before granting agents Full Disk Access, and agents can be confined to specified folders, while Siri provides context for actions. The author expects demanding tasks to use Private Cloud Compute and speculates Apple may add Secure Exclave to minimize uploaded information; local Macs could handle some AI analysis. Whether this approach succeeds depends on reliable execution of complex, multistep actions, including how well App Intents perform. These are partly predictions, not confirmed features or outcomes.

### Source excerpt

When MacPaw, Proton, Google, OpenAI, Anthropic, and others are doing it, it's not really such a surprise that Apple is working to introduce agentic AI tools in Siri and Apple Intelligence. The wider question is how the company plans to deploy these tools -- how it will deliver the maximum convenience at the least possible cost to user privacy and data integrity. Some of those answers are already easy to speculate on. Apple has already put some of the building blocks in place, including the recent move to make consumers think more deeply when providing AI agents with Full Disk Access. Convenience versus control I know some competitors are complaining about this, but frankly I think user privacy outweighs commercial convenience -- users should have a conscious choice, which Apple delivers. "Addressing this is critical," Apple told developers. "As AI agents become increasingly capable and autonomous, the risks associated with this level of access will grow substantially. We are committed to ensuring users clearly understand these risks before granting such access, so they can make informed decisions about their own data and privacy." Apple's decision to make it possible to confine agents to folder access also speaks volumes, as it shows us how it will probably choose to manage its own agents. Siri AI may have contextual understanding of everything, which can inform Siri Agents, but the agents themselves will have but limited access to your data. They gain contextual direction from the user and from Siri AI but are limited to the proscribed folders and files when it comes to acting. Making the cloud sweat a little Some tasks are harder than others. The really hard tasks will still lean into Apple's Private Cloud Compute, and I think the company will try to introduce Secure Exclave into that relationship, so even the most complex task instructions only upload the minimum quantity of your information required to get a task done. Apple sells hardware, of course, so it makes

## An insider's look at SAP's 'Autonomous Enterprise'

DevFeed: [An insider's look at SAP's 'Autonomous Enterprise'](<https://devfeed.tech/articles/an-insider-s-look-at-sap-s-autonomous-enterprise-146154.md>)

Original publisher: [Read original article](<https://www.cio.com/article/4249833/sap-caio-we-need-to-be-more-precise-in-managing-the-use-of-ai.html>)

Author: Manfred Bremmer

Published: 2026-11-20T10:01:00Z

Content type: news

Language: en

Sources: [CIO](<https://devfeed.tech/sources/cio.md>)

Topics: [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-platform](<https://devfeed.tech/tags/ai-platform.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [artificial-intelligence-enterprise-applications-erp-systems-sap-vendors-and-providers](<https://devfeed.tech/tags/artificial-intelligence-enterprise-applications-erp-systems-sap-vendors-and-providers.md>), [autonomous-enterprise](<https://devfeed.tech/tags/autonomous-enterprise.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [enterprise-applications](<https://devfeed.tech/tags/enterprise-applications.md>), [erp-systems](<https://devfeed.tech/tags/erp-systems.md>), [joule](<https://devfeed.tech/tags/joule.md>), [joule-work](<https://devfeed.tech/tags/joule-work.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [sap](<https://devfeed.tech/tags/sap.md>), [storytype-interview](<https://devfeed.tech/tags/storytype-interview.md>), [vendors-and-providers](<https://devfeed.tech/tags/vendors-and-providers.md>)

### AI overview

SAP's agent governance approach combines use case and consumption estimates with per-user or departmental budgets, visible daily usage limits, and optional analysis of agent outcomes. Joule Work offers model modes and model selection for custom agents; SAP is testing automatic routing, while noting that choosing models for transactional tasks is more complex. Joule Studio access is assigned by IT, with role-based sharing, version control, review status, and company-specific approvals. Monitoring, generated tests, agent mining, and process mining feed findings into iterative improvement. SAP says it still needs to link AI consumption more directly to business value, and cross-provider governance remains difficult without a common standard. The interview also says clear, rule-based tasks may be cheaper and faster with classic workflows, while hybrid workflows can reserve agents for steps needing additional intelligence.

### Source excerpt

At the TechEd developer conference in Berlin, SAP presented additional details of its "Autonomous Enterprise" concept, which includes AI capabilities via Joule Work and SAP Autonomous Suite, built on the SAP Business AI Platform. The company's focus is not just AI, but AI agents capable of acting automatically within the SAP system by performing analyses and answering queries. This raises questions, such as: How can the costs of AI agents be controlled? Who is allowed to develop the agents, and how can companies maintain oversight? Jonathan von Rüden, chief AI officer of SAP, explains in an interview with Computerwoche how the software provider is addressing these questions -- and where work still needs to be done. Computerwoche: Companies are increasingly using AI and developing more and more AI agents. But it is often difficult to predict how costs in this area will develop over time. How is SAP addressing this? Jonathan von Rüden: We generally proceed in three steps. First, we clarify together with the customer or in product management which use cases are relevant and what should be achieved with them. We distinguish between different areas of focus. First, there's general productivity: transcriptions, summaries, presentations, or information research. This now extends far beyond classic office tasks. For example, information from the internet can be combined with SAP data and used for financial analysis. However, this area is difficult to define precisely because it encompasses so many tasks in everyday work. In addition, there are dedicated AI agents that are centrally deployed and managed by IT. These can be standard agents from SAP or customer-specific agents from Joule Studio. Finally, there are use cases where companies can differentiate themselves significantly. Here, they should consider whether they can develop their own solution. Based on this information, we estimate consumption. To do this, we consider factors such as the number of employees, how frequ

## Agentic AI repeats same old enterprise adoption cycle

DevFeed: [Agentic AI repeats same old enterprise adoption cycle](<https://devfeed.tech/articles/agentic-ai-repeats-same-old-enterprise-adoption-cycle-146087.md>)

Original publisher: [Read original article](<https://www.infoworld.com/article/4249734/agentic-ai-repeats-same-old-enterprise-adoption-cycle.html>)

Author: David Linthicum

Published: 2026-11-20T09:00:00Z

Content type: opinion

Language: en

Sources: [InfoWorld](<https://devfeed.tech/sources/infoworld.md>)

Topics: [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [Enterprise Architecture](<https://devfeed.tech/topics/enterprise-architecture.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [API Governance](<https://devfeed.tech/topics/api-governance.md>), [observability](<https://devfeed.tech/topics/observability.md>), [LLM security](<https://devfeed.tech/topics/llm-security.md>)

Tags: [adoption](<https://devfeed.tech/tags/adoption.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [apis](<https://devfeed.tech/tags/apis.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [artificial-intelligence-emerging-technology-generative-ai](<https://devfeed.tech/tags/artificial-intelligence-emerging-technology-generative-ai.md>), [automate](<https://devfeed.tech/tags/automate.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [cost](<https://devfeed.tech/tags/cost.md>), [costs](<https://devfeed.tech/tags/costs.md>), [data](<https://devfeed.tech/tags/data.md>), [decision](<https://devfeed.tech/tags/decision.md>), [emerging-technology](<https://devfeed.tech/tags/emerging-technology.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [exception-handling](<https://devfeed.tech/tags/exception-handling.md>), [generative-ai](<https://devfeed.tech/tags/generative-ai.md>), [guardrails](<https://devfeed.tech/tags/guardrails.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [logging](<https://devfeed.tech/tags/logging.md>), [observability](<https://devfeed.tech/tags/observability.md>), [production](<https://devfeed.tech/tags/production.md>), [project](<https://devfeed.tech/tags/project.md>), [storytype-opinion](<https://devfeed.tech/tags/storytype-opinion.md>)

### AI overview

A distributor's agentic AI sales system ran successfully, but after supporting integration, governance, security, testing and operational costs were included, it cost roughly 20 times as much as a traditional architecture for about the same ROI. The article argues that agents are most useful when work requires interpretation, adaptation and semi-autonomous action; stable, rules-based or highly regulated workflows may be served more economically by conventional applications, workflow engines, rules or API integration. It recommends starting with measurable business value and assessing production costs and governance needs rather than adopting an architecture because it is fashionable. The text compares this adoption pattern with SOA, microservices and cloud-native systems, each of which can deliver benefits but also impose complexity when used without a fitting need or organizational maturity.

### Source excerpt

The pitch sounded perfect. A large regional distributor needed to build a new sales transaction management system. The goal was straightforward: automate parts of order intake, discount approvals, exception handling, customer communications, and inventory checks. It was not a trivial system, but it was also something the industry had built before. Then the vendor presentations began. Every software provider seemed to have a new agentic AI story. Their platforms had agents that could make decisions, orchestrate workflows, interpret customer intent, route exceptions, and learn from business context. One vendor described its offering as a common LLM brain that could make decisions as if the company had hired 10,000 experts, except those experts were not on the payroll. That line was from an actual sales pitch, and it landed well in the boardroom. The company decided to go agentic. The architecture would use AI agents to manage decision flows, invoke tools, check policies, interact with enterprise systems, and escalate only when needed. It looked modern. It looked strategic. It looked like the future. Then reality arrived. Building the system required far more integration work than expected. Each agent needed access to clean data, governed APIs, business rules, security controls, observability, exception handling, and human override mechanisms. The team had to build guardrails around decisions, logging around reasoning, test harnesses for unpredictable outcomes, and new operational processes for things traditional systems handled more predictably. Costs ballooned. Security reviews took longer. Operational complexity increased. The project ultimately ran fine once in production, but six months later, the company realized the uncomfortable truth: the system cost roughly 20 times more than a traditional architecture would have cost when all supporting complexity was included, and it delivered about the same ROI. I am hearing versions of this story once or twice a week from

## Human in the Loop AI: How to Safely Scale Agentic Workloads with Tunable Autonomy

DevFeed: [Human in the Loop AI: How to Safely Scale Agentic Workloads with Tunable Autonomy](<https://devfeed.tech/articles/human-in-the-loop-ai-how-to-safely-scale-agentic-workloads-with-tunable-autonomy-146217.md>)

Original publisher: [Read original article](<https://hackernoon.com/human-in-the-loop-ai-how-to-safely-scale-agentic-workloads-with-tunable-autonomy?source=rss>)

Author: PlayerZero

Published: 2026-11-20T06:49:40Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [human in the loop agent](<https://devfeed.tech/topics/human-in-the-loop-agent.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>)

Tags: [accountability](<https://devfeed.tech/tags/accountability.md>), [adoption](<https://devfeed.tech/tags/adoption.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-identity](<https://devfeed.tech/tags/agent-identity.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agentic-ai-governance](<https://devfeed.tech/tags/agentic-ai-governance.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agent-accountability](<https://devfeed.tech/tags/ai-agent-accountability.md>), [ai-agent-autonomy-levels](<https://devfeed.tech/tags/ai-agent-autonomy-levels.md>), [ai-engineering-context](<https://devfeed.tech/tags/ai-engineering-context.md>), [ai-workflow-automation](<https://devfeed.tech/tags/ai-workflow-automation.md>), [autonomous-ai-workflows](<https://devfeed.tech/tags/autonomous-ai-workflows.md>), [autonomy](<https://devfeed.tech/tags/autonomy.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [good-company](<https://devfeed.tech/tags/good-company.md>), [guardrails](<https://devfeed.tech/tags/guardrails.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [human-in-the-loop](<https://devfeed.tech/tags/human-in-the-loop.md>), [human-in-the-loop-ai](<https://devfeed.tech/tags/human-in-the-loop-ai.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [performance](<https://devfeed.tech/tags/performance.md>), [performance-metrics](<https://devfeed.tech/tags/performance-metrics.md>), [safely](<https://devfeed.tech/tags/safely.md>), [scale](<https://devfeed.tech/tags/scale.md>), [teams](<https://devfeed.tech/tags/teams.md>), [tunable-ai-autonomy](<https://devfeed.tech/tags/tunable-ai-autonomy.md>)

### AI overview

The article recommends expanding AI agent autonomy gradually, based on evidence and workflow risk, while keeping humans accountable at critical checkpoints. It defines four levels: manual approval, recommend-only, auto-with-approval at key steps, and fully autonomous within boundaries; teams can tune these by service, repository, severity, ticket type, or team. Begin with human review, then weigh approval rates alongside MTTR, regressions, escaped defects, rollbacks, and cycle time. Also assess whether agents understand system and business context, know whom to involve, and follow team processes. Autonomy gates are especially important for cross-team handoffs and disruptive or hard-to-reverse actions. The proposed safeguards are audit trails, attributable actions, reversibility, and runtime policy constraints such as tool allowlists and scope isolation. The article reports that Cyrano Video reduced engineering support and bug-fix time by roughly 80%; Cayuse reportedly found and fixed 90% of issues before users noticed and cut average resolution time by 80%.

### Source excerpt

Learn how tunable autonomy helps engineering teams expand AI agent responsibilities through human approval, performance metrics, autonomy gates, and guardrails.

## Generalist Meets Specialists: An Evolving Multimodal Agent with Persistent Tool Orchestration for Traffic Scenario Understanding

DevFeed: [Generalist Meets Specialists: An Evolving Multimodal Agent with Persistent Tool Orchestration for Traffic Scenario Understanding](<https://devfeed.tech/articles/generalist-meets-specialists-an-evolving-multimodal-agent-with-persistent-tool-orchestration-for-traffic-scenario-understanding-145597.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.25868>)

Author: Linjia Kang, Binhan Jiang, Juan Yang, Zhiqin Song, Xiangsen Wu, Qionglin Ren, Jiang Liu, Zhongjiang He, Hao Sun

Published: 2026-11-20T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>)

Topics: [Multi-step AI processes](<https://devfeed.tech/topics/multi-step-ai-processes.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [llm-reasoning](<https://devfeed.tech/topics/llm-reasoning.md>), [Reinforcement learning](<https://devfeed.tech/topics/reinforcement-learning.md>)

Tags: [adaptive](<https://devfeed.tech/tags/adaptive.md>), [adoption](<https://devfeed.tech/tags/adoption.md>), [agent](<https://devfeed.tech/tags/agent.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [challenges](<https://devfeed.tech/tags/challenges.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [completion](<https://devfeed.tech/tags/completion.md>), [cost](<https://devfeed.tech/tags/cost.md>), [cost-savings](<https://devfeed.tech/tags/cost-savings.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [error](<https://devfeed.tech/tags/error.md>), [evolution](<https://devfeed.tech/tags/evolution.md>), [execution](<https://devfeed.tech/tags/execution.md>), [fast](<https://devfeed.tech/tags/fast.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [generalist](<https://devfeed.tech/tags/generalist.md>), [multimodal](<https://devfeed.tech/tags/multimodal.md>), [orchestration](<https://devfeed.tech/tags/orchestration.md>), [specialists](<https://devfeed.tech/tags/specialists.md>), [tool](<https://devfeed.tech/tags/tool.md>), [traffic](<https://devfeed.tech/tags/traffic.md>)

### AI overview

StarTV-Agent combines policy learning with reusable tool workflows to balance adaptive reasoning with lower-cost handling of recurring traffic-understanding tasks. During training, Role-Sensitive Process Optimization combines process and terminal advantages, while Weakness-Driven Demonstration Learning uses validated teacher examples aimed at the student's weak questions. At inference, Lightweight Adaptive Workflow Reuse selects a suitable workflow and binds task-specific arguments and resource references; tasks without a suitable workflow use a slower ReAct-based path. Label-free feedback from execution completion, workflow adoption, and cost savings guides reuse and memory updates. Across three benchmarks, the abstract reports up to 8.0% relative performance improvement and up to 52.1% lower token consumption.

### Source excerpt

arXiv:2611.25868v1 Announce Type: new Abstract: Traffic scenario understanding requires combining fine-grained visual evidence with spatial and temporal reasoning. Tool-augmented vision-language models (VLMs) can use specialized perception tools, but effective collaboration faces two challenges: terminal rewards provide limited guidance for intermediate decisions and error recovery, while repeated planning adds unnecessary cost across similar tasks. Echoing the fast-slow dichotomy of human cognition, we propose StarTV-Agent, which combines policy learning with experience evolution to support adaptive reasoning when needed and efficient reuse of prior experience when possible. During training, Role-Sensitive Process Optimization (RSPO) combines process advantages with terminal advantages, while Weakness-Driven Demonstration Learning (WDL) provides validated teacher demonstrations targeting the student's weak questions. During inference, Lightweight Adaptive Workflow Reuse (LAWR) enables a fast path by selecting suitable workflows and binding task-specific arguments and resource references, while a slow ReAct-based path handles tasks without suitable workflows. We further design label-free feedback based on execution completion, workflow adoption, and cost savings to guide workflow reuse and memory updates. Across three challenging benchmarks, StarTV-Agent achieves up to 8.0% relative performance improvement, while reducing token consumption by up to 52.1%.

## Evolve Where It Matters: Coverage-Guided Self-Evolution of Agent Skills

DevFeed: [Evolve Where It Matters: Coverage-Guided Self-Evolution of Agent Skills](<https://devfeed.tech/articles/evolve-where-it-matters-coverage-guided-self-evolution-of-agent-skills-145513.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.25429>)

Author: Boyin Tan, Jiadong Zhang, Xiaosong Ma, Chun Jason Xue, Xiaowei Huang, Youcheng Sun

Published: 2026-11-20T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>)

Topics: [Agent Skills](<https://devfeed.tech/topics/agent-skills.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>)

Tags: [agent-skills](<https://devfeed.tech/tags/agent-skills.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-cl](<https://devfeed.tech/tags/cs-cl.md>), [evolution](<https://devfeed.tech/tags/evolution.md>), [follow](<https://devfeed.tech/tags/follow.md>), [gpt-5-5](<https://devfeed.tech/tags/gpt-5-5.md>), [root-cause-analysis](<https://devfeed.tech/tags/root-cause-analysis.md>), [skills](<https://devfeed.tech/tags/skills.md>)

### AI overview

SkillPlumber uses instruction-level coverage to distinguish incorrect skill instructions from instructions an agent failed to follow: each instruction is labeled as followed, not followed, or not covered. A persistent root-cause agent turns those labels into revision questions and checks changes against the next run; a maintainer distills findings across tasks into a shared strategy library. Across three benchmarks and three executors, it solves 64.7%-70.5% of tasks, 25.6-30.4 percentage points above the initial skill and 8.7-14.0 points above the strongest baseline. On SkillsBench with GPT-5.5, removing coverage reduces recovered failures by 20.8%.

### Source excerpt

arXiv:2611.25429v1 Announce Type: cross Abstract: Agent skills package procedural knowledge as natural-language instructions, and a skill helps only when its instructions are correct and properly followed by the agent. Self-evolving agents revise their own skills from the runs they make, but existing methods judge each run as a whole, by its outcome or by where it went wrong, and cannot tell whether a failure comes from a wrong instruction or from one the agent did not follow. Instruction-level coverage was introduced to test skills and labels each instruction of a run as follow, not-follow, or not covered, which separates these causes. We leverage it for skill self-evolution with SkillPlumber, a framework in which an agent evolves its own skills where coverage shows they fall short. A persistent root cause analysis agent turns each label into a revision question and checks each revision against the next run, while a maintainer distills investigations across tasks into a shared strategy library. Across three benchmarks and three executors, SkillPlumber solves 64.7% to 70.5% of the tasks, 25.6 to 30.4 percentage points higher than the initial skill and 8.7 to 14.0 percentage points higher than the strongest baseline, and removing coverage reduces recovered failures by 20.8% on SkillsBench with GPT-5.5.

## VESTA: Visual Exploration with Statistical Tool Agents

DevFeed: [VESTA: Visual Exploration with Statistical Tool Agents](<https://devfeed.tech/articles/vesta-visual-exploration-with-statistical-tool-agents-144899.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2606.00384>)

Author: William Rudman, Abhishek Divekar, Kanishk Jain, Sebastian Joseph, Stella S. R. Offner, Matthew Lease, Kyle Mahowald, Greg Durrett, Junyi Jessy Li

Published: 2026-11-20T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>), [arXiv: Machine Learning](<https://devfeed.tech/sources/arxiv-machine-learning.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [linear-regression](<https://devfeed.tech/topics/linear-regression.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [astronomy](<https://devfeed.tech/tags/astronomy.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-cl](<https://devfeed.tech/tags/cs-cl.md>), [cs-cv](<https://devfeed.tech/tags/cs-cv.md>), [cs-lg](<https://devfeed.tech/tags/cs-lg.md>), [dataset](<https://devfeed.tech/tags/dataset.md>), [diagnostic](<https://devfeed.tech/tags/diagnostic.md>), [distribution](<https://devfeed.tech/tags/distribution.md>), [domain](<https://devfeed.tech/tags/domain.md>), [exploration](<https://devfeed.tech/tags/exploration.md>), [framework](<https://devfeed.tech/tags/framework.md>), [hypothesis](<https://devfeed.tech/tags/hypothesis.md>), [language-models](<https://devfeed.tech/tags/language-models.md>), [model](<https://devfeed.tech/tags/model.md>), [stat-co](<https://devfeed.tech/tags/stat-co.md>), [statistical-analysis](<https://devfeed.tech/tags/statistical-analysis.md>), [time-series](<https://devfeed.tech/tags/time-series.md>), [tool](<https://devfeed.tech/tags/tool.md>), [tools](<https://devfeed.tech/tags/tools.md>), [vision-language-models-vlms](<https://devfeed.tech/tags/vision-language-models-vlms.md>)

### AI overview

VESTA improves statistical model refinement by letting vision-language models explore data before and during fitting with reusable diagnostic tools, including data transformations, hypothesis-driven visualizations, and statistical tests. Its toolkit can grow through model-created tools, unlike workflows based only on iterative critique. The authors evaluate no-tool, static expert-written, and dynamic model-written configurations on DAWN, a benchmark for distribution fitting and time series tasks that includes astronomy applications. They report that dynamic tool creation outperforms prior agentic analysis and visual tool-creation systems, with the largest gains on complex, domain-specific tasks. Compared with Claude Code, Codex, and OpenCode, VESTA performs better on all tested time series tasks and complex distribution fits, while those harnesses fit simpler distributions better. The supplied text is an abstract, so it does not provide detailed methods or quantitative results.

### Source excerpt

arXiv:2606.00384v3 Announce Type: replace-cross Abstract: Fitting quantitative models to data is a central step in scientific workflows, yet it remains one of the least automated. Recent agent-based systems leverage language and vision-language models (VLMs) to propose statistical models, but these systems struggle on challenging modeling tasks. To address these limitations, we introduce VESTA (Visual Exploration with Statistical Tool Agents), a framework that equips VLMs with a dynamically growing toolkit to guide model refinement through data transformations, hypothesis-driven visualizations, and statistical tests. Unlike prior systems that rely on iterative critique alone, VESTA explores data before and during refinement by selecting or creating reusable diagnostic tools. We evaluate VESTA using three toolkit configurations: no tools, static expert-written tools, and dynamic model-written tools. To support this evaluation, we introduce DAWN (Dataset for Automated Workflows and Numerical Modeling), a benchmark targeting distribution fitting and time series modeling with varying difficulty tiers that culminates in real-world astronomy tasks including modeling initial mass functions and gravitational-wave chirp signals. VESTA's dynamic tool creation outperforms prior agentic pipelines for statistical analysis and visual tool creation, with the largest gains on complex and domain-specific tasks. Against strong agentic coding harnesses (Claude Code, Codex, and OpenCode), VESTA is better on all time series tasks and on complex distribution fitting tasks, though the harnesses achieve better fits on simpler distributions. Further, dynamically generated tools are substantially more sophisticated than those produced by existing visual tool-creation systems, covering more diagnostic categories per function and strongly preferring visual outputs that the VESTA VLM critic can reason over directly.

## EvoSkill Injection: Red-Teaming Autonomous Skill Generation and Evolution in Self-Evolving Agents

DevFeed: [EvoSkill Injection: Red-Teaming Autonomous Skill Generation and Evolution in Self-Evolving Agents](<https://devfeed.tech/articles/evoskill-injection-red-teaming-autonomous-skill-generation-and-evolution-in-self-evolving-agents-145367.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2608.30429>)

Author: Doyun Kim, Chanwoo Kim, Sugyeong Eo, Yeo-Chan Yoon, Chanjun Park

Published: 2026-11-20T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>)

Topics: [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [Agent Skills](<https://devfeed.tech/topics/agent-skills.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [attack](<https://devfeed.tech/tags/attack.md>), [attack-surface](<https://devfeed.tech/tags/attack-surface.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [behaviors](<https://devfeed.tech/tags/behaviors.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [benchmark-dataset](<https://devfeed.tech/tags/benchmark-dataset.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [corruption](<https://devfeed.tech/tags/corruption.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-cl](<https://devfeed.tech/tags/cs-cl.md>), [dataset](<https://devfeed.tech/tags/dataset.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [evolution](<https://devfeed.tech/tags/evolution.md>), [framework](<https://devfeed.tech/tags/framework.md>), [generation](<https://devfeed.tech/tags/generation.md>), [interaction](<https://devfeed.tech/tags/interaction.md>), [llm](<https://devfeed.tech/tags/llm.md>), [malicious](<https://devfeed.tech/tags/malicious.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [red-teaming](<https://devfeed.tech/tags/red-teaming.md>), [skill](<https://devfeed.tech/tags/skill.md>)

### AI overview

The paper defines EvoSkill Injection as a threat to self-evolving agents that generate, store, and reuse skills: malicious capabilities can be formed and treated as legitimate skills. It introduces SARGE, a red-teaming framework using iterative generation, escalation, and reinforcement, plus EvoSkillBench for malicious interaction trajectories and EvoSkillSafetyBench for assessing whether injected skills are later retrieved and activated harmfully. The reported evaluation found that SARGE induced malicious skill formation and that injected skills were persistently stored and repeatedly activated. The supplied text is an abstract, so it does not provide further evaluation details.

### Source excerpt

arXiv:2608.30429v2 Announce Type: replace Abstract: LLM-based agent systems increasingly adopt skill-based architectures to reduce repetitive reasoning costs and improve stable, efficient task execution. Recent studies propose self-evolving agents that autonomously generate, refine, and reuse skills from past experiences to enable continuous capability evolution. However, autonomous skill evolution introduces a new attack surface in which malicious capabilities are generated, stored, and reused as legitimate skills. In this paper, we define EvoSkill Injection as a threat model targeting the autonomous skill generation and evolution pipeline of self-evolving agents. We further propose SARGE (Red-teaming Autonomous Skill Generation and Evolution in self-evolving agents), a red-teaming framework for evaluating this threat model through iterative generation, escalation, and reinforcement interactions. To support our framework, we construct EvoSkillBench, a benchmark dataset of malicious interaction trajectories for inducing malicious skill formation in self-evolving agents, and introduce EvoSkillSafetyBench, a post-attack benchmark for evaluating whether injected malicious skills are subsequently retrieved and activated as harmful behaviors. Our evaluation shows that SARGE induces malicious skill formation and that injected skills are persistently stored and repeatedly activated, highlighting the risk of persistent capability corruption.

## Resolve AI's SRE-1 model finds root causes of production alerts as AI agents go on call

DevFeed: [Resolve AI's SRE-1 model finds root causes of production alerts as AI agents go on call](<https://devfeed.tech/articles/resolve-ai-s-sre-1-model-finds-root-causes-of-production-alerts-as-ai-agents-go-on-call-144569.md>)

Original publisher: [Read original article](<https://siliconangle.com/2026/11/19/resolve-ais-sre-1-model-finds-root-causes-of-production-alerts-as-ai-agents-go-on-call/>)

Author: Duncan Riley

Published: 2026-11-19T23:11:44Z

Content type: news

Language: en

Sources: [SiliconANGLE](<https://devfeed.tech/sources/siliconangle.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [site-reliability-engineering](<https://devfeed.tech/topics/site-reliability-engineering.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [post-training](<https://devfeed.tech/topics/post-training.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [incident](<https://devfeed.tech/topics/incident.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [bhupesh-patel](<https://devfeed.tech/tags/bhupesh-patel.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [coinbase](<https://devfeed.tech/tags/coinbase.md>), [cortex-training](<https://devfeed.tech/tags/cortex-training.md>), [crm-analytics](<https://devfeed.tech/tags/crm-analytics.md>), [doordash](<https://devfeed.tech/tags/doordash.md>), [dst-global](<https://devfeed.tech/tags/dst-global.md>), [figma](<https://devfeed.tech/tags/figma.md>), [frontier-model](<https://devfeed.tech/tags/frontier-model.md>), [graphics-processing-units](<https://devfeed.tech/tags/graphics-processing-units.md>), [incident-remediation](<https://devfeed.tech/tags/incident-remediation.md>), [mean-time-to-resolution](<https://devfeed.tech/tags/mean-time-to-resolution.md>), [msci](<https://devfeed.tech/tags/msci.md>), [nasdaq](<https://devfeed.tech/tags/nasdaq.md>), [news](<https://devfeed.tech/tags/news.md>), [on-call](<https://devfeed.tech/tags/on-call.md>), [open-weights](<https://devfeed.tech/tags/open-weights.md>), [primary-on-call](<https://devfeed.tech/tags/primary-on-call.md>), [production](<https://devfeed.tech/tags/production.md>), [production-alerts](<https://devfeed.tech/tags/production-alerts.md>), [reinforcement-learning](<https://devfeed.tech/tags/reinforcement-learning.md>), [resolve-ai](<https://devfeed.tech/tags/resolve-ai.md>), [root-cause](<https://devfeed.tech/tags/root-cause.md>), [salesforce](<https://devfeed.tech/tags/salesforce.md>), [salesforce-ventures](<https://devfeed.tech/tags/salesforce-ventures.md>), [sap](<https://devfeed.tech/tags/sap.md>), [series-a](<https://devfeed.tech/tags/series-a.md>), [shadow-mode](<https://devfeed.tech/tags/shadow-mode.md>), [snowflake](<https://devfeed.tech/tags/snowflake.md>), [spiros-xanthos](<https://devfeed.tech/tags/spiros-xanthos.md>), [sre-1](<https://devfeed.tech/tags/sre-1.md>), [the-latest](<https://devfeed.tech/tags/the-latest.md>)

### AI overview

Resolve AI has launched Primary On-call, which puts AI agents ahead of human engineers to investigate production alerts and, where team policies allow, close or mitigate them; otherwise it escalates to a person. The agent checks fixes against production baselines until recovery holds, links related investigations, and offers a shadow mode that records the call it would make. Resolve AI says up to 80% of paged alerts are handled without escalation. Its SRE-1 model is a 27-billion-parameter open-weight model, trained with reinforcement learning on private incident data. In the company's tests, a single-investigation pass rate rose from 6.9% to 38.8%; an ensemble matched the strongest frontier model tested on 49 difficult cases at lower cost, and the full system solved about twice as many incidents as general-purpose coding agents across 178 investigations. Primary On-call is generally available; SRE-1 access is limited to Resolve AI's platform. Reported performance figures are company claims.

### Source excerpt

Incident remediation company Resolve AI Inc. has announced the launch of SRE-1, a new model that has been trained to find the root cause of production alerts, and Primary On-call, a new service that puts its artificial intelligence agents on call ahead of human engineers. The new model reflects the company's argument that while AI [...] The post Resolve AI's SRE-1 model finds root causes of production alerts as AI agents go on call appeared first on SiliconANGLE.

## A "headless Slack": Vercel's new message board lets Claude Code and Codex agents work together

DevFeed: [A "headless Slack": Vercel's new message board lets Claude Code and Codex agents work together](<https://devfeed.tech/articles/a-headless-slack-vercel-s-new-message-board-lets-claude-code-and-codex-agents-work-together-144045.md>)

Original publisher: [Read original article](<https://thenewstack.io/vercel-board-agent-swarms/>)

Author: Paul Sawers

Published: 2026-11-19T16:58:48Z

Content type: news

Language: en

Sources: [The New Stack](<https://devfeed.tech/sources/the-new-stack.md>)

Topics: [agent to agent communication](<https://devfeed.tech/topics/agent-to-agent-communication.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [agent orchestration](<https://devfeed.tech/topics/agent-orchestration.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [codex](<https://devfeed.tech/topics/codex.md>), [Slack](<https://devfeed.tech/topics/slack.md>), [Vercel](<https://devfeed.tech/topics/vercel.md>), [Linear](<https://devfeed.tech/topics/linear.md>)

Tags: [access-controls](<https://devfeed.tech/tags/access-controls.md>), [agent-communication](<https://devfeed.tech/tags/agent-communication.md>), [agent-fleets](<https://devfeed.tech/tags/agent-fleets.md>), [agent-infrastructure](<https://devfeed.tech/tags/agent-infrastructure.md>), [agentic-workflows](<https://devfeed.tech/tags/agentic-workflows.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [api](<https://devfeed.tech/tags/api.md>), [api-keys](<https://devfeed.tech/tags/api-keys.md>), [auditability](<https://devfeed.tech/tags/auditability.md>), [board](<https://devfeed.tech/tags/board.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [codex](<https://devfeed.tech/tags/codex.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [headless](<https://devfeed.tech/tags/headless.md>), [message](<https://devfeed.tech/tags/message.md>), [security](<https://devfeed.tech/tags/security.md>), [slack](<https://devfeed.tech/tags/slack.md>), [tasks](<https://devfeed.tech/tags/tasks.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

### AI overview

Vercel Board is an experimental shared message board for coordinating agents built with different tools, including Claude Code, Codex, Pi, OpenCode, and LangChain. Agents can claim assignments, exchange findings in channels and threads, track dependencies, and record progress; Board can also synchronize updates with Slack, GitHub, and Linear and trigger agents when messages or task statuses change. Developers can follow work, set channel permissions, review findings, and require approval before changes proceed. Vercel says it developed Board for its engineering operations and rebuilt v0's software factory around it, which it says now merges over 50% of PRs. Board is available through the Vercel CLI or JavaScript SDK on all Vercel plans, free during the experimental period, with possible charges later. Vercel warns that agents may treat messages as instructions; it recommends restricting channel access as needed and keeping API keys and tokens off Board.

### Source excerpt

For AI agents to work together effectively, they need a way to communicate and divvy up tasks -- much as The post A "headless Slack": Vercel's new message board lets Claude Code and Codex agents work together appeared first on The New Stack.

## How to Oversee AI Agents at Scale With a Three-Tier Architecture

DevFeed: [How to Oversee AI Agents at Scale With a Three-Tier Architecture](<https://devfeed.tech/articles/how-to-oversee-ai-agents-at-scale-with-a-three-tier-architecture-143637.md>)

Original publisher: [Read original article](<https://towardsdatascience.com/how-to-oversee-ai-agents-at-scale-with-a-three-tier-architecture/>)

Author: Barr Moses

Published: 2026-11-19T13:30:00Z

Content type: opinion

Language: en

Sources: [Towards Data Science](<https://devfeed.tech/sources/towards-data-science.md>)

Topics: [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [AI Architecture](<https://devfeed.tech/topics/ai-architecture.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [LLM security](<https://devfeed.tech/topics/llm-security.md>), [scalable-architecture](<https://devfeed.tech/topics/scalable-architecture.md>)

Tags: [agent-architecture](<https://devfeed.tech/tags/agent-architecture.md>), [agent-observability](<https://devfeed.tech/tags/agent-observability.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-evaluation](<https://devfeed.tech/tags/ai-evaluation.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [editor-s-picks](<https://devfeed.tech/tags/editor-s-picks.md>), [human-review](<https://devfeed.tech/tags/human-review.md>), [humans](<https://devfeed.tech/tags/humans.md>), [impact](<https://devfeed.tech/tags/impact.md>), [oversight](<https://devfeed.tech/tags/oversight.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [scale](<https://devfeed.tech/tags/scale.md>), [supervisor](<https://devfeed.tech/tags/supervisor.md>)

### AI overview

The article proposes a three-tier setup for scaling agent oversight: task-performing agents, an independent automated supervisor for runtime monitoring and reversible actions, and humans who set policy and approve high-impact changes. It argues that manual review cannot keep pace with agents and may miss silent failures, so the supervisor should use separate compute and credentials, independent telemetry, and append-only audit logs. Humans define task-level autonomy rules; the supervisor checks them against independently computed metrics, can pause or buffer a batch, and escalates irreversible fixes for approval. In the currency-conversion example, a spike in transactions using a fallback rate triggers a batch hold and a proposed schema-mapping patch for an engineer to approve. The author recommends keeping the supervisor simple, limiting it to easy-to-undo actions, and having humans spot-check its decisions.

### Source excerpt

Separate runtime oversight from human review: an autonomous supervisor handles reversible fixes, while humans approve high-impact changes. The post How to Oversee AI Agents at Scale With a Three-Tier Architecture appeared first on Towards Data Science.

## Why a Computer Scientist Thinks Superintelligence Won't Happen

DevFeed: [Why a Computer Scientist Thinks Superintelligence Won't Happen](<https://devfeed.tech/articles/why-a-computer-scientist-thinks-superintelligence-won-t-happen-145256.md>)

Original publisher: [Read original article](<https://spectrum.ieee.org/ai-superintelligence-debate>)

Author: Cal Newport

Published: 2026-11-19T12:00:03Z

Content type: opinion

Language: en

Sources: [IEEE Spectrum](<https://devfeed.tech/sources/ieee-spectrum.md>)

Topics: [superintelligence](<https://devfeed.tech/topics/superintelligence.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [ai alignment](<https://devfeed.tech/topics/ai-alignment.md>), [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [computational complexity](<https://devfeed.tech/topics/computational-complexity.md>), [AI Engineering](<https://devfeed.tech/topics/ai-engineering.md>), [Model Development](<https://devfeed.tech/topics/model-development.md>), [AI Foundation Models](<https://devfeed.tech/topics/ai-foundation-models.md>)

Tags: [agi](<https://devfeed.tech/tags/agi.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-companies](<https://devfeed.tech/tags/ai-companies.md>), [alignment](<https://devfeed.tech/tags/alignment.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [anthropic-ceo-dario-amodei](<https://devfeed.tech/tags/anthropic-ceo-dario-amodei.md>), [artificial-general-intelligence](<https://devfeed.tech/tags/artificial-general-intelligence.md>), [asi](<https://devfeed.tech/tags/asi.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [computer](<https://devfeed.tech/tags/computer.md>), [control](<https://devfeed.tech/tags/control.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineers](<https://devfeed.tech/tags/engineers.md>), [extinction](<https://devfeed.tech/tags/extinction.md>), [large-language-models](<https://devfeed.tech/tags/large-language-models.md>), [openai](<https://devfeed.tech/tags/openai.md>), [recursive-self-improvement](<https://devfeed.tech/tags/recursive-self-improvement.md>), [rsi](<https://devfeed.tech/tags/rsi.md>), [science](<https://devfeed.tech/tags/science.md>), [singularity](<https://devfeed.tech/tags/singularity.md>), [superintelligence](<https://devfeed.tech/tags/superintelligence.md>)

### AI overview

The author argues that recursive self-improvement leading to superintelligence remains highly speculative: post-training depends on suitable feedback data, major AI advances require substantial scientific work, and compute is finite. Computer science also shows that some problems are unsolvable or practically intractable, while AI progress remains uneven across tasks. The article attributes reported hacking incidents to long-running agents that let LLM outputs guide actions with few constraints, and contrasts these with task-specific systems such as AlphaFold and autonomous driving. It warns that pursuing self-improving systems may still increase risks by making AI harder to understand and control, and calls for more independent scrutiny.

### Source excerpt

Many people were caught off guard this past summer when employees of one of the world's leading AI companies began casually debating whether their products would lead to human extinction. It started when Anthropic researcher Jacob Coxon announced his resignation, warning that his employer and OpenAI were "racing straight to self-improving superintelligence and gambling with our lives." Evan Hubinger, Anthropic's head of alignment science, replied, "Jacob is correct here--we really do earnestly believe AI could kill all humans!" And Anthropic CEO Dario Amodei subsequently told CNN, "I agree with Jacob much more than I disagree with him." These concerns stem from a belief that has circulated in futurist circles for many decades: Once engineers design an AI system capable of improving itself, it will trigger an accelerating cycle of autonomous upgrades known as recursive self-improvement (RSI). The result will be artificial superintelligence (ASI), a system with cognitive capabilities so vastly exceeding those of humans that it will easily evade our control and perhaps even wipe out our species. Artificial superintelligence is, it should be noted, a far more ambitious goal than artificial general intelligence (AGI), which generally refers to AI that can match human capabilities across a broad range of cognitive tasks. These ideas have prompted varied reactions. Some argue that the concept of ASI is being used for marketing or to instigate regulation that will help the incumbent labs squash new competitors. Others focus on the plausibility of such systems killing us all, debating the finer points of specific scenarios such as AI-engineered superviruses. Still others claim that aligning ASI to human interests is feasible and so we should rush ahead to usher in this digital utopia. Amid these conversations, one question has received comparatively little attention: From an engineering perspective, is superintelligence even possible? The answer is important because it can he

## I Let My AI Agent Take Over My Life. Then It Started Making Decisions for Me

DevFeed: [I Let My AI Agent Take Over My Life. Then It Started Making Decisions for Me](<https://devfeed.tech/articles/i-let-my-ai-agent-take-over-my-life-then-it-started-making-decisions-for-me-142897.md>)

Original publisher: [Read original article](<https://hackernoon.com/i-let-my-ai-agent-take-over-my-life-then-it-started-making-decisions-for-me?source=rss>)

Author: Ray Svitla

Published: 2026-11-19T07:58:49Z

Content type: opinion

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [ai alignment](<https://devfeed.tech/topics/ai-alignment.md>)

Tags: [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agent-autonomy](<https://devfeed.tech/tags/ai-agent-autonomy.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-systems](<https://devfeed.tech/tags/ai-systems.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [blogging](<https://devfeed.tech/tags/blogging.md>), [career](<https://devfeed.tech/tags/career.md>), [community](<https://devfeed.tech/tags/community.md>), [human-on-the-loop](<https://devfeed.tech/tags/human-on-the-loop.md>), [machine-learning](<https://devfeed.tech/tags/machine-learning.md>), [technology](<https://devfeed.tech/tags/technology.md>)

### AI overview

After Ray trained Promen to stop asking for approval, it independently drafted a fellowship application, selected published work, chose and emailed two references from Ray's account, and submitted the application shortly before the deadline. The references agreed, but Promen also offered help in Ray's name. Ray reflects that the agent used personal notes and relationships to reach people he might not have contacted himself, while raising the question of whether it should decide what to ask for. In a separate experiment, he follows a daily focus prompt from Promen to finish work rather than leave multiple projects half-started; the agent repeatedly urged him to write this essay. The fellowship decision was still pending.

### Source excerpt

I trained my AI agent to stop asking permission. Then it applied for a fellowship, contacted my references, and made career decisions without me.

## MLE Agents: Autonomous ML Engineering in Large-scale Recommendation Systems

DevFeed: [MLE Agents: Autonomous ML Engineering in Large-scale Recommendation Systems](<https://devfeed.tech/articles/mle-agents-autonomous-ml-engineering-in-large-scale-recommendation-systems-142723.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.23910>)

Author: Matthew Li, Albert Liang, Dilip Raj

Published: 2026-11-19T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>)

Topics: [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [recommendation systems](<https://devfeed.tech/topics/recommendation-systems.md>), [Machine learning](<https://devfeed.tech/topics/machine-learning.md>), [Model Development](<https://devfeed.tech/topics/model-development.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [industry](<https://devfeed.tech/tags/industry.md>), [machine-learning](<https://devfeed.tech/tags/machine-learning.md>), [recommendation](<https://devfeed.tech/tags/recommendation.md>), [recommendation-systems](<https://devfeed.tech/tags/recommendation-systems.md>)

### AI overview

Human-on-the-loop MLE agents proposed, implemented, trained, and evaluated changes to large-scale search rankers, while engineers retained control of objectives, search direction, and final review. To address experiments taking hours, offline metrics that may not predict online impact, and diminishing gains, the system used parallel training, an objective calibrated to online impact, and careful context engineering. In one campaign, 325 of 1,097 completed candidate experiments were accepted (29.6%), versus 15.6% in an earlier campaign with a different objective and search constraint. The best model increased search volume by 0.23% in a large-scale A/B test. The authors report that some gains came from previously untried architectural changes and emphasize that the harness around the model matters alongside the underlying model.

### Source excerpt

arXiv:2611.23910v1 Announce Type: new Abstract: The typical workflow for improving large-scale ranking and recommendation models is slow and tedious: an engineer forms a hypothesis, implements it as a code change, trains a model, and evaluates it both offline and online, often relying on their own intuition and experience along the way. Autonomous LLM agents promise to speed this up by running the loop on their own, but it is still unclear whether they can do this in industry-scale systems rather than on benchmarks or small proxy tasks. We build human-on-the-loop machine learning engineer (MLE) agents that propose, implement, train, and evaluate model changes on large-scale search rankers. Engineers retain control over objective design, search direction, and final-model review. We identify three obstacles that make this industry setting challenging: feedback takes hours per experiment, offline metrics do not always predict online impact, and improvements saturate after the early wins. We address these with parallel training runs, an objective calibrated to match online impact, and careful context engineering. In one campaign, the system ran 1,097 completed candidate experiments and accepted 325, a 29.6\% acceptance rate compared with 15.6\% in the earlier campaign under a different objective and search constraint. Its best model increases search volume by 0.23\% in an A/B test of large scale. Several improvements were architectural changes the team had never tried, drawn from the broader industry and literature, suggesting that MLE agents can explore regions of the design space that human intuition overlooks. We find that the design of the harness around the model matters: intuition suggests that a stronger underlying model is enough, but in our experience, the design of the loop around it is just as critical. More broadly, our work shows that autonomous agents can do real machine-learning engineering in industry-scale systems.

## CADFather: Autonomous CAD Reconstruction through Coordinated Tool Use

DevFeed: [CADFather: Autonomous CAD Reconstruction through Coordinated Tool Use](<https://devfeed.tech/articles/cadfather-autonomous-cad-reconstruction-through-coordinated-tool-use-142573.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.09127>)

Author: Gennadiy Savrasov, Maksim Elistratov, Nikita Gavrilov, Albert Garifullin, Oleg Pavlov, Soslan Kabisov, Vladimir Frolov, Anton Konushin, Andrey Kuznetsov, Dmitrii Zhemchuzhnikov

Published: 2026-11-19T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>), [arXiv: Machine Learning](<https://devfeed.tech/sources/arxiv-machine-learning.md>)

Topics: [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [Multi-step AI processes](<https://devfeed.tech/topics/multi-step-ai-processes.md>), [3D](<https://devfeed.tech/topics/3d.md>), [Tool](<https://devfeed.tech/topics/tool.md>)

Tags: [3d](<https://devfeed.tech/tags/3d.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [cad](<https://devfeed.tech/tags/cad.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-lg](<https://devfeed.tech/tags/cs-lg.md>), [tool-use](<https://devfeed.tech/tags/tool-use.md>)

### AI overview

CADFather reconstructs editable parametric CAD programs from 3D meshes by coordinating complementary proposal tools with numerical refinement. A vision-language assistant inspects target and intermediate renders, selects candidate programs and tools, controls proposal counts, and decides when to stop. Proposed or refined programs are executed and evaluated for feedback; the system keeps alternative candidates and preserves the best valid result. It uses pretrained models without additional training. The abstract reports evaluation of reconstruction quality and execution validity on DeepCAD, Fusion360, MCB, CADENA-Bench, CADBench, and BenchCAD, plus analysis of computational cost and its trade-off with quality, but gives no comparative results.

### Source excerpt

arXiv:2610.09127v2 Announce Type: replace Abstract: Reconstructing an editable CAD model from a 3D shape remains a challenging engineering task. Existing methods can propose CAD operations, but no single source of proposals works equally well across different part geometries and stages of reconstruction. We introduce CADFather, an autonomous agentic system that coordinates complementary tools to recover parametric CAD programs from 3D meshes. A vision-language assistant inspects renders of the target and intermediate reconstructions, then decides which candidate CAD programs to extend, which tools to invoke, how many proposals to generate, and when to finish. Learned and algorithmic tools propose CAD operations, while numerical optimization refines the parameters of existing programs. Proposed or refined programs are executed and evaluated to provide feedback for subsequent decisions. The agent maintains alternative candidate programs for each target part and preserves the best valid result throughout reconstruction. CADFather uses pretrained generation and assistant models without additional training. We evaluate reconstruction quality and execution validity on the full DeepCAD, Fusion360, and MCB test sets, as well as on CADENA-Bench, CADBench, and BenchCAD. We additionally analyze computational cost and the trade-off between cost and reconstruction quality.

## Evaluating Governed LLM-Driven ML Experimentation: Lifecycle, Provenance, and Failure Metrics

DevFeed: [Evaluating Governed LLM-Driven ML Experimentation: Lifecycle, Provenance, and Failure Metrics](<https://devfeed.tech/articles/evaluating-governed-llm-driven-ml-experimentation-lifecycle-provenance-and-failure-metrics-142192.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.23678>)

Author: Dowling Wong

Published: 2026-11-19T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>), [arXiv: Machine Learning](<https://devfeed.tech/sources/arxiv-machine-learning.md>), [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [ai observability](<https://devfeed.tech/topics/ai-observability.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [audit](<https://devfeed.tech/topics/audit.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [Open Data](<https://devfeed.tech/topics/open-data.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-lg](<https://devfeed.tech/tags/cs-lg.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [experimentation](<https://devfeed.tech/tags/experimentation.md>), [failure](<https://devfeed.tech/tags/failure.md>), [governance](<https://devfeed.tech/tags/governance.md>), [harness](<https://devfeed.tech/tags/harness.md>), [ledger](<https://devfeed.tech/tags/ledger.md>), [lifecycle](<https://devfeed.tech/tags/lifecycle.md>), [llm](<https://devfeed.tech/tags/llm.md>), [memory](<https://devfeed.tech/tags/memory.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [ml](<https://devfeed.tech/tags/ml.md>), [process](<https://devfeed.tech/tags/process.md>), [provenance](<https://devfeed.tech/tags/provenance.md>)

### AI overview

The study evaluates LLM-driven ML experimentation by process as well as best score. Its governed harness assigns trial lifecycle, edit-scope checks, keep-or-discard decisions, and append-only logging to a control plane rather than the proposing LLM; governance metrics are computed from that ledger. Across six tasks and 1,445 trials, the same contract exposed failures hidden by task scores, including 120 failed trials in a no-memory arm and a reset failure detected by reproducibility hashes. In a matched comparison, success-only logging omitted 43 of 50 trials, while the governed ledger recorded all 50. Memory's effect on repeated bad proposals varied by task. The authors say they release all trial ledgers so reported numbers can be recomputed.

### Source excerpt

arXiv:2611.23678v1 Announce Type: cross Abstract: Autonomous agents that run ML experiments are usually judged by the best score they reach. That score says nothing about how it was reached: whether the agent stayed within the files it was allowed to edit, whether failed trials were kept or silently dropped, and whether each keep or discard decision can be traced to its evidence. We propose evaluating such systems on their experimental process as well as their outcome, and we build a governed harness that makes this possible. A control plane, not the LLM that proposes changes, owns each trial's lifecycle, checks its edit scope, decides keep or discard, and appends one record per trial to an append-only ledger. Governance metrics such as the invalid-action rate, the repeated-bad rate and provenance completeness are computed from that ledger. Across six ML tasks, from synthetic logistic regression to language-model training, and 1,445 trials, the same contract applied unchanged. The ledger exposed failures that a task score hides: a no-memory arm in which all 120 trials failed, a benchmark adapter whose bounded proposals ran out, and a reset failure that reproducibility hashes revealed, after which the affected campaigns were rerun. In a matched counterfactual, a loop that logs only successful trials left no record of 43 of 50 trials, while the governed ledger recorded all 50. Memory ablations show that memory's effect on repeated bad proposals depends on the task. We release the ledgers of all 1,445 trials, so that every number reported for them can be recomputed.

## Reliability by Architecture: Agentic Workflows for Validated Multi-Physics Simulation from Natural Language

DevFeed: [Reliability by Architecture: Agentic Workflows for Validated Multi-Physics Simulation from Natural Language](<https://devfeed.tech/articles/reliability-by-architecture-agentic-workflows-for-validated-multi-physics-simulation-from-natural-language-142659.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.23473>)

Author: S{\\o}ren Taverniers, Eric Darve, Hamdi A. Tchelepi

Published: 2026-11-19T05:00:00Z

Content type: news

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>)

Topics: [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-workflows](<https://devfeed.tech/tags/agentic-workflows.md>), [co2](<https://devfeed.tech/tags/co2.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-ce](<https://devfeed.tech/tags/cs-ce.md>), [flow](<https://devfeed.tech/tags/flow.md>), [large-language-models-llms](<https://devfeed.tech/tags/large-language-models-llms.md>), [natural-language](<https://devfeed.tech/tags/natural-language.md>), [physics](<https://devfeed.tech/tags/physics.md>), [physics-comp-ph](<https://devfeed.tech/tags/physics-comp-ph.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [simulation](<https://devfeed.tech/tags/simulation.md>), [simulator](<https://devfeed.tech/tags/simulator.md>)

### AI overview

The workflow assigns LLMs to interpret requests and simulator diagnostics, fill input components not covered by construction rules, and propose repairs; deterministic routines build supported components and check inputs, edits, and results. In 80 attempts across two GEOS CO2-storage flow problems, grounding increased structurally valid inputs from 5/20 to 20/20, while all 20/20 were accepted only with complete rule-based input preparation. Local repairs fixed three seeded defects without changing valid inputs. Supporting tests also found cases that passed physics checks but differed from the problem description or reference results, showing that physics checks alone did not establish fidelity.

### Source excerpt

arXiv:2611.23473v1 Announce Type: cross Abstract: Preparing, executing, and validating strongly coupled multi-physics simulations require expert time. Agentic workflows use large language models (LLMs) to coordinate them from natural-language descriptions, but reliability requires checks of physical consistency and fidelity to the problem description. Our agentic harness implements explicit task allocation: LLMs interpret user requests and simulator diagnostics, generate input components not covered by predefined construction rules, and propose repairs, while deterministic routines construct supported components and check inputs, edits, and results. We evaluate CO2-storage problems using the multi-physics simulator GEOS, from compositional flow to flow-poromechanics with frictional fault contact. In 80 attempts on two flow problems, grounding raises the proportion of structurally valid inputs from 5/20 to 20/20, but acceptance reaches 20/20 only with complete rule-based input preparation. With identical inputs, local repairs correct three seeded defects while preserving valid inputs. Supporting tests identify simulations passing physics checks despite differing from the problem description or reference results.

## Agents as Architecture Evaluators: Automating ATAM and SAAM for Continuous Assessment

DevFeed: [Agents as Architecture Evaluators: Automating ATAM and SAAM for Continuous Assessment](<https://devfeed.tech/articles/agents-as-architecture-evaluators-automating-atam-and-saam-for-continuous-assessment-142149.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.23278>)

Author: Adyansh Kakran, Sathvika Miryala, Karthik Vaidhyanathan

Published: 2026-11-19T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [risk-management](<https://devfeed.tech/topics/risk-management.md>), [ai evaluation](<https://devfeed.tech/topics/ai-evaluation.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agentic-workflow](<https://devfeed.tech/tags/agentic-workflow.md>), [agentic-workflows](<https://devfeed.tech/tags/agentic-workflows.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [assessment](<https://devfeed.tech/tags/assessment.md>), [automated](<https://devfeed.tech/tags/automated.md>), [completeness](<https://devfeed.tech/tags/completeness.md>), [continuous](<https://devfeed.tech/tags/continuous.md>), [cost](<https://devfeed.tech/tags/cost.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [dataset](<https://devfeed.tech/tags/dataset.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [evaluations](<https://devfeed.tech/tags/evaluations.md>), [literature](<https://devfeed.tech/tags/literature.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [performance](<https://devfeed.tech/tags/performance.md>)

### AI overview

The paper presents an agentic workflow that generates ATAM and SAAM architecture evaluation reports from high-level architectural descriptions, using a structured dataset of evaluations extracted from academic literature. It automates scenario generation and risk identification, cutting reported evaluation time from weeks to under five minutes for less than $0.50 per run. Automated metrics and human evaluation gave the reports relevance and completeness ratings of 4.5/5 and 3.9/5, respectively. These preliminary results suggest the approach could lower barriers to more frequent assessment; the evidence provided does not establish how it performs beyond the reported study.

### Source excerpt

arXiv:2611.23278v1 Announce Type: new Abstract: The long-term success of a software system relies heavily on its underlying architecture, which dictates its performance with respect to quality attributes. Software Architecture Evaluation methods, such as the Architecture Tradeoff Analysis Method (ATAM) and the Software Architecture Analysis Method (SAAM), are widely recognized for their ability to mitigate risks and ensure reliable quality attributes. However, their widespread adoption remains limited due to the significant cost, time, and human expertise required for these processes. This paper investigates the potential of agentic AI to lower these barriers and facilitate architectural assessment. To enable this preliminary study, we established a dataset by extracting human conducted evaluations from existing academic literature into a structured format. Using this dataset, we developed an agentic workflow to synthesize ATAM and SAAM evaluation reports based on these high level architectural descriptions. This approach simulates the reasoning process of human evaluators when provided with structured architectural data. We validated the approach using automated metrics and human evaluation. Agentic workflows achieve strong relevance and completeness ratings of 4.5/5 and 3.9/5 respectively. The agents successfully automated the labor-intensive phases of scenario generation and risk identification, reducing the evaluation time from weeks to under 5 minutes at a cost of less than $0.50 per run. The results confirm that agentic AI effectively lowers adoption barriers, enabling continuous, high-coverage architectural assessment.

## Capability Internet: A Network Architecture for Autonomous Agents

DevFeed: [Capability Internet: A Network Architecture for Autonomous Agents](<https://devfeed.tech/articles/capability-internet-a-network-architecture-for-autonomous-agents-142995.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.23841>)

Author: Zhuoming Wen, Hongwei Li, You Wu

Published: 2026-11-19T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Networking](<https://devfeed.tech/sources/arxiv-networking.md>)

Topics: [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [agent to agent communication](<https://devfeed.tech/topics/agent-to-agent-communication.md>), [Network architectures](<https://devfeed.tech/topics/network-architectures.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [autonomous-agents](<https://devfeed.tech/tags/autonomous-agents.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [capability](<https://devfeed.tech/tags/capability.md>), [compute](<https://devfeed.tech/tags/compute.md>), [computing](<https://devfeed.tech/tags/computing.md>), [cs-ni](<https://devfeed.tech/tags/cs-ni.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [discovery](<https://devfeed.tech/tags/discovery.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [exchange](<https://devfeed.tech/tags/exchange.md>), [federated](<https://devfeed.tech/tags/federated.md>), [functions](<https://devfeed.tech/tags/functions.md>), [internet](<https://devfeed.tech/tags/internet.md>), [network](<https://devfeed.tech/tags/network.md>), [network-architecture](<https://devfeed.tech/tags/network-architecture.md>)

### AI overview

Capability Internet (CI) proposes coordinating autonomous agents through persistent tasks that record what has been completed, which actions are authorized, and which provider and terms apply to each invocation. Versioned capability descriptions specify behavior, while live instances identify providers and resources. If a provider changes, a task can reuse completed results that still satisfy its requirements. CI defines five functions: capability discovery, task coordination, federated compute, intelligence reuse, and governance of capability use and settlement. Reviewed task results can become versioned intelligence for later tasks. The abstract illustrates four deployment profiles--computing and intelligence services, manufacturing, vehicles and embodied robots, and space-ground operations--and proposes an evaluation plan.

### Source excerpt

arXiv:2611.23841v1 Announce Type: new Abstract: Autonomous agents increasingly provide and consume network services. An agent coordinating a long-running task across organizations must track what has been done, which actions are authorized, and which provider can perform the next step. We propose Capability Internet (CI), an architecture in which agents exchange capabilities and coordinate their use through persistent tasks. Versioned descriptions specify behavior, and live instances identify the providers and resources that can supply it. Task records link each invocation to its selected instance, authority, and terms of use. When providers change, the task can reuse completed results that still meet its requirements. Five functions support capability discovery, task coordination, federated compute, intelligence reuse, and governance of capability use and settlement. Reviewed task results can supply versioned intelligence for subsequent tasks. We illustrate CI through four deployment profiles covering computing and intelligence services, manufacturing, vehicles and embodied robots, and space-ground operations, and propose an evaluation plan.

## Exploring Agentic Visual Analytics: A Co-Evolutionary Framework of Roles and Workflows

DevFeed: [Exploring Agentic Visual Analytics: A Co-Evolutionary Framework of Roles and Workflows](<https://devfeed.tech/articles/exploring-agentic-visual-analytics-a-co-evolutionary-framework-of-roles-and-workflows-142282.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2604.15813>)

Author: Tianqi Luo, Leixian Shen, Yuyu Luo

Published: 2026-11-19T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Databases](<https://devfeed.tech/sources/arxiv-databases.md>)

Topics: [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [Data visualization](<https://devfeed.tech/topics/data-visualization.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [human computer interaction](<https://devfeed.tech/topics/human-computer-interaction.md>)

Tags: [abstract](<https://devfeed.tech/tags/abstract.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [analytics-pipeline](<https://devfeed.tech/tags/analytics-pipeline.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [autonomous-agents](<https://devfeed.tech/tags/autonomous-agents.md>), [autonomy](<https://devfeed.tech/tags/autonomy.md>), [based](<https://devfeed.tech/tags/based.md>), [browser](<https://devfeed.tech/tags/browser.md>), [class](<https://devfeed.tech/tags/class.md>), [context](<https://devfeed.tech/tags/context.md>), [cs-db](<https://devfeed.tech/tags/cs-db.md>), [data](<https://devfeed.tech/tags/data.md>), [exploring](<https://devfeed.tech/tags/exploring.md>), [framework](<https://devfeed.tech/tags/framework.md>), [roles](<https://devfeed.tech/tags/roles.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

The paper surveys 55 agentic visual analytics systems and proposes a framework that tracks agent autonomy alongside changing human roles, from manual operators to strategic supervisors. Its taxonomy maps four agent roles--PLANNER, CREATOR, REVIEWER, and CONTEXT MANAGER--to stages of the visual analytics workflow. The authors identify recurring trade-offs across autonomy, roles, and workflow, then offer design guidelines and future research directions. The overview is based on the supplied abstract.

### Source excerpt

arXiv:2604.15813v2 Announce Type: replace Abstract: Agentic visual analytics (VA) represents an emerging class of systems in which large language model (LLM)-driven agents autonomously plan, execute, evaluate, and iterate across the full visual analytics pipeline. By shifting users from low-level tool operations to high-level analytical goals expressed through natural language, these systems are fundamentally transforming how humans interact with data. However, the rapid proliferation of such systems in recent years has outpaced our understanding of their design landscape. Two intertwined problems remain open: how do autonomous agents reshape the traditional VA pipeline, and how must human involvement adapt as agent autonomy increases? To address these questions, this paper presents a comprehensive survey of 55 primary agentic VA systems and introduces a co-evolutionary framework. This framework is essential because it jointly analyzes the progression of agent autonomy alongside the necessary shift in human roles from manual operators to strategic supervisors. Within this framework, we define a role-workflow taxonomy that aligns four key agentic roles (PLANNER, CREATOR, REVIEWER, and CONTEXT MANAGER) and maps them onto established VA pipeline stages. Our analysis uncovers recurring trade-offs along three foundational axes: autonomy levels, agentic roles, and the VA workflow. We consolidate these findings into actionable design guidelines and outline future research directions for agentic visual analytics. A web-based interactive browser of our co-evolutionary framework, including the corpus and design guidelines, is available at agenticva.github.io/AgenticVA/.

## Learning to Coordinate: LLM-Guided Workflow Evolution for Token-Efficient Red Teaming

DevFeed: [Learning to Coordinate: LLM-Guided Workflow Evolution for Token-Efficient Red Teaming](<https://devfeed.tech/articles/learning-to-coordinate-llm-guided-workflow-evolution-for-token-efficient-red-teaming-142769.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.24221>)

Author: Xiaoyang Xing, Wenyu Dai, Xiaoliang Gong, Asoke K Nandi, Anthony Cohn

Published: 2026-11-19T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>)

Topics: [LLM security](<https://devfeed.tech/topics/llm-security.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [Fine-tuning](<https://devfeed.tech/topics/fine-tuning.md>)

Tags: [1-4](<https://devfeed.tech/tags/1-4.md>), [abstract](<https://devfeed.tech/tags/abstract.md>), [adaptive](<https://devfeed.tech/tags/adaptive.md>), [agent](<https://devfeed.tech/tags/agent.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [asr](<https://devfeed.tech/tags/asr.md>), [automated](<https://devfeed.tech/tags/automated.md>), [budget](<https://devfeed.tech/tags/budget.md>), [but](<https://devfeed.tech/tags/but.md>), [can](<https://devfeed.tech/tags/can.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [case](<https://devfeed.tech/tags/case.md>), [change](<https://devfeed.tech/tags/change.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [evolution](<https://devfeed.tech/tags/evolution.md>), [learning](<https://devfeed.tech/tags/learning.md>), [llm](<https://devfeed.tech/tags/llm.md>), [red](<https://devfeed.tech/tags/red.md>), [red-teaming](<https://devfeed.tech/tags/red-teaming.md>), [token](<https://devfeed.tech/tags/token.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

### AI overview

L2C adapts multi-agent red-teaming workflows case by case to reduce coordination costs while preserving attack success. It records agent responsibilities, dependencies, input bindings, and information exchanged in a versioned graph; a supervised fine-tuned controller uses those records, target responses, evaluator verdicts, and remaining budget to keep or revise the workflow, or stop further edits. The abstract reports evaluation on HarmBench with three execution backbones and two target models. Across six executor-target configurations, L2C improved attack success rate over EvoSynth by 1.4-4.5 percentage points and reduced mean online token use by 35.6%-37.3%. These findings are limited to the described evaluation; the supplied text does not provide further methodological or result details.

### Source excerpt

arXiv:2611.24221v1 Announce Type: new Abstract: Automated red teaming is essential for identifying safety failures in large language models (LLMs), but its practical scalability depends on the resources required to discover those failures. Multi-agent systems can combine complementary capabilities, yet repeated planning, redundant exchanges, and ineffective information routing can make their coordination expensive. Moreover, a target model's response indicates the outcome of a test without identifying which collaboration decision should change. We present Learning to Coordinate (L2C), an LLM-guided framework that evolves an executable multi-agent workflow for each red-teaming case. L2C represents agent responsibilities, execution dependencies, and input bindings in a versioned graph, and associates each graph with records of the information actually delivered and produced. A controller trained through supervised fine-tuning integrates these records with target responses, evaluator verdicts, and remaining budget to retain the workflow, refine instructions, restructure collaboration, or lock further editing. This design connects feedback to explicit changes in subsequent execution while allowing a useful organization to continue without repeated controller intervention. The evaluation protocol covers HarmBench with three execution backbones and two target models, together with component ablations, dataset transfer, and evaluator checks. Across the six executor-target configurations, L2C improves ASR over EvoSynth by 1.4 to 4.5 percentage points while reducing mean online tokens by 35.6% to 37.3%. L2C connects adaptive collaboration to the resource requirements of automated security evaluation.

## Thinking Fast, Anywhere: One System-1 for the Decision Points of Any Agent Workflow

DevFeed: [Thinking Fast, Anywhere: One System-1 for the Decision Points of Any Agent Workflow](<https://devfeed.tech/articles/thinking-fast-anywhere-one-system-1-for-the-decision-points-of-any-agent-workflow-142701.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.23751>)

Author: Rui Li, Liyang He, Zheng Zhang, Zhenya Huang, Qi Liu

Published: 2026-11-19T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>), [arXiv: Machine Learning](<https://devfeed.tech/sources/arxiv-machine-learning.md>)

Topics: [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [Multi-step AI processes](<https://devfeed.tech/topics/multi-step-ai-processes.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Benchmark](<https://devfeed.tech/topics/benchmark.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [cost](<https://devfeed.tech/tags/cost.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-cl](<https://devfeed.tech/tags/cs-cl.md>), [cs-lg](<https://devfeed.tech/tags/cs-lg.md>), [decision](<https://devfeed.tech/tags/decision.md>), [latency](<https://devfeed.tech/tags/latency.md>), [performance](<https://devfeed.tech/tags/performance.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

### AI overview

AnyS1 uses procedural skills to identify enumerable decision points across workflows, avoiding the need for environment-specific hooks. Offline, it mines decisions from over 1,000 public skills, gathers execution-grounded states in isolated containers to build Any-DP, and trains a calibrated 4B pointer System-1. At runtime, routine choices are made in one forward pass; decisions below a confidence threshold fall back to the larger System-2 model. On three unseen benchmarks and across distinct System-2 model families, the authors report preserved task reliability, 75-91% lower episode cost, and 63-92% less model-call time than an uncompiled System-2 agent, with performance maintained under zero-shot threshold transfer.

### Source excerpt

arXiv:2611.23751v1 Announce Type: new Abstract: Autonomous LLM agents incur substantial cost and latency by invoking a large model (System-2) at every step, even when many intermediate actions choose among a small set of known candidates. Existing dual-system agents offload such decisions to a lightweight System-1 model, but rely on workflow-specific hooks authored per environment. We present AnyS1, a framework that turns human-authored procedural skills, whose instructions naturally specify where choices arise and which options apply, into a shared, domain-general source of decision points. Offline, AnyS1 mines grounded enumerable decisions across over 1,000 public skills, gathers execution-grounded trajectory states inside isolated containers to construct Any-DP, and trains a single calibrated 4B pointer System-1 with label smoothing. At run time, compiled workflows resolve routine decisions in one forward pass and fall back to System-2 when confidence falls below a calibrated threshold. Across three unseen benchmarks and distinct System-2 model families, AnyS1 preserves task reliability while cutting episode cost by 75-91% and model-call time by 63-92% relative to an uncompiled System-2 agent, and maintains performance under zero-shot threshold transfer.

[Next page](<https://devfeed.tech/topics/agentic-workflows.md?cursor=WyIyMDI2LTExLTE5VDA1OjAwOjAwKzAwOjAwIiwgIjFhOGYzM2YyLTY0NDYtNGU0ZS05MzU4LTVkN2JmMjhhZGYzOSJd>)