Integrations

GitHub integration

Connect GitHub to XOROX so AI coding agents can work from GitHub Issues and GitHub Project items, and keep Rulesets in repository files. What is read, what is written, and what is not.

With the GitHub integration, XOROX can use GitHub Issues and GitHub Project items as project work for AI coding agents such as Cursor and Claude Code. GitHub stays the system of record: XOROX reads the work from GitHub when an agent asks for it, and keeps only its own execution state next to it. It does not mirror your GitHub data.

How it works: two levels

Workspace connection

GitHub is connected once per workspace, by a workspace owner or admin, from Integrations in the dashboard. This installs the XOROX GitHub App on your GitHub account or organization and establishes the GitHub access available to XOROX. Manage opens GitHub's own installation settings, where you control which repositories the app can reach.

Connecting at the workspace level does not hand every repository to every project. Each project chooses its own sources.

Project sources

Open a project's Sources tab to choose what that project works from. Two GitHub sources are currently supported, and a project can use either or both:

• Repository · Issues — one repository whose open Issues become work items.
• GitHub Project · Project items — one GitHub Project (the board-style Projects feature) whose items become work items. Items can be Issues from any repository the app can reach, or draft Issues that exist only inside the Project.

An Issue that appears through both sources is one work item, not two. If GitHub isn't connected to the workspace yet, the Sources tab sends you to Integrations first.

How an agent uses GitHub-backed work

Through XOROX's MCP tools, an agent sees GitHub work in the same queue as native XOROX Tasks:

• xorox_list_tasks and xorox_get_next_task include GitHub Issues and Project items. When picking the next task, native XOROX Tasks come first, then GitHub work.
• Open Issues appear automatically. A closed Issue appears only if XOROX was already tracking it, and a closed Issue is never offered as the next task.
• The agent starts a work item, moves it to implementing, and marks it implemented with the same tools it uses for native Tasks.

XOROX execution state is separate from GitHub state

For each GitHub work item XOROX tracks its own execution state — ready, analysing, implementing, implemented — exactly as for native Tasks. This describes where the agent's work stands. It is stored in XOROX and is independent of the Issue's open/closed state and of any status field on your GitHub Project board. XOROX does not map one onto the other.

What XOROX writes to GitHub

The only thing XOROX ever writes to GitHub is an optional comment:

• When an agent marks an Issue-backed work item implemented and supplies a summary, that summary is posted as a comment on the Issue. With no summary, nothing is written.
• Draft Issues in a GitHub Project have no comment thread, so a summary for one is not saved anywhere. The tool's response says whether the summary was posted.

XOROX does not close Issues, change labels or assignees, edit Issue text, or change a GitHub Project's fields or status. There is no two-way synchronization: changes you make in GitHub are read the next time an agent asks, and changes to XOROX execution state are not pushed to GitHub.

Rulesets from repository files

With GitHub connected, a project's Ruleset can be created from a file in a repository — for example AGENTS.md or a docs file. This works for Rulesets only (not Specifications). The document is read-only in XOROX and updates automatically when a push to that branch changes the file; the Refresh button on the document remains as a fallback. Disconnect and keep current text turns it into an ordinary editable Ruleset.

Disconnecting

Disconnect in Integrations removes only XOROX's record of the connection. It does not uninstall the GitHub App, and nothing in GitHub changes — repositories, Issues, and comments XOROX has posted stay as they are. Projects that used the connection can't read GitHub work until it's reconnected.

Related

• Tasks — the execution states and how agents move work through them.
• Notion — another source of Rulesets, Specifications and work.
• Claude Code and Cursor — setting up the coding agent.