← Back to Chat · Agent Builder · Desktop capture · Legal home · Search Privacy · Terms

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

URL: https://chat.omnilore.ai

Sign-in: your OmniLore LDAP username and password (same password family as RepoHub / Mattermost).

As-of: 2026-08-11 · includes desktop seat capture (Chat + CoTrinity)

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:

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.

Related surfaces (not Chat, but same account):

2. Tour of the Chat screen

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

Mental model

  ┌─────────────────────────────────────────┐
  │  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 primary modes (use these first)

Image mode

Select Image for paperclip create / edit / cutout / restore / animate on OmniLore’s local image plane (not Quick/Auto).

• Transparent cutout — true alpha via rembg (say “remove background transparent”).
• Upscale / restore — Real-ESRGAN (2× mild or 4× default); deterministic, not generative rewrite.
• Semantic edit / sharpen — FLUX Kontext; may invent detail (“generative enhance”).
• Inpaint — fill with a mask (subject/background via rembg, or coarse center). Exact inpaint needs a real mask.
• Animate — short draft I2V (LTX).

Results return as Chat delivery markdown under /images/omnilore-outbox/. Failures must not look like silent stub “success.”

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 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.3 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):

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)

1. Click the option you want.
2. 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

6.3 Why most members should prefer Modes, not invent agents

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

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:

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:

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:

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 (+)

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

11. Conversation starters (chips)

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

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

12. Parameters, side panel, and prompts

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. The same implementer powers CoTrinity on the desktop.

One-time on the machine (summary — full paths; tools may not be on PATH yet):

~/omnilore/ops/bin/omnilore-desk enroll
bash ~/omnilore/ops/bin/install-seat-agent-user.sh
# installer also puts wrappers in ~/.local/bin (add to PATH if needed)
~/omnilore/ops/bin/omnilore-seat-agent register-remote
~/omnilore/ops/bin/omnilore-desk grant-capture

Also in CoTrinity (VS Code / Cursor ≥ 1.0.34): say “take a screenshot” or use OmniLore: Seat screenshot.

Not included: remote mouse/keyboard control, free shell, capturing someone else’s computer. You can revoke a device anytime (membership portal or tools).

Security model: account-bound device, opt-in grant, fixed private save path. Full member page: DESKTOP_SEAT_CAPTURE.md.

13. Common mistakes (and fixes)

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

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)
Desktop screenshot (your enrolled PC)      →  OmniLore + seat online + grant-capture
CoTrinity screenshot (at the desk)         →  “take a screenshot” / Seat screenshot command

16. Glossary

17. Related docs (ops / deeper)

*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.*

Source markdown (ops SoT): docs/member/USER_GUIDE_CHAT_OMNILORE_AI.md · desktop capture: docs/member/DESKTOP_SEAT_CAPTURE.md. Labels: OmniLore · Quick · CodeHub · Advanced · Models · seat capture.