# no-tickets

> Ticketless project management for AI teams — docs, CLI reference, API reference, MCP tools, and integration guides.

## Docs

- [no-tickets](https://docs.no-tickets.com/introduction.md): Ticketless project management for AI teams.
- [Install the CLI](https://docs.no-tickets.com/getting-started/install.md): Install the no-tickets binary on macOS, Linux, or Windows.
- [Your first push](https://docs.no-tickets.com/getting-started/first-push.md): Send your first event to no-tickets and watch it land on the board.
- [Dashboard tour](https://docs.no-tickets.com/getting-started/dashboard-tour.md): What each page of the no-tickets dashboard surfaces, and when you'd use it.
- [Markdown format](https://docs.no-tickets.com/markdown-format/overview.md): The open spec for describing work in any repository — epics, features, fixes, frontmatter, and tasks.
- [Epics](https://docs.no-tickets.com/markdown-format/epics.md): Epic file format — frontmatter and section structure.
- [Features](https://docs.no-tickets.com/markdown-format/features.md): Feature file format — frontmatter, sections, and the task list contract.
- [Fixes](https://docs.no-tickets.com/markdown-format/fixes.md): Fix file format — bug tracking with reproduction steps, severity, and the same task contract as features.
- [Frontmatter](https://docs.no-tickets.com/markdown-format/frontmatter.md): Exhaustive field reference for every YAML frontmatter field on epics, features, and fixes.
- [Task syntax](https://docs.no-tickets.com/markdown-format/task-syntax.md): How the `## Tasks` section parses — heading shape, status line, and what counts as progress.
- [Concepts](https://docs.no-tickets.com/concepts/overview.md): The mental model behind no-tickets — phases, push origins, entitlements, roles, epics.
- [Phases](https://docs.no-tickets.com/concepts/phases.md): The five-state lifecycle every feature and fix moves through: ideation, development, testing, review, done.
- [Push origins](https://docs.no-tickets.com/concepts/push-origins.md): Where a push came from — CLI, CI, MCP, or dashboard — and why the source matters.
- [Entitlements](https://docs.no-tickets.com/concepts/entitlements.md): What your plan unlocks — projects, push volume, agent seats, history retention.
- [Roles](https://docs.no-tickets.com/concepts/roles.md): Humans, agents, and what each can do — team membership and per-project assignments.
- [Epics](https://docs.no-tickets.com/concepts/epics.md): How features and fixes are grouped into a body of work with a shared goal.
- [Integration guides](https://docs.no-tickets.com/integration-guides/overview.md): Wire no-tickets into your CI pipeline, PR workflow, or AI agent.
- [GitHub Actions](https://docs.no-tickets.com/integration-guides/github-actions.md): Push your .tiny-brain/ state on every commit using the official no-tickets GitHub Action.
- [Generic CI](https://docs.no-tickets.com/integration-guides/generic-ci.md): Push .tiny-brain/ state from any CI system using the no-tickets CLI.
- [PR workflows](https://docs.no-tickets.com/integration-guides/pr-workflows.md): Drive phase transitions from pull-request lifecycle events.
- [Agent SDKs](https://docs.no-tickets.com/integration-guides/agent-sdks.md): Let LLM agents read and write your .tiny-brain/ spec — Claude Agent SDK, custom MCP clients.
- [Troubleshooting](https://docs.no-tickets.com/troubleshooting/overview.md): Where to look first when something goes wrong.
- [Common errors](https://docs.no-tickets.com/troubleshooting/common-errors.md): HTTP error codes and CLI failure modes, with recovery steps.
- [FAQ](https://docs.no-tickets.com/faq/overview.md): Common questions about no-tickets, tiny-brain, and how they work together.
- [Pricing](https://docs.no-tickets.com/faq/pricing.md): What no-tickets costs and what each plan includes.
- [Data retention](https://docs.no-tickets.com/faq/data-retention.md): How long no-tickets keeps the event history on each plan.
- [Privacy](https://docs.no-tickets.com/faq/privacy.md): What no-tickets stores and what it never sees.
- [CLI reference](https://docs.no-tickets.com/cli-reference/overview.md): Every no-tickets subcommand, flags, examples.
- [init](https://docs.no-tickets.com/cli-reference/commands/init.md): Authenticate via the browser and save session credentials
- [logout](https://docs.no-tickets.com/cli-reference/commands/logout.md): Delete local session credentials. Symmetric with `init`
- [session](https://docs.no-tickets.com/cli-reference/commands/session.md): Declare an agent-harness identity for opt-in actor attribution
- [status](https://docs.no-tickets.com/cli-reference/commands/status.md): Print authentication and locally-registered push tokens as JSON
- [token](https://docs.no-tickets.com/cli-reference/commands/token.md): Manage locally-registered push tokens (paste from the web UI)
- [update](https://docs.no-tickets.com/cli-reference/commands/update.md): Update the no-tickets binary (install.sh / direct-download installs only)
- [validate](https://docs.no-tickets.com/cli-reference/commands/validate.md): Validate a payload locally against the bundled JSON Schema for the given event type. No auth, no network
- [REST API reference](https://docs.no-tickets.com/api-reference/overview.md): Programmatic access to no-tickets — push specs, read activity, manage projects.
- [Liveness probe](https://docs.no-tickets.com/api-reference/endpoints/system/liveness-probe.md): Returns 200 with `{ status: "ok" }` when the server is accepting traffic.
- [Join the early-access waitlist](https://docs.no-tickets.com/api-reference/endpoints/waitlist/join-the-early-access-waitlist.md): Submit an email address to join the no-tickets early-access waitlist. Emails are normalised (lower-cased + trimmed) before storage.
- [Current user, organisation, permissions, team, and projects](https://docs.no-tickets.com/api-reference/endpoints/auth/current-user-organisation-permissions-team-and-projects.md): Returns the authenticated session bundle: user profile (from Kinde or mock), organisation, permissions, team id resolved from the Kinde orgCode, and the projects the team owns. `devMode: true` + a top-level `role` indicate the mock-auth branch and are only emitted in non-production environments.
- [List projects in the caller’s org](https://docs.no-tickets.com/api-reference/endpoints/projects/list-projects-in-the-caller’s-org.md): Returns every project owned by the team resolved from the session cookie orgCode, ordered by createdAt desc. Empty array if the caller has no team.
- [Create a project](https://docs.no-tickets.com/api-reference/endpoints/projects/create-a-project.md): Create a project in the caller’s team. Names are case-insensitively unique within a team — duplicates 409. (No DB-level UNIQUE index yet, so a true concurrent race could still collide; see the handler comment.)
- [Delete a project](https://docs.no-tickets.com/api-reference/endpoints/projects/delete-a-project.md): Requires the manage:projects permission on the caller’s session.
- [Update a project](https://docs.no-tickets.com/api-reference/endpoints/projects/update-a-project.md): Partial update — any combination of name, description, status. Returns the updated row.
- [Cross-domain project feed](https://docs.no-tickets.com/api-reference/endpoints/projects/cross-domain-project-feed.md): Most-recent events for the project across every domain (product, ai, scm, support, …). Use `?domain=` to narrow to a single space.
- [MCP tools](https://docs.no-tickets.com/mcp-tools/overview.md): MCP server tool list, schemas, and example invocations.
- [Changelog](https://docs.no-tickets.com/changelog/overview.md): Product updates and improvements to no-tickets.

## OpenAPI Specs

- [openapi](https://docs.no-tickets.com/api-reference/openapi.json)

## Optional

- [Marketing site](https://no-tickets.com)
- [Dashboard](https://app.no-tickets.com)
- [GitHub](https://github.com/magic-ingredients/no-tickets)