A chat that runs on the box, TandemLLM v0.14.2 documentation

The dashboard's Chat tab feels like the chat products you know from the cloud, and it runs on your own box. A run lives on the server. Close the browser in the middle of an answer, open the chat on your phone, and it shows the answer at the token the engine is writing now.

The Chat tab. On the left, the chat list with pinned chats, folders and a running chat. In the middle, a run that calls a file-editing tool, a follow-up message queued to go in after the current step, and a terminal inside the chat's sandbox with no network. On the right, the context panel: the window in use by part, the live decode rate, and which model and weights serve the chat. — A run in progress, with a follow-up queued behind it and the chat's sandbox terminal open below. Rendered from the dashboard's mock data; the figures in it are not measurements.

Each chat gets its own sandbox container: no capabilities, a read-only root, 1 GiB of memory, 4 CPUs and no GPU. Its internet goes through a per-chat proxy that refuses your local network, and you can switch it off per chat.
The model gets a shell, file tools, terminals and page rendering inside that sandbox. Web search goes through DuckDuckGo or your own SearXNG. MCP servers plug in; stdio servers run inside the sandbox, and their secrets never come back in an answer.
You choose how much it may do alone: Ask, Auto (the default) or YOLO. A tool call that needs your answer waits, and gives its slot back while it waits.
Images go to a model that reads images. A text file goes into the prompt within a token budget, and a larger one goes to the chat's workspace for the tools to read.

A chat waiting for permission. The model read a file, and its next tool call, an edit of that file, shows the change it wants to make with three buttons: Allow once, Always allow edit_file, and Deny. — A tool call waiting for your answer, with the exact change it wants to make. Mock data.

The Chat tab is in beta, and its page in the docs lists what it does not do yet. Your own client works too: Open WebUI, opencode and pi talk to the engine through the OpenAI-compatible API, and every client shows up in the same dashboard, down to a year of usage.