Skip to content
Live
Opinion#Engineering
Oct 25Sun
  1. The Decoder71

    Anthropic claims that a single agent is superior to a multi-sub-agent architecture in terms of quality, cost, and latency.

    Anthropic indicates that a single context-loaded agent is often superior to a multi-sub-agent architecture in terms of quality, cost, and latency, and releases a migration toolkit to help teams evaluate whether to merge sub-agents. Anthropic claims that new models starting from Opus 4.5 can directly manage complex plans in a single loop, with a single-agent architecture running about twice as fast as a multi-agent solution in a single comparison.

    Why it matters: Anthropic based on enterprise deployment experience gives a judgment that a single agent is better than multiple sub-agents, and lists the applicable boundaries and migration paths.

Oct 24Sat
Oct 23Fri
  1. Tessl Blog38

    Who should own the keys when writing code through an agent?

    The amount and speed of code generated by the agent make manual review a bottleneck; the team needs to use tools as a substitute; the agent is only responsible for writing code without deployment permissions, deployment is controlled by pipelines; all data read by the agent is considered untrusted, the pipeline must ensure security through hash verification and short-term identity, and continuously monitor permission changes.

Oct 21Wed
  1. Tessl Blog75

    Jellyfish Analysis: The review bottleneck of AI coding agents restricts development efficiency

    22% of the PRs of Median Company are completed by AI coding agents, with 90% reaching 53%, but only 0.6% of the PRs are reviewed and merged by AI, with 10% reaching 9%. The abandonment rate (40%) of code generated by agents is twice that of manual (20%), and the review volume increases after merging. The leadership faces ROI issues, as the upstream code generation acceleration (2x PR growth) far exceeds the downstream output (40-50% feature growth), with the review bottleneck becoming a constraint factor.

Oct 20Tue
  1. Tessl Blog75

    From Standalone Coding Tools to Development Platforms: How Trust Affects the Adoption of AI Code Assistants

    Engineering teams' trust in AI code assistants determines their scope of use, ranging from viewing code differences to full authorization for merging. Trust is built through rapid validation mechanisms. Development platform costs increase with the intensity of AI agent work, with about 80% of the budget consumed by 20% of heavy users, requiring an evaluation of the effective cost per unit of work. Successful teams start with auxiliary tasks and gradually expand the scope of AI, rather than applying it directly to core systems.

Oct 10Sat
  1. Interconnects65

    Researchers expect AI to surpass its performance in the workplace in a few years, but not general superintelligence

    Researchers predict that AI will surpass its performance in work in the next few years, but it will not be general superintelligence. The infrastructure and engineering capabilities of models will be significantly accelerated, making experiments and model adjustments easier to implement, but it will not change the nature of the model. The effective cost of AI intelligence is expected to decline exponentially in the coming years, and demand will increase as industries explore the direction and delivery methods of intelligent agents.

Oct 7Wed
  1. AWS Machine Learning Blog

    AWS has launched an automated value model, redefining the business case for agent automation.

    AWS has proposed an automated value model, redefining the business case for agent automation. Traditional RPA investment return models overlook the value of agent automation in exception handling, decision quality, process adaptability, and value realization. Enterprises need to consider the redeployment value of released labor time or the reduction in cash costs, as well as the cost of exception correction, to build a credible business case.

Sep 25Fri