Nexa Bridge

Run a model on your own computer and use it in Nexa Agora: install the app, pair the computer, choose the model and place it in your order.

For everyoneConnect your tools · page 9 of 35

Nexa Bridge links a model you run on your own computer, in LM Studio, Ollama, llama.cpp or vLLM, to Nexa Agora. Your computer calls out over one encrypted line, so no port opens on your network. A bridged model spends no Nexa credits, only a daily token allowance. This page helps you install the app, pair your computer with the workspace, and use your model like any other.

Why teams use it, and what travels through Nexa: the Nexa Bridge page.

Before you start

Everyone can read the page. An owner or admin approves each computer.
Have a model server running on your computer: LM Studio, Ollama, llama.cpp or vLLM, with a model loaded.
Open Governance › Settings › Nexa Bridge.

Settings › Nexa Bridge as Tom Becker, admin, with the three promises "No open ports", "No Nexa credits, a daily allowance" and "The model stays yours". — 01A model you run on your own hardware, used in Agora like any other.

Get the app

On Settings › Nexa Bridge, go to Get Nexa Bridge and click Get the app.
The page detects your system from your browser. To download for another computer, pick another system.

Get Nexa Bridge with macOS detected and the three steps. — 02The download matches the system of the browser you use.

Download the file for your system:
macOS — a disk image.
Windows — an installer, or an MSI package for managed machines.
Linux — a Debian / Ubuntu package, or an AppImage.
Install it on the computer that runs your model.
The app starts on login and lives in the tray.

To verify the file you downloaded, open Check a file and use Copy the command. Source on GitHub opens the app's source code.

Pair the computer with your workspace

In the app, click Connect to Agora and name the computer.
The app shows a code and opens your browser on the approval page. The code lasts 10 minutes.
If you are not signed in, click Sign in. You come straight back to the page.
Read the page Approve a computer: the computer, the workspace and You approve as, with your name and role. An Expires in countdown runs.
Check that the code matches the one Nexa Bridge shows on that computer.
Under Where it joins, choose:
A new connection
its own line to Nexa's relay, for its own model. When your plan has a limit, the page shows how many connections it allows and how many you use.
Add to an existing connection
it serves the same model as the computers already there, and they share the work. This is never limited by your plan.
Click Approve this computer.
The page says Approved; waiting for Nexa Bridge on that computer to connect…, then that Nexa Bridge picked it up. The app shows Connected.

The Approve a computer page for "Studio Mac mini" joining Harbor & Pine, with the code, the Expires in countdown, and A new connection selected. — 03Approve only if the code matches the one on that computer.

The computer joins the workspace the page is open in. To approve it for another workspace, switch workspace first.

If you are a member

The page reads Owners and admins approve — Only an owner or admin can approve a computer or device.

Click Copy this page's link.
Send the link to an owner or admin. The code in it is valid for 10 minutes from when Nexa Bridge made it.

The approval page as Sara Lin, member, sees it: "Owners and admins approve", with Copy this page's link. — 04A member sends the approval link to an owner or admin.

Choose the model it serves

In the app, go to Choose model and click Find local models.
Select one loaded model.
Go to Review, check the workspace and the model, and click Connect.
The app tells Agora the exact name your model server gives that model.

On Settings › Nexa Bridge, the connection shows that name under Model served, for example Qwen3.8-27B-INT4. Agora sends every request for that model.

Choose its preset

The Preset sets how Agora runs the model you serve: for example how long it thinks before it answers. An owner or admin picks one of Nexa's presets for bridges, such as Qwen, Qwen High or Qwen Extra High.

Agora doesn't check that the preset fits your model: pick the one made for the model you serve. How to serve it shows the preset's guide for each model server, for example Load it with a context window of N tokens.

The preset then appears in Your models › Your own models, private to the workspace.

Your computers with one connection online, serving Qwen3.8-27B-INT4 with the Qwen High preset, and the daily allowance card reading "Plenty left". — 05Your computers, their state and today's allowance.

Use it in your agents' order

