> For the complete documentation index, see [llms.txt](https://coldbox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coldbox.ortusbooks.com/digging-deeper/desktop-applications.md).

# Desktop Applications

Build cross-platform desktop applications with ColdBox and the BoxLang Desktop runtime.

ColdBox applications can run as fully functional **desktop apps** through the BoxLang Desktop runtime — same handlers, models, and views you already know, packaged for Windows, macOS, and Linux.

🚀 **BoxLang only.**

📖 **Runtime documentation:** [BoxLang Desktop Applications](https://boxlang.ortusbooks.com/getting-started/running-boxlang/desktop-applications)

## Quick Start

Use the official starter template:

```bash
# Create a new desktop app from the template
coldbox create app name=myDesktopApp skeleton=https://github.com/coldbox-templates/boxlang-desktop
```

The [boxlang-desktop template](https://github.com/coldbox-templates/boxlang-desktop) wires the BoxLang runtime, an embedded webview, and the build pipeline for packaging installers.

## How It Works

A BoxLang Desktop app is a ColdBox app served by the embedded runtime, rendered in a native webview window:

* Your ColdBox app runs **locally** — no external server needed
* Views render in a system webview (your existing HTML/CSS/JS works)
* BoxLang gives you OS-level access (filesystem, dialogs, menus) from the same codebase
* Package installers per platform with the template's build scripts

## When to Use It

* Internal tools that need offline capability
* Kiosk or point-of-sale applications
* Cross-platform utilities where a JVM is acceptable but a browser tab isn't
* Reusing an existing ColdBox codebase on the desktop

## See Also

* [Application Templates](/getting-started/application-templates.md)
* [Deployment](/reference/deployment.md)
* [BoxLang Desktop docs](https://boxlang.ortusbooks.com/getting-started/running-boxlang/desktop-applications)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://coldbox.ortusbooks.com/digging-deeper/desktop-applications.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.