🤖 Byte Flusher - File 📁

Home · Text Flush · Docs · GitHub · Usage

Device

Nickname

Saved to board; reflected in advertising name (alphanumeric/-/_).

Status Disconnected

Cautions

Authorized environments only: Intended for testing/development automation/demo purposes on systems you own/manage or in explicitly authorized environments.
Do not use for unauthorized access, security bypass, unauthorized file creation/input, or any illegal/unethical purpose.
No OS pre-pairing needed; just use Connect Device from the browser (Chrome/Edge).
Target directory: absolute path / ASCII only / no spaces
Input: one top-level folder or one file
Content: bytes preserved as-is (Base64 → WriteAllBytes)
PowerShell: auto-launched via Win+R (vulnerable to focus/popup/UAC/IME)
Even without user interaction, system UI (notifications/antivirus/updates/UAC) can steal focus and cause failure
Recommended: screen saver/auto-lock/sleep OFF, notifications OFF, no mouse/keyboard use during operation
Recommended: use a path under user folder to avoid permission issues (e.g. C:\Users\me\...)

Transfer Settings

Typing delay (ms)

Wait time after each keystroke. Too short may cause drops in console/IME environments. (Aggressive tuning possible: 0~)

Key press hold (ms)

How long a key is held down. Too short may not register in some environments.

Line (Enter) delay (ms)

Stabilization wait after Enter. Helps in environments with slow command processing/screen refresh.

Command interval (ms)

Wait after a PowerShell command (one line) before the next (important for chunk loops).

Base64 / Chunk Settings

Bootstrap chunk length (Chars)

Determines how many characters per bf_boot_append chunk (bootstrap -EncodedCommand Base64). Longer is faster but increases risk of keystroke drops.

Chunk length (Chars)

Determines how many characters per Base64 chunk. Longer is faster but increases error/drop risk.

Inter-chunk delay (ms)

Wait after sending one chunk before the next (for input/processing stabilization).

Write Settings

Overwrite Policy

Behavior when a target file already exists. Keep 'fail' by default; use overwrite/backup only when needed.

Automation / Bootstrap

Run (Win+R) dialog delay (ms)

Wait for the Run dialog to fully gain focus after Win+R.

PowerShell launch delay (ms)

Wait for PowerShell to open and the prompt to become ready for input.

Post-bootstrap delay (ms)

Stabilization wait after bootstrap script initialization before continuing.

Enable diagnostic logging

On failure, writes error log to targetDir\.tmp\bf_last_error.txt.

Notes

Execution procedure (summary)

PowerShell launch (Win+R) → console warmup/BF_READY → launcher install (bf_boot_append/run) → bootstrap send (bf_boot_append…) → bootstrap execute (bf_boot_run) → file loop (prepare_out → tmp_reset → tmp_append… → commit) → decode (WriteAllBytes) → SHA-256 verify (Get-FileHash) → cleanup (.tmp delete) → done

Stage display mapping: Prepare (Win+R/warmup/BF_READY) → Boot (launcher+bootstrap install) → Send (Base64 chunk input) → Decode (WriteAllBytes) → Verify (Get-FileHash) → Cleanup (temp file delete)

Web Bluetooth only works in Chrome/Edge.
Target PC must allow USB keyboard devices.
Verification uses SHA-256; mismatches stop immediately.
Temporary Base64 files are auto-created as targetDir\.tmp\bf_payload_<auto>.b64; existing temp files are deleted before start.
If targetDir does not exist, folders are created automatically.
May fail depending on security policy/write permissions.
When diagnostic logging is enabled, targetDir\.tmp\bf_last_error.txt may be created on failure.

Multi-file Creation

Select a single file or folder to create files on the Target PC under targetDir, preserving the selected structure. Each file is verified with SHA-256 after creation; mismatches/failures stop immediately with an error. If the run completes and no error report (targetDir\.tmp\bf_last_error.txt) is generated, the created files are error-free.

Source Selection

Select file(s) or folder to create on the Target PC.

Selected items -

Target System

Windows macOS (coming soon) Linux (coming soon)

Target Directory

Enter the directory on the Target PC where files will be created.

ASCII only, no spaces. (Recommended: use a path under user folder to avoid permission issues)

ETA -

Start -

Files -

Bytes -

Stage -

Elapsed -

Progress -

End -

Basis -