Overview

Before diving deep into the kernel functions, this page provides an overview of the kernel design to illustrate how the different modules in the AIOS kernel interact with each other. The AIOS Kernel comprises several key modules, each playing a specialized role to facilitate and manage agent requests effectively.

Details of how agents leverage SDK to interact with AIOS kernel and how AIOS kernel leverages syscalls in different modules to achieve functionalties

LLM Core(s)

The LLM core wraps the deployed instances of LLM from different providers in a unified manner, treating each LLM as a core similar to CPU cores. This abstraction allows multiple LLMs to be integrated via a single interface, enabling flexible and efficient usage of different LLM models.

Context Manager

The Context Manager is responsible for handling context management (such as context switch) during the processing of each LLM Core. In the LLM agent scenario, "context" refers to the data that is actively fed into each LLM Core during processing.

Memory Manager

The Memory Manager handles data storage in RAM that agents need during runtime, distinguishing it from persistent storage. "Memory" here refers to transient data necessary for ongoing operations, such as temporary variables or recently processed data. It supports memory operations required by agents to store and retrieve information quickly during active tasks.

Storage Manager

The Storage Manager is designed for handling persistent storage operations, where "storage" refers to data saved on disk that agents may require for future tasks or for logging purposes.

Tool Manager

The tool manager loads and manages various tools available within the AIOS-Agent SDK. This module manages tool call conflicts and prioritizes tool operations to ensure the stable execution of tool calls.

Key Differences among Context, Memory, and Storage

Context: Data that is fed into the LLM core and is under processing by the LLM core.

Memory: Transient data stored in RAM, which agents require temporarily during active tasks or sessions. Memory is cleared after tasks complete.

Storage: Persistent data saved on disk, intended for long-term use or logging, accessible by agents even after a session ends.