The companion for local inference and AI-assisted coding

Your local AI,
on every device.

Corewire connects the runtimes you already run — Ollama, LM Studio, ComfyUI and more — across all your computers, gives every model one name your coding agents can use, and lets you drive those agents on one machine from another.

corewire launch claude-code -model mac-studio/qwen3-coder:30b

WireGuard, device to devicecomputer/modelFree for 10 devices

01 · Connect

Bring the runtimes you already run

Corewire finds Ollama, LM Studio, ComfyUI and the rest on each machine and shares them with your other devices over an encrypted network only your devices can join — direct, device to device, no ports to open.

Fig. 01 · Your devices
gaming-pcubuntu-boxmac-studiolaptopphone
On mac-studio
corewire runtimesNAME      STATE          MODELS  SHARED  VERSION  ADDRESSollama    answering      3       yes     0.14.3   http://127.0.0.1:11434comfyui   answering      0       no      0.3.66   http://127.0.0.1:8188lmstudio  not installed  0       yes     —        http://127.0.0.1:1234 corewire runtimes install lmstudio

Adopted where it runs, or installed through the machine’s own package manager — Homebrew, winget, uv — with the exact command shown before anything runs, and never with administrator rights. Each runtime is shared with your other devices, or kept to its machine, with one switch.

Share Ollama across your devices →

02 · Use

Every model, from every agent, by one name

Your laptop’s coding agent runs on the Mac Studio’s model without a config file edited or a port opened.

On laptop
corewire modelsNAME                          RUNTIME   STATE    WORKS WITHmac-studio/qwen3-coder:30b    ollama    serving  claude-code, codex, opencodegaming-pc/openai/gpt-oss-20b  lmstudio  serving  claude-code, codex, opencode OpenAI clients: http://127.0.0.1:36121/v1   Anthropic clients: http://127.0.0.1:36121 corewire launch claude-code -model mac-studio/qwen3-coder:30bstarting Claude Code on mac-studio/qwen3-coder:30b through this device's gateway (key 9f2c41d07e5ab316)
U-01

One name, on every device

A model is computer/model — mac-studio/qwen3-coder:30b, gaming-pc/openai/gpt-oss-20b — and it means the same thing from every machine you own. The endpoint on each device speaks OpenAI chat, completions, Responses and embeddings, and Anthropic Messages, and relays each request to a runtime that speaks it natively.

U-02

Agents, launched in one line

corewire launch starts Claude Code, Codex, OpenCode, Pi, Hermes, OpenClaw or Continue on any model, configured for that run only — your own settings are left alone — and corewire agents install puts one on a machine with its own package manager. A model the agent cannot talk to is refused before anything starts, with the models that would work.

U-03

A key per tool

Every editor, script and agent gets its own gateway key: corewire keys new -label "Zed on this laptop" -scopes models. It reaches your models and nothing else, is stored only as a hash, and is revoked in one command.

U-04

An MCP hub

Any MCP server — curated, from the MCP Registry, imported from Claude, Cursor, VS Code or Codex, or your own — on one machine, usable by the agents on all of them through Corewire's /mcp. Nothing is shared until you switch it on.

03 · Drive

Start an agent on one machine, drive it from another

Run a coding agent on the Mac Studio from your laptop. It lives there in a terminal that outlives your connection: detach, close the lid, attach again and see what you missed — the way tmux works. When it starts a dev server, forward it and it opens on your laptop.

On mac-studio, once
corewire sessions enable -workspace ~/code -agents opencode,claude-coderemote sessions are on: opencode, claude-code may start in /Users/you/code
On laptop
corewire sessions open -node mac-studio -agent opencode -workspace '~/code/app'session mac-studio/3f9a1c07b2e4d856 started — Ctrl-] detaches, and it keeps running corewire sessions attach mac-studio/3f9a1c07b2e4d856corewire forward mac-studio:5173http://localhost:5173 → OpenCode started a server on :5173 on mac-studio

Only your own devices

