GitHub tools `list_user_installations` and `list_app_installations` fail with app installation auth
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github, typescript
- Domain
- api, authentication
Research direction
Start by tracing authenticateApp and the implementations of list_user_installations and list_app_installations, then reproduce both failures with GitHub App installation authentication. Compare each endpoint's required token with the token supplied by the tools; done means an agreed handling for incompatible authentication is implemented and both error cases are covered.
Written by the indexing model from the issue text.
Description
Problem
The list_user_installations and list_app_installations tools fail when using GitHub App installation authentication (the default auth method in scout-agent).
Errors
list_user_installations:
Resource not accessible by integration - https://docs.github.com/rest/apps/installations#list-app-installations-accessible-to-the-user-access-token
list_app_installations:
A JSON web token could not be decoded - https://docs.github.com/rest
Root Cause
These two endpoints require different authentication than what authenticateApp() provides:
| Tool | Endpoint | Required Auth | What we provide |
|---|---|---|---|
list_user_installations |
GET /user/installations |
User access token (OAuth/PAT) | Installation token |
list_app_installations |
GET /app/installations |
App JWT (signed with private key) | Installation token |
When withContext({ appAuth }) is used, the authenticateApp() function exchanges the app JWT for an installation access token. This works for most repository operations, but these two endpoints specifically need different token types.
Suggested Solutions
- Remove these tools from the default toolset when using app auth, since they're not compatible
- Add a separate auth path for
list_app_installationsthat uses the raw JWT instead of exchanging it for an installation token - Document the limitation so users know these tools require user token auth
- Throw a more helpful error when these tools are called with incompatible auth (e.g., "This tool requires a user access token and is not compatible with GitHub App authentication")
Reproduction
- Set up scout-agent with GitHub App auth
- Call either
github_list_user_installationsorgithub_list_app_installations - Observe the errors above
- Dominant language
- TypeScript
- Stars
- 165
- Forks
- 20
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from coder/blink
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Similar issues
-
[Integration]: eRPCOpen
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ava-labs/builders-hub#4826 ·
Maintainers usually reply within 1 day
-
记忆分析的默认模型显示与实际使用不一致Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
anomalyco/opencode#59886 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
a10y a10y-audit ai-driven-qa claude
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day