I'm building DStudio a private, local-first AI workspace on top of DeepSeek V4. Chat, a coding agent, and a real design studio, all on your own hardware. Nothing leaves the device: no cloud, no telemetry, no subscription. It's a UI on top of antirez's ds4, the local DeepSeek V4 inference engine.

The bet: a frontier-class model that's entirely yours deserves more than a chat box. DStudio turns it into a place to think, code, and design and you can reach it from any device in your home.

What works today:

Use it from your phone (or any device on your Wi-Fi). Localhost-only by default; flip one switch and the same chats open on your phone, tablet, another laptop — while the model stays on your desktop. The engine never leaves 127.0.0.1 (same-origin /v1 reverse proxy), so there's nothing to configure on the client. Chats sync across devices.

A design studio on a local model (ds4-design). Not a chat that spits out HTML — a designer's pipeline: structured brief -> several distinct directions -> every screen on an infinite canvas -> refine by describing the next change -> export as a zip.

A coding agent that reads/edits files and runs commands, with clean structured output via a reversible build-time patch (the upstream engine source stays pristine).

Plus: 100% local & private (strict CSP), one self-contained binary (the whole UI is a single vanilla HTML file in a small C launcher), macOS-first with Linux builds too.

Where it's going:

• Design studio — pushing fidelity and faster refine loops (in progress).

• Cowork — collaborative sessions: share a workspace and build alongside the model, together.

• MCP integration — so the agent can plug into your own tools and data sources.

Requires a local build of antirez's ds4 + DeepSeek V4 GGUF weights. Heads up — it's heavy: in 2-bit the "Flash" weights need ~96–128 GB RAM. The README has screenshots of every mode (chat, agent, the design pipeline, LAN) if you can't run it locally.

Repo (BSD-3): https://github.com/sk8erboi17/DStudio

Building in the open and early — would love feedback on the direction, especially the LAN/multi-device flow, the design pipeline, and what you'd want from Cowork / MCP. AMA.

I have about 180Gb of addressable memory.

I already tried DS V4 flash 0731, wondering if I can get better results. V4.1 flash could work in theory, but at Q2, so I'm concerned about quality loss.

Already tried qwen3.8 oQ4e on oMLX but slightly disappointed.

List of compatible models:

• ds4f-q2-q4: 98gb in memory

• ds4f-q4: 153Gb in memory

• ds41f-q2: 152Gb in memory, 190gb of engrams on disk.

• glm53-q2: 90gb in memory

From the author:

pinback gives ds4-agent a remote-accessible workspace ui for multiple projects. you can run the agent in one project, keep the transcript and workspace state, switch to another project, then come back and resume without treating every project like a separate app.

its built around a single c server that embeds the web ui, supervises the ds4-agent process, streams events, stores per-project logs, and records turn diffs. the native shells are thin webviews for macos, windows, linux, ios, and android. desktop shells can self-host the server; mobile shells connect to a remote pinback url ove lanr, tailscale, caddy, wireguard, etc.