Katia Bulatova
9a3bee0288
Stacked on #4418. Merge that first. The UI slice of the dashboard agent: the side panel, the chat transport wiring, message and card rendering, suggested prompts, and chat history. #4418 works without this — the system is simply invisible. The diff is mostly components, so the notes below cover only the three decisions you can't read off the markup. Behavior and a hands-on walkthrough live in GUIDEBOOK.md, which lands with #4525. ## Decisions worth knowing - **Action rows always render at the end of a turn.** The model's emission order isn't trusted for layout, so action blocks are split out of the stream and appended last. Display only — `answered` stays keyed on the emission index. - **The last-chat memory is org-true.** It's keyed by the chat's own organization, and a foreign or deleted chat comes back as a 404 the client treats as gone, rather than an empty chat it keeps around. - **A dead stream self-heals from the settled transcript.** Terminal records are written to the chat row after the client's stream closes, so the panel re-reads it. The poll gate is any unfinished turn — a dangling tool part, not just an open investigation. ## Notes - Gated by `canAccessDashboardAgent`; no behavior change with the flag off. - Page marks: `handle.agentPageContext` on 47 routes, ~20 lines each. - Entry points: Ask Trigger button, ⌘J, Help & Feedback. The old ⌘I and `?aiHelp=` links keep working. ## Screenshots <img width="1440" height="788" alt="Screenshot 2026-08-07 at 15 14 29" src="https://github.com/user-attachments/assets/f4e89e8d-13ed-4be3-a88d-d5cca3ece0fa" />
27 lines
977 B
TypeScript
27 lines
977 B
TypeScript
import { useLocation, useMatches } from "@remix-run/react";
|
|
import type { AgentPageContext } from "~/components/dashboard-agent/page-context-types";
|
|
import type { Handle } from "~/utils/handle";
|
|
|
|
/**
|
|
* The page context the dashboard agent sees. Routes opt in with `handle = { agentPageContext }`.
|
|
* The deepest mapper that returns something wins; pages with no mapper fall back to the path.
|
|
*/
|
|
export function useAgentPageContext(): AgentPageContext {
|
|
const matches = useMatches();
|
|
const location = useLocation();
|
|
|
|
for (let i = matches.length - 1; i >= 0; i--) {
|
|
const match = matches[i];
|
|
const mapper = (match.handle as Handle | undefined)?.agentPageContext;
|
|
if (typeof mapper !== "function") continue;
|
|
try {
|
|
const context = mapper(match.data);
|
|
if (context) return context;
|
|
} catch {
|
|
// A broken mapper must not take the page down with it.
|
|
}
|
|
}
|
|
|
|
return { page: { kind: "other", path: location.pathname }, signals: [] };
|
|
}
|