Local models keep all processing on your Mac, offering complete privacy at the cost of more processing time and battery usage.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/JerryZLiu/Dayflow/llms.txt
Use this file to discover all available pages before exploring further.
Supported Engines
Dayflow supports three local inference engines:Ollama
Default port:
11434Popular open-source modelsLM Studio
Default port:
1234User-friendly GUI for model managementCustom
Any OpenAI-compatible endpointBring your own server
Installing Ollama
Download Ollama
Visit https://ollama.com and download the macOS installer
Pull a model
Installing LM Studio
Download LM Studio
Visit https://lmstudio.ai and download the latest version
Launch and download a model
Open LM Studio, browse the model library, and download a vision-capable model
LM Studio documents full offline operation once models are downloaded. No internet connection required after setup.Source: https://lmstudio.ai/docs/app/offline
Configuring in Dayflow
Set endpoint URL
- Ollama:
http://localhost:11434 - LM Studio:
http://localhost:1234 - Custom: Enter your server URL
Model Selection
Dayflow reads available models from your local engine:UserDefaults and persisted across app launches.
Recommended Models
For vision tasks (screenshot analysis), use models with multimodal capabilities:- Ollama:
llama3.2-vision:11b,minicpm-v,llava - LM Studio: Look for models tagged with “vision” or “multimodal”
Performance Considerations
Processing Speed
Local models process each screenshot individually: Total: 33+ LLM calls per 15-minute batchGPU Acceleration on Apple Silicon
Both Ollama and LM Studio leverage Metal (Apple’s GPU framework) for acceleration:Battery and Power Trade-offs
Local inference is GPU-intensive:- Battery drain: Expect 20-40% higher battery consumption during processing
- Heat: MacBook may run warmer under sustained inference load
- Best practice: Keep your Mac plugged in during processing
- Processing schedule: Consider processing batches only when charging
Ollama GPU acceleration documentation: https://github.com/ollama/ollama/blob/main/docs/gpu.md
Privacy Benefits
All data stays on your Mac:- Screenshot capture: Stored locally in
~/Library/Application Support/Dayflow/recordings/ - Model inference: Runs entirely on-device via localhost
- Timeline data: Saved in local SQLite database
- No internet required: After initial model download, works completely offline
Custom Endpoints
The Custom engine option allows any OpenAI-compatible API:- Must support OpenAI-compatible
/chat/completionsendpoint - Must support vision/multimodal input (base64 images)
- Must return responses in OpenAI format
Optional API Key
For custom endpoints requiring authentication:Authorization: Bearer <key> header if configured.
Troubleshooting
Server Not Responding
If Dayflow can’t connect to your local server:-
Verify the server is running:
- Check port conflicts: Ensure nothing else is using the port
- Firewall: Verify macOS firewall isn’t blocking localhost connections
Model Not Found
If the model isn’t listed in Dayflow:- Ensure the model is fully downloaded
- Restart the local inference server
- Refresh the model list in Dayflow settings
Slow Processing
If processing is taking too long:- Use a smaller model: Try a quantized or smaller parameter version
- Reduce screenshot frequency: Fewer frames = fewer LLM calls
- Batch processing: Let multiple batches accumulate before processing
- Check GPU usage: Verify Metal acceleration is active in Activity Monitor
Quality Issues
If timeline quality is poor:- Try a larger/better model: Larger vision models produce better descriptions
- Experiment with prompts: Fork Dayflow and customize the prompt templates in
OllamaProvider.swift - Consider switching providers: Gemini or ChatGPT/Claude may provide better results for your use case