---
document_id: USER_GUIDE_CHAT_OMNILORE_AI
status: ACTIVE
as_of: 2026-08-11T20:29:24Z
audience: Members & operators using https://chat.omnilore.ai
authority: Live LibreChat config + product UX (Modes labels)
related:
  - PRODUCT_NARRATIVE_DUAL_SEAT.md
  - CLOSEOUT_CHAT_MODE_LABELS_UX_2026-08-08.md
  - PASSWORD_SELF_SERVICE.md
---

# User guide — Chat.OmniLore.ai (models, modes, agents, pins)

**URL:** [https://chat.omnilore.ai](https://chat.omnilore.ai)
**Public guide:** [https://chat.omnilore.ai/help](https://chat.omnilore.ai/help) · [full HTML](https://chat.omnilore.ai/legal/chat-user-guide.html)
**Sign-in:** your OmniLore LDAP username and password (same password family as RepoHub / Mattermost).
**As-of:** 2026-08-11

This guide explains the **Chat interface only**: how to pick a mode or model, what **My Agents** is, what **pin** means, and **when to use each option**. It uses the **simple labels** you see in the UI:

| UI label | What it is (plain language) | Older / ops name (if you see it) |
|----------|-----------------------------|----------------------------------|
| **OmniLore** | Trusted answers + fabric tools (default) | Shared Operator |
| **Image** | Create / edit / animate photos (paperclip) | Image agent |
| **Quick** | Fast chat & code, **no** fabric tools | OmniLore Auto (routed) |
| **CodeHub** | Private git write / PRs / multi-file | CodeHub Operator |
| **Advanced · Models** | A fixed model tag (no tools) | Raw Ollama |

---

## 1. First-time setup

1. Open **https://chat.omnilore.ai** and sign in.
2. Accept **Terms** if prompted.
3. Prefer a **new chat** after major UI or tool updates (sidebar: **New chat**, or the **+** control that starts a new conversation).
4. Confirm the top selector shows **OmniLore** for product / fabric questions.

**Password:** Settings → password change, or follow [PASSWORD_SELF_SERVICE.md](./PASSWORD_SELF_SERVICE.md).

**Related surfaces (not Chat, but same account):**

| Surface | URL |
|---------|-----|
| RepoHub (private git) | https://repohub.omnilore.ai |
| Mattermost | https://mattermost.omnilore.ai |
| Mail | https://mail.omnilore.ai |
| Edge board | https://omnilore.ai |

---

## 2. Tour of the Chat screen

LibreChat-style layout (labels can shift slightly with UI version):

| Area | What it does |
|------|----------------|
| **Left sidebar** | Conversation list, **New chat**, search, **Bookmarks**; also entry points for **Prompts**, **Skills**, **Memory** (see §12b) |
| **Top selector** | **Mode / model** picker — the most important control |
| **Message box** | Type prompts; optional **paperclip** for files/images |
| **Starter chips** | Suggested first questions (vary by mode) |
| **Right side panel** (if open) | Agent details, parameters, tools, files |
| **Banner** (top) | Short reminder of which mode is for product truth |

### Mental model

```text
  ┌─────────────────────────────────────────┐
  │  MODE (OmniLore / Quick / CodeHub / …)  │  ← what kind of help you want
  │         may use a MODEL underneath      │  ← which LLM engine runs
  └─────────────────────────────────────────┘
```

- **Mode** = product path + tools (or not).
- **Model** = which language model answers (speed vs strength).
- **Agent** = a saved “assistant profile” (instructions + tools + model). **OmniLore** and **CodeHub** are agents under the hood.

---

## 3. The three primary modes (use these first)

### 3.1 OmniLore (default) — “I need the real fabric / tools”

**Select when you want:**

- Product truth: “What is OmniLore?”, dual-seat, HOOTL, OmniGuard
- Fabric health, topology, where models run
- Files / PDF paperclip + search
- Images (create / edit) and job status
- Web research (Frontier Search) when the fabric doesn’t know
- Light RepoHub / forge work
- Personal Google corpus search (if linked for your account)

**Why:** This path has **MCP tools** and **Source of Truth**. Answers about OmniLore should be grounded—not invented from training data.

**Do not use for:** Nothing is “wrong,” but for huge multi-file PR sprints, **CodeHub** is cleaner; for pure throwaway coding without tools, **Quick** is lighter.

**Under the hood:** Agent `agent_omnilore_shared_operator`, model typically `qwen3.6:27b` (vision + tools).

---

### 3.2 Image — “Edit or create photos”

**Select when you want:**

- Remove / change background (generative; not always perfect alpha)
- Sharpen, restyle, isolate subject
- Create a new image from a text prompt
- Animate a still

**Why:** Tiny tool list + hard “always call `image_edit`” instructions so the model is less likely to refuse or send you only to remove.bg.

**How:** Mode **Image** → paperclip attach → ask for the edit → expect a pasted result image (or Chat outbox URL).

**Do not use for:** OmniLore product definition (use **OmniLore**).

**Honest limit:** Local Comfy/FLUX — true rembg-style transparent PNG is **not guaranteed**.

---

### 3.3 Quick — “Fast chat or code, I don’t need fabric tools”

**Also known as:** OmniLore Auto, Auto (routed).

**Select when you want:**

- Quick coding snippets, explanations, rewrites
- Brainstorming that is **not** about OmniLore product facts
- Lower friction / faster responses when tools aren’t needed

**Why:** Chat auto-routes to a strong **server** model for you. **No MCP tools** — no `architecture_card`, no RepoHub tools, no image jobs via tools.

**Do not use for:**

- “What is OmniLore?” / dual-seat / completeness
- Anything that needs live fabric, git write, or Frontier tools

If you ask product questions here, the model is instructed to **redirect you to OmniLore mode** (or answer only as ungrounded general advice).

**Under the hood:** Endpoint **OmniLore Auto** · model tag `auto` (router may rewrite to a concrete tag like a coder or vision model).

---

### 3.4 CodeHub — “I need to write code in private git”

**Select when you want:**

- List / create private repos
- Read / write / multi-file commits
- Issues / pull requests on **RepoHub** (not GitHub.com)

**Why:** Slimmer, forge-heavy tool set. Product encyclopedia questions should go back to **OmniLore**.

**Hosts:** https://repohub.omnilore.ai · https://codehub.omnilore.ai

**Under the hood:** Agent `agent_omnilore_codehub_operator`.

---

## 4. Advanced · Models — pick a fixed model (no tools)

Under **Advanced · Models** you choose a **specific Ollama model tag** (examples you may see):

| Example label | Typical use case |
|---------------|------------------|
| `qwen3.8:27b` | **Primary** strong coding (no fabric tools) |
| `qwen3-coder:30b` | Coding fallback (no fabric tools) |
| `qwen3.6:27b` | General + vision-capable **without** MCP tools on this path |
| `qwen3:32b` | Heavier general chat |
| `deepseek-r1:32b` | Reasoning-style answers (slower) |
| `qwen2.5:14b-instruct` | Lighter / faster instruct |
| `llama3.3:70b` | Large general model (if loaded) |
| `gemma3:27b` | General; **not** for tool agents |

**Select Advanced when:**

- You know you want a **specific** model’s style or size
- You are debugging “does this model answer better for X?”
- You deliberately want **no tools** and a fixed engine

**Do not use Advanced for product truth** — same rule as Quick: switch to **OmniLore** for fabric facts.

---

## 5. How to change modes / models in the UI

### 5.1 Main selector (top of the conversation)

1. Click the **current mode/model name** at the top of the chat (or the endpoints / models control).
2. You should see groups similar to:
   - **Modes** → OmniLore · CodeHub · Quick
   - **Advanced · Models** → fixed tags
   - Possibly **My Agents** / **Agents** (see §6)
3. Click the option you want.
4. Start typing (or click a **starter chip**).

**Tip:** After a change, use a **new chat** if the previous thread was started on a different mode—old threads keep history and sometimes old assumptions.

### 5.2 softDefault (why you might not land on OmniLore)

**OmniLore** is the **soft default** for new chats. If you previously chose **Quick** or an Advanced model, LibreChat may **remember your last choice**.

**If product answers look wrong:** open the selector → choose **OmniLore** again → new chat.

---

## 6. “My Agents” — what it is and when to use it

### 6.1 What “My Agents” means

**Agents** are saved assistant profiles:

- System instructions
- Allowed tools
- Preferred model
- Optional starters

**OmniLore** and **CodeHub** are **promoted agents** the organization provides.
**My Agents** (LibreChat Agents menu) is the list of agents **you can use**—including those promoted ones and any you create (if creation is allowed for your account).

### 6.2 Why you would open My Agents

| Reason | Example |
|--------|---------|
| See all agents available to you | OmniLore, CodeHub, any custom agents |
| Switch agent without using a Mode shortcut | Same backend as Modes, different menu |
| Create / edit a personal agent (if enabled) | Custom instructions for a recurring task |
| Check which agent a conversation is bound to | Side panel / agent dropdown |

### 6.2b Deep guide — Create custom agents

| Audience | Guide |
|----------|--------|
| **Members (T1)** | `docs/member/USER_GUIDE_CREATE_CUSTOM_AGENTS_CHAT.md` — product-safe recipes only |
| **Operators / power** | `docs/USER_GUIDE_CREATE_CUSTOM_AGENTS_CHAT_OMNILORE_AI_2026-08-10.md` — forge write, publish, release agents |

**Law:** 5–25 tools (not full ~160 MCP catalog); **`qwen3.6:27b`** for any tool agent; prefer Modes for daily work; local models are low-parallelism.


### 6.3 Why most members should prefer Modes, not invent agents

| Prefer | Avoid for daily work |
|--------|----------------------|
| **OmniLore** / **CodeHub** / **Quick** presets | Building a new agent that loads **all** tools (causes slow/broken chats) |
| Org-seeded tool lists | Copying “everything” MCP tools into one agent |

**Policy note:** Creating agents may be allowed in config (`agents.create: true`), but **kitchen-sink tool lists break context budget** (`empty_messages`). Prefer Modes.

### 6.4 When “My Agents” is confusing

If you pick an agent that is **not** OmniLore/CodeHub:

- It may have fewer tools, wrong tools, or no tools.
- It may not follow product SoT rules.

**Safe default:** always return to **OmniLore** for real OmniLore questions.

---

## 7. OmniLore Auto / Quick — models under Auto

### 7.1 Naming

| You may see | Same path |
|-------------|-----------|
| **Quick** | Member-facing label |
| **OmniLore Auto** / **Auto (routed)** | Endpoint / older docs |
| Model tags `auto`, `auto-code`, `auto-vl`, `auto-reason`, `auto-tools` | **Routing tags**, not “more tools” |

### 7.2 What “routed” means

The Auto endpoint asks the dual-seat **inventory router** to pick a good **server** model for the request (e.g. coder vs vision).

**Important:** `auto-tools` / `auto-vl` name **model routing**, **not** “turn on OmniLore MCP tools.” Tools stay off on Quick/Auto.

### 7.3 When to change the Auto/Quick model tag

If the UI exposes Auto sub-models:

| Tag (if shown) | Use case |
|----------------|----------|
| `auto` | General default routing |
| `auto-code` | Prefer coding models |
| `auto-vl` | Prefer vision-capable routing |
| `auto-reason` | Prefer reasoning-oriented models |

If unsure, leave **`auto`** and use **OmniLore** when you need tools.

---

## 8. Pinning — what “pin” means

LibreChat uses “pin” in more than one place. On OmniLore Chat, the important cases are:

### 8.1 Pinned tools (organization default)

Config includes **default pinned tools** such as **MCP** so tool-capable chats keep fabric tools visible/available in the UI chrome.

**You usually don’t need to change this.** Unpinning MCP can make tool-using agents harder to use correctly.

### 8.2 Pinning a mode or model (favorites / sticky selection)

In the model/endpoint UI, a **pin** (or star / favorite, depending on version) typically means:

- Keep this option **easy to re-select**
- Or **stick** as your preferred selection across sessions

**Use cases for pinning:**

| Pin this | Why |
|----------|-----|
| **OmniLore** | You mostly do product / fabric / tools work |
| **Quick** | You mostly write throwaway code snippets |
| **CodeHub** | You’re in a multi-day forge sprint |
| A specific Advanced model | You’re A/B testing one model’s style |

**Caution:** If you pin **Quick** or Advanced as your sticky default, new chats may **not** open on OmniLore—then product questions go wrong. Unpin or re-select **OmniLore** for product work.

### 8.3 What pin is *not*

- Pin does **not** grant extra tools.
- Pin does **not** make Quick into OmniLore.
- Pin does **not** change dual-seat topology or who owns the data.

---

## 9. The “+” button — what it can mean

Depending on where you click, **+** may mean different things:

| Where | Typical meaning | Use case |
|-------|-----------------|----------|
| **Sidebar / top** | **New chat** | Clean thread; required after mode/tool budget changes |
| **Composer / paperclip area** | **Attach file** (sometimes separate paperclip) | PDF, image, text for OmniLore mode |
| **Agents / side panel** | **Create agent** or add resource | Power users only; keep tool lists small |
| **Prompts library** | **New prompt** template | Save a recurring instruction |

### 9.1 When to use New chat (+)

- After switching **OmniLore ↔ Quick ↔ CodeHub**
- After an error like **empty_messages** / “context window”
- When the bot seems stuck on old wrong assumptions
- When starters disappear or tools feel stale

### 9.2 When to attach files (+)

| Attach | Prefer mode | Why |
|--------|-------------|-----|
| PDF / docs | **OmniLore** | `file_search` / RAG path |
| Images | **OmniLore** | Vision + tools model |
| Code paste only | Quick or OmniLore | Either works; OmniLore if you also need forge |

---

## 10. Use-case matrix (choose in one glance)

| You want to… | Select | Why |
|--------------|--------|-----|
| “What is OmniLore / dual-seat / HOOTL?” | **OmniLore** | Product SoT + tools |
| Fabric health / where models run | **OmniLore** | Live probes + architecture card |
| Generate or edit an image / remove bg | **Image** (or OmniLore) | Image tools + status; Image mode preferred |
| Web research / news with citations path | **OmniLore** | Frontier tools |
| Personal Drive/Gmail search (if linked) | **OmniLore** | Personal corpus tools |
| List/write private git files | **CodeHub** (or light work on OmniLore) | Forge tools |
| Multi-file PR sprint | **CodeHub** | Coding profile tools |
| Quick Python helper / essay draft | **Quick** | Fast, no tool overhead |
| Force a specific open model | **Advanced · Models** | Fixed tag |
| Debug “is it the model or the tools?” | Compare **Quick** vs **OmniLore** | Isolates tools |
| Build a personal bot | **My Agents** (+) carefully | Small tool list only |

---

## 11. Conversation starters (chips)

On a **new** chat, chips under the box are **suggested first messages** for that mode.

| Mode | Example starters |
|------|------------------|
| OmniLore | What is OmniLore? · Where do models run? · Create an image · Latest AI news · Show my repos |
| Quick | Write a Python function… · big-O… · switch to OmniLore for product |
| CodeHub | List repos · Read README · Create scratch repo · Write a file |

Click a chip instead of typing if it matches your goal.

---

## 12. Parameters, side panel, and prompts

| Control | When to touch it |
|---------|------------------|
| **Parameters** (temperature, etc.) | Advanced tuning; leave default unless you know why |
| **Side panel** | Inspect agent, files, tool resources |
| **Prompts** library | Reuse long instructions without retyping |
| **Presets** | Organization has presets **off** so Modes stay clear |

### 12b. Skills, Prompts, Memory, Bookmarks (sidebar libraries)

Deep guide: [`CHAT_SIDEBAR_SKILLS_PROMPTS_MEMORY_BOOKMARKS.md`](./CHAT_SIDEBAR_SKILLS_PROMPTS_MEMORY_BOOKMARKS.md).

| Feature | Plain meaning | Product truth? |
|---------|---------------|----------------|
| **Bookmarks** | Star/tag **your** conversations | No |
| **Prompts** | Reusable message templates | No (does not add tools) |
| **Skills** | Agent instruction packs (LibreChat) | Partial; Modes+tools still primary |
| **Memory** | Personal Chat memory about *you* | **No** — not fabric SoT |

For “What is OmniLore?” always use **OmniLore** mode, not Memory or a saved Prompt alone.

---


---

## 12c. Desktop seat capture (your computer + Chat)

You can use **OmniLore mode** in Chat to request a **screenshot of a computer you enrolled**, if that machine is online and you allowed capture.

| Step | Action |
|------|--------|
| 1 | On the **desktop**, install the seat agent once — full steps: [DESKTOP_SEAT_CAPTURE.md](./DESKTOP_SEAT_CAPTURE.md) |
| 2 | Leave the PC on with the seat agent running (`systemctl --user status omnilore-seat-agent`) |
| 3 | In Chat use **OmniLore** mode (not **Quick**) |
| 4 | Ask: “Is my seat online?” or “Capture my desktop screenshot” |

**Also available in CoTrinity** (on the same machine) with “take a screenshot” — same grants, local path.

**Not included:** remote mouse/keyboard control, free shell, capturing someone else’s computer.

---

## 13. Common mistakes (and fixes)

| Symptom | Likely cause | Fix |
|---------|--------------|-----|
| Invents OmniLore features | On **Quick** or Advanced | Switch to **OmniLore**, new chat |
| “dual-set” / “I don’t know dual-seat” | Ungrounded path | **OmniLore** + ask for product answer / architecture |
| empty_messages / context error | Old fat tool thread or wrong agent | **New chat** + **OmniLore** (slim tools) |
| No forge tools | On Quick/Advanced | **CodeHub** or OmniLore |
| Tools 404 / MCP errors | Stale session after ops restart | Refresh; if needed ask ops to restart Chat |
| Always opens Quick | Pinned / last selection | Select **OmniLore**, new chat; unpin Quick if sticky |
| “Device offline” on screenshot | Seat agent not running / PC asleep | Start agent on desk; see [DESKTOP_SEAT_CAPTURE](./DESKTOP_SEAT_CAPTURE.md) |
| Capture denied | No `desk.capture` grant | On desk: `~/omnilore/ops/bin/omnilore-desk grant-capture` (full path; see [DESKTOP_SEAT_CAPTURE](./DESKTOP_SEAT_CAPTURE.md)) |

---

## 14. Privacy, legal, and web research

- **Frontier / web research** (inside OmniLore mode) may use self-hosted and third-party search. OmniLore does **not** control third-party page content.
- Details: https://chat.omnilore.ai/legal/search-privacy.html
- Terms: https://chat.omnilore.ai/legal/terms.html
- **Illegal use is prohibited.**

---

## 15. Short cheat sheet

```text
Product / fabric / files / images / search  →  OmniLore
Fast code chat, no tools                    →  Quick  (was “Auto”)
Private git write / PRs                     →  CodeHub
Pick exact model engine                     →  Advanced · Models
List/create assistants                      →  My Agents
Clean thread after changes                  →  +  New chat
Keep a favorite mode handy                  →  Pin (don’t pin Quick as default if you need product truth)
```

---

## 16. Glossary

| Term | Meaning |
|------|---------|
| **MCP** | Tool bus that lets OmniLore mode call fabric functions |
| **SoT** | Source of Truth (disk docs / product narrative)—not random web |
| **Dual-seat** | Server spine + workstation operator seat (not “dual-set”) |
| **Agent** | Saved assistant (instructions + tools + model) |
| **Mode** | Human label for a recommended agent/endpoint path |
| **Model** | The LLM weights/engine (qwen…, auto, …) |
| **softDefault** | Suggested default that yields to your last choice |
| **Frontier** | Web research path (untrusted drafts until you verify) |
| **Seat implementer** | Agent on *your* machine that can capture screen under grants |

---

## 17. Related docs (ops / deeper)

| Doc | Audience |
|-----|----------|
| `CLOSEOUT_CHAT_MODE_LABELS_UX_2026-08-08.md` | Label rename closeout |
| `PRODUCT_NARRATIVE_DUAL_SEAT.md` | What OmniLore is |
| `LIBRECHAT_PRODUCT_UX_2026-08-02.md` | Historical UX controls |
| `PASSWORD_SELF_SERVICE.md` | Password change |
| `FEATURES_USER.md` | Feature index for members |
| `DESKTOP_SEAT_CAPTURE.md` | Install + use desktop capture (Chat + CoTrinity) |

---

*End of user guide. For UI bugs or access issues, contact your OmniLore operator with: mode selected, new-chat yes/no, and a screenshot of the top selector.*

## Agent Builder

Want a private specialist agent? Prefer **OmniLore** mode and describe the job
(“second brain for my Drive”). Details: [`AGENT_BUILDER.md`](./AGENT_BUILDER.md).