Who this site is for

This documentation is for anyone using Ticket House at their organization — project managers, developers, team leads, and anyone else involved in managing or contributing to projects. Whether you're setting up your first project, configuring AI agents, or managing tickets day-to-day, these guides are written for you.

Overview

Ticket House is an AI-first ticketing system built on Git. It combines project management with AI agent integration, giving developers and AI agents a shared workspace for tracking and completing work.

Unlike traditional ticketing tools, Ticket House is designed around the idea that AI agents are first-class participants in your development workflow. Agents can read tickets, update statuses, create new issues, and work in isolated environments — all through a standard MCP interface.

Key Concepts

Projects

A project maps to a Git repository. It has a name, a slug (used in URLs), and a ticket prefix (e.g., MA produces ticket IDs like MA-1, MA-2). Projects are registered on the Ticket House server and configured locally via a .ticket-house.json file.

Tickets

Tickets are work items with a title, description, status, priority, tags, and assignee. Descriptions support rich Markdown. Tickets can be linked to epics for grouping related work.

Workstations

A workstation is a local process that connects your repository to a remote Ticket House server. It manages Git worktrees, runs the MCP server for AI agents, and provides a local HTTP interface. You start it with npx ticket-house from your project root.

Worktrees

Each ticket gets its own Git worktree — an isolated branch checkout in .ticket-house/worktrees/. This means multiple tickets can be worked on simultaneously without branch switching or stashing. AI agents work inside these worktrees.

Architecture

Ticket House uses a server + workstation model:

  • Server — hosts the web UI, stores tickets, manages projects, and coordinates work across team members. Runs as a central service.
  • Workstation — runs locally in your repository. Connects to the server, manages worktrees, and exposes MCP tools for AI agents. Started with npx ticket-house.

The workstation communicates with the server over HTTP. When you click "Work Locally" on a ticket in the web UI, the workstation creates a worktree and sets up the environment for that ticket.

Next Steps