Agents

Chiltepin integrates with Academy Agents to support distributed agent-based workflows. Agents enable long-running, stateful computations that can be launched on remote resources and interacted with asynchronously through an agent_action-based API.

Note

Chiltepin’s agent system builds on Academy Agents to provide:

  1. Automatic workflow lifecycle management: Agents manage their own Parsl workflow context

  2. Simplified agent creation: Use @chiltepin_agent decorator on regular Python classes

  3. Runtime configuration: Pass workflow config, executors, and paths via manager.launch()

  4. Serializable behavior: Decorated classes remain fully serializable for remote execution

For more information about Academy Agents, see the Academy documentation.

Note

Decorator Order: The order of @agent_action and @python_task decorators does not affect behavior—both orders are supported and tested. For consistency and readability, we recommend using @python_task outermost and @agent_action innermost (closest to the function), but either order will work.

Important

ChiltepinManager and AgentSystem only support agents decorated with @chiltepin_agent. Native Academy agents (not decorated) are not supported and will raise an error if launched with ChiltepinManager. Use the base Academy Manager for native agents.

Warning

Multi-Agent Deployments on Shared Filesystems:

When launching multiple agents on systems with shared filesystems (e.g., HPC clusters, shared network storage), you must provide unique agent_workflow_run_dir values to each agent to avoid Parsl directory collisions. If agent_workflow_run_dir is not specified, a unique directory is auto-generated using a UUID.

Recommended practice: Explicitly set agent_workflow_run_dir in manager.launch() to use predictable paths for debugging:

agent1 = await manager.launch(
    MyAgent,
    agent_workflow_config=config,
    agent_workflow_run_dir="/scratch/agent1_runinfo"  # Unique path
)

agent2 = await manager.launch(
    MyAgent,
    agent_workflow_config=config,
    agent_workflow_run_dir="/scratch/agent2_runinfo"  # Different path
)

Overview

Chiltepin provides five main components for agent-based workflows:

  • @chiltepin_agent: Decorator to wrap a regular Python class as an agent

  • @agent_action: Decorator to mark methods that should be exposed as agent actions (works with sync or async)

  • @agent_loop: Decorator to mark async methods that should run as background loops (must be async)

  • AgentSystem: Helper class to simplify Academy Manager setup with Parsl executors

  • ChiltepinManager: Custom Manager that supports workflow configuration parameters

When to Use Agents

Use agents when you need:

  • Long-running services: Agents that persist beyond a single task execution

  • Stateful computations: Maintaining state across multiple agent_action invocations

  • Background processing: Loops that update state while handling requests

  • Autonomous behavior: Agents that can make decisions and act without external prompts

  • Remote interaction: Asynchronous communication with computations on remote resources

For one-off tasks without shared state, use Tasks instead.

Basic Usage

Creating an Agent

Use the @chiltepin_agent decorator to wrap a regular Python class:

from chiltepin.agents import chiltepin_agent, agent_action, agent_loop
from chiltepin.tasks import python_task

@chiltepin_agent(agent_workflow_include=["compute"])
class WeatherModel:
    """A simple weather model agent."""

    def __init__(self, temperature: float):
        self.temperature = temperature

    @agent_action
    @python_task
    def forecast(self) -> str:
        """Generate a forecast based on current temperature."""
        import random
        conditions = ["sunny", "cloudy", "rainy"]
        return f"{random.choice(conditions)} at {self.temperature}°C"

    @agent_action
    async def get_temperature(self) -> float:
        """Get the current temperature."""
        return self.temperature

    @agent_loop
    async def update_temperature(self, shutdown):
        """Background agent_loop that updates temperature."""
        import asyncio
        import random
        while not shutdown.is_set():
            await asyncio.sleep(1)
            self.temperature += random.uniform(-2, 2)

Key Features

  1. Regular Python class: No inheritance required, fully serializable

  2. Access instance state: Task-decorated methods can access self.temperature

  3. Mixed sync/async: Use @agent_action on both sync and async methods

  4. Background loops: Use @agent_loop on async methods for continuous background processing or autonomous behavior

  5. Infrastructure separation: Workflow config passed via manager.launch(), not __init__

