> For the complete documentation index, see [llms.txt](https://cloakedkeys.gitbook.io/ofsc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cloakedkeys.gitbook.io/ofsc/command-reference/shared-options/scrape-metadata-options/general-scraper-args.md).

# Automation Options

These options allow you to configure automated actions performed by the program and control its background execution

## Background Execution

### -d, --daemon \[argument]

* **Runs:** The program in the background as a daemon process.
* **Argument:** (required) Specify the desired interval in minutes between program runs; decimals are allowed (e.g., `-d 60` for hourly runs).

#### Trigger the next pass early

> ℹ️ **Since 3.15.0, Docker/Linux.** See [Fork Changes](/ofsc/fork-changes.md).

While the daemon is waiting between passes, send `SIGUSR1` to start the next pass without restarting it:

```sh
docker kill --signal=SIGUSR1 <container>
```

Outside Docker, `kill -USR1 <pid>` does the same.

* The signal is ignored during an active pass. Repeated signals don't queue extra passes.
* After the triggered pass, the normal interval starts again.
* SIGTERM and Ctrl+C still shut the daemon down, including while it's waiting between passes.
* Native Windows has no SIGUSR1, so this isn't available there.

## Automated Actions

### -a, --action (also `--actions`) \[argument]

* **Selects:** The automated action to perform on posts.
* **Possible choices:**
  * `like`: Like each post encountered during processing.
  * `unlike`: Unlike each post encountered during processing.
  * `download`: Download media associated with each post encountered during processing.

**Combined actions:** You can combine the `-a` option multiple times to specify multiple actions. For example, `-a like -a download` or `-a like,download` would like and download media for each post. `like` and `unlike` cannot be combined.

#### **Action Descriptions:**

> ℹ️ **Like and unlike are limited by rate limiting**

* **Like:** Attempts to like each post processed by the program.
* **Unlike:** Attempts to unlike each post processed by the program
* **Download:** Downloads associated media (e.g., images, videos) from each post processed by the program

## Fansly Livestreams

These options apply to Fansly only (`--site fansly`) and are available in the main program.

### --live

* Records the selected creators (all followed creators without `-u`) who are live now, then continues.

### --live-watch

* Keeps checking who is live and records them. With `--daemon` it runs beside the scheduled scrapes.

### --live-interval \[argument]

* Seconds between live checks in `--live-watch`. Whole number, at least 10 (default 60, plus up to 10 seconds of jitter).

### --live-max \[argument]

* The most livestreams recorded at the same time. Whole number, at least 1 (default 2).

### --live-chat

* Also saves livestream chat to a `.jsonl` file (read-only; off by default).


---

# 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://cloakedkeys.gitbook.io/ofsc/command-reference/shared-options/scrape-metadata-options/general-scraper-args.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.