Skip to content

BLEA 0.7.0

Latest
Latest

Choose a tag to compare

View all tags
@Nitmi Nitmi released this 29 Sep 11:40
v0.7.0
6608a1b

BLEA 0.7.0 adds explicit Bluetooth pairing and host bond removal to the CLI and MCP server.
Agents can pair a selected peripheral and remove its host bond without switching to OS settings.

  • CLI: ble pair and ble unpair; MCP: ble_pair and ble_unpair.
  • Both operations require an exact id: selector, explicit enablement, and matching device
    confirmation. They are not triggered automatically after a protected GATT read fails.
  • Windows six-digit PIN pairing uses WinRT custom pairing, requires encryption and authentication,
    refreshes OS bond state, and reports whether the PIN was actually used. Existing bonds do not
    count as PIN verification. No fallback to weaker protection occurs in the PIN path.
  • CLI --pin-env reads a process environment variable so the PIN is absent from command arguments.
    MCP accepts pin; BLEA omits it from result fields, but the MCP host may retain tool arguments.
  • Discovery defaults to 5 seconds independently of the 60-second pairing operation timeout.
  • Skill instructions, examples, replay rejection, structured errors, and cleanup tests are updated.

Validation: 147 adapter-free tests; Plugin/Skill validators; local wheel cold installs on Windows
with Python 3.10, 3.11, 3.12, and 3.13; offline replay and MCP pairing guards. One Windows source-CLI
real-device cycle confirmed authenticated PIN pairing, independently verified the OS bond, and
removed it successfully. The final host state was unpaired and disconnected.

Explicit PIN input is Windows-only. Linux uses its configured BlueZ pairing agent and remains
native-hardware unverified. macOS has no explicit pair/unpair operation in Bleak. Host unpairing
does not prove that the peripheral erased its own stored keys and can disconnect other clients.

The Windows standalone archive is not Authenticode-signed. Verify its checksum and GitHub
attestation from the tag build before installing it. Local pre-publication checks do not establish
GitHub build provenance; public CI, attestation, and public-distribution reinstall are release gates.

Assets 4
Loading