starred/aryx
1
0
Fork 0
mirror of https://github.com/davidkaya/aryx.git synced 2026-08-27 05:13:58 +02:00
Code Issues 3 Packages Projects Releases 10 Wiki Activity

docs: mark Copilot connection roadmap progress

Browse Source 
- record shipped Copilot connection diagnostics and settings UI
- split the roadmap item into implemented foundation vs remaining work
- update sequencing and shortlist to focus on the unfinished pieces

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
David Kaya
2026-03-22 15:03:15 +01:00
co-authored by Copilot
parent e97d00e362
commit 5e0167cf1d
1 changed files with 17 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
ROADMAP.md
+17 -10
View File
@@ -27,6 +27,7 @@ Based on the current codebase, Kopaya already has:
- a right-side activity panel that already surfaces per-agent state, model, and effort in `src/renderer/components/ActivityPanel.tsx` - a right-side activity panel that already surfaces per-agent state, model, and effort in `src/renderer/components/ActivityPanel.tsx`
- a pattern editor and settings flow in `src/renderer/components/SettingsPanel.tsx` - a pattern editor and settings flow in `src/renderer/components/SettingsPanel.tsx`
- Copilot CLI-backed runtime access via the system-installed `copilot` command, with Kopaya sanitizing inherited runtime env vars before spawning the sidecar - Copilot CLI-backed runtime access via the system-installed `copilot` command, with Kopaya sanitizing inherited runtime env vars before spawning the sidecar
- refreshable Copilot connection diagnostics and settings UI for `ready`, `copilot-cli-missing`, `copilot-auth-required`, and `copilot-error` states in `src/renderer/components/CopilotStatusCard.tsx`, `src/renderer/components/SettingsPanel.tsx`, `src/main/KopayaAppService.ts`, and `sidecar/src/Kopaya.AgentHost/Services/SidecarProtocolHost.cs`
- an OS secret store wrapper in `src/main/secrets/secretStore.ts` that can support future non-Copilot secrets and integrations - an OS secret store wrapper in `src/main/secrets/secretStore.ts` that can support future non-Copilot secrets and integrations
That is a strong base. The biggest gaps are not around "can it run agents?" but around: That is a strong base. The biggest gaps are not around "can it run agents?" but around:
@@ -73,14 +74,20 @@ These are the improvements users will expect from any serious AI desktop app.
#### Copilot connection and account status management #### Copilot connection and account status management
- a dedicated settings area for Copilot install, login, and connection health Implemented foundation:
- installed / missing / outdated Copilot CLI state
- logged in / expired / broken auth state - [x] a dedicated settings area for Copilot install, login, and connection health
- active GitHub account or organization context when available - [x] installed / missing Copilot CLI state
- test-connection and last-validated status - [x] logged in / auth-required / broken connection state
- clear model availability explanation when a model is unavailable - [x] refresh and last-validated status
- reconnect and troubleshooting actions
- optional per-project or per-pattern account selection later if Kopaya supports multiple Copilot identities Still worth adding:
- [ ] outdated Copilot CLI state
- [ ] active GitHub account or organization context when available
- [ ] clear model availability explanation when a model is unavailable
- [ ] reconnect and troubleshooting actions beyond refresh
- [ ] optional per-project or per-pattern account selection later if Kopaya supports multiple Copilot identities
Because Kopaya currently appears to authenticate through the system-installed Copilot CLI rather than owning provider secrets directly, this should be treated as a connection/account-state UX problem first, not a raw credential-storage problem. Because Kopaya currently appears to authenticate through the system-installed Copilot CLI rather than owning provider secrets directly, this should be treated as a connection/account-state UX problem first, not a raw credential-storage problem.
@@ -399,7 +406,7 @@ The best sequence is not to chase the fanciest orchestration idea first. It is t
Focus on: Focus on:
- Copilot connection and account status management - complete the remaining Copilot connection and account status management work
- conversation search and organization - conversation search and organization
- export/share - export/share
- attachments and artifacts - attachments and artifacts
@@ -442,7 +449,7 @@ Focus on:
If only a handful of roadmap items are chosen next, these would likely create the most user value: If only a handful of roadmap items are chosen next, these would likely create the most user value:
1. Copilot connection and account settings 1. Finish the remaining Copilot connection and account settings work
2. Conversation search, pinning, archive, and export 2. Conversation search, pinning, archive, and export
3. Session forking and branch comparison 3. Session forking and branch comparison
4. Project context controls with git-aware working sets 4. Project context controls with git-aware working sets