GitHub Issues as your system of record

GitHub remains the system of record when you use Gitsu. Your issues, labels, milestones and GitHub Projects boards are still the ones your team uses on GitHub. Gitsu reads and edits them through the GitHub API, so adopting the client does not require migrating your team to a second tracker.

What does Gitsu store, and where?

GitHub holds the authoritative issues and projects. Gitsu also processes project data to display boards and produce AI suggestions, and caches responses on your device.

Importing a board selects which GitHub projects Gitsu shows and loads their data into its cache. It does not create a separate Gitsu-owned project. The query cache has a 24-hour restoration limit; that is a cache-use rule, not a promise that every cached file is erased after 24 hours. The privacy policy describes project processing, account records and third-party providers.

How do edits reach GitHub?

As GitHub API calls made with your own token. The desktop app calls GitHub directly for board reads and edits. The Web App sends each request to a Gitsu function, which attaches the token from your signed-in session, forwards the request to GitHub, and passes GitHub's answer back. The proxy processes this data without maintaining a separate issue database. It limits which GitHub endpoints it will call and how often.

Because Gitsu writes as you, an edit made in Gitsu looks on GitHub like an edit you made on github.com. By default, comments an agent posts through Gitsu carry a hidden mark naming the agent, described on agent safety. Starting an agent run does not itself post a GitHub label or comment.

What data do AI suggestions send?

AI priority and milestone suggestions send the current issue's title and a portion of its body, the available choices, and example issue titles with the values previously assigned to them. Gitsu's API sends that request to TypeSafe AI's hosted Jev service. When the issue is eligible for suggestions, the request can start as you open its detail panel; accepting a suggestion is a separate action that writes the selected value to GitHub.

This processing is separate from optional product analytics. TypeSafe's privacy policy describes its treatment of API inputs. It states that inputs are not used to train or fine-tune models, but does not promise immediate deletion of every request. Read that policy if third-party processing is a constraint for your repository. Keeping GitHub as the authoritative store does not mean issue text stays exclusively on GitHub's servers.

Why keep GitHub as the system of record?

Because the team can keep working on the same issues. Pull requests, commits and issues already link to each other in GitHub. A client can edit those records without creating a second tracker that needs a sync. If you stop using Gitsu, your GitHub issues and projects remain available on github.com.

It also changes how a team can adopt a tool. The web board is free, and a paid plan covers only the people on it: Pro covers one person, and a Team plan covers each GitHub user given one of its Seats. One developer on a four-person team can start using Gitsu, and the other three keep working in GitHub as before: they see the same issues, the same board and every change the Gitsu user made. Gitsu's own planning notes put it as "Nobody else on your team has to change anything."

Where does this approach fall short?

• Gitsu can only do what GitHub's API allows. A field GitHub Projects does not have, Gitsu cannot add. Board structure, permissions and automations are still GitHub's.
• Your board is only as fast as GitHub. Gitsu caches responses and updates the screen before GitHub confirms, but a first load of a large board still waits on GitHub.
• Everyone else still uses github.com. Your teammates get Gitsu's speed only if they use Gitsu too. The work is shared; the interface is not.

A tracker that holds its own copy of the data can offer features GitHub does not, at the cost of moving the team's work into it.

Who is this for?

Teams that already run their work in GitHub Issues and Projects and want a better client without a migration, and individual developers who want that client before the rest of the team decides anything. The free Web App covers the boards; the desktop app adds coding agents. The getting started guide walks through signing in and importing your first board.