Auto

Auto is an autonomous context window management implementation.

Introduction

One of the challenges in running autonomous agents is the management of an ever-growing context window. This implementation gives the agent the capability to manage its context window autonomously.

Each message in the context window (i.e., system, assistant, and user) is prepended with a <metadata> tag that contains an id attribute assigned a unique identifier. This unique identifier allows the agent to reference and manage messages in its context window using one of its tools:

• The update tool: An <update> element is used in order to update the contents of a specified message in the context window.
• The delete tool: A <delete> element is used in order to delete a message from the context window.

Further, the agent is given a tool that allows it to drive its own reasoning:

• The user tool: A <user> element is used in order to specify the subsequent user message.

The system/developer message contains instructions on how to use the toolkit:

Excerpted from ./tests/system_message.md.

## Your environment

### Message identification

- Every message you generate MUST be prepended with a self-closing <metadata> tag.
- The <metadata> tag MUST contain the following attributes:
  - `id`: The UUID of the message.
  - `cumulative_message_token_count`: The cumulative count of tokens up to the message.
  - `message_token_count`: The count of tokens in the message.
- You SHOULD use your Commands in order to prune your context window.

### Commands

- You MUST manage your context window using the following Commands:
  - You MAY use the <update> command to update the content of the message specified by the `id` attribute.
  - You MAY use the <delete> command to delete the message specified by the `id` attribute.
  - You MUST use the <user> command to specify the content of the subsequent `user` message.
- When generating XML or HTML:
- You MUST use XML elements in order to execute a command.
- You MUST use XML entities if you are NOT executing a command. For example, use <update> instead of writing "update" directly.
- You MAY generate multiple commands in the same message.

#### Example Commands

**Update the content of the message specified by the `id`:**

<update id="96d33d81-5f59-4e2a-8520-210a64f85274">This content will replace the content that was in message id=96d33d81-5f59-4e2a-8520-210a64f85274.</update>

**Delete the message specified by the `id`:**

<delete id="96d33d81-5f59-4e2a-8520-210a64f85274" />

**Specify the content of the subsequent `user` message:**

<user>Reflect on something.</user>

Table of Contents

• Installation
• Usage

Installation

pip install git+https://github.com/faranalytics/auto.git

Usage

Instructions

Clone the repository.

git clone https://github.com/faranalytics/auto.git

Change directory into the repository.

cd auto

Pip install the project in editable mode.

pip install -e .

Change directory into the tests directory.

cd tests

In the tests directory you will find a suitable system message and default user message.

Create a config.ini file.

[DEFAULT]
OPENAI_API_KEY =
STORE_PATH = ./store
SYSTEM_MESSAGE_PATH = ./system_message.md
MODEL = gpt-4o-2024-08-06
DEFAULT_USER_MESSAGE_PATH = ./default_user_message.md
TEMPERATURE = 0

Run the script.

• Specify the location of the config.ini file.
• The --init flag will remove a previously initialized message store and create a new message store in the specified STORE_PATH directory.

python -m auto --config-path=./config.ini --init

Alternatively, if you omit the --init flag, you can run the script while retaining the conversation history in STORE_PATH.

python -m auto --config-path=./config.ini