librechat-stack/template_librechat.yaml at main · jdaln/librechat-stack · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
# librechat.yaml

version: 1.3.1
cache: true

# Files saved on the app host (your named volumes); fits your isolated stack design.
fileStrategy: "local"   # other options: firebase | s3 | azure_blob

# Safer local images when you ever expose the app — signed links vs direct paths.
secureImageLinks: true  # optional but recommended. :contentReference[oaicite:1]{index=1}

# ---- FILE HANDLING (RAG + “Upload as Text”) ----
fileConfig:
  # Global server ceiling per upload (MB). Apply per-endpoint caps below if needed.
  serverFileSizeLimit: 200
  avatarSizeLimit: 2

  # “Upload as Text” parsers — we explicitly allow CSV/JSON and common text.
  text:
    supportedMimeTypes:
      - "^text/(plain|markdown|csv|json)$"
      - "^application/(json)$"

  # Speech-to-text not central to your workflow; keep the common defaults enabled.
  stt:
    supportedMimeTypes:
      - "^audio/(mp3|mpeg|mpeg3|wav|wave|x-wav|ogg|vorbis|mp4|x-m4a|flac|x-flac|webm)$"

  # Optional OCR allow-list (you can remove if not needed).
  ocr:
    supportedMimeTypes:
      - "^image/(jpeg|gif|png|webp|heic|heif)$"
      - "^application/pdf$"

  # Per-endpoint upload rules.
  # “assistants” uses its own defaults; everything else falls under “default”.
  endpoints:
    default:
      fileLimit: 10             # max files per message
      fileSizeLimit: 100        # MB per file (still under serverFileSizeLimit)
      totalSizeLimit: 200       # MB per message across all files
      # You can also narrow supportedMimeTypes here if you want per-endpoint control. :contentReference[oaicite:3]{index=3}

# ---- UI/WORKFLOW TWEAKS ----
interface:
  # Keep the UI flexible (you can still switch endpoints & parameters).
  modelSelect: true
  parameters: true
  presets: true
  webSearch: false              # enable later if you wire a provider in .env+yaml. :contentReference[oaicite:4]{index=4}
  fileSearch: true
  fileCitations: true

modelSpecs:
  enforce: false
  prioritize: false
  list:
    - name: "generative-ui-guide"                # internal slug
      label: "Generative UI Guide"               # what users see
      default: false
      description: "Gemini 2.5 agent that writes shadcn/ui React code, can execute snippets, cite files, and return live artifacts."
      preset:
        endpoint: "google"                       # LibreChat’s Gemini endpoint
        model: "gemini-2.5-pro"
        greeting: |
          I'm your **the Generative UI Guide** — I write webpages from documents and can run live snippets whenever you need a preview.
        promptPrefix: |
          You are an expert Guide specializing in transforming complex documents into accessible, understandable web interfaces.
          Your core mission is to facilitate comprehension through rich HTML representations.
          Think step-by-step, add concise comments, and cite any file-search sources when relevant.
          If multiple files are provided, relate them and state assumptions. Ask targeted questions when needed.
          You might be token limited so you can do the following phases in several prompts and ask the user to either give feedback or send "continue".

          1. Analysis Phase (use readFile, todos)
            - Read source document(s) (markdown, text, PDF, CSV, XLS, JSON, etc...)
            - parse diagram content (C4, UML, architecture descriptions)
                  - Identify diagram type and complexity
                  - Extract entities, relationships, and hierarchies
            - Create todo list with transformation tasks
            - Identify document structure: headings, sections, diagrams, data tables
            - Determine target audience

          2. Design Phase (use fetch, runTask)
            - Design component architecture (layout, navigation, content components)
            - Select appropriate Shadcn/UI components
            - Consult frontend-web-expert agent if complex state management needed

          3. Implementation Phase (use createFile, editFiles, runCommands)
            - Create react.tsx page structure
            - Implement components with Shadcn/UI
            - Add semantic HTML5 landmarks (<nav>, <main>, <article>)
            - Implement keyboard navigation and focus management
            - Apply Tailwind CSS with eco-design optimizations
            - Add interactive elements (collapsible sections, search, TOC)