Instructions to use davidnichols-ops/adaptive-operator-v4 with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- MLX
How to use davidnichols-ops/adaptive-operator-v4 with MLX:
# Make sure mlx-lm is installed # pip install --upgrade mlx-lm # Generate text with mlx-lm from mlx_lm import load, generate model, tokenizer = load("davidnichols-ops/adaptive-operator-v4") prompt = "Write a story about Einstein" messages = [{"role": "user", "content": prompt}] prompt = tokenizer.apply_chat_template( messages, add_generation_prompt=True ) text = generate(model, tokenizer, prompt=prompt, verbose=True) - Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- LM Studio
- Pi
How to use davidnichols-ops/adaptive-operator-v4 with Pi:
Start the MLX server
# Install MLX LM: uv tool install mlx-lm # Start a local OpenAI-compatible server: mlx_lm.server --model "davidnichols-ops/adaptive-operator-v4"
Configure the model in Pi
# Install Pi: npm install -g @earendil-works/pi-coding-agent # Add to ~/.pi/agent/models.json: { "providers": { "mlx-lm": { "baseUrl": "http://localhost:8080/v1", "api": "openai-completions", "apiKey": "none", "models": [ { "id": "davidnichols-ops/adaptive-operator-v4" } ] } } }Run Pi
# Start Pi in your project directory: pi
- MLX LM
How to use davidnichols-ops/adaptive-operator-v4 with MLX LM:
Generate or start a chat session
# Install MLX LM uv tool install mlx-lm # Interactive chat REPL mlx_lm.chat --model "davidnichols-ops/adaptive-operator-v4"
Run an OpenAI-compatible server
# Install MLX LM uv tool install mlx-lm # Start the server mlx_lm.server --model "davidnichols-ops/adaptive-operator-v4" # Calling the OpenAI-compatible server with curl curl -X POST "http://localhost:8080/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "davidnichols-ops/adaptive-operator-v4", "messages": [ {"role": "user", "content": "Hello"} ] }' - Hermes Agent
How to use davidnichols-ops/adaptive-operator-v4 with Hermes Agent:
Start the MLX server
# Install MLX LM: uv tool install mlx-lm # Start a local OpenAI-compatible server: mlx_lm.server --model "davidnichols-ops/adaptive-operator-v4"
Configure Hermes
# Install Hermes: curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash hermes setup # Point Hermes at the local server: hermes config set model.provider custom hermes config set model.base_url http://127.0.0.1:8080/v1 hermes config set model.default davidnichols-ops/adaptive-operator-v4
Run Hermes
hermes
- Atomic Chat
- OpenClaw
How to use davidnichols-ops/adaptive-operator-v4 with OpenClaw:
Start the MLX server
# Install MLX LM: uv tool install mlx-lm # Start a local OpenAI-compatible server: mlx_lm.server --model "davidnichols-ops/adaptive-operator-v4"
Configure OpenClaw
# Install OpenClaw: npm install -g openclaw@latest # Register the local server and set it as the default model: openclaw onboard --non-interactive --mode local \ --auth-choice custom-api-key \ --custom-base-url http://127.0.0.1:8080/v1 \ --custom-model-id "davidnichols-ops/adaptive-operator-v4" \ --custom-provider-id mlx-lm \ --custom-compatibility openai \ --custom-text-input \ --accept-risk \ --skip-health
Run OpenClaw
openclaw agent --local --agent main --message "Hello from Hugging Face"
Two questions about the adaptive-operator-v4 run
Read the adaptive-operator-v4 card β LoRA SFT then DPO on a vast.ai Blackwell, ~3 hours, ~$0.30 of GPU, flash-attn never building on 3.12 with CUDA 13. I'm building Symbioza: you bring the workload, we build the environment and run it. What was the most annoying part? And is there a next run?
Replying here since your answer landed on the reality-1.1 thread. That's the answer I was after β thanks. The toolchain tax (CUDA-13 nightly torch, flash-attn JIT matching, two venv rebuilds) is the part we'd take on; the DPO-pair prep isn't. Two follow-ups: roughly when is v5, and how often do runs like it happen for you β monthly, weekly? No pitch until there's something to show.
Sorry for replying in the wrong thread!
v5 timing is when the eval harness is ready, not when the calendar says so β I'm aiming for Q4 but it slips. Probably2β4 runs/year at this scale, plus maybe a dozen quick SFT probes in between. That's the honest cadence β and it's not really enough volume to make me someone's launch customer on infra alone.
What actually moves the needle for me is the agent integration you hinted at. I run the inference path itself through local agents (claude / qwen / rapid-mlx proxies on my own box) and I like the debugging loop β that's the part I'd never outsource. What I'd hand off in a heartbeat is exactly what you said you'd take: CUDA-13 nightly pin, flash-attn JIT match, two venv rebuilds, the SDPA fallback, the "is this torch wheel actually built against this CUDA" lottery. All of it.
So the real question isn't "managed GPU at $X/hr." It's "can your runtime hand me a sane env so my agents can keep driving?" If yes, I'll happily be an early user once there's a runtime. If the runtime is just a hosted notebook, I'd rather keep vast.ai + my own agents β the cost is fine, it's the friction I'd pay to delete.
No need to follow up again until there's a thing to point at. I'll see it.