hezo/src/lib/ at main · burrito.space/hezo · Tangled

burrito.space / hezo

0

group conversations with models and local files

0

hezo / src / lib /

at main 14 files

dietrich ayala feat: safer bot file edits — surgical edit_file + write-conflict guard 7w ago

feat: safer bot file edits — surgical edit_file + write-conflict guard Two safeguards on bot file writes: 1. edit_file (surgical): replace an exact old_string with new_string, matched against current content. A non-matching or ambiguous match is rejected without changing the file, and untouched regions — including a human's concurrent edit elsewhere — are preserved. Preferred over update_file for changes. 2. update_file (whole-file rewrite) now uses optimistic concurrency: the bot must read_file this turn AND the content must be unchanged since, or the write is rejected and the bot is told to re-read — so a concurrent human edit can't be silently clobbered. A per-invocation read-snapshot map (seeded by read_file/create_file and refreshed after each write) backs the check. Refactor: the tool set moved to a standalone buildFileTools(deps) so the write-safety logic is unit-testable against a fake store; ProjectStore delegates to it. System preamble updated to steer bots to edit_file. Verified the real buildFileTools end to end (12 cases): surgical replace/non-match/ambiguous/replace_all, must-read-first, stale-rejection, applies-when-fresh, and surgical-edit-preserves-concurrent-human-change.

1 month ago

Symmetric auth: passphrase-only accounts can add a passkey Closes the asymmetry from the previous commit. New endpoint /api/auth/passkey/enroll/{begin,finish} lets an already-authenticated user attach a passkey to their account. The new passkey's PRF output derives a wrap key (domain-separated via INFO_PASSKEY_MASTER_WRAP) that wraps the in-memory master; the ciphertext lands in users.wrapped_master_passkey. Future passkey logins unwrap with that key to recover the same master that a passphrase login would yield. - migration v6: ALTER TABLE users ADD COLUMN wrapped_master_passkey BLOB (nullable) - server/auth.ts: makePasskeyEnrollOptions + finishPasskeyEnroll; finishAuthentication now returns wrappedMasterPasskey (null for legacy passkey-first signups whose master IS the PRF result) - server/index.ts: enroll routes + login finish ships the wrap blob - Identity gains hasPasskey, computed everywhere alongside hasPassphrase - crypto.ts: derivePasskeyMasterWrapKey (HKDF info "hezo.passkey-master-wrap.v1") — distinct from the project wrap key so neither leaks the other on compromise - src/lib/auth.ts: loginPasskey unwraps when the server returns a blob, else falls back to master = PRF; enrollPasskey(email, master) runs the ceremony, wraps, and posts - App.tsx: SettingsModal grows a parallel "Enroll passkey on this device" section (visible only when hasPasskey is false); PasskeyNudge banner mirrors PassphraseNudge; on successful enrollment, the in-memory identity is optimistically updated so the banner + section disappear without a server round-trip

1 month ago

feat: never let auto-naming override a user-set conversation title Manual renames now lock the title: renameConversation({ manual: true }) sets a titleLocked flag on the conversation, and auto-naming refuses to touch a locked title. Closes the race where a user renamed a still- "Untitled" conversation while the title model was mid-generation — the guard was only checked before the multi-second generateText await, so a late result could clobber the fresh manual title. Auto-naming now also re-reads the conversation after the await and discards its result if the title was locked or changed during generation. titleLocked is an optional CRDT field (absent on older conversations = unlocked), so it merges and back-compats cleanly. Verified with a mock model: unlocked/Untitled gets a title; locked and already-titled conversations are untouched; and a manual rename (or any title change) during generation wins over the model.

1 month ago

feat: add known collaborators to a project directly (skip invite-code loop) Owners can add people they already co-member projects with to a new project without running the full invite-code exchange. Uses each account's existing X25519 identity_pub: the owner seals the project key to the collaborator's pubkey via an ephemeral-static ECDH sealed box, so the add is fully offline — no fresh handshake, no second party online, no schema change. The collaborator unwraps from their account master on next login. - crypto: peerWrap/peerUnwrapProjectKey + unwrapMyProjectKey (PRF self-unwrap with peer-wrap fallback so all call sites handle both formats) - server: listKnownCollaborators / addMemberDirect / getIdentityPub; GET /api/me/collaborators, POST /api/projects/:id/members (owner-only, gated on actual shared membership) - client: inline collaborator picker on owner project rows - name cache: client-only IndexedDB store (nameCache, DB v6->7) harvested from per-project CRDT profiles so the picker shows friendly names instead of sliced user-ids; no server-side name store

1 month ago

