Skip to main content
More than the dashboard talks to a Clawboo server: the clawboo command, a desktop app that bundles the server, a reverse proxy in front of it, and apps on other devices. Use this page to know which versions work together and what each surface offers.

The support window

A Clawboo server supports clients of its current minor release and the previous one. A 0.6.x server keeps every route, response field and stream event that a client built for 0.5.x or 0.6.x uses. A client built for 0.4.x is outside the window and should ask you to update one side.
  • A patch release never removes or renames anything a client uses.
  • When a route, field or event has to go, it goes in a minor release, and the server’s API revision goes up by one. Adding a route, field, event or flag never changes the revision.
  • A major release starts a new window: a 1.0 server serves 1.0 clients.
Security fixes ship only in the latest release (see SECURITY.md), so update the server first when you can.

How a client checks

  1. Call GET /api/system/capabilities (see the System API).
  2. A 401 means the server has an access token: sign in first.
  3. An answer that is not the capabilities JSON (a 404, or the dashboard’s HTML page) means the server is older than the route and reports no flags. Use only what that older release had, or ask the person to update the server.
  4. Compare versions. The server promises to serve the client when the client’s own major.minor is at least the answer’s supportFloor and no newer than its version. Below the floor, ask the person to update the client. A client newer than the server gets no promise, and works only through the flags in the next step.
  5. Before using an optional feature, check its flag in features. A flag that is missing counts as off: the server is older than the feature.
apiRevision adds one more check for a client that records the revision it was built against: when the server reports that same revision, nothing the client relies on has been removed or renamed, whatever the two versions are.

What each surface offers

Every surface talks to the same server, so a feature the server has can reach every surface. The table tracks where each one can be used today.
  • npm install: npx clawboo or npm install -g clawboo, with the dashboard in a browser on the same computer, or reached from another one as in Reach Clawboo from another machine.
  • Desktop app: an app that runs this same server, unchanged, with its own Node.js. It is not available to download yet.
  • Phone web app: the npm install’s own dashboard, installed to a phone’s home screen from a secure address, as in Put the dashboard on your phone. It is a web app, not an app from an app store, and keeps nothing for offline use. Being the same dashboard, it has what the npm install has, so the table gives it no column of its own. On a phone’s width, the sidebar, the Board, chats and Home are laid out for the screen; other pages, such as Settings, the Org chart, Memory and Routines, open but are not laid out for one yet (see On a phone).
Supported means released on that surface. Beta means released, with behavior that may still change. Planned means not released on that surface yet. A flag being on means the server has the feature. It does not mean the surface you use shows it yet.
  • System API: the GET /api/system/capabilities answer and every flag.
  • Deployment: running the server as a service, and updating it.
  • CLI reference: the clawboo command, which checks the running server’s version when it attaches.
Last modified on November 18, 2026