Skip to main content

Effective harnesses for long-running agents Anthropic

·794 words·4 mins
Articoli AI Agent
Articoli Interessanti - This article is part of a series.
Part : Everything as Code: How We Manage Our Company In One Monorepo At Kasava, we've embraced the concept of "everything as code" to streamline our operations and ensure consistency across our projects. This approach allows us to manage our entire company within a single monorepo, providing a unified source of truth for all our configurations, infrastructure, and applications. **Why a Monorepo?** A monorepo offers several advantages: 1. **Unified Configuration**: All our settings, from development environments to production, are stored in one place. This makes it easier to maintain consistency and reduces the risk of configuration drift. 2. **Simplified Dependency Management**: With all our code in one repository, managing dependencies becomes more straightforward. We can easily track which versions of libraries and tools are being used across different projects. 3. **Enhanced Collaboration**: A single repository fosters better collaboration among team members. Everyone has access to the same codebase, making it easier to share knowledge and work together on projects. 4. **Consistent Build and Deployment Processes**: By standardizing our build and deployment processes, we ensure that all our applications follow the same best practices. This leads to more reliable and predictable deployments. **Our Monorepo Structure** Our monorepo is organized into several key directories: - **/config**: Contains all configuration files for various environments, including development, staging, and production. - **/infrastructure**: Houses the infrastructure as code (IaC) scripts for provisioning and managing our cloud resources. - **/apps**: Includes all our applications, both internal tools and customer-facing products. - **/lib**: Stores reusable libraries and modules that can be shared across different projects. - **/scripts**: Contains utility scripts for automating various tasks, such as data migrations and backups. **Tools and Technologies** To manage our monorepo effectively, we use a combination of tools and technologies: - **Version Control**: Git is our primary version control system, and we use GitHub for hosting our repositories. - **Continuous Integration/Continuous Deployment (CI/CD)**: We employ Jenkins for automating our build, test, and deployment processes. - **Infrastructure as Code (IaC)**: Terraform is our tool of choice for managing cloud infrastructure. - **Configuration Management**: Ansible is used for configuring and managing our servers and applications. - **Monitoring and Logging**: We use Prometheus and Grafana for monitoring,
Part : This Article
Featured image
#### Source

Type: Content via X
Original link: https://x.com/omarsar0/status/1993778780301873249?s=43&t=ANuJI-IuN5rdsaLueycEbA
Publication date: 2025-11-28


Summary
#

Introduction
#

The article “Effective harnesses for long-running agents” by Anthropic explores the challenges and solutions for managing AI agents in tasks that require prolonged work over time. In an era where AI agents are becoming increasingly capable, the ability to maintain consistency and progress in tasks that span hours or days is crucial. This article focuses on how Anthropic has developed a system to address these challenges, making AI agents more reliable and manageable in complex projects.

The content was shared on X with the comment “This is a great read for anyone working with long-running AI agents. It provides practical solutions to common problems and insights into how to structure your workflows effectively.” This comment underscores the practical importance of the proposed solutions, making the article particularly useful for developers and researchers working with long-term AI agents.

What It Offers / What It’s About
#

The article by Anthropic focuses on how to manage AI agents in tasks that require prolonged work over time. AI agents, when faced with complex tasks that span hours or days, must work in discrete sessions, without memory of previous sessions. This creates a significant challenge, as each new session starts without context, making it difficult to maintain progress.

To address this challenge, Anthropic has developed a two-part solution: an initializer agent and an encoding agent. The initializer agent sets up the environment at the beginning of the project, creating a log file and an initial commit. The encoding agent, on the other hand, works in subsequent sessions, making incremental progress and leaving the environment in a clean state at the end of each session. This approach ensures that each new session can start with a clear understanding of the current state of the project, facilitating more efficient and consistent work.

Why It’s Relevant
#

Practical Solutions for Common Problems
#

The article is particularly relevant for anyone working with long-term AI agents. It provides practical solutions to common problems, such as managing context and maintaining progress across multiple sessions. This makes the content extremely useful for developers and researchers looking to improve the efficiency and consistency of their AI agents.

