Every chat message already carries the page the operator is on (page: currentPage() in the chat stream request), but the composer never shows it, so "retry this" reads as ambiguous to the operator even when Archie receives the context.
Wanted: a small context tag in the composer naming what the next message is about, for example "Dashboard" or "Task #249", taken from the same value the request sends. The operator can clear it to ask without page context.
Done when the tag always matches the page sent with the message, and clearing it sends no page.
Every chat message already carries the page the operator is on (`page: currentPage()` in the chat stream request), but the composer never shows it, so "retry this" reads as ambiguous to the operator even when Archie receives the context.
Wanted: a small context tag in the composer naming what the next message is about, for example "Dashboard" or "Task #249", taken from the same value the request sends. The operator can clear it to ask without page context.
Done when the tag always matches the page sent with the message, and clearing it sends no page.
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.
Every chat message already carries the page the operator is on (
page: currentPage()in the chat stream request), but the composer never shows it, so "retry this" reads as ambiguous to the operator even when Archie receives the context.Wanted: a small context tag in the composer naming what the next message is about, for example "Dashboard" or "Task #249", taken from the same value the request sends. The operator can clear it to ask without page context.
Done when the tag always matches the page sent with the message, and clearing it sends no page.