feat: add known collaborators to a project directly (skip invite-code loop) Owners can add people they already co-member projects with to a new project without running the full invite-code exchange. Uses each account's existing X25519 identity_pub: the owner seals the project key to the collaborator's pubkey via an ephemeral-static ECDH sealed box, so the add is fully offline — no fresh handshake, no second party online, no schema change. The collaborator unwraps from their account master on next login. - crypto: peerWrap/peerUnwrapProjectKey + unwrapMyProjectKey (PRF self-unwrap with peer-wrap fallback so all call sites handle both formats) - server: listKnownCollaborators / addMemberDirect / getIdentityPub; GET /api/me/collaborators, POST /api/projects/:id/members (owner-only, gated on actual shared membership) - client: inline collaborator picker on owner project rows - name cache: client-only IndexedDB store (nameCache, DB v6->7) harvested from per-project CRDT profiles so the picker shows friendly names instead of sliced user-ids; no server-side name store

1 month ago

keystore: auto-upload local keys when server has none Accounts predating the sync feature have keys only in IndexedDB on the device where they were entered, with nothing on the server. Without intervention, the other device's loadKeysSynced sees null and shows an empty Settings panel. loadKeysSynced now: when the server returns null AND the local cache has at least one key, push the local set up. Next device load gets the populated state. Fire-and-forget (.catch -> warn); no blocking on network.

1 month ago

namebackfill.ts

feat: proactively backfill stuck userId-as-display-name across all projects The per-open self-heal only fixes the project being opened. This boot-time sweep heals the local user's own display name in EVERY project they belong to, so peers see the corrected name without the user visiting each one. How: read each project's locally-persisted (unencrypted) Automerge doc — no key needed — to find ones where our profile is still the auto-seed userId.slice(0,8). For only those, briefly open a real ProjectStore (which persists + broadcasts the heal) on a DEDICATED OutboxClient, never the shared app outbox, so the sweep can't collide with or tear down the subscription of the project the user is actively viewing. Scope/limits: only the local user's own name can be healed (a peer's real name isn't available here); no-ops with no email or nothing stuck; idempotent (a healed profile no longer matches the seed). Runs in the existing boot harvest effect. Selection logic unit-tested.

1 month ago

feat: add known collaborators to a project directly (skip invite-code loop) Owners can add people they already co-member projects with to a new project without running the full invite-code exchange. Uses each account's existing X25519 identity_pub: the owner seals the project key to the collaborator's pubkey via an ephemeral-static ECDH sealed box, so the add is fully offline — no fresh handshake, no second party online, no schema change. The collaborator unwraps from their account master on next login. - crypto: peerWrap/peerUnwrapProjectKey + unwrapMyProjectKey (PRF self-unwrap with peer-wrap fallback so all call sites handle both formats) - server: listKnownCollaborators / addMemberDirect / getIdentityPub; GET /api/me/collaborators, POST /api/projects/:id/members (owner-only, gated on actual shared membership) - client: inline collaborator picker on owner project rows - name cache: client-only IndexedDB store (nameCache, DB v6->7) harvested from per-project CRDT profiles so the picker shows friendly names instead of sliced user-ids; no server-side name store

1 month ago

Outbox: client watermarks instead of server-side ack-delete Each device now persists a per-project watermark (highest createdAt seen) and passes it on subscribe; server returns rows past that and no longer deletes on ack. Outbox rows TTL out at 30d as before. Fixes the multi-device race where two devices for the same user shared a queue: whichever acked first deleted the row from under the other. iOS in particular kept getting an empty project after desktop's snapshot had already been ack-consumed by desktop itself. Reset-local now also wipes the cursor so the next subscribe starts from zero.

1 month ago

Smoke test + IndexedDB unify (v2 end-to-end smoke is green) scripts/smoke.mjs drives the Phase 1-4 stack end-to-end: - kills + respawns dev (`npm run dev`) against a fresh global.sqlite - pulls the Anthropic key from macOS Keychain (services "hezo", "centrosome", or "multiclaude") or $ANTHROPIC_KEY - launches Chromium via Playwright with a CTAP2.1 virtual authenticator that supports the PRF extension - registers smoke@hezo.local with a passkey - saves the key via the Settings modal - creates a project, adds @claude (Anthropic claude-sonnet-4-6), opens a conversation, sends a marker prompt, waits for the bot reply Fix during bring-up: persistence.ts and keystore.ts each opened the 'hezo' IndexedDB with a different version (1 vs 2). Whichever opened first won; the other's `indexedDB.open` failed with "requested version (1) is less than existing version (2)". - src/lib/idb.ts (new): single openDb() + withStore() pair shared by both modules. One DB, two object stores ('crdt' and 'providerKeys'). - src/lib/persistence.ts + src/lib/keystore.ts: switched to idb.ts. End-to-end: registration → key save → project create → bot add → message send → streamed Claude reply lands in the CRDT in ~1.5s. (Smoke test commit added at the same time so the fix can be re-verified later by running `npm run smoke`.)

1 month ago

