Batch Workflows

Batch Workflows

Batch mode runs every compatible installed batch-capable plugin against a validated target file. Use cases instead when work must be durable, resumable, and tied to an authorization record.

Target file

The default file is ~/.config/osint-forge/targets.txt.

[Emails]
analyst@example.com

[Usernames]
example_handle

[Domains]
example.com

[IPs]
192.0.2.10

[Images]
./photograph.jpg

[Files]
./evidence.bin

Entries are trimmed, normalized where appropriate, validated by type, and deduplicated. A target before any recognized section is rejected.

Preview and run

osint batch --dry-run --name preview
osint batch --name initial-sweep
osint batch --plugins maigret sherlock --jobs 2 --name usernames-only

Unknown plugin filters are rejected. Only installed plugins that declare compatible batch adapters are scheduled.

Output

Results default to ~/OSINT-Cases/Batch-Runs/. Each run receives a collision-resistant UTC timestamped directory containing the copied target list, logs, per-job output, and a summary. Framework-created roots, adapter output directories, and artifacts use owner-only permissions.

Failure behavior

A plugin launch failure is recorded in the summary instead of crashing without a status record. Batch mode is not a substitute for case resume semantics; use Case Management for investigations that must be resumed or reviewed later.

Safety

• Preview new workflows with --dry-run.
• Use restrained --jobs values.
• Never scan infrastructure without explicit authorization.
• Never commit target files or output directories.
• Review upstream tool terms, rate limits, and authentication requirements.