engineering · 2026-09-10

One tool contract across three providers

Three vendor CLIs, three stream formats, one vocabulary of phases — and a rule that the adapter never summarises.

Written and covered by tests — not yet observed in a live runDeskworth · published · updated · 3 sources · Deskworth OS 0.0.22

Deskworth drives command-line tools you already pay for. Three are in the core registry today, and each emits a different stream.

#What the adapter is allowed to do

Map the vendor stream onto a common vocabulary of phases so a trace reads the same whichever CLI produced it. What it must never do is condense. Every line of trace corresponds to an event that occurred, and the raw output stays available underneath, whole, with the exact command line.

#The tools are the other half

Tools are served over a local Model Context Protocol server bound to the loopback address 2. Twenty-three of them, each declaring an input schema and a required capability. The role decides what it sees; the adapter has no say. That separation is why adding a fourth provider does not widen anyone’s reach.

LimitThree adapters exist. This site does not name a fourth, and will not until the core registry does 1.

#Sources

  1. The provider registry, mirrored on this siteDeskworthinternal registry · provider registry mirror of providers::ALL · read 2026-09-10Internal document, not published
  2. Model Context Protocol — specificationModel Context Protocol projectofficial documentation · read 2026-09-10https://modelcontextprotocol.io/
  3. Deskworth OS — handover report 0.0.22Deskworthinternal handover report · Deskworth OS 0.0.22 · commit d59e30e · published 2026-09-10 · read 2026-09-10Internal document, not published

Read next