OpenCode: Response and recovery
Expanded web report · Related PDF snapshot: 22 October 2026 · PDF page 8
Research reviewed 22 October 2026 · Evidence and editorial planning guidance are distinguished below.
Start with the incident-specific sequence
For suspected exposure, use a clean provider account session to follow current vendor guidance on revocation and account review. Preserve relevant usage and billing evidence without copying secret values into tickets.
Use the current primary guidance and the accountable incident lead to resolve sequencing conflicts. Coordinate parallel teams before changing shared identities or destroying evidence. Urgent containment may need to proceed before every record is collected, but the decision and evidence lost should be documented.
Restore a trusted operating path
Reconnect only through a reviewed integration with a distinct, narrowly scoped credential where supported. Establish separate ownership for the console configuration and upstream account spending.
- Plan reconnection with distinct credentials and review available usage controls.
- Test the replacement on a scoped workload and check the corresponding provider usage record.
- Identify projects blocked by the affected model access and prioritise the necessary fallback.
Verify before resuming
Confirm the retired credential no longer works, the replacement has the intended scope, and unusual usage can be detected in the authoritative provider account.
Ask the operational owner to exercise the essential workflow, including background tasks and customer exceptions. Keep a short record of what passed, what failed and what remains untested. Define who may accept an exception and when it must be revisited; an exception should not disappear into a general restoration announcement.
A scenario to rehearse
Illustrative exercise, not an observed customer incident: A development team removes a key from a coding tool but leaves the same key active at its provider. The exercise tests whether the team recognises that removing a local configuration entry is not revocation.
Keep customers informed
Direct account-specific AI billing questions to the designated account owner.
An approved service-impact message with a named escalation route for billing or privacy questions.
Restart decision
Restore the integration when its owner accepts the current vendor guidance and the business can observe and limit the new credential’s use.
After stabilization, review which shared dependency allowed the exposure to spread or slowed recovery. Choose a measurable improvement and an accountable owner. A new platform is useful only when its responsibilities, evidence and recovery path fit the business requirement.