The chat dock's suggested prompts come from a fixed list per page type in ui/src/chat/suggestions.ts (tasks, workflows, schedules, settings, default). They don't reflect what is actually on the page: the workflows that exist, the run that just failed, the task open in front of the operator. They read as canned.
They now hide while no chat model is connected, so a prompt can't be sent only to fail.
Wanted
Prompts derived from the page's real state, for example by asking the configured chat model for a few short questions given the page context the composer already sends, with the static list removed rather than kept as a fallback.
Done when
On a page with real data, the prompts name that data (a workflow, a run, a task), not generic questions.
No prompts show while no chat model is connected.
ui/src/chat/suggestions.ts's hard-coded lists are gone.
## What is wrong
The chat dock's suggested prompts come from a fixed list per page type in `ui/src/chat/suggestions.ts` (tasks, workflows, schedules, settings, default). They don't reflect what is actually on the page: the workflows that exist, the run that just failed, the task open in front of the operator. They read as canned.
They now hide while no chat model is connected, so a prompt can't be sent only to fail.
## Wanted
Prompts derived from the page's real state, for example by asking the configured chat model for a few short questions given the page context the composer already sends, with the static list removed rather than kept as a fallback.
## Done when
- On a page with real data, the prompts name that data (a workflow, a run, a task), not generic questions.
- No prompts show while no chat model is connected.
- `ui/src/chat/suggestions.ts`'s hard-coded lists are gone.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What is wrong
The chat dock's suggested prompts come from a fixed list per page type in
ui/src/chat/suggestions.ts(tasks, workflows, schedules, settings, default). They don't reflect what is actually on the page: the workflows that exist, the run that just failed, the task open in front of the operator. They read as canned.They now hide while no chat model is connected, so a prompt can't be sent only to fail.
Wanted
Prompts derived from the page's real state, for example by asking the configured chat model for a few short questions given the page context the composer already sends, with the static list removed rather than kept as a fallback.
Done when
ui/src/chat/suggestions.ts's hard-coded lists are gone.Superseded by #1974, which generates suggestions from the conversation.