> ## Documentation Index
> Fetch the complete documentation index at: https://docs.heybee.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Active acquisition and ComfyUI

> Let your own generation setup produce new outputs while an evaluation runs.

Sometimes the answer to "collect more votes" is "generate better candidates." Active acquisition lets a running evaluation request new outputs, and lets your generation environment, such as a local ComfyUI or a GPU box, pick up that work and deliver the results. Your machines call HeyBee, so nothing on your side needs to be reachable from the internet.

Requests can target optimization, benchmarks, regression checks, RLHF rounds, coverage exploration, or a manual batch.

## Connect a generator

Create a **connector** from the **Generators** panel in the Outputs workspace, or with `heybee acquisition connector create`. Choose whether each generation run needs your approval or runs automatically once you have authorized the generator.

Pausing a connector stops new work immediately without losing anything queued. Revoking one is permanent. Credentials stay in the CLI credential store on your machine; never embed them in ComfyUI workflows you share.

## Run the worker

Queue a request in the app or with `heybee acquisition request create`, then point the official worker at your local ComfyUI:

```bash theme={null}
heybee acquisition worker comfyui \
  --connector-id CONNECTOR_ID \
  --worker-id comfy-studio-1 \
  --comfyui-url http://127.0.0.1:8188 \
  --workflow workflow.json
```

Use `--once` for a single claim or `--poll-interval` to keep a worker running. The worker reports progress while generating, retries what is safe to retry, and submits each output together with the workflow, model, and parameters that produced it. That record stays attached to the output, so results and parameter analysis always reflect the exact settings behind each asset.

Prefer to stay inside ComfyUI? The **HeyBee Acquisition Input** and **HeyBee Submit Output** nodes drop into any compatible workflow and speak the same contract as the worker.