Open Settings › Your models, then Edit the order.
Pick your bridge's preset under On your bridge or Your own models · BYOM.
Save the order.

Settings › Your models › Your own models · BYOM, showing the bridged model "In your chain · 2nd". — 06A bridged model takes its place in the order like any other.

See Your models for the whole order.

Revoke a computer or remove a connection

In Your computers, open the computer and click Revoke this computer.
The confirmation says what stops. The other computers on the connection keep running; if it was the only one, the connection stops too.
A connection with no computers left offers Remove this connection — none of its computers is left.

To use a revoked computer again, link it again with Connect to Agora.

When something is wrong

The usual causes, in order:

The computer is off or asleep.
The model server isn't running. Start it, then click Find local models.
No model is loaded.
The computer was revoked. Click Connect to Agora again.
The computers on one connection serve different models. Select the same model on each, or give each computer its own connection.

Still stuck? In the app, click Save diagnostics. It writes a file with the version and the channel, and no secrets, that you can send to Support.

What you will see

Computer states: Online, Approved · not seen yet, Offline · last seen … and Revoked · link it again.

None of its computers can be reached now. on a connection.

Not published yet, under Model served — no computer on the connection has told Agora which model it serves. In the app, select the model and click Connect. Until then, a chain skips this bridge and tries the next model, if there is one.

Its computers serve different models — the computers sharing the connection don't serve the same model. Agora doesn't guess which one to call: select the same model on each, or give each computer its own connection.

… doesn't include bridge connections — your plan has no bridge connections.

This workspace has reached its plan's limit of N bridge connections. Revoke an unused connection or upgrade the plan for more. — with Revoke one and See plans.

Code not valid — the code has expired, was already used, or isn't known. On that computer, click Connect to Agora again for a fresh link.

Too many attempts. — wait a minute, then check again.

The daily allowance card, Your own models (Bridge and your keys), with the tokens used today and Resets at … your time. It reads Plenty left, Close to today's limit, Used up until midnight UTC or No daily limit. The count can lag a few minutes.

Your own model rests until …: today's allowance is used up. — your own models are refused until 00:00 UTC. Nexa's models in the same chain keep answering.

… is under 128K: long conversations and large documents may not fit. — the model is loaded with a small context window.

Good to know

What Nexa sees: the model runs on your hardware, and the app's keys stay in your system keychain. The line is encrypted, but Nexa's relay carries your prompts and the answers: it is not end-to-end encrypted through the relay.

The "What Nexa sees, along the line" panel. — 07What travels through Nexa's relay, and what stays on your computer.

The daily allowance is shared by Nexa Bridge and your own keys. It is set by the plan, seats add to it, and it resets at 00:00 UTC.
When the allowance is used up, your own models stop for the day, on the bridge and on your keys alike. An agent or a chain link on Nexa credits still answers, but a chain stops at its bridge or own-key link instead of moving on.
Adding a computer to a connection you already have never counts against the plan's limit.
Only builds named Nexa Bridge from Nexa's repository are Nexa's. A modified copy must carry another name.
Builds for macOS and Windows are signed. Linux files are verified by their build attestation.

Nexa Bridge

Run a model on your own computer and use it in Nexa Agora: install the app, pair the computer, choose the model and place it in your order.

For everyoneConnect your tools · page 9 of 35

Why teams use it, and what travels through Nexa: the Nexa Bridge page.

Before you start

Everyone can read the page. An owner or admin approves each computer.
Have a model server running on your computer: LM Studio, Ollama, llama.cpp or vLLM, with a model loaded.
Open Governance › Settings › Nexa Bridge.

Get the app

On Settings › Nexa Bridge, go to Get Nexa Bridge and click Get the app.
The page detects your system from your browser. To download for another computer, pick another system.

Download the file for your system:
macOS — a disk image.
Windows — an installer, or an MSI package for managed machines.
Linux — a Debian / Ubuntu package, or an AppImage.
Install it on the computer that runs your model.
The app starts on login and lives in the tray.

