Understand the product loop from upload to grounded answers.

LiquidLM is a knowledge product with a documented API and MCP surface. Start with the product guides, then jump into the generated API and tool references when you need exact fields or commands.

• Indexing pipeline — How uploads, notes, links, and MCP writes become searchable knowledge.
• Search and retrieval — How hybrid retrieval, rerank, temporal metadata, and supersedes filtering shape results.
• Chat with grounded sources — How chat sessions retrieve context, stream answers, and cite knowledge from selected vaults.
• Keyboard shortcuts — Global navigation, block editing, block selection, and chat composer controls.
• Settings, auth, and scopes — CLI login, PAT fallback, token bundles, active orgs, and per-vault grants.
• Data lifecycle — Vault storage, file versions, Trash, restore, reversible forget, audit, and retention expectations.
• Sync a GitHub repository — Connect GitHub and keep repositories synced into a vault, with automatic updates and delete propagation.
• Connect your AI assistant — Native OAuth first, LiquidLM CLI login and stdio second, PAT last.
• Connect LiquidLM in ChatGPT web — ChatGPT web setup: native OAuth first, CLI-managed OAuth second, PAT only as a last fallback.
• Connect LiquidLM in Codex — Codex setup: native OAuth first, CLI-managed OAuth second, PAT only as a last fallback.
• Connect LiquidLM in Claude Code — Claude Code setup: native OAuth first, CLI-managed OAuth second, PAT only as a last fallback.
• Connect LiquidLM in OpenCode — OpenCode setup: native OAuth first, CLI-managed OAuth second, PAT only as a last fallback.
• Connect LiquidLM in Cursor editor and CLI — Cursor editor and CLI setup: native OAuth first, CLI-managed OAuth second, PAT only as a last fallback.
• Connect LiquidLM in Claude Desktop — Claude Desktop setup: native OAuth first, CLI-managed OAuth second, PAT only as a last fallback.
• Authenticate local and headless agents — OAuth remains the default. Reuse a CLI-managed OAuth session before considering a PAT.
• Command-line reference — Install status, login, workspace selection, vault operations, local media fetch, search, and MCP client setup.
• MCP tool reference — Eight native LiquidLM tools plus standard search and fetch compatibility aliases.
• REST API reference — Generated OpenAPI reference for every canonical /v1 route, with field-level schemas and scope badges.
• Changelog — Product and platform updates for LiquidLM — CLI fetch, MCP OAuth, and more.