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
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ copilot-cost install
32
32
33
33
Then **restart your shell and restart `copilot`**. That's it.
34
34
35
-
The installer configures the Copilot CLI statusline, appends an idempotent OpenTelemetry block to your shell profile, and enables local JSONL span output under `~/.copilot/otel/`. It does **not** start the dashboard.
35
+
The installer configures the Copilot CLI statusline (including the required `"experimental": true` flag in `~/.copilot/settings.json` — the GitHub Copilot CLI gates custom status lines behind that flag), appends an idempotent OpenTelemetry block to your shell profile, and enables local JSONL span output under `~/.copilot/otel/`. It does **not** start the dashboard.
36
36
37
37
Prefer to edit your shell profile yourself? Run `copilot-cost install --no-otel-profile` — the OpenTelemetry block is printed for manual setup.
38
38
@@ -142,7 +142,7 @@ More on the underlying telemetry pipeline: [Copilot OpenTelemetry observability]
142
142
143
143
## 🩺 Troubleshooting
144
144
145
-
-**The statusline does not appear.** Run `copilot-cost doctor`, then confirm the Copilot CLI was restarted after install.
145
+
-**The statusline does not appear.** Run `copilot-cost doctor`. The custom statusline requires `"experimental": true` in `~/.copilot/settings.json` — without it the GitHub Copilot CLI ignores the `statusLine` block entirely (its logs show `STATUS_LINE: false`). Re-running `copilot-cost install` sets both keys; then restart Copilot CLI.
146
146
-**No usage shows up yet.** Make sure you're on the latest Copilot CLI, restart your shell and `copilot`, send a prompt, then check for JSONL files in `~/.copilot/otel/`.
147
147
-**I do not want profile edits.** Use `copilot-cost install --no-otel-profile` and paste the printed OpenTelemetry block into the shell profile you choose.
148
148
-**The dashboard will not bind.** Use a local host only, e.g. `copilot-cost dashboard --host 127.0.0.1 --port 4567`.
if(!okLine("settings experimental",experimentalEnabled,experimentalEnabled ? `${paths.settingsPath} has \"experimental\": true (required for custom statusLine)` : `${paths.settingsPath} is missing \"experimental\": true; the Copilot CLI ignores statusLine without it. Re-run 'copilot-cost install' or set it manually.`))failed=true;
okLine("shell restart",envEnabled,envEnabled ? "current shell has COPILOT_OTEL_* file exporter variables" : "restart your shell and Copilot CLI so COPILOT_OTEL_* variables take effect",false);
`Copilot CLI feature flag STATUS_LINE=false in ${statusLineFlag.logFile??copilotLogsDir(paths.home)}. The CLI gates the custom statusLine behind \"experimental\": true in ${paths.settingsPath}. Ensure that flag is set, then restart Copilot CLI.`,
317
+
false,
318
+
);
319
+
}else{
320
+
okLine(
321
+
"copilot statusline feature",
322
+
true,
323
+
statusLineFlag.state==="enabled" ? "Copilot CLI feature flag STATUS_LINE=true" : "Copilot CLI feature flag STATUS_LINE not observed yet; start Copilot CLI once to populate logs",
0 commit comments