Hey, thanks for the detailed report. Answering the two parts separately:
- Repository access denied loop. This looks a lot like a case from a nearby thread: Cloud automation cannot authenticate with GitHub despite permissions granted. What helped there was this sequence:
- Open Settings → Integrations, disconnect GitHub
- Go to Sign in to GitHub · GitHub and make sure the Cursor GitHub App has access to the right repo. If the repo is in an org, make sure an org admin allowed access
- Reconnect GitHub in Cursor
- Delete and recreate the automation in Slack. Important: don’t edit the existing one, recreate it so it picks up fresh auth
If the repo is in a GitHub org and you’re not an org admin, that’s a separate known case. Let me know and we can check repo visibility for non-admins.
Also agree that the agent going into a retry loop instead of failing with a clear error like “reconnect GitHub” is bad UX.
- Reading older Slack messages. Right now the agent’s Slack tool only reads recent messages in a channel or thread, with a limit up to 100, and no date range params or
oldest. So it can’t summarize patterns from a week or a month of history yet. This is a known limitation.
If it’s still looping after reconnect and recreate, please share the automation run ID (or a link to the specific run) and whether the repo is personal or org-owned, and we’ll dig deeper.