- Workspace state, the "Workspace Now" block, the home briefing and the
proactive handlers read the workspace's memory through server.memory:
decisions are memories of kind 'decision', critical ones or ones worded
as decisions; summaries list memories most important first. They no
longer open workspace .mind files, so the builders are async and
ProactiveContext carries `memory` instead of `getWorkspaceMindDb`.
- The home briefing counts extracted personal facts that are neither
confirmed nor archived as awaiting review (memory-status.ts).
- Workspace routes count memories through the contract, seed template
starter memories with remember() in the background (origin
'workspace-template'), export memories through list(), and deleting a
workspace forgets its memory scope and clears its awareness items before
the directory is removed; the delete is refused if forgetting fails.
agentState.releaseWorkspace() replaces closeWorkspaceMind for callers.
- The command palette searches personal memory and the active workspace's
memory (UF-033).
- chat.ts drops the MindDB-flake diagnostics; the mind cache they guarded
no longer serves chat turns.
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).
The WhatsApp card in Settings > Channels now says the client is
unofficial, that WhatsApp may block the account, and that a browser is
downloaded (about 170 MB) when none is installed. While the adapter
looks for or downloads the browser, its status detail is shown above
the QR.
The setup hint told users to send /pair from the "Message yourself"
chat, which the adapter never reads because own messages are dropped.
It now says to send it from another WhatsApp account (UF-030).
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.
- Analytics are opt-in (decision Q7, ADR-0006). PostHog does not start or
capture anything until the user clicks Allow in a first-run dialog that
says what is sent. Escape or closing stores nothing and asks again. The
existing Privacy & Telemetry toggle in Settings withdraws consent at once.
Builds without VITE_POSTHOG_KEY show no dialog and send nothing.
- Remove the remaining upsell copy: the /team page with its per-seat price,
Stripe and Teams wording in the erase-data dialog, Teams/Enterprise hints.
- Remove team screens (decision Q3): Waggle Dance, team presence in chat,
team storage and sharing in workspace creation, storage and files.
- Hide memory features that are not in v1 (decision Q2) behind one map in
lib/memory-features.ts: the knowledge graph, import history, wiki, agent
memory hooks and Room launches. The map is the seam P1.5 fills from the
memory store's capabilities.
- Say Windows, macOS and Linux instead of "Linux soon".
- Update the e2e specs for the removed and hidden screens.
Also logs UF-029: the Settings "Import Data" button has no handler.
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).
ADR-0007 maps today's memory usage onto the contract and mem0: profile
card and tasks move to waggle.db, learned facts stay in mem0, extraction
runs in the background in batches. Research notes cover what mem0 3.3.1
does and how 68 files use memory today. Two defects found on the way are
logged for the main project (UF-025, UF-026).
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).
The marketplace installer and the skill security cache resolve paths from
os.homedir() at import time, so npm run test wrote fixtures into the real
~/.waggle/security-cache and ~/.waggle/plugins/registry.json. Point HOME
and USERPROFILE at a temporary directory per worker and silence npm's
update notice that a fresh home triggers (UF-022). Log the four test
files that fail on macOS (UF-023).