Configuration files
We use YAML files to define the structure of AI agents, persist their runtime state, specify the actions they can execute, and configure web scraping workflows. This approach keeps configurations human-readable, versionable, and easy to validate, while separating logic from data for cleaner, more maintainable systems.
| File extension | Index | Description |
|---|---|---|
| .halguru.yaml | A-Z | The full configuration of an agent. |
| .halguru-action.yaml | A-Z | Represents an action performed by an agent within the system. |
| .halguru-ksef.yaml | A-Z | Represents a KSEF ivoice document. |
| .halguru-license.yaml | A-Z | Represents a license granted to a user. |
| .halguru-rag.yaml | A-Z | Represents an RAG container definition within the system. |
| .halguru-ragfile.yaml | A-Z | Represents an RAG file definition within the system. |
| .halguru-state.yaml | A-Z | Defines the operational state and associated metadata for a session of an agent. |
| .halguru-webscraping.yaml | A-Z | Represents the configuration settings for a website crawler or scraper. |
| .halguru-website.yaml | A-Z | Represents the output of a web scraping operation executed by the application. |
→ JSON Schemas#
↗ YAML Tutorial#
↗ YAML Official Manual#
| Last updated: | 2026-03-19 | |
| Autogenerated: | Yes | |
| AI powered: | Yes | |
| Core version: | 1.93.0 |