Agency is a python library that provides an Actor model framework for creating agent-integrated systems.

The library provides an easy to use API that enables you to connect agents with traditional software systems in a flexible and scalable way, allowing you to develop any architecture you need.

Agency's goal is to enable developers to create custom agent-based applications by providing a minimal foundation to both experiment and build upon. So if you're looking to build a custom agent system of your own, Agency might be for you.

• Straightforward class/method based agent and action definition
• Up to date documentation and examples for reference

• Supports multiprocessing and multithreading for concurrency
• AMQP support for networked agent systems

• Action and lifecycle callbacks for observability or other needs
• Access policies and permission callbacks for access control
• Logging with support for LOGLEVEL environment variable

• Javascript client in progress

• Planned

• Multiple agent examples for experimentation
  • Two OpenAI agent examples
  • HuggingFace transformers agent example
  • Operating system access
• Includes Gradio UI (An updated React UI is in progress. See here.)
• Docker configuration for reference and development

In Agency, all entities are represented as instances of the Agent class. This includes all AI-driven agents, software interfaces, or human users that may communicate as part of your application.

All agents may expose "actions" that other agents can discover and invoke at run time. An example of a simple agent could be:

class CalculatorAgent(Agent):
    @action
    def add(a, b):
        return a + b

This defines an agent with a single action: add. Other agents will be able to call this method by sending a message to an instance of CalculatorAgent and specifying the add action. For example:

other_agent.send({
    'to': 'CalcAgent',
    'action': {
        'name': 'add',
        'args': {
            'a': 1,
            'b': 2,
        }
    },
})

Actions may specify an access policy, allowing you to control access for safety.

@action(access_policy=ACCESS_PERMITTED) # This allows the action at any time
def add(a, b):
    ...

@action(access_policy=ACCESS_REQUESTED) # This requires review before the action
def add(a, b):
    ...

Agents may also define callbacks for various purposes:

class CalculatorAgent(Agent):
    ...
    def before_action(self, message: dict):
        """Called before an action is attempted"""

    def after_action(self, message: dict, return_value: str, error: str):
        """Called after an action is attempted"""

    def after_add(self):
        """Called after the agent is added to a space and may begin communicating"""

    def before_remove(self):
        """Called before the agent is removed from the space"""

A Space is how you connect your agents together. An agent cannot communicate with others until it is added to a common Space.

There are two included Space implementations to choose from:

• LocalSpace - which connects agents within the same application.
• AMQPSpace - which connects agents across a network using an AMQP server like RabbitMQ.

Finally, here is a simple example of creating a LocalSpace and adding two agents to it.

space = LocalSpace()
space.add(CalculatorAgent, "CalcAgent")
space.add(MyAgent, "MyAgent")
# The agents above can now communicate

These are just the basic features that Agency provides. For more information please see the help site.

pip install agency

or

poetry add agency

The demo application is maintained as an experimental development environment and a showcase for library features. It includes multiple agent examples which may communicate with eachother and supports a "slash" syntax for invoking actions as an agent yourself.

To run the demo, please follow the directions at examples/demo.

The following is a screenshot of the Gradio UI that demonstrates the example OpenAIFunctionAgent following orders and interacting with the Host agent.

Agency is driven by a vision of the future where intelligent agents are ubiquitous, powerful, and free. A future where agents work for us and have the freedom to act upon systems as they see fit. In this vision, human driven software takes a backseat to AI driven software. Why implement an interface when an agent can build it for you as needed?

By providing a minimal messaging-based foundation that is usable not only by humans but by the agents themselves, we create a common base environment that allows AI developers to observe, train, and work with their agents hand-in-artificial-hand.

This project seeks to enable others to experiment and create agent-based systems of their own. I hope it helps you explore this exciting new technology, and I hope that you use it to help others.

Though you could entirely create a simple agent using only the primitives in Agency (see examples/demo/agents/), it is not intended to be an all-inclusive LLM-oriented toolset like other libraries. For example, it does not include support for constructing prompts or working with vector databases. Implementation of agent behavior is left entirely up to you, and you are free to use other libraries as needed for those purposes.

Agency focuses on the lower level concerns of communication, observation, scalability, and security. The library strives to provide the operating foundations of an agent system without imposing additional structure on you.

The goal is to allow you to experiment and discover the right approaches and technologies that work for your application. And once you've found an implementation that works, you can scale it out to your needs.

• Agency is still in early development.

  Like many projects in the AI agent space it is somewhat experimental at this time, with the goal of finding and providing a minimal yet useful foundation for building agent systems.

  Expect changes to the API over time as features are added or changed. The library follows semver versioning starting at 1.x.x. Minor version updates may contain breaking API changes. Patch versions should not.

• This API does not assume or enforce predefined roles like "user", "system", "assistant", etc. This is an intentional decision and is not likely to change.

  Agency is intended to allow potentially large numbers of agents, systems, and people to come together. A small predefined set of roles gets in the way of representing many things generally. This is a design feature of Agency: that all entities are represented similarly and may be interacted with through common means.

  The lack of roles may require extra work when integrating with role based APIs. See the implementation of OpenAIFunctionAgent for an example.

• There is currently not much by way of storage support. That is mostly left up to you and I'd suggest looking at the many technologies that focus on that. The Agent class implements a simple _message_log array which you can make use of or overwrite to back it with longer term storage. More direct support for storage APIs will likely be considered in the future.

Please do!

If you're considering a contribution, please check out the contributing guide.

See the issues page.

If you have any suggestions or otherwise, feel free to add an issue or open a discussion.