Remote Workflows

One of mold's best deployment patterns is simple:

• run mold serve on the GPU machine
• point MOLD_HOST at it from everywhere else

That gives you local-first ergonomics with remote GPU horsepower.

Basic Laptop → GPU Server

On the GPU host:

mold serve --bind 0.0.0.0 --port 7680

From your laptop or devbox:

export MOLD_HOST=http://gpu-host:7680
mold run "a cinematic portrait"

Recommended Pattern

1. mold pull models on the GPU host, not from every client machine.
2. Keep the server running so models stay warm between requests.
3. Use mold ps to confirm the client can reach the server.
4. Set HF_TOKEN on the server if you use gated Hugging Face repos.

OpenClaw and Discord

Remote workflows pair well with both:

• OpenClaw when you want agent-driven generation
• Discord Bot when you want a chat interface

In both cases, the key variable is still MOLD_HOST.

Remote Pulls vs Local Pulls

Behavior depends on where the command runs:

• mold pull against a reachable server downloads onto that server
• if no server is reachable, the CLI falls back to local pulling

That distinction matters if your laptop has little disk space or no GPU.

Example Multi-Client Setup

Machine	Role
GPU host	Runs mold serve, stores model files
Laptop	Runs mold run, mold list, mold ps
Discord worker	Runs mold discord or mold serve --discord
OpenClaw host	Uses mold via MOLD_HOST

Deployment Choices

• Docker & RunPod for cloud or containerized GPUs
• NixOS for declarative infra
• Deployment Overview for the high-level options

Remote Troubleshooting

If remote generation fails:

• verify MOLD_HOST
• check firewall and bind address
• run mold ps
• hit /health directly with curl

curl http://gpu-host:7680/health
curl http://gpu-host:7680/api/status