Jakob Wennberg
bcbe9b0903
* feat(assistant): say what the conversation is anchored to agent_conversations.context_ref has been written since the first intents shipped and read by nothing. The panel ignored it, so a thread resumed three days later showed the messages with no indication of which invoice or which bokslut it concerned, even though the row knew. /chat did worse: it printed the ref raw, so the subtitle under someone's own conversation read "invoice:5f3a-9c21-...", a database identifier shown to an accountant. Both surfaces now render the same chip, which names the thing and links to it. This matters more since the panel docks: sitting beside the page, "what is this about" is a question the surface should answer rather than the user's memory. The mapping is a data map in route-mapping.ts, not a switch in a component (plan seam 8.5), so a flow run's ref renders in both surfaces with no change to either. A ref it cannot read renders nothing rather than a broken chip. Two refs deliberately have no link. There is no /transactions/[id] route, so a transaction chip points at the list. The document inbox is an extension mounted under /e/[sector], and core must not hardcode a path that exists only when the extension is enabled, so that one is named without being linked. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(assistant): review triage: make the colon test observable, drop an overclaim The colon-splitting test asserted on a kpi ref, and kpi discards its id, so it passed even with a parser that dropped everything after the second colon. Moved to invoice:abc:2026, where the id reaches the href. Verified by switching indexOf to lastIndexOf and confirming the test fails. ContextChip's comment said a flow run's ref renders with no change to either surface. It does not: an unknown kind maps to null and renders nothing until the map gains an entry. The seam is that adding one is a single entry in one file, which is what the comment now says. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
87 lines
3.1 KiB
TypeScript
87 lines
3.1 KiB
TypeScript
'use client'
|
|
|
|
import { useMemo } from 'react'
|
|
import Link from 'next/link'
|
|
import { ArrowLeft } from 'lucide-react'
|
|
import AgentChat, { attachStagedOperations, normalizeStoredMessages } from './AgentChat'
|
|
import type { StoredStagedOperation } from '@/types'
|
|
import AgentAvatar from './AgentAvatar'
|
|
import ContextChip from './ContextChip'
|
|
import SandboxAgentPreview from './SandboxAgentPreview'
|
|
import { useAgentSheet } from './AgentSheetProvider'
|
|
import { useCompanyOptional } from '@/contexts/CompanyContext'
|
|
|
|
interface Props {
|
|
conversationId: string
|
|
intentId: string
|
|
contextRef: string | null
|
|
title: string
|
|
rawMessages: { role: string; content: unknown; hidden?: boolean }[]
|
|
// Proposals this conversation staged that are still awaiting an answer, so
|
|
// the approval card reappears on resume instead of the proposal silently
|
|
// waiting out its expiry in Granskning.
|
|
stagedOperations?: StoredStagedOperation[]
|
|
}
|
|
|
|
// Full-page conversation view. Wraps AgentChat with a header that shows the
|
|
// title (or intent label). AgentChat handles the streaming + input + render.
|
|
export default function ChatConversationView({
|
|
conversationId,
|
|
intentId,
|
|
contextRef,
|
|
title,
|
|
rawMessages,
|
|
stagedOperations,
|
|
}: Props) {
|
|
const initialMessages = useMemo(
|
|
() => attachStagedOperations(normalizeStoredMessages(rawMessages), stagedOperations ?? []),
|
|
[rawMessages, stagedOperations],
|
|
)
|
|
const { identity } = useAgentSheet()
|
|
const companyCtx = useCompanyOptional()
|
|
const isSandbox = companyCtx?.isSandbox ?? false
|
|
const agentName = identity.displayName?.trim() || null
|
|
|
|
return (
|
|
<>
|
|
<header className="flex items-center gap-3 border-b border-border px-5 py-4 shrink-0">
|
|
{/* Mobile-only back-to-list arrow. On desktop the sidebar is always
|
|
visible so a back button would be redundant. */}
|
|
<Link
|
|
href="/chat"
|
|
className="md:hidden inline-flex h-9 w-9 items-center justify-center rounded-md text-muted-foreground hover:bg-secondary hover:text-foreground transition-colors -ml-1"
|
|
aria-label="Tillbaka till konversationer"
|
|
>
|
|
<ArrowLeft className="h-4 w-4" />
|
|
</Link>
|
|
<AgentAvatar
|
|
avatarId={identity.avatarId}
|
|
size="sm"
|
|
alt={identity.displayName ?? 'Assistent'}
|
|
/>
|
|
<div className="min-w-0">
|
|
<h1 className="font-display text-lg leading-tight tracking-tight truncate">{title}</h1>
|
|
{/* Was printing context_ref raw, so the subtitle read
|
|
"invoice:5f3a-9c21-...": a database identifier, shown to an
|
|
accountant, under the title of their own conversation. */}
|
|
<ContextChip contextRef={contextRef} className="mt-0.5" />
|
|
</div>
|
|
</header>
|
|
|
|
<div className="flex-1 min-h-0 flex flex-col">
|
|
{isSandbox ? (
|
|
<SandboxAgentPreview agentName={agentName} />
|
|
) : (
|
|
<AgentChat
|
|
intentId={intentId}
|
|
contextRef={contextRef ?? undefined}
|
|
initialConversationId={conversationId}
|
|
initialMessages={initialMessages}
|
|
scrollerClassName="px-6 py-8"
|
|
/>
|
|
)}
|
|
</div>
|
|
</>
|
|
)
|
|
}
|