> 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/manual-mode-args.md).

# Manual Mode Options

These options allow you to download media from specific URLs or post IDs without relying on user lists or other automated selection methods.

## Syntax

```
ofscraper manual [options]
```

### example

```
ofscraper manual --url test
```

## General Options

[General Program Options](/ofsc/command-reference/shared-options/common-option-groups.md)

## Text

### **-tn, --text**

* Specify to download text with any media tied to that text

### **-tp, --text-only**

* Specify to download only text, skipping any media

`--text` and `--text-only` cannot be used together.

## Download Sources

### **-f, --file \[argument]:**

Download media from a file containing URLs or post IDs, separated by line breaks.

### **-u, --url \[argument]:**

Download media directly from one or more URLs provided as arguments (separate URLs with spaces).

One of `-u` or `-f` is required.

### **-fo, --force**

Force retrieval of new post information from the API.

***

**Combining Options:** Use either `-f` or `-u`, not both. The program requires exactly one of them.


---

# 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/manual-mode-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.