Catalog describe for any entity (table, view, schema, zone, workspace, pipeline). Routes through the control-plane DESCRIBE endpoint.
/describe <name>## Overview `/describe` is the polymorphic catalog inspector. Given a name, it asks the control plane to identify what the name refers to (table, view, schema, zone, workspace, pipeline, compute node) and returns a detail card tailored to that entity kind. It is the single-verb alternative to typing `/columns`, `/schemas`, `/workspace`, `/pipeline-status`, and friends when you don't know (or care) about the entity type up front. ## Behavior - Calls the catalog `describe` endpoint on the control plane. Requires an authenticated session; fails with an auth error if the cached token cannot be refreshed. - Resolution is name-based. Fully-qualified names (`zone.schema.table`) resolve unambiguously. Partial names resolve against the session's default zone and workspace; if still ambiguous, the card lists the candidates as drill-ins. - The detail card includes a hero summary, quick stats (row count, size, last updated for tables; pipeline state for pipelines), and navigable sections (columns, foreign keys, lineage, recent history). Every section link is a drill-in: `/open N` on a column row calls `/columns`, on a lineage row calls `/describe`, etc. - Does NOT execute SQL. `/describe sales.orders` hits the catalog metadata service; it does not SELECT from the table. - Useful as the second command after `/context` when exploring an unfamiliar environment. ## Compatibility - Names are case-insensitive for the resolver but preserved exactly in the rendered output. - Works with the `entity_ref` form (`table:zone.schema.name`, `pipeline:name`, `workspace:name`) when you want to skip the polymorphic dispatch.
/describe sales.orders/describe landing/describe ws_analytics/describe pipeline:etl_daily