← Member help · Chat

Known limitations (members)

Honest limits of this OmniLore install. Updated as product maturity changes.

Experience

| Limitation | What you may notice |
|------------|---------------------|
| Model choice matters | “Auto” is faster for coding-style help; product/fabric facts need OmniLore mode with tools |
| Context limits | Very long chats may summarize or drop older turns |
| LibreChat Skills names | Agent skills: [] labels may not fully load as a Skills catalog — Modes + MCP tools are authoritative |
| Chat Memory ≠ product docs | Personal Memory UI is not dual-seat SoT or the knowledge base |
| Bookmarks / Prompts | Per-account convenience; not shared tribal memory |
| Tool failures | Occasional “tool unavailable” — retry or contact support |
| Image jobs | Queue time and quality vary with GPU load; local FLUX path is still images, not cinema-grade video |
| No default local frontier video HQ | MiniMax H3–class short video+audio is not a shipped member product path on this fabric |
| Desktop tools | CoTrinity features depend on your seat and permissions |

Scheduled jobs (v1)

| Limitation | What you may notice |
|------------|---------------------|
| Gated surface | Scheduling needs OmniLore mode + schedule tools; not free-form cron or shell |
| No Chat popup at fire time | Results land under your workspace schedules/<id>/ (and optional ops notify) — not a guaranteed in-thread message at 2 AM |
| Allowlisted job kinds only | Workspace note, personal brief, capped agent prompt; timed frontier digest is ops-only beta — not forge write or unrestricted tools |
| Frontier digest ≠ deep research | Timed digests are FRONTIER DRAFT; thin SERP fails quality_ok closed; use Chat Deep Research agent for tool-using research |
| Narrow queries work better | Broad marketing-style digest queries often quality-fail honestly |
| Notify is not free-form | Mattermost-style notify, when used, follows ops allowlists — not arbitrary channels for every member |
| Dogfood → broader beta | Feature is live for ops dogfood; treat broad multi-tenant schedule policy as still maturing |

Account and access

| Limitation | What you may notice |
|------------|---------------------|
| Invite-only | New accounts generally require invitation |
| Role limits | Not every member has every tool or admin surface |
| Password flows | Self-service depends on IdP configuration |

Project continuity / posture

| Limitation | What you may notice |
|------------|---------------------|
| Posture is not ML | Rolling retrieval from intents/handoff/feed — not a predictive user model |
| Session feed is yours only | You cannot search other members’ session corpus |
| No Core predict tools | Dual-seat does not expose Core predict_warmup / Gartner on Chat |

Desktop / CoTrinity

| Limitation | What you may notice |
|------------|---------------------|
| VS Code vs Cursor | CoTrinity installs in both; VS Code is lower friction |
| Cursor account wall | Using Cursor as the host usually requires a Cursor account (Cursor’s product — not OmniLore). OmniLore does not issue Cursor logins |
| Cursor Pro vs CoTrinity | CoTrinity Chat / local Ollama / OmniLore tools do not require Cursor Pro; Cursor’s built-in AI features follow Cursor’s plan |
| Desktop tools | CoTrinity features depend on your seat, install, and permissions |
| Seat capture (screenshots) | Needs enroll + running seat agent + opt-in capture grant; PC must be online for remote Chat; Wayland may need grim |
| No L4 remote control | Mouse/keyboard automation from Chat is not offered |

Personal Google corpus

| Limitation | What you may notice |
|------------|---------------------|
| Opt-in / re-link | Needs OAuth consent; vault rekey without re-link breaks decrypt until re-auth |
| Private only | Never treated as product SoT or shared tribal knowledge |

Privacy and data

| Limitation | What you may notice |
|------------|---------------------|
| Shared vs personal | Org/shared knowledge is separate from personal corpora where configured |
| Retention | Logs and backups follow operator policy — see PRIVACY_NOTICE.md |

When something looks wrong

  1. Check STATUS.md if published for this install
  2. Retry once; try a new chat for stuck threads
  3. Contact SUPPORT.md with time, browser, and what you expected

Operators track deeper governance residuals on the internal release board; those are not member-actionable unless support says otherwise.

End.