Support multiple connected Github/Gitlab organizations

[shssoichiro]

Description

For features such as Code Review and Auto-Triage, we would like to support a single Kilo account connecting to multiple Github or Gitlab organizations which they are an admin of.

Use Case

Many users are admins of organizations on Github or Gitlab for a variety of reasons. For example, a user may be a maintainer of an open-source project that they have moved into its own organization, or an organization may have a large number of repos that they have split into multiple Github orgs for organizational reasons. Currently, a Kilo user cannot link these organizations to their account without creating an Organization in Kilo, which is unsuitable especially for the open-source use case, since Kilo organizations have a cost per user, and many users do not need the administrative features of Kilo organizations.

Context

Discord conversation

[Dahgoth]

Re-posting my original message in Discord

Context

I use one Kilo account across multiple GitHub contexts at the same time:

• my personal repos
• repos in orgs I own/manage
• repos in orgs where I’m a member
• repos I collaborate on through my business partner’s setup
• additional service/bot-owned repos

Warning

The issue is that, even though the Kilo GitHub App can be installed in multiple GitHub accounts/orgs simultaneously, Kilo seems to allow only one active connected GitHub installation/context per Kilo account at a time.

This affects all GitHub-connected Kilo features for me, especially:

• Code Reviewer
• Webhooks
• Cloud Agents
• App Builder
• Security Agent
• Auto Triage
• KiloClaw server time usage

Current behavior:

• In the Kilo app, I have to click “Uninstall Apps” to remove the current account connection.
• Then I click “Install App” again.
• GitHub opens, and I select a different personal account/org/installation.
• After that, Kilo only works with repos from that selected context.

Caution

There are no explicit errors, but the visible/usable repo list changes depending on which GitHub entity is currently connected. So the problem is not GitHub App installation itself — it’s that Kilo binds my account to only one active installation/context at a time.

Why this is a problem:

• I need Code Reviewer, Webhooks, and Cloud Agents to work across all relevant repos in parallel.
• Switching contexts breaks normal multi-org and multi-repo workflows.
• It creates a lot of execution friction, which is the main pain point.
• It also indirectly pushes users toward maintaining multiple paid Kilo accounts just to cover repo ownership boundaries, which feels like the wrong workaround.

Note

• This does not seem to be a GitHub limitation.
• Other GitHub Apps I use can operate across all installed orgs/accounts at the same time without this issue.

Expected behavior:

• One Kilo account should be able to use all GitHub App installations already authorized for that user.
• Ideally, Kilo should support multi-installation access with tool-specific behavior, for example:
  • unified access to all allowed repos
  • per-repo Code Reviewer settings and instructions
  • per-project or per-tool installation selection where needed

Tip

• Perplexity GitHub integration works across all repositories the user have access to
• Almost every GitHub App I've been using so far have no issues with it

Can you clarify:

• Is this a known limitation, bug, or current product design?
• Is multi-installation / multi-owner support planned?
• Is there any better workaround than disconnecting and reconnecting the app every time?

Important