FlashID Auto
A Python automation tool for FlashID browsers. Connect to an existing, running FlashID browser environment, execute modular browser tasks, and receive structured JSON results.
Features
- Connect to FlashID through its Local API and an existing browser's CDP endpoint.
- Run browser automation modules using Playwright.
- Execute individual modules or chain multiple steps with JSON data bindings.
- Return structured results, execution status, and error details.
- Clean up task-created tabs during normal completion while preserving existing tabs.
- Extend automation with custom Python modules.
Requirements
- Python 3.10 or later.
- FlashID with Local API enabled.
- A running FlashID browser environment for browser tasks.
Playwright connects to FlashID's existing browser, so no separate Chromium download is required for these tasks.
Installation
python -m pip install flashid-auto
Configuration
Set the following environment variables, or create a .env file in your working
directory:
FLASHID_API_BASE_URL=http://127.0.0.1:58931
FLASHID_API_KEY=YOUR_FLASHID_API_KEY
Use your own FlashID API key and keep the .env file private. Existing process
environment variables take precedence over values in the file.
Usage
Check the FlashID Local API connection:
flashid health
Run a browser automation task in the running environment named Navigator:
flashid-auto --profile Navigator --module duckduckgo -- \
--search-key "FlashID browser automation" --result-count 3
Use the exact name of your running FlashID environment for --profile.
Commands return JSON that can be consumed by scripts and other automation tools.
For multi-step tasks, supply a JSON execution plan:
flashid-auto --profile Navigator --chain-file tasks.json
See flashid-auto --help and flashid --help for command-line options.
License
MIT. This project is independent of FlashID.
Metadata
Release files for flashid-auto 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| flashid_auto-0.2.1.tar.gz | 122.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| flashid_auto-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 178.5 kB
Release files / flashid_auto-0.2.1.tar.gz
| Download URL | flashid_auto-0.2.1.tar.gz |
|---|---|
| Size | 122.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
751b30b0a658b83c2c92854c111e849add086e330a668d985d1ecb4d1253c9bb
|
|
BLAKE2b-256 checksum How to use checksums |
e39cc95985906fc96a0ffd75fa72097e32f8e1064f2a57c9d5b203715510a580
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.12
|
Release files / flashid_auto-0.2.1-py3-none-any.whl
| Download URL | flashid_auto-0.2.1-py3-none-any.whl |
|---|---|
| Size | 55.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e911971d0ca22b7926a16552abb3e2f24befb1e007aff69eaf811f42ea1e2fb0
|
|
BLAKE2b-256 checksum How to use checksums |
58ee3173ca2ae16d42fe275f7367d43f5bb16824db6af70a182f8f786a380fcd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.12
|
Security for flashid-auto 0.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.