Enhanced ChatGPT Clone: Features Agents, MCP, Skills, DeepSeek, Anthropic, AWS, OpenAI, Responses API, Azure, Groq, o1, GPT-5, Mistral, OpenRouter, Vertex AI, Gemini, Artifacts, AI model switching, message search, Code Interpreter, langchain, DALL-E-3, OpenAPI Actions, Functions, Secure Multi-User Auth, Presets, open-source for self-hosting. Active
TypeScript aianthropicartifactsawsazurechatgptchatgpt-cloneclaudeclonedeepseekgeminigooglegpt-5librechatmcpo1openairesponses-apivisionwebui
import { hasConfiguredFooter } from 'librechat-data-provider';
import { injectBootstrapConfig } from './bootstrap';
const CONFIGURED_FOOTER_SENTINEL = 'data-librechat-configured-footer="true"';
/** What the deployment configured, as the server holds it: the footer env var
* and the base config's `interface.landingFooter`. */
export interface ConfiguredFooterSource {
customFooter?: string | null;
landingFooter?: boolean | null;
}
/**
* Emits the deployment's footer answer with the HTML shell.
*
* A conversation's composer lays out against whether a footer bar sits beneath
* it, and `/api/config` answers that only after the composer has painted. The
* server already knows when it serves the document, so it says so and no client
* has to guess: a first-ever visit to a configured deployment paints the
* composer in its final position instead of correcting by the bar's height.
* The answer is the deployment's own `CUSTOM_FOOTER`, because the document is
* served before there is a caller whose config overrides could be resolved; the
* client prefers `/api/config`'s resolved answer once it has it.
*
* The welcome screen's own footer is answered the same way: a deployment that
* turned it off would otherwise paint it until `/api/config` removed it.
*
* Always injected, including the negative answer, so an absent flag means "no
* server said" (the Vite dev server) rather than "no footer".
*/
export const injectConfiguredFooterBootstrap = (
html: string,
source?: ConfiguredFooterSource | null,
): string =>
injectBootstrapConfig(html, {
sentinel: CONFIGURED_FOOTER_SENTINEL,
values: {
hasConfiguredFooter: hasConfiguredFooter({
customFooter: source?.customFooter ?? undefined,
}),
landingFooter: source?.landingFooter !== false,
},
});