Potential Impact
#

The solutions proposed by Anthropic can have a significant impact on the efficiency and quality of AI agent work. By implementing these techniques, developers can reduce time wasted on context recovery and improve the quality of the code produced. This is particularly important in complex projects that require prolonged work over time.

Who It’s Useful For
#

This article is useful for a wide range of professionals in the field of AI, including developers, researchers, and software engineers. Anyone working with AI agents that need to handle complex and prolonged tasks will find value in the proposed solutions. Additionally, those interested in improving context management and the consistency of AI agent work will find this article particularly useful.

How to Use It / Dig Deeper
#

To delve deeper into the solutions proposed by Anthropic, you can read the full article on Effective harnesses for long-running agents. The article provides technical details and practical examples that can be implemented in your projects.

If you are interested in exploring further, you can also consult Anthropic’s guide on how to use the Claude Agent SDK, which includes best practices for multi-context workflows. Additionally, you can explore other Anthropic resources for further insights into managing AI agents in complex tasks.

Final Thoughts
#

The article by Anthropic fits into a broader context of research and development in the field of AI, where managing long-term agents is an increasing challenge. The proposed solutions reflect a trend towards creating more reliable and interpretable AI systems, which can work consistently on complex tasks. This article is an example of how software engineering practices can be applied to improve the efficiency and quality of AI agent work, contributing to a more robust and reliable AI ecosystem.


Use Cases
#

  • Private AI Stack: Integration into proprietary pipelines
  • Client Solutions: Implementation for client projects

Resources
#

Original Links #


Article highlighted and selected by the Human Technology eXcellence team, processed via artificial intelligence (in this case with LLM HTX-EU-Mistral3.1Small) on 2025-11-28 19:23 Original source: https://x.com/omarsar0/status/1993778780301873249?s=43&t=ANuJI-IuN5rdsaLueycEbA

Related Articles #

Articoli Interessanti - This article is part of a series.
Part : Everything as Code: How We Manage Our Company In One Monorepo At Kasava, we've embraced the concept of "everything as code" to streamline our operations and ensure consistency across our projects. This approach allows us to manage our entire company within a single monorepo, providing a unified source of truth for all our configurations, infrastructure, and applications. **Why a Monorepo?** A monorepo offers several advantages: 1. **Unified Configuration**: All our settings, from development environments to production, are stored in one place. This makes it easier to maintain consistency and reduces the risk of configuration drift. 2. **Simplified Dependency Management**: With all our code in one repository, managing dependencies becomes more straightforward. We can easily track which versions of libraries and tools are being used across different projects. 3. **Enhanced Collaboration**: A single repository fosters better collaboration among team members. Everyone has access to the same codebase, making it easier to share knowledge and work together on projects. 4. **Consistent Build and Deployment Processes**: By standardizing our build and deployment processes, we ensure that all our applications follow the same best practices. This leads to more reliable and predictable deployments. **Our Monorepo Structure** Our monorepo is organized into several key directories: - **/config**: Contains all configuration files for various environments, including development, staging, and production. - **/infrastructure**: Houses the infrastructure as code (IaC) scripts for provisioning and managing our cloud resources. - **/apps**: Includes all our applications, both internal tools and customer-facing products. - **/lib**: Stores reusable libraries and modules that can be shared across different projects. - **/scripts**: Contains utility scripts for automating various tasks, such as data migrations and backups. **Tools and Technologies** To manage our monorepo effectively, we use a combination of tools and technologies: - **Version Control**: Git is our primary version control system, and we use GitHub for hosting our repositories. - **Continuous Integration/Continuous Deployment (CI/CD)**: We employ Jenkins for automating our build, test, and deployment processes. - **Infrastructure as Code (IaC)**: Terraform is our tool of choice for managing cloud infrastructure. - **Configuration Management**: Ansible is used for configuring and managing our servers and applications. - **Monitoring and Logging**: We use Prometheus and Grafana for monitoring,
Part : This Article