🗺️ Master Copilot Integration Roadmap

## 🗺️ Master Copilot Integration Roadmap

This issue tracks the roadmap and criteria for Elsa Copilot integration. Based on the recent design simplification, here's the updated, focused roadmap. Only requirements reflecting GitHub Copilot SDK integration remain. All provider-agnostic abstractions, registries, custom orchestration engines, and security layers are deemed out of scope.

---

### Roadmap Principles
- **No provider abstraction:** Copilot SDK only. No plans for OpenAI, Azure, etc. Remove all abstraction layers and extension points.
- **Minimal module structure:** All modules are optional, focused, and integrate directly with Elsa Studio and Elsa Server via the Copilot SDK.
- **Security/tenancy:** Use Elsa's built-in auth, tenancy, and audit logging—no custom AI-specific scopes or gates.
- **All code should deliver Copilot-powered chat, diagnostics, and proposal flows only.**

---

### Updated Phases

#### Phase 0: Foundation
- Workbench Solution: [Epic 6](https://github.com/elsa-workflows/elsa-copilot/issues/6)
- Project scaffolding (ASP.NET Core hybrid solution)
- Integrate Elsa Studio BlazorServer Template (pruned of demo/sample code)
- Structure solution for isolated module loading
- Configure Program.cs & DI for hybrid host
- Dockerfile & local debug config
- Documentation: Running, debugging, module integration

#### Phase 1: Copilot Chat API Endpoint
- Implement `POST /copilot/chat`: Create a single chat endpoint in Elsa Server using Copilot SDK, with streaming support.
- Wire up Copilot SDK's native function calling; register Elsa-specific tools/functions directly in SDK.

#### Phase 2: Server-Side Context Resolution
- Feed workflow instance, graph, and history as context to Copilot conversation (for accurate suggestions).
- No context pruning or token management abstractions. Only pass relevant instance state and logs.

#### Phase 3: Blazor Chat UI (Studio Integration)
- Implement floating/dockable chat sidebar in Elsa Studio (Blazor) for real-time AI dialogues.
- Display streaming Copilot responses. Support ephemeral message history.

#### Phase 4: Diagnostics & Failure Explanation
- AI-Assisted diagnostics: Explain workflow failures, root cause analysis, and suggest next actions using Copilot.
- Build snapshot instrumentation to capture workflow state for effective Copilot context.

#### Phase 5: Proposal/Review Flows
- Enable Copilot-generated workflow change proposals.
- Build review/apply UX for proposals. Log merges, reversals, and approvals using Elsa audit trail.

---

### Critical Criteria
- **Sibling Workspace Strategy**: No Git submodules or forked code copies. See `DEVELOPMENT.md`.
- **Extension points**: Only inside Elsa Core/Studio, never in Copilot.
- **All plans, amendments, and stakeholder comments must be tracked in this issue.**

---

### To Do
- [x] Merge PR #47 and close obsolete issues/PRs
- [x] Rewrite or prune all issues referencing provider abstractions, custom AI auth, skill registries, or orchestration engines
- [x] Begin implementation with chat API endpoint (Phase 1)
- [x] Iteratively build Studio chat UI, diagnostics, and proposal flows

---

_View all issues here: https://github.com/elsa-workflows/elsa-copilot/issues_