Note

@agent_loop requires async methods: The @agent_loop decorator can only be applied to async methods. This is validated at decoration time, and a TypeError will be raised if you attempt to use it on a synchronous method. Background loops must be async to properly cooperate with the agent’s event loop.

Launching Agents

Use AgentSystem to create a manager and launch agents:

from chiltepin import Workflow, AgentSystem

# Configuration for the manager's workflow (where agents run)
manager_config = {
    "manager-executor": {
        "endpoint": ENDPOINT_UUID,
        "provider": "localhost",
    }
}

# Configuration for the agent's internal workflow (where tasks run)
agent_config = {
    "compute": {
        "provider": "slurm",
        "partition": "compute",
        # ... other config
    }
}

# Start workflow for hosting agents
workflow = Workflow(manager_config, include=["manager-executor"])
workflow.start()

# Create agent system
agent_system = AgentSystem(
    workflow=workflow,
    executor_names=["manager-executor"],
)

# Launch and interact with agent
async with await agent_system.manager() as manager:
    model = await manager.launch(
        WeatherModel,
        agent_workflow_config=agent_config,   # Agent's workflow config
        agent_workflow_include=["compute"],   # Which executors to use
        args=(25.0,),                # Arguments for __init__
        executor="manager-executor"  # Where to run the agent
    )

    # Call agent actions
    temp = await model.get_temperature()
    forecast = await model.forecast(executor=["compute"])

workflow.cleanup()

Runtime Configuration

Infrastructure concerns (workflow config, executors, directories) are passed to manager.launch() rather than the behavior class:

model = await manager.launch(
    WeatherModel,
    agent_workflow_config=agent_config,         # Workflow configuration dict or YAML path
    agent_workflow_include=["compute"],         # List of executors to include (None = all)
    agent_workflow_run_dir="/custom/path",      # Directory for Parsl runtime files
    args=(25.0,),                # Behavior arguments (domain logic)
    kwargs={"units": "C"},       # Behavior keyword arguments
    executor="manager-executor"  # Agent executor (where agent runs)
)

This separation keeps behavior classes focused on domain logic:

@chiltepin_agent()
class WeatherModel:
    def __init__(self, temperature: float, units: str = "C"):
        # Only domain logic, no infrastructure concerns
        self.temperature = temperature
        self.units = units

Decorator Parameters

The @chiltepin_agent decorator accepts default values that can be overridden at runtime:

@chiltepin_agent(agent_workflow_include=["default-compute"], agent_workflow_run_dir="./runs")
class MyAgent:
    pass

# Use decorator defaults
agent1 = await manager.launch(MyAgent, agent_workflow_config=cfg)

# Override at runtime
agent2 = await manager.launch(
    MyAgent,
    agent_workflow_config=cfg,
    agent_workflow_include=["special-compute"],  # Overrides decorator default
    agent_workflow_run_dir="/tmp/runs"           # Overrides decorator default
)

Action Decorators

Use @agent_action to expose methods as agent actions. The decorator works with both synchronous and asynchronous methods:

Synchronous Actions

from chiltepin.agents import chiltepin_agent, agent_action
from chiltepin.tasks import python_task

@chiltepin_agent()
class DataProcessor:
    @python_task
    @agent_action
    def process_data(self, data: str) -> str:
        """Synchronous task-decorated method."""
        return data.upper()

    @agent_action
    def get_config(self) -> dict:
        """Synchronous helper method."""
        return {"version": "1.0"}

Asynchronous Actions

@chiltepin_agent()
class AsyncService:
    @agent_action
    async def fetch_data(self, url: str) -> str:
        """Async method using httpx, aiohttp, etc."""
        import httpx  # ✅ Import inside method for serializability
        # ✅ Create client temporarily, don't store in self.__init__
        async with httpx.AsyncClient() as client:
            response = await client.get(url)
            return response.text

Task-Decorated Actions

When using @python_task with @agent_action, the order does not matter and both are supported:

@chiltepin_agent()
class Computer:
    @python_task
    @agent_action
    def compute(self, x: int) -> int:
        return x ** 2

This allows the task to access instance state (self) while still executing remotely.

