Skip to content

Releases

Model Farm 0.8.0

Choose a tag to compare

@acsdd acsdd released this 16 Nov 08:29

Model Farm 0.8.0

Ollama is not the only local runtime, and it is not always installed. This
release finds the runtimes that are already on the machine, lets you pick the
one you want to use, and installs Ollama for you when you want a fresh
version.

What's changed

Local runtimes: find what you already have

  • A new Local runtimes card in the Model Farm scans the machine for
    Ollama, LM Studio, llama.cpp, Jan, GPT4All, KoboldCpp, LocalAI, vLLM,
    llamafile and text-generation-webui
    , and reports each one as installed,
    running or missing.
  • A runtime is found three ways: a server answering on its well-known port
    (11434, 1234, 8080, 1337, 4891, 5001, 8000, 5000), its command line on
    PATH, and the program in its install folder.
  • A leftover data folder is not an install. An app you uninstalled but
    whose settings remain is reported as missing, so the panel never sends you
    to a program that is no longer there.
  • The server banner names the runtime that holds a port. When two runtimes
    share one — llama.cpp, LocalAI and llamafile all want 8080 — the one that
    identifies itself wins and the others say who holds it.
  • Versions are read from the CLI, including the ones a runtime prints on
    stderr (llama-server does), and from the banner a runtime prints when it
    has no semantic version (LM Studio answers CLI commit: 43d4b26).

Use the runtime you want

  • use this makes a runtime the one the Model Farm installs into. The
    choice is stored in ~/.toolbox-mcp/settings.json and survives a restart.
  • The Model Farm follows the choice. Ollama pulls a GGUF straight from the
    Hub; a runtime that takes files instead of pulls (LM Studio, Jan, GPT4All,
    KoboldCpp, text-generation-webui) gets the weights downloaded into its own
    models folder; a runtime that serves one model per process (llama.cpp,
    llamafile, vLLM) is started with the model it was given.
  • The install action now reads Install in <runtime>, so it always
    names the runtime that will actually receive the model.

Install or update Ollama

  • Install / update Ollama downloads the official installer and runs it
    silently — per user, so no administrator rights are needed — then starts
    the server and confirms the version.
  • It always installs from the official source, so you get a fresh version
    rather than whatever was on the machine.
  • Runtimes with their own installer get a get it link to their homepage
    instead of a button that would fail.

Five new MCP tools

  • runtimes_detect — every runtime on the machine, with its state, version,
    path and the models it serves.
  • runtimes_install — install a runtime from its official installer.
  • runtimes_use — pick the runtime the Model Farm installs into.
  • runtimes_models — the models a runtime is serving right now.
  • runtimes_download — download a GGUF into a runtime's models folder.

The tool count goes from 24 to 29.

Notes

  • Detection never launches a desktop app. A program found in its install
    folder is reported; only a command on PATH is executed for the version
    probe.
  • The runtime choice is the only new setting, and it lives in the same
    owner-only settings file as the rest.
  • Nothing about this release changes how the Gmail App Password is stored —
    it still never leaves ~/.toolbox-mcp/settings.json.

Model Farm 0.7.0

Choose a tag to compare

@acsdd acsdd released this 15 Nov 13:08

Model Farm 0.7.0

The panel stops being a debugging page and becomes the server's front page.
The Overview now leads with what this server actually is: an MCP server with
24 tools, what it has been asked to do, and what it is wired to on this
machine — plus a visual refresh across the whole panel.

What's changed

An Overview that shows the MCP surface

  • The Overview used to be four JSON dumps. It is now the server's identity
    card: version, transport, tool count, panel URL and repo link, followed by
    stat tiles for tools, recorded calls and failures.
  • The MCP tool surface lists every tool the server exposes, grouped by
    feature (Crypto watch, Gmail announcer, Resource monitor, Model Farm,
    AstrLink gateway, Marketplace, Remote servers, Widget bundles). Search by
    name, group or purpose; filter by group; every tool shows its parameters as
    chips, with required fields marked.
  • A Live activity feed lists tool calls as they land, with outcome and
    duration, so a running agent is visible without reading a log.
  • The widget cards are real UI now: a price table, a mail list, CPU/memory/
    disk meters and a widget bundle summary — the JSON is one click away instead
    of being the whole card.

One catalogue, so the panel cannot lie

  • The tool list now lives in a single shared catalogue that both the MCP
    server and the panel read. The panel renders the same definitions the server
    registers, so a tool that is added, renamed or re-parameterised shows up on
    both sides at once. A test asserts the panel's catalogue and the server's
    tool list are the same set.
  • Each MCP call is recorded with its outcome and duration in a rolling buffer
    and exposed by the panel at /api/activity.

A visual refresh

  • A dark green design system replaces the ad-hoc colours: one token set for
    surfaces, borders, text and accents, layered panels, softer shadows and a
    calmer grid.
  • Navigation and buttons have larger hit areas, the layout collapses cleanly
    on narrow windows, and long text no longer collides with the values beside
    it.

Packaging

  • The portable build no longer sweeps the runtime Electron profile into the
    bundle, and it looks for the sibling desktop checkout under its real name
    instead of an old one.

Details

  • Turn the ops panel into an MCP-first front page (1ab79f5)

Model Farm 0.6.1

Choose a tag to compare

@acsdd acsdd released this 15 Nov 12:35

Model Farm 0.6.1

A maintenance round: the server tells the truth about itself, the local panel
only answers this machine, and the settings you can see are now settings you
can edit.

What's changed

Version and tool results

  • The MCP handshake and the HTTP user agent read the version from
    package.json instead of a hardcoded string, so they cannot drift away
    from the release again.
  • A tool that fails now says so: payloads with ok: false or a non-empty
    error come back with isError, so a client cannot mistake an error
    message for data. A gateway that is merely stopped stays a state, not a
    failure.
  • crypto_series takes the 30, 90 or 180 day window the widget core
    supports, instead of any number.

A panel that only answers this machine

  • Requests with a foreign Host header (DNS rebinding) or a foreign Origin
    (a web page driving the panel) are refused with 403.
  • Request bodies are capped at 1 MB, and malformed JSON answers 400 instead
    of 500.
  • The page loads nothing from the network — no webfont — so it works offline
    and runs under a strict content security policy with nosniff,
    no-referrer and X-Frame-Options: DENY.

Settings you can edit

  • A new Settings section edits the crypto watchlist, the disk the
    resource monitor reports on and the process list toggle, and writes them to
    ~/.toolbox-mcp/settings.json.
  • The terminal command history is kept in the browser's local storage, so it
    survives a page reload but never leaves the browser.

Repository

  • The repository is public. The Gmail App Password is still stored only in
    ~/.toolbox-mcp/settings.json on your machine — no credential has ever
    been committed, and the README now spells that out.

Details

  • Harden the local panel and let it edit the settings (f8fb80e)
  • Report the server version from the manifest and flag failed tool calls (20d30aa)
  • Prepare the 0.6.1 release (9e928b5)