> For the complete documentation index, see [llms.txt](https://docs.couchdrop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.couchdrop.io/storage/local-storage/running-the-couchdrop-agent-as-a-service.md).

# Running the Couchdrop Agent as a Service

Learn how to run the Couchdrop Agent as a Service for file server transfers.

## Overview

The Couchdrop Agent, also known as the Couchdrop Cloud Connector, can run as a Windows service.

Running the agent as a service allows it to continue operating in the background without requiring the desktop application to remain open.

The service must run under the same Windows user account that was used to configure the agent. The Couchdrop Agent configuration is stored within that user's profile, so using a different account can prevent the service from connecting correctly.

## How to run the Couchdrop Agent as a service

{% hint style="warning" %}

#### Before you start

Before installing the service:

* Install and configure the Couchdrop Cloud Connector by following the [Windows / Mac File Server](/storage/local-storage.md) setup instructions.
* Confirm that the agent is connected and working correctly.
* Close the Couchdrop Cloud Connector desktop configuration application and system tray application.
* Make sure you know which Windows user account was used to configure the agent.
  {% endhint %}

{% stepper %}
{% step %}

### Open the Couchdrop Cloud Connector folder

Open a command line and navigate to the Couchdrop Cloud Connector installation folder under **Program Files**.
{% endstep %}

{% step %}

### Install the Windows service

Run the following command from the Couchdrop Cloud Connector folder:

```
.\couchdrop-cloud-connector-service.exe install
```

This installs the Couchdrop Cloud Connector as a Windows service.
{% endstep %}

{% step %}

### Open Windows Services

Open the Windows Service Manager by running:

```
services.msc
```

Find **Couchdrop Cloud Connector** in the list of services and open its properties.
{% endstep %}

{% step %}

### Configure the service account

Open the **Log On** settings for the **Couchdrop Cloud Connector** service.

Configure the service to run using the same Windows user account that was used to configure the Couchdrop Agent.

{% hint style="warning" %}
The agent configuration is stored under the Windows user's profile. If the service runs under a different account, it may not be able to access the configuration and connect to Couchdrop.
{% endhint %}
{% endstep %}

{% step %}

### Start the service

Start the **Couchdrop Cloud Connector** service.

Once the service is running, reopen the Couchdrop Cloud Connector configuration application.

The application should show the agent as **Running in Background**.
{% endstep %}
{% endstepper %}


---

# 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://docs.couchdrop.io/storage/local-storage/running-the-couchdrop-agent-as-a-service.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.