> For the complete documentation index, see [llms.txt](https://docs.darcyiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.darcyiq.com/core-features/darcy-desktop.md).

# Darcy Desktop (Beta)

Run Darcy as a native desktop app on Windows, macOS, and Linux — with direct access to your local projects, files, and tools

Darcy Desktop brings the full DarcyIQ experience to a native application for **Windows, macOS, and Linux** — the same chat, integrations, workflows, and features you use in the browser, plus something the browser can't do: **direct interaction with your local computer**.

{% hint style="info" %}
**Beta**: Darcy Desktop is currently in beta. Features and setup steps may change as we iterate — check the [release notes](/release-notes.md) for the latest updates.
{% endhint %}

## Overview

| Capability                     | Description                                                                                       |
| ------------------------------ | ------------------------------------------------------------------------------------------------- |
| **Native apps for every OS**   | Install Darcy as a first-class desktop application on Windows, macOS, or Linux                    |
| **Full platform parity**       | Chat, agents, integrations, workflows, and artifacts — everything from the browser version        |
| **Local computer interaction** | Grant Darcy access to folders on your machine so agents can read, edit, and create files directly |
| **Run real tools**             | Execute your actual test suites, builds, and scripts against your real codebase                   |
| **Seamless cloud sync**        | Move files and context between your desktop and the cloud sandbox                                 |

## Local Computer Interaction

The defining feature of Darcy Desktop is the ability to work on your local projects directly.

* **Folder access** — Grant Darcy access to a specific folder on your machine. Agents can then read, edit, and create files inside it — changes appear in your IDE the moment they're saved.
* **Real tooling** — Run your actual test suites, execute builds, and work with your real codebase instead of a copy.
* **You stay in control** — Darcy can only touch the folders you explicitly grant access to.

{% hint style="success" %}
**Use case**: Working on a codebase? Grant Darcy access to your project folder and ask it to run your test suite, fix the failing tests, and update your source files directly — all without leaving the desktop app or switching to your terminal.
{% endhint %}

## Cloud Sync

Files and context move seamlessly between your desktop and Darcy's cloud sandbox, so you can combine local project access with cloud-based analysis and processing.

| Workflow            | How it works                                                             |
| ------------------- | ------------------------------------------------------------------------ |
| **Local → Cloud**   | Send local files to the cloud sandbox for heavy processing or analysis   |
| **Cloud → Local**   | Bring artifacts and results from cloud runs back into your local project |
| **Mixed workflows** | Edit code locally while agents run large-scale analysis in the cloud     |

## Getting Started

{% stepper %}
{% step %}
**Download the app** Install Darcy Desktop for Windows, macOS, or Linux.
{% endstep %}

{% step %}
**Sign in** Use your existing DarcyIQ account — your chats, integrations, and settings carry over.
{% endstep %}

{% step %}
**Grant folder access** When you want Darcy to work on a local project, grant access to that folder. You can revoke access at any time.
{% endstep %}

{% step %}
**Start working** Ask Darcy to read your code, run your tests, or make changes — and watch them land in your IDE in real time.
{% endstep %}
{% endstepper %}

## Security & Permissions

| Aspect                    | Detail                                                                            |
| ------------------------- | --------------------------------------------------------------------------------- |
| **Folder scope**          | Darcy can only access folders you explicitly grant — nothing else on your machine |
| **Revocable**             | Folder access can be revoked at any time                                          |
| **Same account security** | Your existing DarcyIQ permissions, integrations, and organization policies apply  |

## Related Documentation

| Goal                     | Documentation                                                             |
| ------------------------ | ------------------------------------------------------------------------- |
| Chat with Darcy          | [Chat](/core-features/darcy-chat.md)                                      |
| Automate multi-step work | [Workflows](/build/ai-workflows.md)                                       |
| Connect your tools       | [Integration Catalog](/build/integration-overview/integration-catalog.md) |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.darcyiq.com/core-features/darcy-desktop.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.