Loop Decorators

Use @agent_loop to create background tasks that run continuously:

from chiltepin.agents import chiltepin_agent, agent_loop
import asyncio

@chiltepin_agent()
class Monitor:
    def __init__(self):
        self.status = "initializing"
        self.count = 0

    @agent_loop
    async def heartbeat(self, shutdown: asyncio.Event):
        """Background agent_loop that runs until agent shuts down."""
        self.status = "running"
        while not shutdown.is_set():
            await asyncio.sleep(1)
            self.count += 1
            if self.count % 10 == 0:
                print(f"Heartbeat: {self.count}")
        self.status = "stopped"

The shutdown event is provided automatically and signals when the agent is shutting down.

AgentSystem Helper

The AgentSystem class simplifies setup by wrapping the complexity of creating an Academy Manager with ParslPoolExecutors:

from chiltepin import Workflow, AgentSystem

# Without AgentSystem (manual setup)
from academy.manager import Manager
from academy.exchange.cloud.client import HttpExchangeFactory
from parsl.concurrent import ParslPoolExecutor

executors = {
    "my-exec": ParslPoolExecutor(dfk=workflow.dfk, executors=["my-exec"])
}

async with await Manager.from_exchange_factory(
    factory=HttpExchangeFactory(
        "https://exchange.academy-agents.org",
        auth_method="globus"
    ),
    executors=executors
) as manager:
    # Use manager
    pass

# With AgentSystem (simplified)
agent_system = AgentSystem(
    workflow=workflow,
    executor_names=["my-exec"],
)

async with await agent_system.manager() as manager:
    # Use manager - ChiltepinManager with config/include/run_dir support
    pass

ChiltepinManager

ChiltepinManager is a custom Manager subclass that intercepts launch() to support Chiltepin-specific parameters (config, include, run_dir). It’s created automatically by AgentSystem.manager().

You can also create it directly:

from chiltepin.agents import ChiltepinManager
from academy.exchange.cloud.client import HttpExchangeFactory

async with await ChiltepinManager.from_exchange_factory(
    factory=HttpExchangeFactory(
        "https://exchange.academy-agents.org",
        auth_method="globus"
    ),
    executors=my_executors
) as manager:
    agent = await manager.launch(
        MyAgent,
        agent_workflow_config=agent_config,
        agent_workflow_include=["compute"]
    )

Best Practices

Import Decorators Correctly

Always use Chiltepin’s decorators (agent_action and agent_loop), not Academy’s native decorators (action and loop):

# ✅ Correct - Use Chiltepin's decorators
from chiltepin.agents import chiltepin_agent, agent_action, agent_loop

# ❌ Wrong - Academy's decorators have different names and semantics
from academy.agent import action, loop

Academy’s @action requires async methods, while Chiltepin’s @agent_action works with both sync and async.

Keep Behavior Classes Serializable

Since agents can run remotely, behavior classes must be serializable:

@chiltepin_agent()
class GoodAgent:
    def __init__(self, value: int):
        self.value = value  # ✅ Serializable types

    @agent_action
    @python_task
    def compute(self):
        # ✅ Import modules inside methods for remote execution
        import numpy as np
        return np.array([self.value])

@chiltepin_agent()
class BadAgent:
    def __init__(self, value: int):
        import numpy as np  # ❌ Don't import at class level
        self.np = np        # ❌ Modules may not serialize
        self.value = value

Separate Infrastructure from Logic

Pass infrastructure concerns via manager.launch():

@chiltepin_agent()
class MyAgent:
    def __init__(self, threshold: float):  # ✅ Domain parameters only
        self.threshold = threshold

# ❌ Bad - mixing infrastructure with domain logic
# def __init__(self, threshold: float, workflow_config: dict):
#     self.threshold = threshold
#     self.config = workflow_config

Use Type Hints

Type hints improve code clarity and enable better IDE support:

from typing import List

@chiltepin_agent()
class TypedAgent:
    def __init__(self, values: List[float]):
        self.values = values

    @agent_action
    @python_task
    def mean(self) -> float:
        return sum(self.values) / len(self.values)

Complete Example

Here’s a complete example combining all features:

