An open-source coding assistant for IDEs and a CLI whose model providers you configure, with a provider overview that lists Ollama for local models beside hosted providers.
Our description, from the pages we read, as of 2026-10-20; reasoned from those pages, not observed running.
Runs onThe places the vendor's own pages say the product runs: your machine, a container environment you run, or a cloud service the vendor runs. It is not a limit.
Models runWhere the vendor's own pages say the product's models run, not a limit: your machine, a container environment you run, the model company's cloud (servers of the company that makes or serves the model), or a cloud provider's model service. For a cloud, read the data and compliance lines of the company running it, linked by its name.
Several providers in one sessionOne session can use models from different providers, for example one agent on one maker's model and another on a second maker's. Switching the single model for the whole session does not count on its own. A tool that is itself a gateway or library routing to the providers its page names counts.
Several endpoints built inThe tool itself can hold more than one provider or address, so nothing has to sit in front of it to reach different providers.
Local and cloud togetherA local model (on your machine or in a container environment you run) and a cloud model (in its model company's cloud or a cloud provider's model service) can both be used in the same session or setup.
Use a local model: How to set it up(docs.continue.dev page, read 2026-10-22) Settings the guide names: provider, apiBase, model.
Use a local and a cloud model together: How to set it up(docs.continue.dev page, read 2026-10-22) Settings the guide names: models, provider, apiBase, roles.
Hold several endpoints in the product: How to set it up(docs.continue.dev page, read 2026-10-22) Settings the guide names: provider, apiBase, model.
Same role (harness / agent client) at the same layer (Coding agents and assistants). Up to 4 others, in alphabetical order; nothing is ranked.
Product
Several providersOne session can use models from different providers, for example one agent on one maker's model and another on a second maker's. Switching the single model for the whole session does not count on its own. A tool that is itself a gateway or library routing to the providers its page names counts.
Several endpointsThe tool itself can hold more than one provider or address, so nothing has to sit in front of it to reach different providers.
Model on your machineThe tool can use a model running on your own computer, for example through Ollama, LM Studio, oMLX or llama.cpp.
Local and cloudA local model (on your machine or in a container environment you run) and a cloud model (in its model company's cloud or a cloud provider's model service) can both be used in the same session or setup.
Words in the cells: YesA page we read says so., PartlyA page says part of it, for example separate models per agent without saying the providers can differ., Via a proxyOnly with a proxy, or a local server that imitates a cloud provider's interface, in front of the tool., NoA page we read says the product does not support it., ClaimedA vendor page says so on a marketing or overview page, and we found no guide showing how to set it up., Not foundWe read pages for it and found nothing there. It says nothing about whether the product has the feature., n/aThe question does not apply to the product, for example because it is a model server and not a tool that connects to models., BlankNothing is published for it yet.
Data and compliance
Compliance: Set by whoever runs itThe answer belongs to whoever runs the software, because open-source software has no maker running it for you., for their own deployment.
Data: Set by whoever runs itThe answer belongs to whoever runs the software, because open-source software has no maker running it for you., with telemetry not checked yetWe have not read a page of the right kind for this question yet..
Model and where it runs: Run by its operator.
Details: What the project's own pages state, not a compliance determination.
What the maker's own pages said on the dates shown, not a compliance determination.
GitHub page: continue(the product's own site, from our list of products; not read for these lines)
The readings behind this page
Our summary of the vendor's pages as of the dates shown on each line (2026-10-20 to 2026-10-24); confirm on the vendor's page.
Local models
Continue's provider overview lists Ollama as a way to run open-source models locally. (docs.continue.dev page, read 2026-10-20)
Cloud models
Continue's provider overview says it supports a wide range of model providers; the table lists Ollama beside hosted providers such as Amazon Bedrock and Google Gemini. (docs.continue.dev page, read 2026-10-20)
Models from different providers in one session
Continue lets the customer pick a preferred provider or add several, which enables using distinct models for separate jobs. You can also try a different model if you are unhappy with what the current model gives you. (docs.continue.dev page, read 2026-10-21)
About the product
Continue's README says Continue is a coding agent offered as a CLI, a VS Code extension and a JetBrains plugin. (github.com page, read 2026-10-24)
Our reading of vendors' pages, as of the dates shown. Confirm on the vendor's page before relying on any line that cites it. To report an error write to report@crinaro.ai