### Telemetry _ opt-out model

PiQrypt v1.9.1

Telemetry, opt-out model

Telemetry is now enabled by default on fresh installs to help improve
the project. A clear opt-out notice is displayed on first CLI run and
in the onboarding dashboard.

No personal data, no agent IDs, no payloads are ever collected.
Full details: https://piqrypt.com/telemetry

To opt out at any time:

piqrypt telemetry disable

Or set: PIQRYPT_TELEMETRY=0

Existing users with a telemetry.json config are unaffected.

Changes

• aiss/telemetry.py, enabled by default on fresh installs
• cli/main.py, first-run notice printed once before any command,
  writes ~/.piqrypt/telemetry.json, sends install event
• static/onboarding/index.html, telemetry notice block in hero
  with one-click opt-out (copies command to clipboard)
• docs/TELEMETRY.md, updated to reflect opt-out model
• scripts/bump_version.py, onboarding HTML now tracked by bump script

Bug fix

• cli/main.py, split multiple imports on one line (ruff E401)

v1.9.0 — Hermes Agent bridge + 10 framework integrations

What's new in v1.9.0

Hermes Agent bridge

Native PiQrypt plugin for Hermes Agent (105k+ stars).

Install:
pip install piqrypt
hermes plugins enable piqrypt-audit

Every tool call Hermes makes is Ed25519-signed and hash-chained. Audit trail stored locally, visible in Vigil (localhost:8421).

10 framework bridges

LangChain · CrewAI · AutoGen · MCP · Ollama · ROS2 · Raspberry Pi · Session · OpenClaw · Hermes

Changes

• bridges/hermes/ — Hermes plugin (pre/post_tool_call, pre_llm_call hooks)
• docs/HERMES_INTEGRATION.md — integration guide
• docs/IMPLEMENTATION_STATUS.md — 10 bridges
• Version bump 1.8.10 → 1.9.0

---

Documentation · AISS Standard · PyPI

v1.8.10

v1.8.10

New

• piqrypt vigil — reopen Vigil dashboard with existing agents
• piqrypt demo — fully isolated sandbox (agents + peers purged before/after)
• Welcome screen in Vigil when no agents exist
• Demo mode banner in Vigil + wizard disabled during demo

Fixes

• Double browser open on demo fixed
• Agent created via piqrypt init now visible in Vigil immediately
• Free tier limit (3 agents) enforced in CLI and Vigil
• External demo peers (peers.json) purged on demo reset
• Post-demo cleanup moved to finally block (guaranteed execution)

v1.8.8 — Onboarding UX + fix CI bump_version

v1.8.8 — Onboarding UX + fix CI bump_version

v1.8.7 — Onboarding UX: demo + init + onboard + static page

v1.8.7 — Onboarding UX: demo + init + onboard + static page

bump: version 1.8.5 -> 1.8.6 — correct PyPI release

v1.8.6

bump: version 1.8.5 -> 1.8.6 — correct PyPI release

v1.8.5 — CI green, 501 tests

What's new

• ✅ 501 tests passing on all OS/Python matrix (3.9–3.12, Linux/macOS/Windows)
• BridgeProtocol v1.1.0 — unified API across all 9 bridges
• Fixed aiss mock contamination in test suite
• Fixed piqrypt.aiss namespace conflict

Install:
pip install piqrypt==1.8.5

v1.8.4 — Security hardening

What's new

Security hardening release — no breaking changes.

KeyStore reinforcement:

• scrypt N=2¹⁷ — brute-force resistance >400ms/attempt
• AES-256-GCM with 96-bit nonce + 128-bit auth tag
• Private key zeroed in RAM after use (_secure_erase())
• Magic bytes validation — corrupted key files rejected cleanly

AgentRegistry:

• Path traversal protection on all agent names (../, null bytes, backslashes)
• Agent directories created with chmod 700

New security test suite — 61 dedicated tests:

• KeyStore: timing attacks, corruption, RAM erasure
• Registry: path traversal, agent isolation
• Chain: signature forgery, payload tampering, fork injection

Install:
pip install piqrypt==1.8.4

fix piqrypt start path resolution + dashboard URL token

"v1.8.3 — fix piqrypt start path resolution + dashboard URL token"

fix piqrypt start path in installed wheel

v1.8.2 — fix piqrypt start path in installed wheel