# Widgets and dashboard tiles

Gideon can present structured information as a widget and turn saved artifacts into dashboard tiles. Use these surfaces when a table, visual, or interactive view makes the work easier to inspect.

## Inline widgets
When generative UI is enabled, an agent-authored widget can render alongside Markdown through the supported component system. Ask for a specific view of real task data. Check the values and actions it exposes; a polished widget still needs reliable source material.

## Pin an artifact
Enable **Settings → Ambient surfaces → Composable home** when available, then pin an eligible saved artifact. Keep the number of tiles small enough that the important information remains visible.

## Refresh behavior
A tile can have a bound data workflow and a refresh interval. The default tile refresh applies to time-based refreshes; a view-trigger binding can override it. Refresh can cause work to run, so inspect the workflow and access it needs before relying on the tile.

## Adjust the surface
Ambient settings control generative UI, the tile limit, default refresh, and surface-layer ceiling. A lower layer setting can simplify or disable the overlay. Chat settings separately control widget density within answers.

## When something looks stale
Check when the tile last refreshed and whether its bound workflow completed. Refreshing a view is not proof that an unavailable service produced new data. Open the underlying artifact or run to inspect the result.