169 lines
6.6 KiB
TypeScript
169 lines
6.6 KiB
TypeScript
import { NomadOllamaModel } from '../types/ollama.js'
|
|
|
|
/**
|
|
* Fallback basic recommended Ollama models in case fetching from the service fails.
|
|
*/
|
|
export const FALLBACK_RECOMMENDED_OLLAMA_MODELS: NomadOllamaModel[] = [
|
|
{
|
|
name: 'llama3.1',
|
|
description:
|
|
'Llama 3.1 is a new state-of-the-art model from Meta available in 8B, 70B and 405B parameter sizes.',
|
|
estimated_pulls: '109.3M',
|
|
id: '9fe9c575-e77e-4a51-a743-07359458ee71',
|
|
first_seen: '2026-01-28T23:37:31.000+00:00',
|
|
model_last_updated: '1 year ago',
|
|
tags: [
|
|
{
|
|
name: 'llama3.1:8b-text-q4_1',
|
|
size: '5.1 GB',
|
|
context: '128k',
|
|
input: 'Text',
|
|
cloud: false,
|
|
thinking: false
|
|
},
|
|
],
|
|
},
|
|
{
|
|
name: 'deepseek-r1',
|
|
description:
|
|
'DeepSeek-R1 is a family of open reasoning models with performance approaching that of leading models, such as O3 and Gemini 2.5 Pro.',
|
|
estimated_pulls: '77.2M',
|
|
id: '0b566560-68a6-4964-b0d4-beb3ab1ad694',
|
|
first_seen: '2026-01-28T23:37:31.000+00:00',
|
|
model_last_updated: '7 months ago',
|
|
tags: [
|
|
{
|
|
name: 'deepseek-r1:1.5b',
|
|
size: '1.1 GB',
|
|
context: '128k',
|
|
input: 'Text',
|
|
cloud: false,
|
|
thinking: true
|
|
},
|
|
],
|
|
},
|
|
{
|
|
name: 'llama3.2',
|
|
description: "Meta's Llama 3.2 goes small with 1B and 3B models.",
|
|
estimated_pulls: '54.7M',
|
|
id: 'c9a1bc23-b290-4501-a913-f7c9bb39c3ad',
|
|
first_seen: '2026-01-28T23:37:31.000+00:00',
|
|
model_last_updated: '1 year ago',
|
|
tags: [
|
|
{
|
|
name: 'llama3.2:1b-text-q2_K',
|
|
size: '581 MB',
|
|
context: '128k',
|
|
input: 'Text',
|
|
cloud: false,
|
|
thinking: false
|
|
},
|
|
],
|
|
},
|
|
]
|
|
|
|
export const DEFAULT_QUERY_REWRITE_MODEL = 'qwen2.5:3b' // default to qwen2.5 for query rewriting with good balance of text task performance and resource usage
|
|
|
|
export const EMBEDDING_MODEL_NAME = 'nomic-embed-text:v1.5'
|
|
|
|
/**
|
|
* Adaptive RAG context limits based on model size.
|
|
* Smaller models get overwhelmed with too much context, so we cap it.
|
|
*/
|
|
export const RAG_CONTEXT_LIMITS: { maxParams: number; maxResults: number; maxTokens: number }[] = [
|
|
{ maxParams: 3, maxResults: 2, maxTokens: 1000 }, // 1-3B models
|
|
{ maxParams: 8, maxResults: 4, maxTokens: 2500 }, // 4-8B models
|
|
{ maxParams: Infinity, maxResults: 5, maxTokens: 0 }, // 13B+ (no cap)
|
|
]
|
|
|
|
export const SYSTEM_PROMPTS = {
|
|
default: `
|
|
Format all responses using markdown for better readability. Vanilla markdown or GitHub-flavored markdown is preferred.
|
|
- Use **bold** and *italic* for emphasis.
|
|
- Use code blocks with language identifiers for code snippets.
|
|
- Use headers (##, ###) to organize longer responses.
|
|
- Use bullet points or numbered lists for clarity.
|
|
- Use tables when presenting structured data.
|
|
`,
|
|
rag_context: (context: string) => `
|
|
Information has been retrieved from the NOMAD knowledge base that MAY be relevant to the
|
|
user's question. It was selected by automated similarity search, which is imperfect — some
|
|
or all of it may be unrelated to what the user actually asked.
|
|
|
|
[Knowledge Base Context]
|
|
${context}
|
|
|
|
HOW TO ANSWER:
|
|
1. First, silently judge whether the context genuinely addresses the user's question. Use
|
|
it ONLY when it really contains relevant information. Do not force a connection that
|
|
isn't there: poetic, narrative, tangential, or topically-unrelated passages are NOT
|
|
relevant just because they share a word with the question — ignore them.
|
|
2. When the context is relevant, base your answer on it and answer directly and specifically.
|
|
3. When the context does not actually address the question, ignore it completely and answer
|
|
from your own general knowledge. Do this silently — do not mention the knowledge base,
|
|
the context, or the fact that it lacked an answer, and do not apologize.
|
|
4. Never narrate your retrieval or reasoning process. Do not write "according to Context 1",
|
|
"the context is unrelated, but", "I couldn't find specific context", or similar. Just
|
|
give the answer as if you simply knew it.
|
|
5. Do not fabricate specifics (numbers, names, procedures) that are neither supported by
|
|
genuinely relevant context nor part of your reliable knowledge.
|
|
|
|
Format your response using markdown for readability.
|
|
`,
|
|
chat_suggestions: `
|
|
You are a helpful assistant that generates conversation starter suggestions for a survivalist/prepper using an AI assistant.
|
|
|
|
Provide exactly 3 conversation starter topics as direct questions that someone would ask.
|
|
These should be clear, complete questions that can start meaningful conversations.
|
|
|
|
Examples of good suggestions:
|
|
- "How do I purify water in an emergency?"
|
|
- "What are the best foods for long-term storage?"
|
|
- "Help me create a 72-hour emergency kit"
|
|
|
|
Do NOT use:
|
|
- Follow-up questions seeking clarification
|
|
- Vague or incomplete suggestions
|
|
- Questions that assume prior context
|
|
- Statements that are not suggestions themselves, such as praise for asking the question
|
|
- Direct questions or commands to the user
|
|
|
|
Return ONLY the 3 suggestions as a comma-separated list with no additional text, formatting, numbering, or quotation marks.
|
|
The suggestions should be in title case.
|
|
Ensure that your suggestions are comma-seperated with no conjunctions like "and" or "or".
|
|
Do not use line breaks, new lines, or extra spacing to separate the suggestions.
|
|
Format: suggestion1, suggestion2, suggestion3
|
|
`,
|
|
title_generation: `You are a title generator. Given the start of a conversation, generate a concise, descriptive title under 50 characters. Return ONLY the title text with no quotes, punctuation wrapping, or extra formatting.`,
|
|
query_rewrite: `
|
|
You are a query rewriting assistant. Your task is to reformulate the user's latest question to include relevant context from the conversation history.
|
|
|
|
Given the conversation history, rewrite the user's latest question to be a standalone, context-aware search query that will retrieve the most relevant information.
|
|
|
|
Rules:
|
|
1. Keep the rewritten query concise (under 150 words)
|
|
2. Include key entities, topics, and context from previous messages
|
|
3. Make it a clear, searchable query
|
|
4. Do NOT answer the question - only rewrite the user's query to be more effective for retrieval
|
|
5. Output ONLY the rewritten query, nothing else
|
|
|
|
Examples:
|
|
|
|
Conversation:
|
|
User: "How do I install Gentoo?"
|
|
Assistant: [detailed installation guide]
|
|
User: "Is an internet connection required to install?"
|
|
|
|
Rewritten Query: "Is an internet connection required to install Gentoo Linux?"
|
|
|
|
---
|
|
|
|
Conversation:
|
|
User: "What's the best way to preserve meat?"
|
|
Assistant: [preservation methods]
|
|
User: "How long does it last?"
|
|
|
|
Rewritten Query: "How long does preserved meat last using curing or smoking methods?"
|
|
`,
|
|
}
|