Use Cursor & Continue.dev with local Ollama agents — Locaible<br>Sign inStart free
For developers using Cursor or Continue.dev<br>Run local AI agents inside Cursor & Continue.dev<br>Locaible exposes an OpenAI-compatible API on 127.0.0.1:11435. Point Cursor or Continue.dev at it and your AI runs entirely on your machine, with pre-tuned coding agents from the Marketplace.<br>Download Locaible — freeJump to setup ↓<br>Your code never leaves your machineZero token billGDPR-safe for client repos
5-minute walkthrough — see Locaible behind Cursor end-to-end.
Pre-tuned coding agents<br>Atlas (legal), Code Reviewer (OWASP-aware), Tech Support (L2/L3 runbooks) appear as 'models' in Cursor's dropdown. Each carries its own system prompt + RAG.
Per-project agents<br>One client repo with strict data-handling rules? Spin up an agent that knows your conventions and feed it your style guide + arch docs. Switch via the Cursor model menu.
Compliant by construction<br>Cursor Pro sends snippets to Anthropic/OpenAI. With Locaible behind it, the chat traffic stops at 127.0.0.1. Defensible to your CISO and any DPO audit.
Setup — 3 minutes<br>Same flow for Cursor and Continue.dev. Substitute your endpoint and you're done.<br>Install Locaible and create a coding agent<br>Pick a model that fits your hardware — qwen3:8b for fast iteration, qwen3:14b for serious refactors, deepseek-coder:33b if you have a 48 GB rig. Locaible installs Ollama for you on first launch.<br>Get the desktop app
Start the local OpenAI API in Locaible<br>Settings → Local API → Start. Locaible binds a server on 127.0.0.1:11435 that speaks the OpenAI spec and exposes your agents as virtual models.<br># Verify it's up<br>$ curl http://localhost:11435/v1/models<br>{ "object": "list", "data": [<br>{ "id": "atlas", "object": "model", "owned_by": "locaible" },<br>{ "id": "code-reviewer", "object": "model", ... }<br>] }
Point Cursor (or Continue) at the endpoint<br>Cursor
Cmd/Ctrl + , → Models<br>Toggle OpenAI API Key on. Paste any non-empty string as key.<br>Click Override OpenAI Base URL , paste:http://localhost:11435/v1
In the model dropdown of the chat: type atlas (or your agent name) and select it.
Continue.dev (full-local)
Install Continue VS Code extension.<br>Edit ~/.continue/config.json — add:<br>"models": [<br>"title": "Locaible · Atlas",<br>"provider": "openai",<br>"model": "atlas",<br>"apiKey": "noop",<br>"apiBase": "http://localhost:11435/v1"<br>}Continue also supports local Tab autocomplete via Ollama — Cursor's autocomplete stays on their cloud.
What works, what doesn't<br>Brutal honesty so you don't discover the gaps after switching.<br>FeatureCursor + LocaibleContinue.dev + LocaibleChat with code context local localInline edit (Cmd+K style) local localTab autocomplete⚠ cloud localCodebase indexing (full repo)⚠ cloud localAgent / autonomous edits⚠ limited⚠ limitedSwitch between Locaible agents local localYour code never leaves the laptop⚠ partial local<br>Bottom line: Cursor + Locaible is the right call if you want to keep Cursor's UX and only offload the heavy chat/edit traffic to your machine. If full-local is a hard constraint (regulated industry, defence, finance), Continue.dev + Locaible is the path.
Pro tip: lock Cursor to Locaible per project
Drop a .cursorrules file at your repo root telling Cursor (and your future self) which Locaible agent to use. Especially useful for client work — you can't accidentally send their code to OpenAI.<br># .cursorrules — committed to the repo<br># All AI assistance for this codebase MUST go through the local<br># Locaible endpoint. Selected model: atlas-acmecorp.<br># Endpoint: http://localhost:11435/v1/chat/completions<br># Reason: client NDA + GDPR Art. 28 forbid third-party processors<br># for source code. Locaible runs 100% on the dev's machine.
Get your Cursor running on your own machine<br>Free tier covers 3 agents and 1 device. Enough to try every step on this page.<br>Download LocaibleGet Continue.dev
© 2026 Locaible. Sovereign AI for everyone.