Problem
Running agentops cockpit before agentops init produces cascading guidance that is not actionable yet and distracts from the required first step.
When neither APPLICATIONINSIGHTS_CONNECTION_STRING nor AZURE_AI_FOUNDRY_PROJECT_ENDPOINT is configured, preflight warns:
No connection string available; production telemetry will be empty.
Cockpit startup also always prints:
Run agentops doctor in another terminal to populate doctor findings.
The workspace warning already explains that AgentOps has not been initialized and tells the user to run agentops init. App Insights has no telemetry context to inspect, and Doctor cannot produce meaningful workspace findings yet. The Doctor message also exposes an unnecessary terminal-management detail and uses the unclear phrase "populate doctor findings."
Expected behavior
- Continue validating an explicit Application Insights connection string when one is configured.
- Continue attempting Foundry discovery when a project endpoint is configured.
- When neither telemetry source exists, report the Application Insights check as
skip instead of warn.
- Do not print Doctor guidance before the workspace is initialized.
- For an initialized workspace without Doctor results, use:
Run agentops doctor to generate readiness findings, then refresh Cockpit.
- Do not print the Doctor guidance when findings already exist.
- Keep the workspace warning and
agentops init remediation as the primary guidance before initialization.
Acceptance criteria
- A fresh directory without AgentOps or Foundry configuration produces no Application Insights warning.
- The preflight summary counts Application Insights as skipped in that scenario.
- A fresh directory does not show the Doctor guidance.
- An initialized workspace without Doctor results shows the clearer, state-aware guidance.
- An initialized workspace with Doctor results does not show the guidance.
- Invalid explicit connection strings still produce a warning.
- Missing App Insights on a configured Foundry project can still produce an actionable warning.
- Preflight and Cockpit CLI tests cover these cases.
Problem
Running
agentops cockpitbeforeagentops initproduces cascading guidance that is not actionable yet and distracts from the required first step.When neither
APPLICATIONINSIGHTS_CONNECTION_STRINGnorAZURE_AI_FOUNDRY_PROJECT_ENDPOINTis configured, preflight warns:Cockpit startup also always prints:
The workspace warning already explains that AgentOps has not been initialized and tells the user to run
agentops init. App Insights has no telemetry context to inspect, and Doctor cannot produce meaningful workspace findings yet. The Doctor message also exposes an unnecessary terminal-management detail and uses the unclear phrase "populate doctor findings."Expected behavior
skipinstead ofwarn.Run agentops doctor to generate readiness findings, then refresh Cockpit.agentops initremediation as the primary guidance before initialization.Acceptance criteria