HTB

TERMINAL-FIRST ISSUE TRACKING

Keep work moving,
without leaving your terminal.

The team tracks stories and technical tasks in the CLI. Clients see published stories, their progress, and the conversation—not the technical breakdown.

Download HTB See a workflow
~/work
$ htb project create --key SITE --name "Website"
Project SITE created. It is now current.
$ htb ticket create --title "Ship the new homepage"
Created SITE-1 · user_story · open
$ htb ticket publish SITE-1
01

Built for commands

Your workflow stays keyboard-first. The CLI is readable for humans and offers JSON and CSV for automation.

02

Useful structure

Stories, technical tasks, bugs, incidents, roadmap features, comments, and revision history live in one small model.

03

Shared without the noise

Invite the right people. Keep project permissions explicit and let every change remain traceable.

A CONCRETE WORKFLOW

Turn a delivery into
a sequence your team can trust.

Start a project, describe the user story, split its technical work, then let the story progress follow its tasks.

  1. htb project create --key API --name "Public API"
  2. htb ticket create --type user_story --title "Let clients export data"
  3. htb ticket create --type technical_task --parent API-1 --title "Add CSV endpoint"

NOT ANOTHER KANBAN

HTB is the ticket layer your terminal can speak.

Traditional ticket tools begin with boards and browser workflows. HTB begins with an API and a CLI: quicker for focused work, scriptable for recurring work, and legible to coding agents.

Read the complete command guide

YOUR CHOICE

Use our server or run your own.

Hosted by Ben-to

Connect to htboard.xyz. We run the service; you use the CLI and invite clients to the portal.

htb config set-server https://htboard.xyzOpen the client portal

Self-host HTB

Run HTB on your server and keep control of its data. The setup guide covers the database, sign-in, and HTTPS.

Read the setup guide

INTERACTIVE PREVIEW

See a workday,
not just commands.

Explore four project moments. This local simulation does not create an account, contact the API, or save anything.

~/website
$ htb ticket create --title "Publish pricing"
Ticket SITE-12 created — open.

$ htb ticket create --type technical_task \
  --parent SITE-12 --title "Add comparison table"
Ticket SITE-13 created — open.

A story and its technical work stay connected from the first command.