9cb1d105e3
* fix(agent): hide Anthropic-only assistant surfaces where the provider cannot run them Self-hosted deployments on an OpenAI-compatible provider (or with no AI configured) still showed every entry point into the tool-loop runtime behind /api/agent/invoke, which answers 503 there. The capability lived server-side only (getAiStatus().assistantAvailable); no UI could read it. Hand the flag to the client through CompanyContext (useAssistantAvailable, beside the paid-capability gate) and gate each entry point that opens AgentChat: the bookkeeping page's "Skapa med assistent" and "Med assistenten", the inbox workspace's "Fråga assistenten" doors, /chat/intake and /chat/new?intent=. The floating trigger falls back to general help (the single-call console runs on any provider) instead of hiding, and AgentChat itself never fires an invoke without the runtime, so a resumed thread or a forgotten entry point shows a notice instead of a 503. The Hem checklist's "Anslut till Claude" step renders only where the assistant runs on Claude and the mcp-server extension is on. Provider-agnostic AI (ask console, categorization, extraction) and the server-side 503 are unchanged; on hosted the flag is true and nothing changes. Closes #2204 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019SaJfqNi4VmsG8FMKq99G6 * test(ai): use a placeholder that cannot match an Anthropic key shape The new direct-Anthropic status test assigned a string in the exact format of a live API key, which trips secret scanners on every run. The config only reads presence, so any non-empty string exercises the path. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> --------- Co-authored-by: Jakob Wennberg <311770904+jakobwennberg-oss@users.noreply.github.com> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
29 lines
1.2 KiB
TypeScript
29 lines
1.2 KiB
TypeScript
import { redirect } from 'next/navigation'
|
|
import ChatIntakeStarter from '@/components/agent/ChatIntakeStarter'
|
|
import { getAiStatus } from '@/lib/ai'
|
|
import { getDashboardAuthContext, getDashboardCompanyId } from '../../request-context'
|
|
|
|
export const dynamic = 'force-dynamic'
|
|
|
|
// /chat/intake: Phase C bootstrap surface. ReviewCard navigates here after
|
|
// Phase B "kör" succeeds. The client component mounts AgentChat with
|
|
// intent='onboarding.intake' in fresh-start mode; AgentChat auto-fires the
|
|
// first invoke which creates the conversation row, and we swap the URL to
|
|
// /chat/[id] when the new id streams back.
|
|
//
|
|
// Plan ref: dev_docs/specialized-agent-plan.md §7 Phase C.
|
|
export default async function ChatIntakePage() {
|
|
const [{ user }, companyId] = await Promise.all([
|
|
getDashboardAuthContext(),
|
|
getDashboardCompanyId(),
|
|
])
|
|
if (!user) redirect('/login')
|
|
if (!companyId) redirect('/onboarding')
|
|
// onboarding.intake runs on the tool-loop runtime; without it (#2204) the
|
|
// starter would fire an invoke that answers 503. The agent is built by now,
|
|
// so the general-help console on /chat is the working next step.
|
|
if (!getAiStatus().assistantAvailable) redirect('/chat')
|
|
|
|
return <ChatIntakeStarter />
|
|
}
|