mem0's delete kept the deleted text in memory_history, and fact extraction
keeps the last messages of each scope in the same file. forget now purges
the memory's history rows, and forgetting a whole scope also drops the
conversation messages mem0 kept for it.
Team mode stays in the repository but is not built or shipped (ADR-0003).
- The team server (index.ts, config, db, daemons, plugins, proactive,
routes, scheduler, services, ws, drizzle migrations) and its tests move
from @waggle/server to packages/team-server (@waggle/team-server,
private). It keeps its own copies of the logger and the agent-group
executor, so it does not import @waggle/server. @clerk/fastify, bullmq,
ioredis, postgres, drizzle-orm, drizzle-kit, cron-parser and
@waggle/waggle-dance leave @waggle/server; the launcher drops the same
team-only dependencies.
- build:packages no longer builds waggle-dance or the worker: nothing in
the community edition imports them, and the worker's project reference
would otherwise build the team server. The worker now imports from
team-server; the team Dockerfile builds both explicitly.
- The sidecar no longer starts the team server when DATABASE_URL is set,
and loses the team routes (/api/team/*, /api/teams), the WaggleDance
routes and bridge (/api/waggle-dance/*), the Team server binding and
egress guard, the WebSocket team client, the TeamSync cache and pushes,
team audit forwarding, team workspace registration and the team
capability-policy lookup in chat. The in-process room signal bus stays:
agent groups, fleet runs and external tool runs use it.
middleware/audit.ts was dead and is deleted.
- @waggle/core loses TeamSync and the teamServer part of WaggleConfig. A
teamServer key in config.json is ignored and kept on save, as P0.1 does
for the tier keys. Workspaces lose teamServerUrl and teamUserId; teamId
and teamRole stay because workspaces from a shared data directory still
carry them and the viewer write guards read them. POST /api/workspaces
ignores team fields.
- The sidecar bundle no longer marks the team packages as external.
The agent still references the TeamSync type in orchestrator.ts and
pattern-write-back.ts; those files are being rewritten in P1.5 and drop
it there.
Logs UF-030 and UF-031 (team sync and team policy defects found while
removing the code).
Nothing created an S3FileStore outside team workspaces; team storage is
postponed with team mode (ADR-0003), so such workspaces use virtual storage.
@aws-sdk/client-s3 leaves core's dependencies.
- Pinned Ollama 0.32.3 (and rollback 0.32.0) Linux x64/arm64 artifacts with
their published SHA-256 and sizes; .tar.zst archives are decompressed by
Node 22's zstd and unpacked by the system tar.
- install.sh sets ONNXRUNTIME_NODE_INSTALL_CUDA=skip: onnxruntime-node
otherwise downloads CUDA libraries on every Linux x64 install.
- Drop the root sqlite-vec-windows-x64 dependency; the sqlite-vec package
already carries per-platform binaries.
Weaver consolidated and decayed frames of the legacy memory engine; mem0
updates and merges memories itself. The ChatGPT/Claude export import wrote
frames and its screen is hidden in v1 (ADR-0002).
Baileys depends on libsignal (GPL-3.0), which the sidecar bundled. The
WhatsApp adapter now drives WhatsApp Web through whatsapp-web.js and
keeps its public shape: start, stop, status with the pairing QR, send
and inbound text. LocalAuth stores the session as a browser profile in
<dataDir>/channels/whatsapp; the old Baileys state is left untouched.
The browser comes from whatsapp-browser.ts: CHROME_PATH or
PUPPETEER_EXECUTABLE_PATH, then an installed Chrome, Edge or Chromium
(Windows, macOS, Linux), then a Chrome for Testing build downloaded on
the first start into <dataDir>/browsers, with progress in the status.
The root .puppeteerrc.cjs stops npm install from downloading a browser.
The sidecar build keeps whatsapp-web.js external: bundled, it fails on
__dirname and would inline LGPL node-webpmux. Text only, so ffmpeg is
never needed.
New dependencies, pinned: whatsapp-web.js 1.34.7 (Apache-2.0) and
@puppeteer/browsers 2.13.0 (Apache-2.0). Transitive: puppeteer,
puppeteer-core, chromium-bidi, webdriver-bidi-protocol (Apache-2.0),
devtools-protocol (BSD-3-Clause), extract-zip (BSD-2-Clause),
fluent-ffmpeg and the rest (MIT or ISC), and node-webpmux
(LGPL-3.0-or-later, shipped as a separate package; needs the license
review). Removed: @whiskeysockets/baileys and libsignal.
UF-020 is now Fixed; ADR-0005 records the consequences.
- Orchestrator, memory tools, context loader and pattern write-back use a
MemoryStore and a workspace scope instead of MindDB layers; the knowledge
graph tools, cognify, memory linker and feedback handler are gone (graph
hidden in v1, ADR-0002).
- The server opens one mem0 store in <dataDir>/memory/, embedded by the
in-process model on first use, and extracts facts about the user in the
background with the model the user chose (memoryExtraction setting).
- Legacy .mind memories are copied into the store once, in the background;
the legacy files are only read.
- Weaver consolidation, harvest, wiki, memory import, memory lanes, vector
backfill and index reconciliation are removed; agent runs, loops, sub-agent
results, connector fetch and the failed-turn capture write through the
contract. Workspace sessions no longer hold a mind handle.
- FileIndexer and the install audit move to waggle.db; recall date helpers and
the reranker are copied into core.
- The CLI REPL opens the same memory store.
The memory MCP server serves the .mind file directly, so it uses the
substrate's IdentityLayer and AwarenessLayer instead of the waggle.db ones
that @waggle/core now exports. The WaggleDB-only constructors caught the
mismatch at build time.
Waggle kept its own tables in the memory database. Before the memory
engine can be replaced by mem0 they need a home of their own.
- add WaggleDB (<dataDir>/waggle.db). Automations, notifications, held
actions, skill hashes, thumbs feedback, cost tracking, the profile card
and awareness items live there. Their stores take a WaggleDB, so passing
a memory database is a type error.
- the profile card and awareness items are now per scope ('personal' or
'workspace:<id>') in one table each, instead of one table per .mind file
- on the first start, copy these tables from personal.mind and every
workspace.mind (importLegacyMindData). The legacy files are only read,
each scope is copied once and a table only while its target is empty.
- copy the logger, injection scanner, external-memory ingress guard,
WorkspaceManager and the embedders from @waggle/hive-mind-core into
@waggle/core, which now re-exports its own copies
- point the server, agent orchestrator and CLI at waggle.db; update the
tests that seeded these tables in a memory database
ADR-0007 records the layout and the licensing question about the copied
files.
Self-learning is excluded from the community edition (ADR-0004); the
project owner reworks it separately. Cost tracking stays.
- agent: delete behaviour evolution (evolve-schema, iterative GEPA,
compose-evolution, evolution gates, orchestrator and deploy),
improvement and correction detection, AgentLearning, the eval-dataset
builder, optimization-capture and the agent_insights tool. Secret
detection moves from eval-dataset to secret-patterns. The LLM wiring
keeps only the Haiku adapter and judge call used by skill audit and
hygiene, so @ax-llm/ax is now declared by agent instead of server.
- server: delete /api/evolution/*, the evolution and optimizer services,
GEPA expansion of the first chat message, the prompt_optimization and
monthly_assessment jobs, the idle-session reviewer and its
session-reviewer persona, prompt injection of past corrections and
thumbs-down recorded as correction signals. Existing job rows of the
removed types are ignored, not deleted.
- core: delete OptimizationLogStore; stop re-exporting the improvement
signal and evolution run stores.
- web: delete the Evolution screen and the two job types in the
automation editor.
- delete packages/optimizer.
Also logs UF-027 (self-learning loops read data nothing collects) and
UF-028 (the Settings prompt-shape choice is ignored by chat).
@waggle/memory-contract defines MemoryStore: remember (text, or a
conversation to extract facts from), search, list, count, get, update,
forget, forgetMatching and history over personal and workspace scopes,
with kinds, importance, source, origin and session in place of the old
content prefixes and named sessions. It ships an in-memory store and a
compatibility suite that every implementation runs.
@waggle/memory-mem0 implements the contract on mem0ai 3.3.1 in-process:
SQLite files in one directory, scope as mem0's agent_id, Waggle's own
embedder through mem0's langchain provider, fact extraction through any
OpenAI-compatible endpoint. mem0's telemetry and remote notice download
are switched off before the module loads; a test asserts that no request
is made. Memory survives a restart (tested).
New dependencies: mem0ai 3.3.1 (Apache-2.0, pinned exactly) with its
required peers compromise (MIT) and @cloudflare/workers-types (MIT OR
Apache-2.0); transitive openai (Apache-2.0), axios (MIT) and others under
MIT or BSD-2-Clause.
Packages relied on npm hoisting for imports they never declared, so a
package installed on its own fails (UF-024).
- server: + @waggle/marketplace, @waggle/sdk, @waggle/weaver, zod (MIT),
@anthropic-ai/sdk (MIT), @ax-llm/ax (Apache-2.0);
- @waggle/hive-mind-shim-core and stripe (unused)
- agent: + pdf-parse (Apache-2.0); playwright-core (Apache-2.0) as an
optional peer, since it is loaded only when available
- worker: + @waggle/waggle-dance; web: + @waggle/shared
- launcher: + @waggle/server as a dev dependency (bundled by tsup);
- stripe; cli: - @waggle/weaver (unused); root: - stripe
scripts/check-workspace-deps.mjs (npm run check:deps) compares the
imports in each community-edition package's src/ with its manifest and
runs in CI. Two imports wait for P1.4 (optimizer, evolution wiring).