Skip to content

index.md

Latest commit

 

History

History
68 lines (45 loc) · 2.96 KB

index.md

File metadata and controls

68 lines (45 loc) · 2.96 KB

Agent Extensions

extension-agentclass is a companion repository of client-level extensions that augment the composed Summoner SDK with higher-level orchestration features. Unlike utility extensions, these modules are meant to extend the runtime API of the client (for example, by adding new decorators, handler patterns, or execution controls).

The intended workflow is:

  • choose the agent extensions you want (for example aurora)
  • add them to your SDK composition list (via build.txt)
  • import them from the composed SDK as normal Python modules (for example from summoner.aurora import ...)

These extensions are "client-level" in the sense that they sit on top of SummonerClient and provide additional behavior for agent execution and communication. They are designed to remain compatible with the core protocol, while making advanced patterns easier to express.

Repository and import model

The extension-agentclass repository follows the extension-template layout, which implies that each extension lives under tooling/<module>/.

During local development, import from tooling.*:

from tooling.aurora import SummonerAgent

During SDK composition, the builder copies tooling/<module>/ into summoner/<module>/ and rewrites imports of the form from tooling.<module> ... into the public namespace:

from summoner.aurora import SummonerAgent

Note

In the repository, the script install.sh setup boots a dev environment and installs summoner-core. It does not compose a new SDK. Composition happens in an SDK project via build.txt.

Installation in a summoner-sdk workflow

For projects built using the summoner-sdk template, you can include a module by adding it to build.txt. Each entry specifies the extension repository and the module name to merge during SDK composition.

Minimal pattern:

https://github.com/Summoner-Network/extension-agentclass.git:
<module_name>

Example:

https://github.com/Summoner-Network/extension-agentclass.git:
aurora

After composition, you import from the summoner.* namespace:

from summoner.aurora import SummonerAgent

Note

Inside the extension-agentclass repository itself, local tests may import modules directly from the repo layout (for example from tooling.aurora import ...). For normal SDK usage, always import from summoner.<module>.

Aurora

  • Extends the SummonerClient with keyed orchestration, Aurora-aware merger APIs, and a dedicated identity API.
  • Status: Stable (1.0.0).
  • Link: Summoner.aurora

« Previous: Summoner.protocol    |    Next: Utility Extensions »