Phase 4: BYO-model bots + composer + invocation Browser-direct model calls via Vercel AI SDK. Per-device multi-provider keystore. Bot data model in CRDT. Composer with @-mention parsing. Invoke flow: @bot in message → that bot replies, billed to @pinger's key, streamed into the CRDT, broadcast to peers. - src/lib/keystore.ts: per-device IndexedDB store for provider keys (anthropic / openai / google / openai-compatible URL + optional key). No server involvement. Shared 'hezo' IndexedDB with the CRDT store, separate object store. - src/lib/providers.ts: thin Vercel AI SDK wrapper. modelFor(bot, keys) returns a LanguageModel for streamText. Anthropic uses the dangerous-direct-browser-access header. MissingKeyError surfaces a friendlier message to the UI than a raw 401. - src/lib/crdt.ts: extended ProjectDoc with bots, conversations, turns. loadDoc backfills missing top-level keys for forward-compat with Phase 3 docs. New selectors: botList / conversationList / turnsInConversation / findBotByName. - src/lib/store.ts: new mutators for bots, conversations, turns. beginBotTurn / updateTurnText / completeTurn / errorTurn drive a streaming assistant turn. invokeBot runs streamText, accumulates chunks, writes through updateTurnText (broadcast throttled to ~400ms so peers don't see every keystroke-equivalent). - src/App.tsx: full rewrite of ProjectView into a sidebar + main pane. Sidebar shows members, bots (with key-status warning), and conversations. Main pane is a flat turn list + composer. Composer parses @mentions, appends a user turn, fans out to matched bots in parallel. Settings modal manages provider keys. Per-turn header shows '@botname' or the human's email handle + timestamp + status. New deps: ai, @ai-sdk/anthropic, @ai-sdk/openai, @ai-sdk/google, @ai-sdk/openai-compatible, zod (for future tool defs). Web + server typecheck clean. Vite build clean (1.28MB JS, gz 261KB — provider SDKs + Automerge make up most of it). Live invocation flow not yet smoke-tested in a real browser.

1 month ago

sessionstash.ts

fix: persist session across tab close via non-extractable key stash The PRF master secret was stashed in sessionStorage, which iOS Safari wipes on tab close. The server session cookie survived but the auth gate needs both, so mobile users hit the re-auth screen on every tab reopen. Move the stash to IndexedDB, encrypted under an AES-GCM key generated with extractable:false. The key's raw bytes are never exposed to script (exportKey throws), so an at-rest storage/profile dump yields only ciphertext plus an unusable key handle -- stronger than plaintext in localStorage, and the downstream key-derivation call sites are untouched since we still recover the raw PRF in memory on restore. - new src/lib/sessionstash.ts: stash/read/clear over a non-extractable IDB key; clears the legacy sessionStorage key on sign-out - idb.ts: add 'session' store, bump DB_VERSION 5 -> 6 - App.tsx: drop the inline sessionStorage stash; boot effect now restores the PRF asynchronously (fetchMe + readStashedPrf in parallel) Trust boundary: raises the at-rest bar; does not defend against live XSS (script on the origin can still decrypt) -- same posture as the 1-year session cookie. Existing users re-auth once, then the durable stash takes over.

1 month ago

feat: safer bot file edits — surgical edit_file + write-conflict guard Two safeguards on bot file writes: 1. edit_file (surgical): replace an exact old_string with new_string, matched against current content. A non-matching or ambiguous match is rejected without changing the file, and untouched regions — including a human's concurrent edit elsewhere — are preserved. Preferred over update_file for changes. 2. update_file (whole-file rewrite) now uses optimistic concurrency: the bot must read_file this turn AND the content must be unchanged since, or the write is rejected and the bot is told to re-read — so a concurrent human edit can't be silently clobbered. A per-invocation read-snapshot map (seeded by read_file/create_file and refreshed after each write) backs the check. Refactor: the tool set moved to a standalone buildFileTools(deps) so the write-safety logic is unit-testable against a fake store; ProjectStore delegates to it. System preamble updated to steer bots to edit_file. Verified the real buildFileTools end to end (12 cases): surgical replace/non-match/ambiguous/replace_all, must-read-first, stale-rejection, applies-when-fresh, and surgical-edit-preserves-concurrent-human-change.

1 month ago

feat: account-level bot-following + navigable browser history Bot-following — configure a bot once and it auto-joins every project you open (current and future, including invited ones), regardless of where you added it: - New per-device recipe store (src/lib/userbots.ts) synced to the server as a wrapped blob (wrapped_user_bots column, /api/me/bots), mirroring the existing provider-key sync. Recipes carry no secrets; the @pinger still spends their own provider key. - Propagation on project open: seed each recipe into the project CRDT with bot id = recipe id so it converges across devices and re-opens; per-device seed tracking so a manual removal sticks. - Startup harvest reads every project's locally-persisted (plaintext) Automerge doc and pulls the user's own bots up into the library, so the set is complete no matter which project is opened first. Sidebar "Add bot" also registers the bot in the library. - New IDB stores + DB v5; migration v8 adds the server column. - "My bots" manager in Settings. Navigation — fix the back button: - Opening a project now pushState's a history entry (was replaceState, so back had nothing to return to). In-app "back to Projects" delegates to history.back(); popstate resolves #p=<id> via an App-held project list so forward/back into a project works while the list is unmounted. History normalized on mount so deep-link/reload into a project still has the list beneath it.

1 month ago