LLM Providers
Supported remote LLM providers, model guidance, and known caveats for AI Now and agent workflows
Choose your setup in three layers:
- Plan or subscription: what account or bundle you already pay for
- Provider or endpoint: where requests actually go
- Model: the concrete tool-capable default you run day to day
Then configure it once in Settings (or nmem CLI/TUI).
For search vector models, read Embedding providers and setup for provider choices, model examples, and index rebuild steps.
Want to keep model calls on your machine?
Follow Use Nowledge Mem with fully local models for LM Studio and Ollama setup, purpose routing, verification, and privacy boundaries.
Nowledge Mem recommends subscription-based defaults for the smoothest daily experience right now:
- OpenAI ChatGPT/Codex subscription
- Kimi Code subscription
- SuperGrok subscription
Cost-aware default recommendation
For day-to-day AI Now usage, prioritize fast tool-capable models over SOTA by default.
For ChatGPT/Codex, fetch the current model list in Settings and choose a supported Codex or base GPT-5 model. Kimi Coding Plan models are also good daily defaults.
If your current setup is spending too many tokens (for example always running gpt-5.3-codex), switch to a lighter tool-capable default first.
For an optional decision model that handles conversation screening, memory checks, and Deep Search, see Fast decisions. It is configured separately from your chat model.
What To Choose
ChatGPT/Codex Subscription
Best default for coding-heavy AI Now workflows with strong tool use support.
Kimi Code Subscription
Great for coding workflows and tool-calling in AI Now.
SuperGrok Subscription
Use your Grok subscription through xAI sign-in, without pasting an API key.
Provider Guides
- Stable tool-calling in AI Now and agents
- Strong ecosystem compatibility
- For ChatGPT Subscription, pick Codex models or base GPT-5 releases. Avoid chat aliases like
gpt-5-chat-latesthere.
- Great fit for coding-heavy AI Now sessions
- Reliable tool workflows in day-to-day usage
- Strong planning and tool use quality
- Good for long multi-step sessions
- Start with
deepseek-v4-flashfor AI Now and agents - Use
deepseek-v4-prowhen quality matters more than speed
- Flexible multi-model routing
- Pick tool-capable models for AI Now / agent workflows
- Supported in AI Now and agent flows
- Smooth fit with Google AI Studio credentials
- Supported with tool workflows in AI Now
- Use this path when you have an xAI API key
- Use SuperGrok instead when you want to sign in with your Grok subscription
- Sign in with xAI from Settings; no API key paste is needed
- Works in AI Now and agent workflows after the local OAuth token is saved
- Keep using the xAI provider if you prefer API-key billing
- Supported in AI Now and extension workflows
- Works with current MiniMax chat models
- Supported for AI Now and agents
- Good regional/provider fit for existing usage
- No cloud dependency for model runtime
- Use tool-capable models for AI Now agents
- Default local URL:
http://127.0.0.1:1234/v1 - The API key is optional unless you enable authentication
- In remote mode, LM Studio must run on the Nowledge Mem server machine
- Use the Lemonade provider instead of a generic custom endpoint
- Default local URL:
http://127.0.0.1:13305/v1 - AI Now can also use Lemonade's HTTP MCP endpoint when you add it as a custom MCP server
- Supported in AI Now
- Low-friction if your team already uses Copilot
- Requires OpenAI-compatible chat completions
- Tool support depends on your gateway/model
DeepSeek model hint
Use deepseek-v4-flash for the quickest DeepSeek setup in AI Now and agent tasks. Choose deepseek-v4-pro when you want the stronger V4 model. deepseek-chat still works, but deepseek-reasoner is not offered for agent workflows because it does not support tool calling.
Context Window
Every model has a maximum number of tokens it can process in a single request. Nowledge Mem auto-detects this limit from the model name. For example, gpt-4o defaults to 128k tokens, gemini-2.0-flash to 1M.
You can override the context window in Settings → Providers → Advanced (or via nmem config provider set --context-window <tokens>).
When to adjust:
- Small or fine-tuned models (8k–32k context): set the actual limit so that AI Now compacts the conversation before it overflows.
- Extended-context models (500k–1M+): increase the window so AI Now uses the full capacity instead of compacting early.
- Custom or self-hosted models: if the model name doesn't match a known pattern, the default is 128k. Set the real value to get accurate compaction behavior.
What happens during compaction
When a conversation approaches the context limit, AI Now automatically summarizes older messages and keeps the most recent exchanges. This lets long sessions continue without losing important context. Setting the right context window ensures compaction fires at the right time, not too early, not too late.
Custom Provider Guidance
If you configure a custom OpenAI-compatible endpoint (openai_compatible) for DeepSeek V4, use deepseek-v4-flash, deepseek-v4-pro, or the exact DeepSeek V4 model id your gateway exposes. DeepSeek V4 uses a provider-specific thinking mode; Mem disables that mode during tool-loop agent calls so tool history remains compatible with strict DeepSeek validation.
If you run DeepSeek V4 through OpenRouter, keep using the OpenRouter provider. Mem leaves OpenRouter-hosted models on OpenRouter's own request contract instead of adding DeepSeek-native thinking fields.
Custom endpoints also support the newer Responses API (/v1/responses) alongside the legacy Chat Completions format. Select the API format when adding or editing the provider.
For Linux headless deployment setup, see Linux Server Deployment.
Use Nowledge Mem with fully local models
Keep memory processing, agents, embeddings, and enabled enrichment on your own machine with LM Studio, Ollama, or another local endpoint
Embedding providers and setup
Choose a search index model, configure remote or local embeddings, and verify the rebuilt index