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
@@ -36,11 +36,11 @@ That structure keeps the LLM as the native execution chat surface while Copilot
36
36
37
37
## 🎬 Demo
38
38
39
-
[](https://www.youtube.com/watch?v=yiJCmwmxEFc)
39
+
[](https://www.youtube.com/watch?v=yiJCmwmxEFc)
40
40
41
41
Use the feature tour below for the slower tab-by-tab explanation.
42
42
43
-
For the step-by-step walkthrough, open [docs/feature-tour.md](docs/feature-tour.md).
43
+
For the step-by-step walkthrough, open [docs/feature-tour.md](https://github.com/goodguy1963/Copilot-Cockpit/blob/main/docs/feature-tour.md).
44
44
45
45
## 🧠 The Core Loop
46
46
@@ -86,7 +86,7 @@ This is efficient because the `CEO` or orchestrator does the initial thinking on
86
86
87
87
Note: Custom subagents must be enabled in //settings/chat.customAgentInSubagent.enabled of github copilot plugin
88
88
89
-

89
+

90
90
91
91
The optional layer stays practical because responsibilities are split deliberately:
92
92
@@ -95,7 +95,7 @@ The optional layer stays practical because responsibilities are split deliberate
95
95
- Specialists such as `Remediation Implementer` or `Documentation Specialist` run bounded work and report back with validation.
96
96
-`Cockpit Todo Expert` owns durable approval state and backlog hygiene in `Todo Cockpit`.
97
97
98
-
Bundled-agent staging and sync are manual by design. `Stage Bundled Agents` refreshes a comparison copy under `.vscode/copilot-cockpit-support/bundled-agents` without touching the live repo-local system. `Sync Bundled Agents` is the explicit live install path into `.github/agents`. Repo-local agent systems are user-owned, so Copilot Cockpit only offers the starter pack as an optional baseline and does not overwrite customized workspace copies during sync. For the deeper operating model, see [docs/agent-workflow.md](docs/agent-workflow.md).
98
+
Bundled-agent staging and sync are manual by design. `Stage Bundled Agents` refreshes a comparison copy under `.vscode/copilot-cockpit-support/bundled-agents` without touching the live repo-local system. `Sync Bundled Agents` is the explicit live install path into `.github/agents`. Repo-local agent systems are user-owned, so Copilot Cockpit only offers the starter pack as an optional baseline and does not overwrite customized workspace copies during sync. For the deeper operating model, see [docs/agent-workflow.md](https://github.com/goodguy1963/Copilot-Cockpit/blob/main/docs/agent-workflow.md).
99
99
100
100
## ✨ Workflow Layers
101
101
@@ -137,7 +137,7 @@ That also creates a control layer for cost: GitHub Copilot or OpenRouter can use
137
137
138
138
### Settings
139
139
140
-
`Settings` configure workspace defaults, integrations, storage mode, and execution preferences so the cockpit matches the repo you are operating in. They are also where you can optionally incorporate repo-local agents or the bundled starter pack when you want an extra control-plane layer that lets the orchestrator stay focused on routing, planning, and validation while specialists handle bounded work. See [docs/agent-workflow.md](docs/agent-workflow.md) for the operating model.
140
+
`Settings` configure workspace defaults, integrations, storage mode, and execution preferences so the cockpit matches the repo you are operating in. They are also where you can optionally incorporate repo-local agents or the bundled starter pack when you want an extra control-plane layer that lets the orchestrator stay focused on routing, planning, and validation while specialists handle bounded work. See [docs/agent-workflow.md](https://github.com/goodguy1963/Copilot-Cockpit/blob/main/docs/agent-workflow.md) for the operating model.
141
141
142
142
### How To Use
143
143
@@ -206,7 +206,7 @@ The point is not to overclaim autonomy. The point is to show recurring, inspecta
206
206
207
207
The `Settings` tab also lets you choose between `Stage Bundled Agents` for a staged comparison/reference copy under `.vscode/copilot-cockpit-support/bundled-agents` and `Sync Bundled Agents` for live `.github/agents` installation when you want that optional specialist layer. This is useful when the orchestrator should hand work to the right specialist instead of stuffing planning, execution, and review into one long chat. Treat any existing repo-local agent setup as user-owned first. Use stage-first when the repo already has a richer local system, and only approve sync when you want the live install path. Back up `.github` first when it already exists, and keep in mind that customized workspace copies are skipped so your repo-specific agent edits are not overwritten.
208
208
209
-
If you want the rationale and workflow diagram for that pattern, see [docs/agent-workflow.md](docs/agent-workflow.md).
209
+
If you want the rationale and workflow diagram for that pattern, see [docs/agent-workflow.md](https://github.com/goodguy1963/Copilot-Cockpit/blob/main/docs/agent-workflow.md).
210
210
211
211
## 🚦 Release Channels
212
212
@@ -216,24 +216,24 @@ If you want the rationale and workflow diagram for that pattern, see [docs/agent
216
216
217
217
## 📚 Documentation
218
218
219
-
Detailed documentation lives under [docs/index.md](docs/index.md).
219
+
Detailed documentation lives under [docs/index.md](https://github.com/goodguy1963/Copilot-Cockpit/blob/main/docs/index.md).
220
220
221
-
-[Getting Started](docs/getting-started.md)
222
-
-[Feature Tour](docs/feature-tour.md)
223
-
-[Agent Workflow](docs/agent-workflow.md)
224
-
-[Workflows](docs/workflows.md)
225
-
-[Integrations](docs/integrations.md)
226
-
-[Storage and Boundaries](docs/storage-and-boundaries.md)
227
-
-[Architecture and Principles](docs/architecture-and-principles.md)
These extend the core workflow. They are optional and should not be mandatory for onboarding.
233
233
234
234
-`MCP` gives AI agents a controlled tool surface to use the plugin inside the workspace.
235
235
- Support for Copilot-first workflows, with experimental Codex integration for repo-local coordination.
236
-
- Bundled starter agents can be staged under `.vscode/copilot-cockpit-support/bundled-agents` for comparison/reference or synced into `.github/agents` as a small default orchestration layer: `CEO`, `Planner`, `Remediation Implementer`, `Documentation Specialist`, `Custom Agent Foundry`, and `Cockpit Todo Expert`. The pattern is optional, keeps the top-level orchestrator cleaner, and is described in [docs/agent-workflow.md](docs/agent-workflow.md).
236
+
- Bundled starter agents can be staged under `.vscode/copilot-cockpit-support/bundled-agents` for comparison/reference or synced into `.github/agents` as a small default orchestration layer: `CEO`, `Planner`, `Remediation Implementer`, `Documentation Specialist`, `Custom Agent Foundry`, and `Cockpit Todo Expert`. The pattern is optional, keeps the top-level orchestrator cleaner, and is described in [docs/agent-workflow.md](https://github.com/goodguy1963/Copilot-Cockpit/blob/main/docs/agent-workflow.md).
237
237
- Specialized agents, skills, prompts, hooks, memories, and tool connections can be maintained as part of the same controlled workflow.
238
238
- External systems such as email handling, web data collection, price checks, or other connected tools can feed into scheduled work when exposed through MCP or related integration layers.
239
239
- Active review state is carried by canonical workflow flags such as `needs-user-review`, `ready`, `ON-SCHEDULE-LIST`, and `FINAL-USER-CHECK`.
0 commit comments