Using HagiTask

Who this is for: Users who have installed HagiCode and need to manage or run tasks.

Prerequisites: You have installed HagiTask, or the application already provides built-in presets.

Discover tasks

Open the application’s HagiTask/community task management interface. The application shows built-in tasks, installed community packages, workspace packages, and managed sources together, identifying each task’s origin and whether it can be removed. The Community Gallery catalog is for finding and retrieving community packages; server-visible directories are for runtime source discovery.

Install tasks

Choose and install a task from the Gallery, or use local archive installation with a supported ZIP you have already obtained. After a successful installation, the application records the canonical ID, version, publisher, source, archive digest, and installation directory. An installed task with the same ID is not silently overwritten; resolve the existing installation first.

Enable and disable tasks

• Enable: Add an installed task to the active task catalog so it can be discovered and run.
• Disable: Keep the installation record and package files, but remove the task from the active catalog so it cannot run.
• Uninstall: Available only for community tasks with installation records; built-in tasks are informational entries and cannot be uninstalled.

The application refreshes the catalog after a state change. If the refresh fails, the lifecycle operation should preserve the previous usable state rather than leave a partially updated catalog.

Refresh and run

Use Refresh to reread the current task catalog. When the Gallery catalog is force-refreshed, the application fetches and verifies it again; an existing valid cache may remain available during a temporary upstream failure. Refreshing does not automatically change a task’s enabled state or version.

Before running a task, confirm that it is enabled and its dependencies are met, then launch it from its panel or the corresponding run entry point. If it is missing, refresh and check the installation state, task ID, and compatibility notices. For invalid Schema or package resources, see the community contribution guide.

Package management vs. server source management

These operations are often confused:

Capability	Purpose	What the path refers to
Package management	Install, enable, disable, and uninstall local HagiTask packages.	The application’s managed data directory.
Server source management	Configure task sources for runtime catalog discovery.	A directory visible to the server.

The backend reads paths configured as server sources to discover task packages in those directories. They are neither browser paths nor upload controls. The current installation flow does not directly upload a browser-local folder as a Community Gallery package. Use the Gallery or a supported local ZIP flow to install packages.

If a task is unavailable

1. Confirm that the task ID, version, and installation record still exist.
2. Confirm that the task is enabled and its required agents, skills, and CLI are ready.
3. Refresh the task catalog and reopen the management interface.
4. For server-directory sources, verify that the backend process can read the path.
5. For archive validation or package resource failures, return to installation troubleshooting. If you maintain the package, read Contributing to the community.

Next step: Contribute to the community, or return to the HagiTask introduction.