Locaible routes Cursor and Continue.dev AI traffic to local Ollama agents
Locaible is a desktop app that exposes an OpenAI-compatible API on `127.0.0.1:11435`, letting Cursor and Continue.dev users run pre-tuned local AI coding agents via Ollama so that code never leaves the machine.
Score breakdown
Locaible gives Cursor users a concrete path to keeping chat and inline-edit traffic entirely on-device, which the post frames as defensible for GDPR Art. 28 compliance and client NDA scenarios where sending source code to third-party processors is forbidden.
- 01Locaible binds a local OpenAI-compatible API server at `127.0.0.1:11435` that Cursor and Continue.dev can be pointed at.
- 02Pre-tuned Marketplace agents include Atlas (legal), Code Reviewer (OWASP-aware), and Tech Support (L2/L3 runbooks), each with its own system prompt and RAG.
- 03Supported local models include `qwen3:8b`, `qwen3:14b`, and `deepseek-coder:33b`; Locaible installs Ollama automatically on first launch.
Locaible is a desktop application that sits between Cursor or Continue.dev and the underlying AI model, exposing a local OpenAI-compatible API at `127.0.0.1:11435`. When Cursor is configured to use this endpoint, chat and inline-edit traffic is handled entirely on the developer's machine via Ollama rather than being sent to Anthropic or OpenAI. The app installs Ollama automatically on first launch and supports models including `qwen3:8b`, `qwen3:14b`, and `deepseek-coder:33b` depending on available hardware.
Developers can also create per-project agents scoped to a specific repo's conventions and style guide, switchable via the model menu.
Pre-tuned coding agents from the Locaible Marketplace — Atlas (legal), Code Reviewer (OWASP-aware), and Tech Support (L2/L3 runbooks) — surface as virtual models in the editor's model dropdown, each bundled with its own system prompt and RAG setup. Developers can also create per-project agents scoped to a specific repo's conventions and style guide, switchable via the model menu. A `.cursorrules` file committed to the repo can lock a project to a specific Locaible agent, preventing accidental data leakage to third-party processors.
The post is candid about limitations: with Cursor, tab autocomplete and codebase indexing still route through Cursor's cloud, and autonomous agent edits are described as limited. Continue.dev paired with Locaible achieves a fully local setup including tab autocomplete. The post recommends Cursor + Locaible for developers who want to preserve Cursor's UX while keeping chat and edit traffic local, and Continue.dev + Locaible for environments where full-local is a hard requirement, such as regulated industries. The free tier covers 3 agents and 1 device.
Key facts
- 01Locaible binds a local OpenAI-compatible API server at `127.0.0.1:11435` that Cursor and Continue.dev can be pointed at.
- 02Pre-tuned Marketplace agents include Atlas (legal), Code Reviewer (OWASP-aware), and Tech Support (L2/L3 runbooks), each with its own system prompt and RAG.
- 03Supported local models include `qwen3:8b`, `qwen3:14b`, and `deepseek-coder:33b`; Locaible installs Ollama automatically on first launch.
- 04With Cursor + Locaible, tab autocomplete and codebase indexing still use Cursor's cloud; Continue.dev + Locaible achieves a fully local setup.
- 05Per-project agents can be locked in via a `.cursorrules` file committed to the repo.
- 06The free tier covers 3 agents and 1 device.
Topics
Summary and scoring are generated automatically from the original article. We always link back to the publisher and never republish images or paywalled content. Last processed Jun 11, 2026 · 08:34 UTC. How this works →