Skip to main content
  • Verify the Asymptote GitHub App is installed on the target repository.
  • Check that webhook deliveries are succeeding under your GitHub App settings → Recent Deliveries.
  • Confirm the ASYMPTOTE_API_KEY secret is set in your repository under Settings → Secrets and variables → Actions.
  • Confirm your ASYMPTOTE_API_KEY secret is correctly set and hasn’t expired.
  • Large pull requests may take a few extra minutes to process.
  • Check the Actions tab in your repository to see if the workflow is running.
Re-install the Asymptote GitHub App and ensure the correct repositories are selected. See the GitHub integration page for a full list of required permissions.
Run asymptote whoami to check your current auth state. If unauthenticated, run asymptote login to re-authenticate. See the CLI authentication docs for more details.
Ensure Asymptote is configured for your agent. See the Coding Agent Integrations docs for setup instructions for your specific tool.
In GitHub: Repository → Settings → GitHub Apps → Asymptote Security, then suspend or uninstall the app.
In GitHub: Organization → Settings → GitHub Apps → Asymptote Security, then suspend or uninstall the app.
Use beacon endpoint hooks uninstall for whichever hook harness you set up:Cursor
Claude Code
Factory Droid
All supported hook integrations
After uninstalling hooks, restart the affected agent or IDE so new sessions pick up the updated hook configuration. See the hook command docs for supported harness names and flags.
For signed macOS package installs, self-update is off by default. Check the configured mode, updater LaunchDaemon state, and local update events:
See Troubleshooting self-update for mode explanations, manual apply, and scheduled updater checks.
Contact us at support@asymptotelabs.ai and we’ll help you get sorted.