V1.4.2 - #432
Open
ahmad-ajmal wants to merge 62 commits into
Open
Conversation
Ai Enhance Fix
Advertisement widget for CraftBot dashboard
Advertisement Widget
Feature/guided tour
…onse-question feat: agent questions with suggested responses (pinned question box)
) * fix: unify Living UI dev/live lifecycle to stop live pb_data wipes * feat: scheduled + pre-promote backups of Living UI live data * change delete orphan living UI project to log only * set living UI launch by default and optimize launch time * fix: naming fix + backup on reset agent * fix: restore UI + restore from leftover backups --------- Co-authored-by: CraftBot <craftbot@craftbot.dev>
fix: merge reset-agent chat options and refresh the session list
…ement Feature/memory system improvement
* feat(integrations): multi-account support with aliases and per-account listeners Rebuilt the integration layer as a host-agnostic package (supersedes PR #370; design: docs/plans/multi-account-v2-plan.md). The 10 major integrations now hold a primary account plus any number of additional accounts with nicknames (shared across the Google family). - AccountSet document store: atomic writes, deterministic account resolution, one-time migration of existing credential files - 10 providers / 397 operations; @action wrappers are generated, with the account param injected centrally so no action can bypass it - OAuth account choosers fixed (Google/Outlook select_account) - Manage-accounts modal with staged edits and add-account OAuth - Gmail/Outlook/Slack listeners run per account, triggers account-tagged - Router extracts account qualifiers ("my job email") and sees live account lists just-in-time 516 tests passing, tsc clean. closes #368 * integrations: multi-account for all 23 platforms via auth-layer bridge Legacy platforms get thin v2 providers (identity + login + bound client + listener); their existing actions stay and become account-aware centrally (contextvar hint + run_client routing + schema injection into 676 actions). whatsapp_web moves from a singleton Node bridge to per-identity bridges with QR sessions and a max_accounts cap; telegram_user logs in via two-phase phone->code(+2FA) token connect. Also fixes: fcntl broke the v2 system on Windows (msvcrt locking); list/info/metrics read legacy cred files so v2 connects showed disconnected; notion token connects could silently overwrite the first account. Adds manage_integration_account agent action and Living UI account param. 609 tests green. * Integrations Fix + media recieve * fix(integrations): resolve tester-reported failures across Jira, disconnect, Lark, WhatsApp, and notifications * fix(integrations): gmail forwards carry the original body, whatsapp replies route to the receiving account, discord multi-server sends land once in the right channel * feat(whatsapp): desktop-parity session durability — per-account session actor with supervised reconnect/heartbeat, bridge.js generation rewrite (no synthetic ready, PID-exact kills), LinkFlow QR with idempotent completion, legacy single-account path removed * fix(whatsapp): adopt the live bridge at link instead of restart-from-disk (torn LocalAuth), park never-connected sessions as needs-relink, resolve account="primary" * feat(whatsapp): migrate bridge from whatsapp-web.js/Chromium to Baileys — protocol-native WebSocket, plain-file sessions, ~50MB/account, legacy system fully removed (existing accounts re-link once via QR) * install whatsapp bridge * update multiaccount integration setting UI * use SVGL for integration logo * fix: env install for transformers --------- Co-authored-by: CraftBot <craftbot@craftbot.dev>
… V1.4.2 # Conflicts: # agent_file_system/ENTITIES.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CraftBot V1.4.2
Changes since V1.4.1.
Highlights
Multi-account integrations (#419)
All 13 legacy integrations migrated to the multi-account architecture via an
auth-layer bridge — connect multiple accounts per platform (Gmail, WhatsApp,
Discord, Slack, YouTube, etc.). WhatsApp moves to a session-actor architecture
on a Baileys bridge (no headless browser); existing accounts re-link once via QR.
Memory graph (#421)
and retrieved as embeddings and a graph visualization UI.
Living UI unified dev/live lifecycle (#427)
Single environment flow that stops live
pb_datawipes on redeploy —schema-only dev DB, with migrations replayed against live data only at promote.
Outdated Living UI settings sections removed.
Agent questions with suggested responses (#430)
Questions from the agent surface as a pinned question box above the composer
with clickable suggested replies, backed by a derived unanswered-question queue.
UI / UX
empty input, disabled send/dictate states, loading spinner, 30s timeout,
splash loading animation.
Fixes
page reload required (fix: merge reset-agent chat options and refresh the session list #429).
run_shelloutput mangling.Testing
New coverage for multi-account WS handlers, WhatsApp bridge/session-actor/
link-flow conformance, YouTube provider, and chat session storage.