Free for open source projects and schools. AI Council costs nothing for OSS maintainers and educational institutions. Apply →

Home / Docs / Tickets

Tickets

Tracker tickets are pulled into project knowledge and re-read when they change. The tracker is read-only: you can't create, edit or close a ticket from Council.

Connecting a tracker

First, set up tracker access: account menu → Ticket Sources. Redmine needs an API access key (My account → API access key). GitHub needs a fine-grained personal access token. A project reads tickets from one tracker: one Redmine server or one GitHub repository.

  1. Open Tickets → Manage sources.
  2. Click + Bind source.
  3. At step 01 TRACKER, choose the tracker and click BIND SOURCE. Tickets appear after the first poll.

Distillation

Each ticket becomes a digest: what kind of ticket it was (an investigation, a code change, a rejection) and a coherent account of what happened. The agent gets the digest instead of reading the tracker, and the What this ticket touched block shows the linked code entities. The distillation model and daily limit are set in Settings → Ticket distillation.

Next: Working in the terminal

Made on
Tilda