Depot
Connect
Connect Depot from the terminal. Pass --help for the flags Depot accepts.
praxen integration connect --type depotAn organization API token from Organization Settings → API Tokens in Depot.
Connect your Depot organization with an organization API token.
- In Depot API tokens, create an organization token.
- Paste the token into Praxen Inc. Praxen Inc. checks it and finds the organization and its GitHub connection.
Read Depot data and request API changes through Praxen Inc. Changes require safety review and approval.
Praxen Inc. maps your Depot projects into the context graph and watches GitHub Actions job failure rates and durations on Depot runners.
Depot organization tokens have no scopes. Praxen Inc. uses these Depot APIs:
| Tool | Depot API | What it unlocks |
|---|---|---|
depotGithubActionsJobs | GithubActionsService jobs | Finds failed, slow, and running GitHub Actions jobs on Depot runners. |
depotGithubActionsLogs | GithubActionsService logs | Searches job log lines and reads the lines around a match. |
depotGithubActionsAnalytics | GithubActionsService analytics | Reads failure rates, durations, and runner size recommendations. |
depotCiRuns | CIService | Follows Depot CI runs, their jobs, and their logs. |
depotBuilds | ProjectService, BuildService | Reads container builds, their steps, and step logs. |
depotApi | Any Depot API | Calls the Depot API; calls that change state require safety review and approval. Depot CI secrets and variables are not available. |
Disconnecting leaves the organization API token in Depot. Remove it under Organization Settings → API Tokens in Depot.
Disconnect
Disconnecting stops every sync and check and deletes the credentials Praxen Inc. held. Praxen Inc. removes what Depot's API lets it remove. The following stays until you remove it yourself:
- Depot organization API token
praxen integration disconnect <id>Tools
6Operations agents can perform in threads.