Glossary
The words XLR8 uses, in alphabetical order. Each entry links to the page that explains more.
An AI tool that reads and changes your issues through MCP: a coding agent like Claude Code or Codex with its own API key, or a chat app connected as a connector. Issues an agent creates land in your inbox, and everything it changes shows up in the issue history under the agent’s name. See Connect an agent.
Command menu
Section titled “Command menu”The searchable list of every action, opened with Ctrl K (⌘ K on a Mac). Type a few letters of what you want to do, a value such as a status name, or an issue identifier. See Keyboard shortcuts.
Connector
Section titled “Connector”A chat app, claude.ai or ChatGPT, connected to XLR8 by signing in rather than with an API key. You start the connection under Settings → Agents → Connect connector and approve it on the XLR8 consent page. A connector counts as an agent.
Dormant team
Section titled “Dormant team”A team you are not actively working in. It moves to the Inactive section of the sidebar and is left out of sprint planning. Its issues stay as they are. See Teams.
Identifier
Section titled “Identifier”The short, readable ID of an issue: the team key, a hyphen and a number, such as ACME-42. Numbers count up per team. You can search for an identifier, and agents use it to refer to issues.
The place where issues created by agents wait for you, and issues shared to XLR8 from other apps on your phone. An entry stays until you remove it; removing it takes it out of the inbox but leaves the issue unchanged. Entries you have opened count as read.
Instance
Section titled “Instance”One installation of XLR8: its own Convex backend, its own Clerk sign-in and its own web address. Every instance belongs to exactly one owner. See Self-hosting.
Knowledge page
Section titled “Knowledge page”A page in a team’s knowledge area: notes and documentation written in Markdown, arranged in a tree and linked with issues. A team can have knowledge pages alongside its issues, or be a knowledge-only team without issues.
Label group
Section titled “Label group”A set of related labels, such as “Type” with Bug and Feature. A group can be single choice, so an issue carries at most one label from it. See Labels.
The Model Context Protocol, an open standard that lets AI tools call functions in other programs. XLR8’s backend offers an MCP endpoint with tools such as search_issues, create_issues and set_status. Agents use it to work with your issues.
The one person who can sign in to an instance. The backend only lets in the Clerk accounts listed in the XLR8_OWNER_IDS setting. There are no other user accounts; agents get access through keys or connectors that the owner creates.
A floating preview of the focused issue in a list, without leaving the list. Press Space to open or close it; hold Space and it closes again when you let go.
Project
Section titled “Project”A larger piece of work that groups issues, such as a release or a feature. Every project belongs to exactly one team and has a status: planned, active, paused and so on.
Sprint
Section titled “Sprint”A fixed stretch of time with a set of issues you plan to finish. XLR8 runs one sprint at a time, and it spans all teams: you plan it, start it, and complete it, deciding what happens with unfinished issues.
Team key
Section titled “Team key”The 2 to 6 capital letters and digits that start every identifier of a team, such as ACME. It can only be changed while the team has no issues, so identifiers stay stable.
Triage
Section titled “Triage”The status for incoming issues that you have not reviewed yet. Issues created by agents start in triage if the team has a triage status. From there you accept an issue (and choose its status), mark it as a duplicate, or decline it.