The integration work, done and queued for one look
A companion works the 4 operations your Codacy account exposes. It can delete an integration, and every one of those waits on an approval card showing the integration before it changes.
Open the integration. Check it against something else. Write the change. Move to the next one. That is the Codacy afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a integration until you approve it.
What it can do is exactly what Codacy exposes to an account you authorise and nothing beyond it: 4 operations, 3 reads and 1 write. In practice that means it can delete an integration, and work across the integrations, authenticated users and organizations.
The Codacy API stops at Codacy. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Which Codacy integrations does a companion see?
3 of the 4 operations are reads.
Your account, not a guess at it: a companion can list organizations, list integrations and get an authenticated user, and the full list below is the whole list, with nothing inferred from Codacy's documentation.
The integrations are what most of this inventory is about, alongside the authenticated users. A companion can hold all 4 of these operations and forty open tabs in the same pass, which is how an afternoon of Codacy admin becomes a queue you review.
- List Organizations
- List Integrations
- Get Authenticated User
What happens before it can delete integration?
The one write operation there is waits for you.
A companion can delete an integration, and each one is staged on an approval card first: you see the integration, the field and the new value before it lands in Codacy.
Nothing in Codacy is sent, changed or deleted on your behalf without that click, and a rejected card leaves the integration exactly as it was. The gate is the same one on every surface, described at security.
- Delete Integration
Can the integrations pass run every Monday?
Yes.
Saved as a routine, the Codacy integrations pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The product and engineering playbook catalogues the other recurring shapes of the site work, the Codacy integrations sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents