Skip to content

v0.2.0 — Trust foundation

Latest
Latest

Choose a tag to compare

View all tags
@ikeikeikeda66 ikeikeikeda66 released this 27 Sep 01:16
· 21 commits to main since this release
v0.2.0
3586eb1
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

0.2.0 — Trust foundation / 信頼の土台

You decide which assistants may read your history, what is never recorded, and how long anything is kept. Roadmap Phase 1 (#3).

Added

  • Per-client tokens for the MCP server (mcp-config issues one per client; only its SHA-256 is stored), with a profile ceiling per client, clients list and clients revoke.
  • First-connection approval: a new client's first call asks in the menu bar app or the Windows control window, also while capture is paused; clients approve from the terminal.
  • Audit log in the encrypted database: client, query text, arguments and returned frame IDs for every tool call. audit list and audit export; never served over MCP.
  • Sensitive input: frames with card numbers (Luhn) or My Number (check digit and label) are dropped; name + address, phone, date of birth or e-mail within 5 lines is redacted; the contacts app and checkout pages are excluded by default. pii-check FILE, and pii-scan [--apply] for earlier history.
  • Data control: purge with a dry run and a cascading delete; retention for previews, text and the audit log; usage; wipe (key first); passphrase-protected backup and restore; export --from/--to --format jsonl|md|csv|viking, audited so purge warns about copies.
  • Settings resolver (managed > user > default) for administrator-locked settings.
  • packaging/macos/signing_identity.sh: a self-signed identity that keeps the Screen Recording permission across rebuilds.
  • Phase 0 probes for real hardware in spikes/phase0/.

Changed

  • Database schema v3. Run screen-context init after updating; health reports needs_init until then.
  • MCP entries now carry SCREEN_CONTEXT_CLIENT_TOKEN. Entries from 0.1 must be created again with mcp-config.
  • export DATE is deprecated; use export --format viking.
  • packaging/build_mac.sh signs every nested extension module and applies packaging/entitlements.plist (library validation off), so a self-signed build starts under the hardened runtime.

Fixed

  • Windows: capture skips a locked session instead of crashing the capture library, and a crashed worker restarts up to 3 times in 10 minutes (#47).
  • Windows: approval dialogs open in front of other windows (#50).
  • Windows: CLI output is UTF-8 in the frozen build (#44); OCR works with the current SoftwareBitmap bindings (#45).
  • uv.lock matches pyproject.toml again, so uv sync --locked works.

Known limitations

  • The macOS app is not notarized: build it on the Mac that runs it.
  • Capture does not yet pause while macOS Secure Input is on (#16).
  • A truncated duplicate OCR line can escape personal-data redaction (#55).
  • Windows remains beta (#25).

日本語の要約

  • 追加：クライアント別トークンと初回承認、監査ログ、機微入力（カード番号・マイナンバー・氏名との組み合わせ）の除外、purge・retention・usage・wipe・backup/restore・期間指定の export、自己署名証明書を作るスクリプト。
  • 変更：DB スキーマ v3（更新後に init を実行）。MCP の設定は mcp-config で作り直す。export DATE は非推奨。
  • 修正：Windows の画面ロック時のクラッシュ、承認ダイアログの前面表示、文字化け、OCR。uv.lock の不整合。
  • 既知の制限：macOS アプリは公証なし（各自の Mac でビルド）、Secure Input 中の撮影停止は未対応、OCR の重複行による伏せ字漏れ、Windows はベータ版。
Assets 2
Loading