# RFT Run From Text

**Flag:** `--rft`

Run From Text compresses the entire source with `zlib`, encodes it as `base64`, and produces a two-line loader that decompresses and `exec()`s the blob at runtime. No plain Python source is visible in the output.

## Output format

```python
import zlib as _z,base64 as _b
exec(_z.decompress(_b.b64decode(b'eJy...')).decode())
```

## Example

**Before:**

```python
def greet(name):
    print("Hello, " + name)

greet("world")
```

**After:**

```python
import zlib as _z,base64 as _b
exec(_z.decompress(_b.b64decode(b'eJxLy8kvLk4tLk4tKs1VSMsvyklRslIqS...')).decode())
```

## Notes

* RFT is a thin encoding layer the original source can be recovered by decoding the blob. Use `--carbon` or `--mix-strings` before `--rft` to obfuscate the source before encoding.
* Stacking `--rft` then `--bcc` (the double-encode pattern) hides the `exec` call inside bytecode, making static recovery harder.
* No external dependencies are required at runtime (`zlib` and `base64` are stdlib).
* Compression level is set to maximum (`zlib` level 9), so the encoded blob is typically smaller than the original source.


---

# Agent Instructions: 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:

```
GET https://rodolphes-organization.gitbook.io/anubis/features/rft.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.