Перейти до вмісту
Oleaflyv0.4.6

Connect an API provider, a local model, or an installed CLI agent.

Цей контент ще не доступний вашою мовою.

Choose how you want to work. Oleafly can run its built-in assistant against a model API, connect to a local model, or use an installed CLI agent.

You already have…Choose…
A model API keyProviders and keys
A local model serverOllama or a custom OpenAI-compatible provider
An installed coding agentCLI agents
An external MCP clientMCP

Open Settings → AI Assistant to configure the route you want. You can keep several providers connected and switch models in chat.

Where AI requests goOleafly's assistant panel runs on your computer and connects in three ways. With a provider key, requests go online to that model provider. With Ollama, requests go to a local model on your computer and stay there. With a CLI agent, Oleafly talks to the agent program on your computer, which uses your own sign-in and contacts its own service.Your computerOnlineOleaflyAssistant panelModel providerYour API keyOllamaLocal modelCLI agentYour sign-inAgent's serviceIts own billingProviders and keysWhere AI requests goOleafly's assistant panel runs on your computer and connects in three ways. With a provider key, requests go online to that model provider. With Ollama, requests go to a local model on your computer and stay there. With a CLI agent, Oleafly talks to the agent program on your computer, which uses your own sign-in and contacts its own service.Your computerOnlineOleaflyAssistant panelModel providerYour API keyOllamaLocal modelCLI agentYour sign-inAgent's serviceIts own billing
With a provider key, your requests go to that provider. Ollama keeps them on your computer, and a CLI agent signs in with your own account and talks to its own service.
Settings → AI Assistant → Providers and keys. Expand your provider to configure it. Ollama is near the bottom of the list.
Settings → AI Assistant → Providers and keys. Expand your provider to configure it. Ollama is near the bottom of the list. Open full screenshot
  1. Open Providers and keys and expand a provider.
  2. Enter its API key and save.
  3. Oleafly checks the connection and refreshes the model list.
  4. Choose a model in the assistant, or set a default in Instructions.
OpenAI
Anthropic
Google Gemini
Perplexity
Z.AI
Groq
OpenRouter
DeepSeek
Mistral
xAI
Ollama

Each provider card in Settings links to its key setup. Ollama connects to a local model server.

Model rows show capability information when available: context size, vision, tools, and reasoning. Use a model with tool support for project work and vision for image inspection.

Verified means a tool-call check succeeded. Untested means the assistant has not verified that model; Blocked includes a reason it cannot be selected. These badges describe tool compatibility. They do not rate the quality of a model’s research or writing.

A model that can’t call tools still works for plain chat. While it’s selected, the composer says Chat only, this model cannot use tools.

Choose Refresh on a provider card when its available models change. Each provider can be refreshed once every 30 seconds; hover over the button to see how long is left. You can also add a model by its identifier.

Install and start Ollama (opens in a new tab), then download a model in Ollama. In Oleafly, open the Ollama card and choose Check for Ollama. Select an installed model once the server is found.

A local model keeps model requests on your machine. Online research tools still contact their source services when used.

Choose Add custom provider for an OpenAI-compatible service, local server, or gateway. Enter a name, base URL, and any required key. Save and choose a model.

Editing a saved provider lets you change its address. A saved key will be sent to the new address when that provider is used, so check the destination before saving.

Instructions holds standing preferences and the default chat model. Use concrete instructions:

Use British spelling. Preserve citation keys. Explain changes to equations before applying them.

Personas stores named instruction presets. Skills supplies procedures for recurring research work. Explore skills →

Provider keys are encrypted in local app storage and kept out of project source files. Hosted requests go to the selected provider with the supplied context. Model API charges and CLI subscriptions are billed by their providers.

Review usage and budgets →

Image preview

AI answers couldn’t load

Try again, or search the documentation.