Harnesses & frontends: what to plug your local model into

A harness is the app or agent layer on top of an inference server. llama-server,Strata, vLLM, and Ollama run the weights. The harness talks to them over anOpenAI-compatible API. It is not the GPU stack. If/v1 is down, the harness is a very expensive timeout.

Cited from official repos and docs, checked 2026-10-12. We do not invent features — unclear items stay “not documented.” Exact serve flags for our rig stay TODO instacks.

You  →  harness (tools, memory, channels, chat UI)
          →  HTTP  OpenAI-shaped /v1
            →  llama-server :8080  /  Strata :8083  /  vLLM :8000  /  Ollama :11434
              →  R9700 (Vulkan or HIP)

Copy-paste connectPick a harnessComparison table

wtpai1

Used on our rig

William’s daily agent on the two-R9700 box. Pointed at Strata:8083 and llama-server:8080.

  • Hermes AgentUsed on our rig

    Dedicated agent CLI/desktop on top of local Qwen — not a dozen chat bridges.

Attach after /v1 is up

  1. 1. Verify ROCm — rocminfo shows gfx1201.
  2. 2. Serve official Qwen instruct — Serve Qwen. llama-server default is 127.0.0.1:8080. This site’s Strata convention is :8083.
  3. 3. Prove the API on loopback. Snippets: Connect.
  4. 4. Watch a GPU meter during that completion. VRAM and compute must move.
  5. 5. Then point the harness at that base URL. Model id must match GET /v1/models (placeholder on this site: qwen).
  6. 6. Only after a chat turn works, enable tools that can touch the filesystem or the network.

Radeon Stack Labqwen-reliable is the daily driver (Qwen3.6-35B-A3B Q5).qwen-fast-agent is Qwen 3.8 Flash on Strata. Cards:recommended stacks.

Categories

Agent harnesses

All agent

Tool loops on top of an OpenAI-compatible /v1. Coding agents, CLIs, and IDE extensions.

Chat UIs

All chat

Talk to the same server without an agent loop. Browser and desktop frontends.

Image / video

All image

Diffusion graphs on ROCm PyTorch. Not an LLM /v1 client.

Overnight research loop (this site’s YAML)

Local Hermes is a practical overnight research agent for the living tracker. It does not publish.

  1. Leave official instruct serving on /v1 (the same URL you just curled).
  2. Attach Hermes to that endpoint — Hermes notes.
  3. Point it at the weekday source list on Weekday scrape.
  4. Ask for a draft diff to the living YAML only. No invented benches. No download stats.
  5. In the morning: read the diff, run the smoke tests if a pin moved, npm run build, commit on main.
esc

Type to filter. Enter opens the first match. Full-text search lives on /search.