grid-operations

Deploy and manage local LLM models across a fleet of machines using the Grid CLI.

465|41|Updated Aug 4, 2026
One-click install
npx skills add https://github.com/autonomous-ai/openharness --skill grid-operations-autonomous-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grid-operations
Source: https://github.com/autonomous-ai/openharness/tree/main/store/agents/autonomous-grid/skills/grid-operations
Command: npx skills add https://github.com/autonomous-ai/openharness --skill grid-operations-autonomous-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Running local language models across one laptop or a fleet of machines involves many error-prone steps: checking hardware capacity, finding and downloading the right GGUF weights, sizing context and concurrency, starting the engine, and verifying it actually answers. This Skill guides an agent through that entire lifecycle safely, avoiding common failures like oversized context windows, missing vision projectors, and unverified deployments. ## Core Features & Use Cases - Guided model selection: Asks three plain-language questions (use case, context length, concurrency), then matches answers against models already on disk, the Grid catalog, or Hugging Face GGUF repos. - Safe deployment workflow: Checks host memory via device-info, verifies the llama.cpp binary directly, sizes context against usable bytes, handles vision projector files, and starts models with join using explicit --ctx-size and --max-concurrency. - Verified serving: Waits for relay registration, then proves the model answers with a single bounded max_tokens request before reporting success. - Fleet operations: Connects and selects grids, manages machines over Harness or SSH transports, changes or stops running models, and uses routing, usage, media, and training commands. - Use Case: A user asks to run a coding model on their GPU workstation. The Skill checks the workstation's free memory, finds a suitable GGUF on Hugging Face, pulls it, starts it with 128K context and 2 slots, verifies it responds, and tells the user to pick it from the model dropdown. ## Quick Start Ask the agent to start a coding model with long context on your GPU machine and it will check capacity, pick a fitting model, deploy it, and verify it answers.

Frequently Asked Questions about grid-operations

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a local LLM on my machine with Grid?

Run device-info to check usable memory, pick a GGUF model from disk, the catalog, or Hugging Face, then use join with explicit --ctx-size and --max-concurrency flags. Verify it answers with one bounded chat completion call using max_tokens before declaring success.

How do I find GGUF models on Hugging Face for llama.cpp?

Query the Hugging Face API with the gguf filter sorted by downloads, then list the repo's sibling files to find .gguf weights and mmproj vision projectors. Prefer official orgs like ggml-org, Qwen, or bartowski, and pick a quant size that fits your usable memory.

Why does my model fail with 'exceeds the available context size'?

This happens when the model was served with too small a context window, usually because --ctx-size was left off and the engine defaulted to 16K. Stop the instance with leave, then join again with the requested context size.

Does Grid support vision models that read images?

Yes, if the model repo contains a top-level mmproj GGUF projector file, the model can read images. The catalog does not mark vision support, so check the Hugging Face siblings list before pulling and verify the .mmproj.gguf file exists on disk after download.

Why is my newly started model not answering requests?

Right after join, the relay may not list the model yet, returning 'No providers available', and Grid sends a ~5K token probe that can hold the single slot for minutes on CPU-only hosts. Wait for relay registration and send exactly one bounded verification call rather than repeating requests.

Can I manage models on remote machines with Grid fleet?

Yes, grid-fleet run --machine targets machines configured via Harness pairing or SSH in grid-fleet.json. Harness transport is noninteractive and requires Grid fleet protocol 1, while SSH uses your existing config, keys, and known_hosts with strict host-key checking.