@withbuddi/buddi 0.1.0-pre.27 → 0.1.0-pre.29

package/node_modules/imapflow/dist/esm/tools.js

@@ -645,9 +645,10 @@ export function getColorFlags(color) {
  *
  * @param untagged - Parsed untagged IMAP response
  * @param mailbox - Current mailbox state object
+ * @param idHashAlgorithm - Hash for the fallback message id, `md5` unless the client was told otherwise
  * @returns Formatted message object with properties like seq, uid, flags, envelope, etc.
  */
-export async function formatMessageResponse(untagged, mailbox) {
+export async function formatMessageResponse(untagged, mailbox, idHashAlgorithm) {
     let map = {};
     // The sequence number indexes into mailbox state, so an unusable one is dropped rather
     // than coerced to NaN or Infinity
@@ -829,13 +830,14 @@ export async function formatMessageResponse(untagged, mailbox) {
                 // ignore
             }
         }
-        // Non-cryptographic identifier: MD5 is used only to derive a stable, compact
-        // account-unique id from non-secret data (path:uidValidity:uid). No security
-        // property (collision/preimage resistance, secrecy) is relied upon, so a fast
-        // hash is the appropriate choice here - not a security-sensitive use.
+        // Non-cryptographic identifier: the hash only derives a stable, compact account-unique
+        // id from non-secret data (path:uidValidity:uid). No security property (collision or
+        // preimage resistance, secrecy) is relied upon, so the fast default is MD5; a host whose
+        // OpenSSL runs in FIPS mode has no MD5 and names another algorithm through the client
+        // option, at the price of ids that differ from the default ones
         map.id =
             map.emailId ||
-                createHash('md5')
+                createHash(idHashAlgorithm || 'md5')
                     .update([path, mailbox.uidValidity?.toString() || '', map.uid.toString()].join(':'))
                     .digest('hex');
     }

package/node_modules/imapflow/dist/esm/types.d.ts

@@ -44,6 +44,14 @@ export interface ImapFlowOptions {
     clientInfo?: IdInfoObject | undefined;
     /** If true, then do not start IDLE when connection is established */
     disableAutoIdle?: boolean | undefined;
+    /**
+     * Hash algorithm (any name Node's crypto supports) for the fallback message `id` that is
+     * derived from the mailbox path, UIDVALIDITY and UID when the server provides no email id
+     * through OBJECTID or X-GM-EXT-1. Defaults to `'md5'`, which keeps the ids earlier releases
+     * produced. A host whose OpenSSL runs in FIPS mode does not offer MD5, and has to set a
+     * different one, for example `'sha256'`, which yields a 64 character hex id
+     */
+    idHashAlgorithm?: string | undefined;
     /**
      * How long (in ms) the connection has to be inactive before IDLE is started automatically.
      * Keep it above the pause your own code usually leaves between two commands, otherwise every
@@ -97,7 +105,7 @@ export interface ImapFlowOptions {
     disableBinary?: boolean | undefined;
     /** If true, do not enable supported extensions */
     disableAutoEnable?: boolean | undefined;
-    /** If true, do not enable IMAP4rev2 mode even if the server advertises it, and do not treat the advertisement as support for anything IMAP4rev2 implies, such as the extended LIST syntax */
+    /** If true, do not enable IMAP4rev2 mode even if the server advertises it, and do not treat the advertisement as support for anything IMAP4rev2 implies, such as the extended LIST syntax. Servers known to misbehave in IMAP4rev2 mode (Strato RZimapd, detected from its ID response) are kept out of it without this option */
     disableIMAP4rev2?: boolean | undefined;
     /**
      * How long to wait for a usable transport, covering DNS resolution, proxy negotiation and the

package/node_modules/imapflow/package.json

@@ -1,6 +1,6 @@
 {
     "name": "imapflow",
-    "version": "2.1.2",
+    "version": "2.2.1",
     "description": "IMAP Client for Node",
     "type": "module",
     "main": "./dist/cjs/imap-flow.js",
@@ -72,13 +72,13 @@
         "c8": "12.0.0",
         "eslint": "10.11.0",
         "eslint-config-prettier": "10.1.8",
-        "globals": "17.12.0",
+        "globals": "17.13.0",
         "prettier": "3.9.9",
         "tsx": "4.23.15",
         "types-node-legacy": "npm:@types/node@20.0.0",
         "typescript": "6.0.3",
-        "typescript-eslint": "8.70.1",
-        "wrangler": "4.142.0"
+        "typescript-eslint": "8.71.0",
+        "wrangler": "4.145.0"
     },
     "dependencies": {
         "@zone-eu/mailsplit": "5.4.19",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@withbuddi/buddi",
-  "version": "0.1.0-pre.27",
+  "version": "0.1.0-pre.29",
   "type": "module",
   "description": "Your personal agents, on your computer",
   "repository": {
@@ -17,7 +17,7 @@
     "buddi": "packages/install/dist/launcher.js"
   },
   "buddi": {
-    "notes": "### Added\n\n- A reply that stops because it used all its steps now offers **Continue**: a button on the \"Turn budget reached\" line under the conversation's latest reply (while nothing is running), and a Continue button under the answer on Telegram. Either sends \"continue\" as you into the same conversation, once, and the agent picks up with the whole history.\n\n### Changed\n\n- The agent's Setup → Brain shows \"Steps per reply\" (was \"Max turns\"), with the built-in default of 40 named when the file sets none, a 10 to 500 range, and a hint that each tool call is a step. It saves through the same path as `buddi agents set --max-turns`.\n- The Developer agent the developer plugin proposes asks for 150 steps per reply instead of the default 40. An agent already installed keeps its file as it is.\n\n- Home opens on a glance: the date, a large greeting and what needs you as one line of counts, each a link to its list (failed jobs, urgent alerts, proposals; approvals and messages scroll to \"Needs you\"). On the right, the Weather plugin's card — now, sky and place, the next twelve hours as a small line, high and low — with the Blob in it; without the plugin the Blob stands there alone. The composer moved under the glance and is one line that grows as you type, with the Continue chips under it. On a phone it stacks.\n- The \"Keep buddi one click away\" card left the top of Home. Home now shows one quiet line at the foot, \"Install buddi as an app, one click from your dock\", only when the browser has offered an install; the owner menu has \"Install the app\" whenever it does, and Settings → System has \"The dashboard as an app\" with the bookmark tip and, on the Mac, `buddi dashboard --install-app`.\n- A plugin's Home glance can carry a card (a figure, one line, a run of numbers drawn as a sparkline, a foot); Home draws the first one on the right of the greeting. The Weather plugin sends one from its next release, and its glance opens the Weather page.\n\n### Fixed\n\n- Restoring a backup before reinstalling its plugins (the normal order on a new machine) skipped those plugins' data, and installing them afterwards gave empty tables. The restore now keeps each missing plugin's data under the data dir and loads it when the plugin is installed (or at the next start), into empty tables only; the recovery checklist says \"finance — 1,544 rows waiting, loaded when you install it\", a table that already had rows stays aside and is listed on its own, and `buddi doctor` shows what is still waiting.\n- An upgrade could leave Postgres unable to start (\"Library not loaded: …libicuuc.77.dylib\"), because npm did not run the Postgres package's script that makes its library links and buddi's own copy pointed back into npm's folder. buddi now makes the missing links itself before every Postgres start and keeps its copy self-contained, and an upgrade first checks that the new version's Postgres starts; if it does not, buddi puts the previous version back, keeps running, and the upgrade result says why.\n- A message an agent sent you repeated its \"@handle:\" at the start of the title on the dashboard, right under the agent's name. Home's Needs you, Settings → Notifications and the toasts now leave the signature off; Telegram keeps it."
+    "notes": "### Added\n\n- Widgets on Home: small live panels from your plugins — the weather at home, today's calendar, who is waiting on your reply — in a Widgets section under Needs you. Pick, order and size them (small or medium) from Edit, by dragging, with the arrow keys or with the move buttons; a widget's ⋯ menu moves, resizes or hides it, with Undo. A widget that fails to refresh keeps its last panel and says how old it is, one that never loaded offers Try again, and a sensitive one is hidden until you show it. The layout is kept by the installation, so your phone shows what your laptop arranged.\n- Widgets have settings of their own: each one on Home (and on the lock screen) can be set apart — the weather's place and units, which calendars and how far ahead, which mailbox, a time format — from Settings… in its ⋯ menu or the gear in Edit, in a sheet that shows it live. The same widget can sit twice (\"Weather\" and \"Weather · Work\"): Add another in Edit.\n- Plugins can export widgets (plugin host API 1.17): a manifest's `widgets`, each a read-only `produce` answering a body from a fixed vocabulary — stat, list, strip, progress, text — that buddi caches for the widget's refresh interval and gives five seconds. The bundled mail plugin adds \"Waiting on you\".\n- Plugin host API 1.19: a widget's settings schema (select, multi-select, toggle, text, place, time format), handed to `produce` resolved; `owner.formats()`; the tile icons `check` and `clock`.\n- The World clock, a widget buddi provides itself: the time at your places in other zones, or towns you pick.\n- The World clock has a Style: Digital, as before, or Analog — faces side by side like a phone's world clock widget, your own zone first and then your places, four at medium and two at small, with hour and minute hands and a thin accent second hand; a face is light while it is day there and dark at night, and under each sit the place, Today, Tomorrow or Yesterday, and the offset (\"+6 h\", \"−1 h 30\", \"Here\"). The faces tick on the page and stop their second hand under reduced motion; on the lock screen they are glass like the tiles. Each face is read aloud as \"Tokyo, 04:05 tomorrow, 8 hours ahead\".\n- Plugin host API 1.21: a widget can answer a `clocks` body — the owner's zone and up to four faces, each a label and an IANA zone — and the page draws and ticks the analog faces itself.\n- A PIN for the dashboard, kept on the server: once you set one, a dashboard session locks after a delay nobody used it for (5 minutes unless you pick 1, 15, 60 or never) or when you lock it, and every API call but the lock screen's own is refused until the PIN is typed — on every device, a remote one included. A new browser session starts locked, five wrong PINs bring a wait that doubles, and `buddi mcp` and Telegram are not covered. Forgot it: `buddi dashboard --unlock` opens the dashboard past it once (with a link for your other devices), `buddi dashboard --remove-pin` removes it.\n- The lock screen: the date and time large, counts of approvals and notifications waiting, your focus, up to four of your widgets (never a sensitive one) and the PIN, on the background you pick (five built-in ones or your own picture), with a pad on a phone. Nothing of the dashboard is drawn under it. Set it up in Settings → Lock screen; lock from the owner menu, the padlock at the end of the status line, or ⌃⌘L (Ctrl+Alt+L off a Mac). Forgot PIN? on the lock screen says what to run.\n- The lock screen keeps its own widgets, apart from Home's, and its own clock: in Settings → Lock screen → What it shows, a live preview beside the time format, the date style, a second clock (one of your places or any town) and up to four widgets, each with its own settings.\n- A tip on Home, \"Lock buddi with a PIN\", while no PIN is set and once there is something to lock — a second device signed in, a mailbox or money connected, or a week of use; it opens Settings → Lock screen, and dismissing it silences it for good.\n- On a phone, the status dot's menu ends with Lock now while a PIN is set, as the footer's padlock does on a wider screen.\n- Screenshots of the lock screen (desk and phone) and of Home with widgets in the README and docs/dashboard.md, from a demo installation.\n- Places in Settings → Profile: Home and Work (offered until you set them) and any other place you name, each with its address, the town it was found as on Open-Meteo, coordinates and its timezone. The front desk knows them, and plugins you allow can read them. The weather plugin's Home and Work move here once, at the first start.\n- Time and Dates in Settings → Profile: Auto (from the browser), 12-hour or 24-hour, and \"Thu, Oct 1\", \"Thursday, 1 October\" or 2026-10-01. Every date and time on the dashboard — Home, the lock screen, the status line, the calendar, tables — reads that way, and agents write them that way too.\n- Plugin host API 1.18: `ctx.buddi.owner.places()` behind the `owner:places` grant (shown on the install card), a manifest's `setup` answer, `requires` (repeated as `buddi.requires`), and `exports` — named read-only queries another plugin that requires it may call through `ctx.buddi.plugins.call`, on the read-only pool, with a timeout, never a tool.\n- A plugin that cannot do anything yet says so: its row on the Plugins page reads \"needs setup\" with what to do first and a Set it up button, the notice after the restart that loads it says the same, and a Home tip can name it.\n- A plugin can require another (`requires`, with a version range): the install card lists each requirement and offers \"Install … first\" for a missing one, and until each is installed, enabled, in range and set up the plugin waits — \"needs weather\" on its row, with the one fix — its tools and widgets off and its data kept. It comes in by itself the moment its requirement is ready.\n- A plugin installed from a folder can be reinstalled from it at the same version: \"Reinstall from folder\" in its row's menu and its detail, and `buddi plugins update <name>`, read and approved like any update, the card saying it is the same version read again.\n- A watcher's wakes can be gathered into one run: a sentinel that sets `coalesce` (plugin host API 1.20) has its wakes for the same agent folded together — the first waits two minutes for company, each that follows pushes it back by two more, none waits past ten — and the agent reads every finding in one run and sends one message. Finance's watchers do, so a bad week is one word from Ledger instead of one per card and bill. The wake mission can also be told to coalesce for every watcher.\n- Owner API tokens, for using buddi from a script or another program without the dashboard: make one in Settings → API tokens or with `buddi api-token create <name>` (shown once, kept only as a SHA-256 fingerprint), send it as `Authorization: Bearer <token>`, list and revoke them in Settings or with `buddi api-token list|revoke`. A token acts as you but never approves anything, writes through a plugin page only by asking (an approval card, never a tool that runs at once), changes an agent's grants, installs code, changes how buddi is reached or unlocked, or reads a secret; a wrong or revoked one counts as a failed sign-in, and the lock screen does not cover it.\n- docs/api.md, the HTTP API reference: every route the dashboard uses (255 of them) by area, with what it takes, what it answers, how it fails, since when, whether an API token may call it and a curl line, plus the base URL, how to authenticate, the error format and the sign-in lockout. Generated from the gateway's route table by `pnpm docs:api`; a test fails when a route has no entry or the page is behind.\n\n…"
   },
   "files": [
     "packages",