You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deterministic deploy recovery will cover the most common, well-understood failure modes, but it will never cover every local Docker and Azure deployment edge case.
After the CLI has:
a stronger deploy-time recovery baseline
Copilot SDK integration
and AI-powered diagnosis with structured deployment context
there should be a preview self-healing workflow that can inspect deployment state, choose from explicit repair tools, apply bounded remediations, and either recover the deployment or stop with precise next steps.
Proposed Solution
Add a preview agentic self-healing deployment workflow built on the GitHub Copilot SDK.
This is not a freeform shell agent. The model should orchestrate a small set of explicit, typed repair tools implemented in Go, with approval boundaries and an audit trail.
Final command naming can be decided during implementation, but the behavior should be the same: inspect -> choose bounded repair -> apply -> retry -> report.
Problem
Deterministic deploy recovery will cover the most common, well-understood failure modes, but it will never cover every local Docker and Azure deployment edge case.
After the CLI has:
there should be a preview self-healing workflow that can inspect deployment state, choose from explicit repair tools, apply bounded remediations, and either recover the deployment or stop with precise next steps.
Proposed Solution
Add a preview agentic self-healing deployment workflow built on the GitHub Copilot SDK.
This is not a freeform shell agent. The model should orchestrate a small set of explicit, typed repair tools implemented in Go, with approval boundaries and an audit trail.
Possible command surfaces:
gh devlake repair gh devlake diagnose --fix gh devlake deploy local --self-heal=previewFinal command naming can be decided during implementation, but the behavior should be the same: inspect -> choose bounded repair -> apply -> retry -> report.
Architecture
Layering
gh devlake diagnose.Repair model
internal/copilot/foundation from Integrate Copilot SDK (Go) —internal/copilotpackage +gh devlake insights#63.Candidate repair tools
These tool names are illustrative, but the important constraint is that each one is:
Safety boundaries
Likely Files
cmd/diagnose.goorcmd/repair.gointernal/copilot/internal/repair/cmd/deploy_local.go/cmd/deploy_azure.goREADME.md/ docsAcceptance Criteria
repairordiagnose --fix).go build ./...,go test ./..., andgo vet ./...pass.Dependencies
Blocked by:
internal/copilotpackage +gh devlake insights#63 — Copilot SDK integration +gh devlake insightsgh devlake diagnose— AI-powered troubleshooting #64 —gh devlake diagnoseTarget Version
v0.4.4 — preview work within the active v0.4.x line once the deterministic recovery and AI diagnosis foundations are in place.
References
internal/copilotpackage +gh devlake insights#63 — Copilot SDK integrationgh devlake diagnose— AI-powered troubleshooting #64 — AI-powered diagnosisinternal/copilot/— future shared SDK/session foundation