Skip to main content
Limits change with product version, plan, deployment, and provider. Use the app, CLI --help, connector authorization, and contract as the authoritative source.

​
Visible limit surfaces

​
Operational boundaries

  • A successful connector does not grant every repository or channel.
  • A high confidence score does not replace required checks.
  • A Beta metric can change as the product evolves.
  • Empty analytics may mean missing source coverage.
  • A generated fix is not a safe deployment until reviewed and tested.
  • Projected savings are not guaranteed billing results.
  • A write-capable prompt can affect external systems.

​
When a limit is reached

Capture the exact message, product, scope, current value, requested action, plan, timestamp, and owner. Do not split data, create extra keys, or bypass provider policy without administrator approval.

​
Next step

Use the troubleshooting hub or contact support.