The open-source agent harness - the runtime layer that turns an LLM into a working agent.
docs cleanup (#202)
qaifi-tf39691bc006ba
diff --git a/docs/docs.json b/docs/docs.jsonindex 03e14b2c3..59d7f6135 100644--- a/docs/docs.json+++ b/docs/docs.json@@ -94,10 +94,7 @@"ui-sdk/guides/layouts","ui-sdk/guides/layouts-and-theme","ui-sdk/guides/agent-modes",- {- "group": "Setup Custom UI",- "pages": ["ui-sdk/setup-custom-ui/custom-theme", "ui-sdk/setup-custom-ui/custom-layout"]- },+ "ui-sdk/setup-custom-ui/custom-theme",{"group": "Setup Custom Server","pages": [diff --git a/docs/ui-sdk/get-started/installation.mdx b/docs/ui-sdk/get-started/installation.mdxdeleted file mode 100644index 338090d22..000000000--- a/docs/ui-sdk/get-started/installation.mdx+++ /dev/null@@ -1,78 +0,0 @@-----title: "Installation"-description: "Install the SDK, import the stylesheet, and satisfy peer dependencies."-hidden: true------## Install--<CodeGroup>--```bash npm-npm install @truefoundry/trueforge-ui-```--```bash pnpm-pnpm add @truefoundry/trueforge-ui-```--```bash yarn-yarn add @truefoundry/trueforge-ui-```--</CodeGroup>--`react` and `react-dom` are required peer dependencies and must be version 18 or 19. `@assistant-ui/core`, `@assistant-ui/react`, and `@types/react` are optional peers, you need to install them yourself only if you use their APIs directly or need to pin a version.--Next: [Quickstart](/ui-sdk/get-started/quickstart).--## FAQs--<AccordionGroup>- <Accordion title="Error: requires an AuiProvider">- Deduplicate the assistant-ui singletons `react`, `react-dom`, `@assistant-ui/core`, `@assistant-ui/react`, and `@assistant-ui/store` must each resolve to exactly one copy in your bundle. Two copies produce a runtime error along the lines of _"requires an AuiProvider"_.-- <CodeGroup>-- ```ts vite.config.ts- export default defineConfig({- resolve: {- dedupe: [- "react",- "react-dom",- "@assistant-ui/core",- "@assistant-ui/react",- "@assistant-ui/store",- ],- },- });- ```-- ```json package.json- {- "resolutions": {- "@assistant-ui/core": "<version>",- "@assistant-ui/store": "<version>"- }- }- ```-- </CodeGroup>-- The `vite.config.ts` approach is usually enough. Reach for `resolutions` (or `overrides` on npm, `pnpm.overrides` on pnpm) when a transitive dependency drags in a second copy.-- Note that `@assistant-ui/store` arrives transitively through `@assistant-ui/core` rather than being declared by the SDK, so there is no published version to look up — pin it to whatever your lockfile resolves `@assistant-ui/core` against.- </Accordion>-- <Accordion title="The UI renders but is collapsed to zero height">- The SDK fills its parent container and does not set its own height. A parent with no resolved height collapses the entire chat UI, which is the single most common cause of a "blank" first install.-- ```tsx- <div className="flex h-dvh min-h-0 w-full flex-1 flex-col">- <TrueforgeUI /* ... */ className="h-full min-h-0" />- </div>- ```-- The SDK fills its parent container and does not set its own height. A parent with no resolved height collapses the entire chat UI, which is the single most common cause of a "blank" first install.- </Accordion>-</AccordionGroup>\ No newline at end of filediff --git a/docs/ui-sdk/get-started/quickstart.mdx b/docs/ui-sdk/get-started/quickstart.mdxindex ebaa82759..63068e343 100644--- a/docs/ui-sdk/get-started/quickstart.mdx+++ b/docs/ui-sdk/get-started/quickstart.mdx@@ -37,7 +37,7 @@ Typed for hosts adopting the harness adapter.```## Rendered UI-+When you run the app, you get a fully functional agent chat experience out of the box, with streaming responses, conversation history, and tool-call support.<Frame caption="What `TrueforgeUI` renders — a full agent chat with streaming, history, and tool calls."></Frame>\ No newline at end of filediff --git a/docs/ui-sdk/guides/agent-modes.mdx b/docs/ui-sdk/guides/agent-modes.mdxindex 1f248e20b..f12d446cb 100644--- a/docs/ui-sdk/guides/agent-modes.mdx+++ b/docs/ui-sdk/guides/agent-modes.mdx@@ -1,6 +1,6 @@---title: "Agent modes"-description: "Choose between a fixed agent, a library, a composer, or both."+description: "Choose from four agent modes: fixed agent, agent library, agent composer, or library + composer."---This can be configured by using the `agentConfig` object.@@ -22,43 +22,15 @@ type AgentConfig =## Single Agent-All chats are done with one named agent which can be configured in `name` param. All selection controls are hidden and the user cannot switch agents or open the composer.+All conversations use a single named agent configured through the name parameter. Agent selection controls are hidden, so users cannot switch agents or open the agent composer.<Frame></Frame>-<AccordionGroup>- <Accordion title="SingleAgent">- Pins the UI to one named agent. All selection controls are hidden and the user cannot switch agents or open the composer.- </Accordion>-- <Accordion title="AgentLibrary">- Users pick from agents your `searchAgents` implementation returns, but cannot author a new one. Note that "new chat" is disabled in this mode only.-- <Frame caption="The Agents Library: users pick from the agents your `searchAgents` returns.">- - </Frame>- </Accordion>-- <Accordion title="AgentComposer">- Users assemble an ad-hoc agent — model, skills, MCP servers — without browsing a library, and can save it back to the library.-- <Frame caption="Composing an agent — pick a model, add connectors and skills, then save it to the library.">- <div style={{ position: "relative", boxSizing: "content-box", width: "100%", aspectRatio: "1.46", padding: "40px 0" }}>- <iframe src="https://app.supademo.com/embed/cmsk13xio00k81p0j1wj6amj6?embed_v=2&utm_source=embed" loading="lazy" title="Compose an agent in TrueForge" allow="clipboard-write" allowFullScreen style={{ position: "absolute", top: 0, left: 0, width: "100%", height: "100%", border: 0 }} />-</div>- </Frame>- </Accordion>-- <Accordion title="AgentLibraryWithComposer">- Both surfaces, and the default. Users can pick an existing agent or author a new one.- </Accordion>-</AccordionGroup>-## AgentComposer-Users compose/create a new agent by selecting models, skills, MCP servers and can save it to the library.+Users can create a new agent by selecting a model, skills, and MCP servers, then save the configured agent to the library for future use.<Frame>@@ -66,7 +38,7 @@ Users compose/create a new agent by selecting models, skills, MCP servers and ca## AgentLibrary-Users chat with agents already saved in your library but cannot compose a new one. Note that “new chat” is disabled in this mode only. Ideally for restricting agent creation by users.+Users can chat with agents already saved in the library but cannot create new agents. The “New Chat” option is disabled in this mode, making it ideal for restricting agent creation while still allowing users to use existing agents.<Frame>@@ -74,7 +46,7 @@ Users chat with agents already saved in your library but cannot compose a new on## AgentLibraryWithComposer-Users can pick an existing agent from the library or create a new one.+Users can choose an existing agent from the library or create a new agent using the composer.<Frame>diff --git a/docs/ui-sdk/guides/layouts-and-theme.mdx b/docs/ui-sdk/guides/layouts-and-theme.mdxindex b145fa757..3c7130f08 100644--- a/docs/ui-sdk/guides/layouts-and-theme.mdx+++ b/docs/ui-sdk/guides/layouts-and-theme.mdx@@ -1,15 +1,15 @@----title: "Layout & Themes"-description: "Layout, Presets themes, branding, and dark mode."+title: "Layout, Theming & Branding"+description: "Layout, Presets themes, Branding, and Dark mode."---## Preset Layouts-The sidebar view is the default option. You can pass a predefined value - sidebar, drawer, dock, or widget to change the layout. You can also build a complete custom layout using the predefined components as [shown here](/ui-sdk/setup-custom-ui/custom-layout).+The sidebar view is the default layout. You can customize the layout by passing one of the predefined options: sidebar, drawer, dock, or widget.<Tabs><Tab title="sidebar(default)">- Full-page chat with a persistent chat history in a left sidebar. The default choice for a dedicated chat surface.+ A full-page chat experience with persistent conversation history in a left sidebar. The default choice for a dedicated chat surface.```tsx<TrueforgeUI server={server} layout="sidebar" />@@ -20,7 +20,7 @@ The sidebar view is the default option. You can pass a predefined value - sideba</Frame></Tab><Tab title="drawer">- Chat history list collapses into an overlay drawer. Click on the history icon to view the past conversations. Suited to smaller viewports like tablets or small monitors.+ Chat history is tucked into an overlay drawer and can be opened using the history icon. Ideal for smaller viewports, such as tablets and compact monitors, where screen space is limited.```tsx<TrueforgeUI server={server} layout="drawer" />@@ -31,7 +31,7 @@ The sidebar view is the default option. You can pass a predefined value - sideba</Frame></Tab><Tab title="dock">- A panel pinned to the right edge, filling the available width up to a 400px cap.+ A chat panel pinned to the right edge, using the available space up to a maximum width of 400px.```tsx<TrueforgeUI server={server} layout="dock" />@@ -42,7 +42,7 @@ The sidebar view is the default option. You can pass a predefined value - sideba</Frame></Tab><Tab title="widget">- Floating launcher that expands into a compact chat panel.+ A floating chat launcher that expands into a compact chat panel when opened.```tsx<TrueforgeUI server={server} layout="widget" />@@ -54,11 +54,11 @@ The sidebar view is the default option. You can pass a predefined value - sideba</Tab></Tabs>-Built-in layouts are code-split, so using one does not pull the other three into your bundle. A placeholder renders for the moment it takes to load.+Built-in layouts are code-split, so only the layout you use is loaded into your bundle. The other three layouts are excluded, keeping your bundle size smaller. A lightweight placeholder is displayed while the selected layout loads.## Preset Themes-You can choose from four preset themes - Claude, ChaptGPT, Gemini, TrueFoundry or you can create a [custom theme](setup-custom-ui/).+Choose from four built-in themes - Claude, ChatGPT, Gemini, and TrueFoundry, or create a [custom theme](../setup-custom-ui/custom-theme) to match your brand.## The theme object@@ -78,7 +78,7 @@ type ThemeConfig = {<TrueforgeUI...theme={{- preset: "claude",+ preset: "trueforge",mode: "system",brand: {name: "TrueForge",@@ -88,7 +88,7 @@ type ThemeConfig = {/>```-The `chatgpt`, `claude`, and `gemini` presets (the default is `trueforge`):+The `chatgpt`, `claude`, and `gemini` themes are shown below:<Columns cols={3}><Frame caption="chatgpt">@@ -106,17 +106,17 @@ The `chatgpt`, `claude`, and `gemini` presets (the default is `trueforge`):## Light and dark mode-When you skip this key then the SDK defaults to system theme. User will get an option to switch to dark or light theme via UI.+If you omit this key, the SDK defaults to the system theme, and users can switch between light and dark mode through the UI.-If you want to control the theme based on the app level theme then pass a value to set a theme to light, dark or system to match the main app theme. Please note, user does not get an option to update it via UI.+If you want the SDK theme to follow your application’s theme, set this value to light, dark, or system. This allows the SDK to stay in sync with the main application theme. When the theme is explicitly set, the user cannot change it through the UI.<Frame caption="Dark mode applied to the chat UI."></Frame>-### Set separate logo for light and dark theme+### Separate logo for light and dark theme-You can also provide different logos for dark and light mode as shown below:+You can also provide separate logos for light and dark modes, allowing your branding to remain visible and optimized for each theme, as shown below:```tsx App.tsx<TrueforgeUI@@ -135,13 +135,25 @@ You can also provide different logos for dark and light mode as shown below:/>```-The source is picked from the resolved mode, so this follows the system theme when `mode` is-omitted. Set only one of `light` / `dark` and it is used for both modes; use `src` for a-mode-agnostic mark. `name` labels the image, and the link when `href` is set.+The logo source is selected based on the resolved theme mode. When mode is omitted, the logo automatically follows the system theme.-To render a component instead of an image — an inline SVG, an animated mark — override the-`BrandLogo` slot rather than passing a node through `theme`:+* Provide both light and dark to use a different logo for each mode.+* Provide only one of light or dark to use the same logo in both modes.+* Use src for a mode-independent logo.+* `name` sets the brand name in the topbar right next to the logo.+* Set `href` to make the logo clickable.++For more advanced use cases, such as rendering an inline SVG or an animated logo, override the BrandLogo slot instead of passing a React node through the theme object.```tsx App.tsx-<TrueforgeUI ... overrides={{ BrandLogo: MyMark }} />+import logoUrl from "./logo.svg";++function MyCustomLogo() {+ return <img src={logoUrl} alt="My custom logo" />;+}++<TrueforgeUI+ ...+ overrides={{ BrandLogo: MyCustomLogo }}+/>```\ No newline at end of filediff --git a/docs/ui-sdk/setup-custom-ui/custom-layout.mdx b/docs/ui-sdk/setup-custom-ui/custom-layout.mdxdeleted file mode 100644index 9c1c2a756..000000000--- a/docs/ui-sdk/setup-custom-ui/custom-layout.mdx+++ /dev/null@@ -1,3 +0,0 @@-----title: "Custom Layout"----diff --git a/docs/ui-sdk/setup-custom-ui/custom-theme.mdx b/docs/ui-sdk/setup-custom-ui/custom-theme.mdxindex c8957e760..fd46e0962 100644--- a/docs/ui-sdk/setup-custom-ui/custom-theme.mdx+++ b/docs/ui-sdk/setup-custom-ui/custom-theme.mdx@@ -5,7 +5,7 @@ description: "Build your own custom theme"## The Theme Object-Theme object supports params to pass `tokens` to override styles of UI components. You can also override app level classes+The theme object lets you customize the appearance of the UI by passing design tokens that override component styles. You can also use it to override app-level CSS classes for broader layout and styling customizations.```jsx App.jsxtype ThemeConfig = {@@ -18,91 +18,80 @@ type ThemeConfig = {## The Token Object-```json Token Object-{- "sidebarBg": "#ffffff",- "topbarBg": "#ffffff",- "primaryBg": "#fdfcfc",- "secondaryBg": "#f8fafd",- "border": "#dadce0",- "fontFamily": "\"GeistSans\", \"GeistSans Fallback\", ui-sans-serif, system-ui, -apple-system, \"Segoe UI\", sans-serif",- "inputBoxBg": "#ffffff",- "inputBorder": "#dadce0",- "textPrimary": "#1f1f1f",- "textSecondary": "#444746",- "cardBg": "#ffffff",- "dropdownSelectedItemBg": "#e9eef6",- "dropdownSelectedItemText": "#1f1f1f",- "userMessageBg": "#f3f6fc",- "userMessageText": "#1f1f1f",- "assistantMessageBg": "transparent",- "assistantMessageText": "#1f1f1f",- "primaryButtonBg": "#1f3b9b",- "primaryButtonHover": "#1a3285",- "primaryButtonText": "#ffffff",- "secondaryButtonBg": "#e8eaed",- "secondaryButtonHover": "#dadce0",- "secondaryButtonText": "#1f1f1f",- "ghostButtonBg": "transparent",- "ghostButtonHover": "#e9eef6",- "ghostButtonText": "#1f1f1f",- "successBg": "#188038",- "successText": "#ffffff",- "failureBg": "#b3261e",- "failureText": "#ffffff",- "warningBg": "#b06000",- "warningText": "#ffffff",- "focusRing": "#1f3b9b",- "radius": "1rem",- "composerRadius": "2rem",- "overlay": "rgb(9 9 11 / 0.5)",- "shadowColor": "#1f1f1f",- "scrollbarThumb": "#444746"-}-```--## Precedence+The theme object provides a flexible way to customize the colors and visual appearance of the Agent SDK. You can override individual design tokens to control the appearance of different UI elements, including the sidebar, page background, popups, buttons, input fields, and more.-The provider resolves the preset for the current mode, merges your `theme.tokens` over it, and writes the result as **inline styles** on the theme root. So within `theme.tokens`, your entries beat the preset — that part is straightforward.+Theme tokens can be configured independently for both light and dark modes, allowing you to create a consistent experience across different color schemes without having to override individual components manually.-<Warning>- Because those tokens land as inline styles, a `:root { --primary-button-bg: … }` rule in your own CSS will **not** override them. This applies to every token a preset defines, whether or not you passed `theme.tokens`. Use `theme.tokens` to change these, not CSS.-</Warning>+The easiest way to explore and customize the theme is through our UI Config App. You can experiment with different color tokens and see your changes reflected in real time in the preview window. Once you’re happy with the theme, you can use the generated configuration in your application. [Visit Config App](https://ui.trueforge.dev/)-`theme.className` is applied to the theme root, for utility-class adjustments alongside the tokens.--<Note>- `brand`, `icons`, and `classNames` are not part of this cascade — they are separate context values, not tokens that layer over one another.-</Note>--## Reading theme state--```tsx-import { useTheme, useThemeMode, useBrand, useBrandName } from "@truefoundry/trueforge-ui";-const { preset, mode, preference, isDark, setTheme } = useTheme();-const resolved = useThemeMode(); // "light" | "dark", defaults to "light" outside a provider-const brand = useBrand();-const brandName = useBrandName(); // brand.name, or "TrueForge"+```json Token Object+{+ "light": {+ "sidebarBg": "#FAFAFA",+ "topbarBg": "#FFFFFF",+ "primaryBg": "#FFFFFF",+ "secondaryBg": "#F4F4F5",+ "border": "#E4E4E7",+ "inputBoxBg": "#FAFAFA",+ "inputBorder": "#E4E4E7",+ "textPrimary": "#18181B",+ "textSecondary": "#62626A",+ "cardBg": "#FFFFFF",+ "dropdownSelectedItemBg": "#F1F1F2",+ "dropdownSelectedItemText": "#18181B",+ "userMessageBg": "#18181B",+ "userMessageText": "#FFFFFF",+ "assistantMessageBg": "transparent",+ "assistantMessageText": "#18181B",+ "primaryButtonBg": "#18181B",+ "primaryButtonHover": "#27272A",+ "primaryButtonText": "#FFFFFF",+ "secondaryButtonBg": "#FAFAFA",+ "secondaryButtonHover": "#E4E4E7",+ "secondaryButtonText": "#18181B",+ "ghostButtonBg": "transparent",+ "ghostButtonHover": "#F4F4F5",+ "ghostButtonText": "#18181B",+ "successBg": "#16A34A",+ "successText": "#FFFFFF",+ "failureBg": "#EF4444",+ "failureText": "#FFFFFF",+ "warningBg": "#D97706",+ "warningText": "#FFFFFF",+ "scrollbarThumb": "#62626A"+ },+ "dark": {+ ... //Same tokens as light mode+ }+}```-`BrandLogo` renders `theme.brand.logo`, resolved against the active mode and labelled with `theme.brand.name`. Omit `logo` — or `brand` entirely — and it falls back to the default mark; `brand` is optional, but setting it requires a `name`. Pair it with `useBrandName()` when you also want the name as text. It is an overridable slot — use `overrides` to render a component instead of an image.-## Token naming-`SemanticTokens` keys map to the kebab-cased CSS variable of the same name — `primaryButtonBg` becomes `--primary-button-bg`, `userMessageText` becomes `--user-message-text`, `composerRadius` becomes `--composer-radius`, `scrollbarThumb` becomes `--scrollbar-thumb`.--One token breaks that rule:+SemanticTokens keys map directly to kebab-cased CSS variables. For example, `primaryButtonBg` maps to `--primary-button-bg`, and `userMessageText` maps to `--user-message-text`. The only exception is `fontFamily`, which maps to the `--font-agent-ui` CSS variable.-| Token | CSS variable |-| --- | --- |-| `fontFamily` | `--font-agent-ui` |--Status tokens use `failure` / `success` / `warning` with `*Bg` / `*Text` pairs (not `*Foreground`). Buttons follow the same pattern: `primaryButtonBg` / `primaryButtonHover` / `primaryButtonText`, and likewise for secondary and ghost.--<Note>- `theme.tokens` is a `Partial`, so you only supply the tokens you want to change and the preset fills in the rest. Building a complete `SemanticTokens` object — for instance when authoring your own preset — requires every key, including the status `*Bg` / `*Text` pairs and the kept internals (`focusRing`, `radius`, `composerRadius`, `overlay`, `shadowColor`, `scrollbarThumb`).-</Note>+Suppose your application uses a specific brand color for primary actions and a custom font. You can override the corresponding semantic tokens to apply your branding across the Agent SDK:+```ts+const theme = {+ tokens: {+ primaryButtonBg: "#635BFF",+ primaryButtonHover: "#5147E5",+ primaryButtonText: "#FFFFFF",+ fontFamily: "Inter, sans-serif",+ composerRadius: "12px",+ },+};+```+These tokens are automatically mapped to CSS variables:+```ts+--primary-button-bg+--primary-button-hover+--primary-button-text+--font-agent-ui+--composer-radius+```+This approach is useful when you want to customize the look and feel of the SDK while keeping the existing components, behavior, and layout intact. Instead of writing component-specific CSS overrides, you can change a small set of semantic tokens and have the changes applied consistently throughout the UI.## Styling rendered content@@ -145,65 +134,4 @@ type ContentClassNames = {};```-| Key | Applied on |-| --- | --- |-| `markdown` | Markdown message body |-| `inlineCode` | Inline code inside markdown |-| `syntaxHighlighter.*` | Fenced non-OpenUI code blocks |-| `openui.*` | Generative UI (OpenUI) fence blocks |-| `monaco.*` | Monaco editor surfaces (e.g. skill / draft editors) |-For CSS-only adjustments you can instead target the stable class names directly: `.aui-markdown`, `.aui-syntax-highlighter`, `.aui-openui`, `.aui-monaco`.--## CSS targeting with `data-slot`--Chat-shell components expose stable `data-slot` attributes — the same styling hook pattern [assistant-ui uses for its UI kit](https://www.assistant-ui.com/docs/tools/generative-ui#styling) (there: `data-aui` on generative vocabulary nodes; here: `data-slot` on thread, composer, and message parts). Prefer `theme.tokens` for colors and radii; use these selectors when you need layout or typography tweaks that tokens do not cover.--```css-/* Scope under the theme root so host-app styles do not leak in the other direction */-.aui-theme-root [data-slot="aui_user-message-content"] {- font-size: 0.95rem;-}--.aui-theme-root [data-slot="aui_composer-shell"] {- box-shadow: 0 8px 24px color-mix(in srgb, var(--shadow-color) 12%, transparent);-}-```--Stable slots (most are prefixed `aui_`; a few are not — inspect the element if unsure):--| `data-slot` | Surface |-| --- | --- |-| `aui_thread-viewport` | Scrollable message list |-| `aui_thread-composer` | Composer region under the viewport |-| `aui_composer-shell` | Composer chrome |-| `aui_composer-root` | Composer inner root |-| `aui_composer-input` | Composer text area |-| `aui_composer-attachment-dropzone` | Attachment drop target |-| `aui_message-group` | Grouped message block |-| `aui_user-message-root` / `aui_user-message-content` | User bubble |-| `aui_user-message-edit` | Edit affordance on a user message |-| `aui_user-edit-composer-root` / `aui_user-edit-input` | In-place edit composer |-| `aui_assistant-message-root` | Assistant bubble |-| `aui_assistant-message-indicator` | Assistant status indicator |-| `aui_thread-list-viewport` | History list scroll area |-| `aui_thread-list-item` / `aui_thread-list-item-age` / `aui_thread-list-item-actions` | History row |-| `aui_history-loader` / `aui_thread-history-skeleton` | History loading UI |-| `aui_attachment-preview` / `aui_attachment-chip` | Attachments |-| `aui_select-agent-empty` | Empty “pick an agent” state |-| `avatar` / `avatar-image` / `avatar-fallback` | Avatar parts |-| `tool-call-card` / `tool-group-card` | Tool call chrome |--There is no `data-id` attribute for theming. Generative charts/cards/tables in chat are **OpenUI** (not `@assistant-ui/react-generative-ui`), so they do not emit assistant-ui’s `data-aui` / `data-aui-*` hooks. Style that surface with `.aui-openui`, `theme.classNames.openui`, or by [overriding the `OpenUiFenceBlock` slot](/ui-sdk/setup-custom-ui/slot-overrides).--## Presets--```ts-import { PRESETS, resolvePresetTokens } from "@truefoundry/trueforge-ui";--const tokens = resolvePresetTokens("gemini", "dark");-```--`PRESETS` is a `Record<ThemePreset, { light, dark }>` — useful for building a preset picker.--Refer to [Building custom theme](/ui-sdk/setup-custom-ui/custom-theme) to build a theme from scratchdiff --git a/docs/ui-sdk/setup-custom-ui/untitled-page.mdx b/docs/ui-sdk/setup-custom-ui/untitled-page.mdxdeleted file mode 100644index 172e777df..000000000--- a/docs/ui-sdk/setup-custom-ui/untitled-page.mdx+++ /dev/null@@ -1,54 +0,0 @@-----title: "Custom Layout"------Define a custom layout but still use the existing components--Pass a component instead of a string. It renders inside the full provider stack, so every container hook and `useSlot` lookup works normally.--```tsx App.tsx-import { Thread, ThreadListContainer, TrueforgeUI } from "@truefoundry/trueforge-ui";--function MyLayout() {- return (- <div className="flex h-full min-h-0">- <aside className="w-72 shrink-0 border-r">- <ThreadListContainer />- </aside>- <main className="min-h-0 flex-1">- <Thread />- </main>- </div>- );-}--<TrueforgeUI server={server} layout={MyLayout} />;-```--<Frame caption="A custom layout renders inside the full provider stack, so every container hook still works.">- -</Frame>--`Thread` is a convenience wrapper equal to `<ThreadContainer composer={<ComposerContainer />} />`. Split them apart when you need the composer somewhere other than directly beneath the transcript.--<Warning>- The settings panel is part of the built-in layouts, so a custom layout does not get one. If you need settings, either stay on a built-in layout or build your own panel against the `catalog` server — see [Server](/ui-sdk/reference/server).-</Warning>--## Composing without TrueforgeUI--For maximum control, mount the providers yourself. Order matters — `SlotsProvider` must be outside `TrueFoundryChatProvider`.--```tsx-<SlotsProvider overrides={overrides} theme={theme}>- <ServerProvider server={server}>- <ShellModeProvider agentConfig={{ mode: "AgentLibrary" }}>- <TrueFoundryChatProvider server={server}>- <MyLayout />- </TrueFoundryChatProvider>- </ShellModeProvider>- </ServerProvider>-</SlotsProvider>-```--This path gives up the automatic runtime reset that `TrueforgeUI` performs when the selected agent changes, so you become responsible for remounting `TrueFoundryChatProvider` — change its `key` — at those moments.\ No newline at end of file