Skip to content

v1.7.2

Choose a tag to compare

@Intina47 Intina47 released this 06 Apr 02:30
· 3 commits to main since this release

jot v1.7.2

This release hardens jot assistant from the first 1.7.x launch into something much more useful for real daily work. The focus is Gmail and Calendar completion, browser-computer form handling, journal backup and restore, and the first native messaging-channel groundwork.

What's new

  • Added journal backup export and restore flows for jot assistant, including:
    • export my jot journal and email it to me
    • import my jot journal from Gmail
  • Added Gmail send fallback to draft, so if sending fails Jot saves the message in Gmail drafts instead of dead-ending.
  • Added inline Gmail send re-auth in assistant flows, so Jot can reconnect Gmail send access and continue the original action automatically.
  • Expanded Gmail and Calendar assistant flows around:
    • read
    • reply
    • schedule
    • clear
  • Added browser-computer form handling with:
    • direct form URL support
    • browser-first filling and review
    • question-by-question progress
    • stronger Microsoft Forms reliability
  • Added the first shared assistant memory scaffolding and native messaging-channel groundwork.
  • Added WhatsApp native bridge scaffolding with a Baileys-backed local bridge under tools/whatsapp-bridge.
  • Improved assistant docs, onboarding guidance, and local developer handoff docs.

Notes

  • This release is still local-first. Gmail and Calendar remain designed around private/local OAuth setup.
  • Browser-computer form support is materially stronger than 1.7.0, but it is still best treated as beta across arbitrary websites.
  • WhatsApp native bridge groundwork is included, but the full always-on message runtime is not the headline production surface yet.

Release notes

  • GitHub release assets are built locally for v1.7.2.
  • Homebrew formula metadata is updated from the local release pipeline.
  • npm metadata is updated to 1.7.2, but publishing still depends on npm authentication.
  • Chocolatey packaging metadata is updated locally; publishing still depends on CHOCO_API_KEY.