GitHub

Splitkick talks to GitHub through the gh CLI. Sign in once with gh auth login; Splitkick uses that login and stores no token of its own.

What you get

• Dashboard per project with Issues, Pull Requests, Security alerts and Advisories.
• Investigate an issue: hand an issue to an agent in a worktree; it gets the issue text as context.
• PR as worktree: check out a pull request into its own worktree to review or continue it.
• Actions: when a workflow fails, let an agent investigate the run.
• Dependabot and security alerts: hand an alert to an agent.
• Auto-archive: a worktree whose PR was merged can archive itself. It waits while a session runs or waits for your input, and while the worktree has uncommitted changes. When the worktree has moved on to a new branch, it follows that branch instead.

Also

In a project with an upstream remote (a fork), the lists come from the repository of the origin remote, so you see the fork's issues and pull requests. A default repository set with gh repo set-default still wins.

Linear and Sentry issues can be loaded as agent context in the same way; the keys for them are stored in Settings in plain text today (see 1Password).

Other git hosts (Forgejo, Gitea, GitLab) have no dashboard, but every git operation works with them: Forgejo and Gitea.