Documentation
How K3 Studio works, area by area. Every page is also plain Markdown at /llms.txt.
Getting started Requirements, Build and run, First run, What do you want to make?, Layout, Settings and keybindings, Installing, Updates, ReleasingEditor K3 Studio draws everything itself: a single GL draw call with SDF rounded rects, its own glyph atlas with kerning, and a rope text buffer. It only redraws when something changes, so it sits at about 0% CPU when idle.Language servers The web servers are installed once with bun and pinned to fixed versions. You can see each server's state (starting / idle) in the Web panel.Live This is what makes K3 Studio different from other editors: it's connected to the server it started.Agent & MCP K3 Studio drives Claude Code (the claude CLI) in its stream-JSON mode. Ctrl+L toggles the panel.Server Running FXServer, Console, New project wizard, server.cfg as a form, server.cfg as textResources fxmanifest.lua as a form, What runs where, Resources panel and details, Focus on a resource, New resource, Generate documentationCore workspace Support for TypeScript monorepos that ship as one core resource: apps/*, lib/, configs/<app>/<side>.json, built with tsdown and vite.Database Connection, What you can do, SQL everywhereGit K3 Studio uses the git CLI (porcelain v2). Status and every git action run on worker threads, so the UI never waits on git.Web & NUI Packages, Scripts, ui_page dev / build, Chrome 103 compatibilityVehicle handling Open it from the Game rail item. K3 Studio lists every vehicle it finds in the handling.meta files of your workspace.Releasing K3 Studio A release is a git tag. Pushing a v* tag runs the release workflow. The workflow builds K3 Studio with that version, packs the installer and publishes it as a GitHub release. Installed copies of K3 Studio see the new release the next time they start and update themselves (see Updates). MCP tools Every tool the agent can call through K3 Studio's MCP server.