You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: agent/README.md
+28-2Lines changed: 28 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,11 @@ The Docker image is built for `linux/arm64` to match AgentCore Runtime requireme
15
15
16
16
### GitHub PAT — Minimal Permissions
17
17
18
-
Create a **fine-grained PAT** at GitHub > Settings > Developer settings > Personal access tokens > Fine-grained tokens.
18
+
Two token types work. Choose based on your access model:
19
+
20
+
#### Fine-grained PAT (recommended for repos you own)
21
+
22
+
Go to GitHub > **Settings** > **Developer settings** > **Fine-grained tokens**.
19
23
20
24
**Repository access**: Select only the specific repo(s) the agent will work on.
21
25
@@ -26,7 +30,29 @@ Create a **fine-grained PAT** at GitHub > Settings > Developer settings > Person
26
30
|**Issues**| Read | Fetch issue title, body, and comments for context |
27
31
|**Metadata**| Read | Granted by default |
28
32
29
-
No other permissions are needed.
33
+
**Limitation:** Fine-grained PATs can only target repos you own or repos in organizations that have opted in to fine-grained token access. If you are a collaborator on someone else's repo (or an org that hasn't enabled the feature), the repo won't appear in the token creation UI.
34
+
35
+
#### Classic PAT (required for collaborator/cross-org access)
36
+
37
+
Use a classic PAT when fine-grained tokens cannot reach the target repository — typically when you are a collaborator on a repo owned by another user or an organization that has not enabled fine-grained token access.
38
+
39
+
Go to GitHub > **Settings** > **Developer settings** > **Personal access tokens** > **Tokens (classic)**.
40
+
41
+
| Scope | Reason |
42
+
|-------|--------|
43
+
|`repo`| Full repository access (clone, push, PRs, issues) |
44
+
|`read:org`| Resolve org membership for org-owned repos |
45
+
46
+
Set an expiration (90 days recommended) and store it in Secrets Manager the same way as a fine-grained token.
47
+
48
+
#### When to use which
49
+
50
+
| Scenario | Token type |
51
+
|----------|-----------|
52
+
| Your own repos or your org has fine-grained enabled | Fine-grained |
53
+
| Collaborator on another user's repo | Classic |
54
+
| Org has not opted in to fine-grained tokens | Classic |
0 commit comments