Field noteNov 16, 20265 min read1 source

Tiles 0.5.0 ships macOS and Linux desktop apps, a local web UI, and Tilekit APIs

In one minute

Tiles 0.5.0 adds desktop apps for macOS and Linux, a daemon-served local web UI, device linking and chat sync, and Tilekit, an HTTP API for its local assistant stack. For builders, the release makes it easier to operate Tiles across desktop and headless setups, while exposing more of its capabilities for integration.

What happened

The Tiles project’s GitHub release notes say version 0.5.0 was released on November 12. The release adds a desktop app for macOS and Linux: a chat window with a menu bar on Mac and a tray on Linux. Running tiles ui opens the app, or opens the browser-based interface when no app or display is present.

The daemon serves a web UI at http://127.0.0.1:1730. The notes describe it as a place to chat, download and select models, and switch the llama.cpp engine. Tiles can detect the GPU and download the corresponding llama.cpp build the first time a model runs; tiles run asks before downloading. Model downloads can resume after a pause or crash, and each file is checked with SHA-256. Users can select the model used for chats and delete downloaded models, including one currently in use after unloading it.

The update adds device linking and chat synchronization. A linked device can be dialed by nickname or DID. Users can also sign in with an ATmosphere account; sign-in reports progress and gives up after five minutes. Old chats can be continued after Tiles restarts. The release adds Gemma 4 E2B, E4B, 26B-A4B and 31B alongside the default Gemma 4 12B.

For operation, tiles service install starts the daemon at login. A headless installer installs only the daemon, without the app or web UI, for servers. Tilekit is described as the daemon’s HTTP API for accounts, sessions, the agent, inference server, models and engines. The notes also say routes that change state now use POST and require a JSON content type, preventing websites from calling the daemon through the browser. Linux ships one tarball with the CPU build of llama.cpp rather than separate GPU-backend tarballs, and every platform uses the same upstream llama.cpp release.

What the archive adds

New Runtime’s earlier coverage noted that Agent Terminal v0.7.0 added Linux desktop support (November 11, 2026). Tiles is a new event, but it extends the practical desktop-and-daemon story: this release pairs desktop access with a local web UI and an API for operating the assistant.

Trend signal

This supports agent-ready software exposes capabilities: the product boundary is a set of observable capabilities external agents and tools can compose. Tiles exposes accounts, sessions, agent, inference, models and engines through Tilekit, while requiring POST plus JSON content type for state-changing routes. Agent-ready software exposes capabilities.

Why now

The release brings the desktop, local web and headless server surfaces into one versioned product experience. The notes do not explain why the project chose this release timing, so there is no broader timing claim to make.

Why it matters

A local assistant is useful only if people can operate it where their work happens and connect it to the surrounding workflow. Tiles 0.5.0 offers a desktop path for interactive use, a browser UI served by the daemon, and a headless installation for servers. That combination gives a builder more than a chat window: it provides explicit handles for model selection, engine changes, sessions and inference.

The API could make Tiles easier to integrate into custom tooling, but the release notes alone do not establish how mature or stable those integrations are. The POST and JSON requirements are a meaningful boundary for state-changing browser requests; teams should still inspect the full API behavior and authentication model before exposing or depending on it. For teams testing local-first assistants, the concrete next step is to evaluate whether this interface and deployment split fit their machines and operational needs.

Limits and uncertainty

The release notes do not report performance, hardware requirements, model quality, synchronization behavior under conflicts, or reliability measurements. They do not state a price or describe support commitments. The changelog identifies Tilekit’s API surface at a high level but does not establish compatibility guarantees, authentication details for every route, or whether the interface is intended for remote access. The release page labels the broader 0.5 line Alpha 24 in a same-day follow-on release note; production readiness should not be inferred from the feature list alone.

Skill to build now

This week, test the headless installation and Tilekit against one narrow workflow: install the daemon on a spare machine, create or select a model, then use a small client to inspect sessions and model state. Keep state-changing calls on POST with JSON content type, and verify what authentication and network binding your setup actually uses before making the service reachable beyond localhost.

Reader takeaway

Tiles 0.5.0 turns a local assistant into a more operable system: desktop and browser interfaces for people, a headless option for servers, and an API for integrations. Treat Tilekit as a capability surface to evaluate, not as proof of production readiness; validate its security, reliability and fit in your own environment.

Evidence / sources

  1. 1github.com/tilesprivacy/tiles/releases/tag/0.5.0
All Field Notes

Next reads

Read next

Open the graph
  1. 01topicAgent InterfacesExplore the agent-interfaces topic hub.
  2. 02topicApi DesignExplore the api-design topic hub.
  3. 03archiveField NotesOpen the latest editorial analysis.
  4. 04sourcesSourcesSee the original sources this archive cites.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract