Skip to content

Profiler surface in IDE extension is pilot-ready

Problem

The inspect workstream produces table profiles, column distributions, and schema metadata, but these outputs are not yet reliably rendered inside the VS Code/Cursor extension. The profiler panel either fails to load for certain datasets, shows stale data after re-profiling, or renders loading spinners indefinitely with no error message. Analysts cannot profile tables or inspect column distributions without leaving the editor to use a separate CLI or web interface, which breaks the integrated authoring flow. Error and empty states (permission failures, missing tables, timeout on large datasets) are also unhandled, leading to silent failures that erode trust.

Context

  • Profiler panel loads table profiles, distributions, and comments reliably across pilot datasets.
  • Error/loading states are clear and recoverable without extension restarts.
  • Profiler behavior is validated against known inspect issue deliverables (#281, #282, #386).

Possible Solutions

Plan

  • Integrate latest inspect payload shape and backward-compatible parsing in extension panel.
  • Polish interaction states (loading, empty, permission errors, stale session) for analyst usability.
  • Run end-to-end validation on pilot repos and capture visual regression evidence.
  • Publish short analyst guide for using profiler inside extension.

Implementation Progress

  • inspect-profiler issues #281, #282, #386
  • M1 internal analyst IDE flow task

Review Feedback

  • Review cleared