To verify the file you downloaded, open Check a file and use Copy the command. Source on GitHub opens the app's source code.

Pair the computer with your workspace

In the app, click Connect to Agora and name the computer.
The app shows a code and opens your browser on the approval page. The code lasts 10 minutes.
If you are not signed in, click Sign in. You come straight back to the page.
Read the page Approve a computer: the computer, the workspace and You approve as, with your name and role. An Expires in countdown runs.
Check that the code matches the one Nexa Bridge shows on that computer.
Under Where it joins, choose:
A new connection
its own line to Nexa's relay, for its own model. When your plan has a limit, the page shows how many connections it allows and how many you use.
Add to an existing connection
it serves the same model as the computers already there, and they share the work. This is never limited by your plan.
Click Approve this computer.
The page says Approved; waiting for Nexa Bridge on that computer to connect…, then that Nexa Bridge picked it up. The app shows Connected.

The computer joins the workspace the page is open in. To approve it for another workspace, switch workspace first.

If you are a member

The page reads Owners and admins approve — Only an owner or admin can approve a computer or device.

Click Copy this page's link.
Send the link to an owner or admin. The code in it is valid for 10 minutes from when Nexa Bridge made it.

Choose the model it serves

In the app, go to Choose model and click Find local models.
Select one loaded model.
Go to Review, check the workspace and the model, and click Connect.
The app tells Agora the exact name your model server gives that model.

On Settings › Nexa Bridge, the connection shows that name under Model served, for example Qwen3.8-27B-INT4. Agora sends every request for that model.

Choose its preset

The preset then appears in Your models › Your own models, private to the workspace.

Use it in your agents' order

Open Settings › Your models, then Edit the order.
Pick your bridge's preset under On your bridge or Your own models · BYOM.
Save the order.

See Your models for the whole order.

Revoke a computer or remove a connection

In Your computers, open the computer and click Revoke this computer.
The confirmation says what stops. The other computers on the connection keep running; if it was the only one, the connection stops too.
A connection with no computers left offers Remove this connection — none of its computers is left.

To use a revoked computer again, link it again with Connect to Agora.

When something is wrong

The usual causes, in order:

The computer is off or asleep.
The model server isn't running. Start it, then click Find local models.
No model is loaded.
The computer was revoked. Click Connect to Agora again.
The computers on one connection serve different models. Select the same model on each, or give each computer its own connection.

Still stuck? In the app, click Save diagnostics. It writes a file with the version and the channel, and no secrets, that you can send to Support.

What you will see

Computer states: Online, Approved · not seen yet, Offline · last seen … and Revoked · link it again.

None of its computers can be reached now. on a connection.

… doesn't include bridge connections — your plan has no bridge connections.

This workspace has reached its plan's limit of N bridge connections. Revoke an unused connection or upgrade the plan for more. — with Revoke one and See plans.

Code not valid — the code has expired, was already used, or isn't known. On that computer, click Connect to Agora again for a fresh link.

Too many attempts. — wait a minute, then check again.

Your own model rests until …: today's allowance is used up. — your own models are refused until 00:00 UTC. Nexa's models in the same chain keep answering.

… is under 128K: long conversations and large documents may not fit. — the model is loaded with a small context window.

Good to know

What Nexa sees: the model runs on your hardware, and the app's keys stay in your system keychain. The line is encrypted, but Nexa's relay carries your prompts and the answers: it is not end-to-end encrypted through the relay.

The daily allowance is shared by Nexa Bridge and your own keys. It is set by the plan, seats add to it, and it resets at 00:00 UTC.
When the allowance is used up, your own models stop for the day, on the bridge and on your keys alike. An agent or a chain link on Nexa credits still answers, but a chain stops at its bridge or own-key link instead of moving on.
Adding a computer to a connection you already have never counts against the plan's limit.
Only builds named Nexa Bridge from Nexa's repository are Nexa's. A modified copy must carry another name.
Builds for macOS and Windows are signed. Linux files are verified by their build attestation.