import asyncio
import logging
from chiltepin import Workflow, AgentSystem
from chiltepin.agents import chiltepin_agent, agent_action, agent_loop
from chiltepin.tasks import python_task

logger = logging.getLogger(__name__)

@chiltepin_agent(agent_workflow_include=["compute"])
class TemperatureModel:
    """Agent that forecasts temperature with background updates."""

    def __init__(self, initial_temp: float, location: str):
        self.temperature = initial_temp
        self.location = location
        self.forecast_count = 0

    @agent_action
    @python_task
    def forecast(self) -> str:
        """Generate forecast using current temperature."""
        import random
        conditions = ["sunny", "cloudy", "rainy", "snowy"]
        condition = random.choice(conditions)
        return f"{self.location}: {condition}, {self.temperature:.1f}°C"

    @agent_action
    async def get_stats(self) -> dict:
        """Get current statistics."""
        return {
            "temperature": self.temperature,
            "location": self.location,
            "forecasts_generated": self.forecast_count
        }

    @agent_action
    async def set_temperature(self, temp: float) -> None:
        """Manually update temperature."""
        self.temperature = temp

    @agent_loop
    async def update_temperature(self, shutdown: asyncio.Event):
        """Simulate temperature changes."""
        import asyncio
        import random

        while not shutdown.is_set():
            await asyncio.sleep(2)
            # Random walk
            self.temperature += random.uniform(-1, 1)
            # Keep reasonable bounds
            self.temperature = max(-50, min(50, self.temperature))

async def main():
    # Manager workflow configuration
    manager_config = {
        "manager-executor": {
            "endpoint": "your-endpoint-uuid",
            "provider": "localhost",
        }
    }

    # Agent workflow configuration
    agent_config = {
        "compute": {
            "provider": "slurm",
            "partition": "compute",
            "cores_per_node": 48,
            "walltime": "01:00:00",
        }
    }

    # Start manager workflow
    workflow = Workflow(manager_config, include=["manager-executor"])
    workflow.start()

    # Create agent system
    agent_system = AgentSystem(
        workflow=workflow,
        executor_names=["manager-executor"],
    )

    async with await agent_system.manager() as manager:
        # Launch agent with runtime configuration
        model = await manager.launch(
            TemperatureModel,
            agent_workflow_config=agent_config,
            agent_workflow_include=["compute"],
            args=(20.0, "Boulder, CO"),
            executor="manager-executor"
        )

        # Interact with agent
        logger.info("Getting initial stats...")
        stats = await model.get_stats()
        logger.info(f"Stats: {stats}")

        logger.info("Generating forecast...")
        forecast = await model.forecast(executor=["compute"])
        logger.info(f"Forecast: {forecast}")

        logger.info("Waiting for temperature updates...")
        await asyncio.sleep(5)

        stats = await model.get_stats()
        logger.info(f"Updated stats: {stats}")

        logger.info("Setting temperature manually...")
        await model.set_temperature(25.0)

        forecast = await model.forecast(executor=["compute"])
        logger.info(f"New forecast: {forecast}")

    workflow.cleanup()
    logger.info("Done!")

if __name__ == "__main__":
    logging.basicConfig(level=logging.INFO)
    asyncio.run(main())

Troubleshooting

Serialization Errors

If you get serialization errors when launching agents:

  1. Check that behavior class doesn’t inherit from non-serializable classes

  2. Move imports inside methods rather than at class level

  3. Avoid storing non-serializable objects (file handles, connections) in self

Action Not Found

If an agent_action isn’t available on the agent proxy:

  1. Check that the method is decorated with @agent_action

  2. Verify you’re using agent_action from chiltepin.agents, not action from academy.agent

  3. Ensure the method name doesn’t start with underscore (private methods aren’t exposed)

Workflow Not Starting

If the agent’s internal workflow doesn’t start:

  1. Check that config is passed to manager.launch()

  2. Verify the configuration dict is valid (see Configuration)

  3. Check that include parameter matches actual executor names in config

  4. Check that requested executors are available and can start (e.g. Slurm partition is correct)

  5. Check that resources are available (e.g. Slurm queue isn’t full)

See Also