mirror of
https://github.com/multica-ai/multica.git
synced 2026-07-29 14:37:44 +02:00
7d2f20f2ee
Chat project context (MUL-5150, #5765) is rendered into the run brief by the daemon, so daemons older than the release that ships it silently drop the project description while still honoring the server-extracted repos. Mirror the handoff-note soft gate: resolve the active agent's runtime cli_version from the warm runtime cache and, when it is a stale release build, surface a warning next to the composer chip and inside the project submenu. Selection is never blocked — dev-describe builds and unknown runtimes stay silent. Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
31 lines
1.2 KiB
TypeScript
31 lines
1.2 KiB
TypeScript
"use client";
|
|
|
|
import { useQuery } from "@tanstack/react-query";
|
|
import {
|
|
runtimeListOptions,
|
|
readRuntimeCliVersion,
|
|
chatProjectContextSupported,
|
|
} from "@multica/core/runtimes";
|
|
|
|
/**
|
|
* Whether the active agent's daemon is new enough to inject a chat session's
|
|
* project description into the run brief. `null` means "cannot tell" (no
|
|
* agent, no bound runtime, or the runtime row not in cache yet) and must NOT
|
|
* warn: this is a soft gate, and a spurious warning is worse than a
|
|
* description an old daemon drops — same policy as the handoff note gate in
|
|
* run-confirm.
|
|
*
|
|
* Shared by both send chains (chat tab controller and floating ChatWindow) so
|
|
* the resolution rule cannot drift between the two surfaces.
|
|
*/
|
|
export function useChatProjectContextSupport(
|
|
wsId: string,
|
|
agent: { runtime_id?: string | null } | null | undefined,
|
|
): boolean | null {
|
|
const { data: runtimes = [] } = useQuery({ ...runtimeListOptions(wsId), enabled: !!wsId });
|
|
if (!agent?.runtime_id) return null;
|
|
const runtime = runtimes.find((r) => r.id === agent.runtime_id);
|
|
if (!runtime) return null;
|
|
return chatProjectContextSupported(readRuntimeCliVersion(runtime.metadata));
|
|
}
|