Skip to main content
You need a Corvo workspace, access to a GitHub App installation, and permission to configure IAM and a log sink in your Google Cloud project. An admin manages integrations; see Workspace roles.

​
1. Connect a notification channel

Open Integrations and connect Telegram or bind a Discord channel. For Telegram, bind the Agent bot for conversations, then select Connect alerts bot to bind the Notify bot for alerts. A bound Discord channel takes priority for alerts; otherwise Corvo uses the Notify bot, falling back to the Agent bot when needed. Check: Telegram shows the connected chat and alerts destinations, or Discord shows CHANNEL BOUND.
Telegram with Group connected and Alerts group badges

Telegram is ready when both the chat connection and alerts connection appear.

​
2. Prepare GitHub

Open Integrations → GitHub and install the Corvo GitHub App. Select the GitHub account and repositories it may access. Then, under Agent environment:
  1. Select Add repo for each repository Corvo should work in.
  2. Enter a setup command for each repository. It runs from the repository root on a machine with Node, Git, and gh; install any other tools your project needs.
  3. Select Save & build. Wait until the environment shows READY.
The App installation sets the access ceiling. The agent environment selects the repositories Corvo prepares for its runs. See GitHub setup for changes and troubleshooting.

​
3. Connect Google Cloud

Open Integrations → GCP Cloud Logging → Manage. Enter the project ID. Cloud Logging read access is required; choose any optional Cloud Run, Cloud Monitoring, or Cloud Trace read access the agent needs. Follow the six-step wizard:
  1. Enable the listed APIs.
  2. Create or reuse the corvo-agent service account. Do not create a key.
  3. Grant that account the read roles listed in Corvo.
  4. On corvo-agent, open Principals with access and grant the Corvo runtime principal Service Account Token Creator.
  5. Select Bind & Verify and wait for every check to pass.
  6. Choose a minimum severity and at least one Cloud Run, GKE, or Compute Engine source. Create the corvo-alert-sink with the destination and inclusion filter Corvo shows, or use its Script · gcloud mode. Select Connect, then Finish.
The read-access choices in the first screen are separate from the log sources in step 6. Select only the resources whose logs should leave your project. See Google Cloud setup for detailed Console steps. Check: The project shows CONNECTED, alert streaming shows STREAMING, and the active filter matches your chosen sources.

​
4. Follow an investigation

When a matching error arrives, open Investigations. Corvo groups alerts with a shared cause and shows the investigation’s status, alerts, findings, Cloud Logging link, and any recorded PR. A completed investigation may have no PR. See Investigations.