Skip to main content

​
Introduction

Hiro Task Manager is a Web/CLI Task Management System. It is designed for humans and AI agents to manage boards, lists and tasks through a common interface. Hiro Task Manager has both a web UI and a CLI. Hiro Task Manager exposes CLI Commands to allow AI agents to use it effectively as humans do. While the Web UI exposes a visual, easy to use interface, for humans to brainstorm, plan and reflect on their tasks.

​
Concepts

The following concepts give you a vocabulary to understand the core concepts of Hiro Task Manager.

​
Boards

A board is a workspace for your project. It groups everything that belongs to one context (for example a product, client, or initiative): the lists tasks live on, how tasks are categorized, prioritized, grouped into releases. Boards are the top-level container you pick when thinking about where tasks live.

​
Lists

A list is a group of tasks on a board. Often a logical grouping of tasks. Tasks belong to a list; lists give structure to the board, allowing you to view and order tasks in a logical way.

​
Tasks

A task is a single unit of work. A card with a title, optional detail, and connections to the board’s organizing dimensions. Everything actionable on the board is ultimately expressed as tasks.

​
Task Groups

Groups segment tasks within the board’s model, e.g. by theme, team, or work type, so you can filter and reason about subsets without splitting the board into many boards. Think of groups as a way to categorize tasks. For example, you may have a list for the CRM Module, it contains tasks to build the CRM Module. Tasks can be categorized into features, bugs, enhancements. Groups are unique to each board. Each board can have any number of groups, not related to other boards. You can filter tasks by group, so you can for example see all the bugs in all task lists, or all enhancements only. Think of Task Groups as Aspects or a second dimension to your task lists.

​
Priorities

Priorities reflect the urgency of a task. You can use the built-in priorities (None, Low, Medium, High, Critical). You can give them custom labels, or colors, but you cannot remove them. Priorities have a weight scale, so you can also create new priorities, and place them in between the built-in priorities.

​
Status

Status is where a task sits in the workflow. A task can be open, in progress, or completed. No custom statuses are supported yet. You can filter tasks by status, for a more focused workflow. There is a special Board View (lanes), where you can see each list grouped by status. In that view, you can drag and drop tasks between statuses, to change their status.

​
Releases

Releases tie tasks to a milestones. You can define releases with names, colors and release dates. You can assign your new tasks automatically to the default release. This is an option for humans, and also for AI agents - if selected. You can filter tasks by release, for a more focused sprint.

​
Access policy

CLI access policy is The CLI Access Control Layer. By default, a user creates a board with no access to the CLI. a red bot icon next to the board name gives you a hint for it. Then he can edit board settings and pick the CLI access policy for that board. By default, CLI can create new boards and use them. This option can be disabled in the Web UI settings. To learn more about CLI access policy, see CLI Access Policy.

​
Profiles

A profile is where the configuration of a Hiro Task Manager instance is defined. Local, remote or server profiles can all coexist on the same machine. A default profile is configured during setup. Other non-default profiles require —profile argument in all CLI commands. If you need to understand the profile config, see Profiles.

​
Application Setup

Hiro Task Manager can be fully installed on the same machine, so the server component that has the Web UI and API lives on the same machine as the CLI that accesses it. This is the default setup as in Quickstart. If the user wishes to have the Web UI on a VPS for online access, an alternative setup lets you install Hiro Task Manager on VPS (server profile), and install the CLI on any machine (client profile). Described in Advanced Setup.

​
Passphrase

This is a password to protect the web UI from unauthorized access. It is set during setup. It doesn’t protect the taskmanager db from direct access through the AI Agent, if it wants to in the standard setup. To protect your db, use the Server/Client setup.

​
CLI API key

By default, during Hiro Task Manager setup, CLI can access local instance without a CLI API key. However, you can require a CLI API key for local access during setup.

​
Trash/Purge/Restore

Deleting boards, lists, or tasks moves them to Trash first; they stay recoverable until permanently deleted. That lifecycle is shared across entity types—conceptually: remove → (optional recovery) → permanent deletion. Details live with the task, board, list, and trash reference pages.