A session can run code, so it runs only between one person's devices — never a teammate's, even in a shared space.

Off until you say so

Sessions are switched on at the machine that hosts them, for the folders and agents you name. Never from another device.

Recorded, not watched

Every open, attach and end is a line in an audit log on the host: who, what, where, when — never what was typed.

A kill switch

corewire sessions kill all ends everything a machine hosts, at once, and turns sessions off.

NextFrom your phone

04 · Studio

Media, powered by ComfyUI

ComfyUI is where new image, video and audio models land first, so Corewire does not compete with it — it carries it. Install it with comfy-cli, start it, and let your other devices open its web interface over an encrypted forward that stays off until you switch it on.

Coming

Studio — a gallery of templates that run through Comfy-Org’s own comfy-mcp, with the full node editor one click away.

On laptop
corewire forward mac-studio:comfyuihttp://localhost:8188 → ComfyUI on mac-studio

05 · Works with

Runtimes

  • Ollama
  • LM Studio
  • ComfyUI
  • MLX LM
  • MTPLX
  • oMLX
  • vLLM
  • SGLang
  • Docker Model Runner
  • Lemonade
  • Any OpenAI-compatible endpoint

Coding agents

  • Claude Code
  • Codex
  • OpenCode
  • More agents coming

And any editor or script that takes an OpenAI- or Anthropic-compatible base URL, with a key of its own.

Product names belong to their owners. Corewire works with these projects and is not affiliated with them.

06 · Why trust it

Private by architecture, not by promise

Prompts, code, outputs and models never touch our servers. A coordinator introduces your devices and steps out of the way; traffic goes device to device over WireGuard, and where two cannot reach each other the fallback relay carries only bytes it cannot read.

Nothing widens from afar

Sharing a runtime, allowing sessions, publishing a port, minting a key, running an install: each is changed at the machine itself, never over the network — so one lost laptop cannot open up your other machines.

Keys you can scope and revoke

Each tool holds its own key — limited to models, or to a few of them, and revocable in one command — never the token that runs Corewire itself, which no tool needs.

07 · Pricing

Free for personal use

Personal use is entirely free: 10 devices, every feature, no card, nothing that expires. Pro raises the ceilings; only relayed traffic is ever metered.

See pricing

08 · Questions

Answers before you ask

Do I have to change how I run Ollama or LM Studio?

No. Corewire looks for each runtime where it normally listens and relays its own API — models stay where the runtime keeps them, pulled the way you already pull them. If a runtime is missing, Corewire can install it through the machine's own package manager, and shows you the exact command before it runs.

Which agents work with which models?

An agent needs a model whose runtime speaks its API: Claude Code needs Anthropic Messages, Codex the Responses API, OpenCode chat completions. Current Ollama and LM Studio speak all three. corewire models shows which agents each model works with.

Can someone else open a shell on my machine?

No. Sessions run only between one person's own devices, and only after that person turns them on at the machine that hosts them. Devices in a shared space refuse sessions altogether until per-member permissions exist.

How is this different from a mesh VPN?

The network underneath is the same idea: WireGuard, device to device. Corewire knows what is on it — which runtimes each machine runs, which models they serve, which agents can use them and which sessions are running where — and gives every model a name your tools can use.

Do I need to open ports or configure my router?

No. Devices find each other through the coordinator and connect directly wherever the network allows. Where it does not — hotel wifi, an office firewall — an encrypted relay carries the difference, and the app tells you when it does.

What leaves my machines?

Coordination metadata — which devices are yours and how to reach them — and monthly counts of what each served. Prompts, code, outputs, models and sessions never reach us: there is nothing to harvest and nothing to subpoena.

Which platforms?

The daemon runs on macOS, Linux and Windows; the desktop app ships for macOS and Linux, with Windows to follow. Sessions are hosted on macOS and Linux — a Windows machine can drive them, not host them yet.

Start where your models run

Install Corewire on the machine that runs Ollama, LM Studio or ComfyUI, then on your laptop. Sign in on both and they find each other.