Skip to main content
By the end of this guide a model running on your own hardware answers one step of a workflow, and a cloud model answers the next. Use it to keep cheap, high-volume steps on a local GPU while the hard steps go to a frontier model. Reliant’s servers make every model call, so they reach a local model through a machine you connected: its daemon finds the model server on that machine and relays requests to it (AI providers).

Before you begin

  • A machine that can reach the model server, usually your own computer, running the desktop app or reliant daemon start (connect your computer). A cloud machine can’t see a server on your laptop.
  • For the cloud step, any connected provider: a subscription, an API key or Reliant AI.
  • The reliant CLI v1.21 or later, signed in (Sign in and tokens).
1

Serve a model on your machine

Start Ollama with a context window big enough for agents, and pull a model. This guide uses a 0.5B model because it downloads in seconds; pick a larger, tool-capable model for real work.
terminal
terminal
LM Studio, llama.cpp and vLLM work the same way: start their OpenAI-compatible server and load a model.
2

Let your machine find it

The daemon checks localhost on ports 11434 (Ollama), 1234 (LM Studio), 8080 (llama.cpp) and 8000 (vLLM) when it connects and every minute after, and publishes the chat models it finds. Open Settings → AI providers → Local & custom to see them, with each model’s context size and whether it supports tools.From a terminal, reliant models list --local prints the same models with their ids and the machine serving each, and reliant models endpoint list shows each server a machine found, or why it couldn’t reach one.A server on another port or host isn’t detected. Add it there: Add endpoint for an address your machine reaches (or reliant models endpoint add http://gpu-box.lan:8000/v1 --machine <machine>), or Add custom endpoint for a server on the public internet (Reliant cloud) or on your LAN or VPN (Through one of my machines).
Settings flags a model whose context is under 64K, and calls one under 16K too small for agent work. For Ollama, raise it with OLLAMA_CONTEXT_LENGTH or the app’s Context length setting, then click Test connection.
3

Name the local model in a workflow step

A detected model’s id is its name on the server plus @local. Here the first step runs on Ollama and the second on the fast tier of whatever cloud provider you have:
.reliant/workflows/local-draft-cloud-review.yaml
terminal
Validation checks the shape, not whether a machine serves the model; that is decided when the step runs.
4

Run it and check which model answered

Run it on the machine that serves the model. Add --daemon <machine> if that isn’t your default machine:
terminal
terminal
Ollama’s own log shows the draft step reached it:
terminal
The 0.5B model’s draft is rough, which is what the cloud review step is for.

What this does not do

  • It doesn’t keep your prompts off Reliant’s servers. Only inference runs on your hardware. The prompt and the reply pass through Reliant and are stored in your chat (Privacy & Security).
  • It doesn’t work while that machine is away. The model is reached through the machine that found it. When that machine is offline or the server stops, the step fails until it is back.
  • It doesn’t make a small model an agent. A step that edits files needs a model that supports tools and a 64K or larger context. The steps above give the agents no tools.

Troubleshooting

None of your connected machines published that model. Start the server, check the name with curl http://localhost:11434/v1/models, and wait up to a minute for the next probe. The run retries the step a few times and then pauses. Once the model shows up, continue it with reliant workflow resume <execution-id>.
The only machine that serves the model isn’t connected. Start the desktop app or reliant daemon start on it (fix an offline machine).
--project-path has just created the project, and its machine hasn’t sent the workflows yet. Wait a minute and run the command again.

Next steps

Use your Claude or ChatGPT subscription

Connect the cloud side of the workflow with a plan you already pay for.

Use a different model for each step

Tags, explicit ids and thinking levels per node.

Write your first multi-agent workflow

A planner, an implementer and a reviewer in one file.

Model configuration

Custom models, tier order and ~/.reliant/config.yaml.