Introduction to HagiTask

Who this is for: HagiTask users, maintainers, and contributors.

Prerequisites: None. To install or run tasks, first set up the HagiCode application and its backend service.

What is HagiTask?

HagiTask is HagiCode’s task package and preset task model. A task package puts its identity, frontend panel, backend prompts, templates, UI text, and store listing in one verifiable directory. The application can discover, install, manage, and run tasks from that directory.

A task package is not the application itself and does not replace its runtime configuration. The application loads and executes the capabilities declared by a task; the package only supplies resources arranged according to the package format.

Roles in the ecosystem

Role	Responsibility
HagiTask	Maintains the shared Schema and the built-in preset packages shipped with the product; it is the source of truth for the package format.
Built-in presets	Ready-to-use tasks provided with the application or runtime, such as normal-session and research-investigation.
Community Packages	Maintains community task source data under data/<taskId>/.
HagiTask Site	Generates the catalog, detail JSON, and ZIP archives from community package sources and publishes them to the Community Gallery.
HagiCode application	Displays tasks, installs packages, saves enabled states, and executes tasks at runtime.

Built-in presets and community tasks use the same package Schema but have different sources and lifecycles: the HagiTask repository maintains built-in presets, while the Community Packages repository maintains community tasks. The site’s /index.json, detail documents, and ZIP files are generated outputs, not source files for contributors to edit directly.

Package management is not source management

Installing a ZIP from the Gallery copies a package to the application’s data directory and records its version, source, and enabled state. Server source management instead configures directories visible to the server so the runtime can discover tasks there; it does not upload a browser-local folder as a package.

For operational boundaries and folder sources, read Using HagiTask. To get started with installation, see Installing HagiTask; to create or publish tasks, see Contributing to the community.

Source-of-truth boundaries

• docs maintains user- and contributor-facing explanations and procedures.
• HagiTask maintains the shared Schema and built-in preset sources.
• Community Packages maintains community package source data.
• HagiTask Site publishes the catalog, details, and archives generated from package sources.

Next step: Install HagiTask.