Class Management β
In Wardian, a Class is more than just a labelβit is a functional blueprint that defines the core identity, intelligence, and equipment of your agents.
ποΈ The Class Library β
Class management has been relocated from the sidebar to the Library view to provide a spacious, professional editor for your blueprints.
- Click LIBRARY in the top bar.
- Select the Classes tab.
- Browse the list of available classes or click Create New Class.
π§ Configuring a Blueprint β
1. Instruction Set (AGENTS.md) β
Each class is governed by a markdown file. This is where you define:
- Role & Personality: Who the agent is (e.g., "A skeptical security auditor").
- Constraints: What the agent cannot do (e.g., "Never overwrite existing .env files").
- Standard Procedures: How the agent should approach tasks (e.g., "Always draft a plan before executing").
2. Pre-Assigned Skills β
You can pre-load a class with specific modular skills.
- When you assign a skill to a class, every agent spawned from that blueprint receives the skill through its provider's discovery path. Wardian may use directory links, provider home projection, generated config, or provider-native include roots depending on the selected CLI.
- This ensures your
Coderclass always starts withgithub-cliandtypescript-toolsready to go.
3. Registry Persistence β
All your custom classes are stored in ~/.wardian/classes.json. This single file is the source of truth for the Rust backend when spawning new sessions.
π Spawning from a Class β
To use your blueprint:
- Navigate to the Agent Configuration tab in the Left Sidebar.
- Select your class from the dropdown.
- Click Spawn Instance. The agent will inherit all instructions and skills defined in the Library for that class.