The checkout-queue test searches memory for 'SSE resilience test frame'. The
text used to reach mem0 only through the background copy of the seeded
legacy personal.mind; write it with server.memory instead.
- harvest-provenance: tested the removed harvest pipeline (RawArchive and
frame metadata), which no longer exists.
- benchmarks: drop the FTS5 frame search and frame/session write
benchmarks; they measured the legacy engine only.
- trust wiring: read install_audit from waggle.db through the server; the
old checks read a legacy personal.mind that nothing writes any more.
- data dir: a fresh install is marked by waggle.db, not personal.mind.
- backup: expect waggle.db and memory/ in the archive.
- cross-platform: replace the MindDB block with waggle.db checks (file, WAL,
foreign keys) and memory round trips (plain, Unicode, 100 KB) through
server.memory. FTS5 and session CRUD were legacy-engine features.
- store fixtures (install audit, cron) open WaggleDB instead of MindDB.
The server no longer opens personal.mind, so tests build it on an empty
data directory. The /memory command test seeds its two memories through
server.memory and now checks that the seeded text is found.
The persona memory-denial and cron Loop tests counted rows in the legacy
personal and workspace minds, which nothing writes any more. Count
server.memory per scope (and origin 'loop' for the truncated Loop report)
instead, and stop seeding a personal.mind the server no longer opens.
- The WaggleDance routes left the sidecar with team mode, so the
x-waggle-run-token header no longer opens /api/waggle-dance/signal or
/api/waggle-dance/signals. A run token still authenticates only as a
Bearer on /v1/chat/completions (OpenClaw).
- Remove the session inactivity timeout. It switched on only in team
mode, when CLERK_SECRET_KEY was set.
Connectors, the connector SDK and registry, setup-connectors, provider-env,
the LiteLLM runtime config and the sidecar's `vault` decoration only read and
write secrets, so they now take the SecretStore interface. VaultStore is still
constructed in the sidecar and the service startup, and its file format is
unchanged. AGENTS.md now points at the interface.
VaultStore.migrateFromConfig had two callers, both in the server. It is now
copyProviderKeysToVault in provider-env.ts, next to
migrateLegacyProviderKeysToVault, with the same rules: copy keys that have a
value, keep keys the vault already holds, store models and baseUrl as metadata.
Its tests moved from core to provider-env.test.ts.
getConnectorCredential, setConnectorCredential and setConnectorCredentialBundle
are now plain functions over a SecretStore in
packages/agent/src/connectors/connector-credentials.ts. The secret names,
metadata layout and the rule that tokens never go into plaintext metadata are
unchanged, so existing vault files keep working.
A bundle still lands as one update: SecretStore gains writeBatch, which
VaultStore applies with a single vault-file replacement.
Connector tests seed a Map-backed SecretStore instead of mocking VaultStore
methods; the helper tests from core and server moved to the agent package.
The memory HTTP API reads and writes server.memory instead of the legacy
MultiMind, FrameStore, SessionStore, KnowledgeGraph, MindErasure,
SuppressionStore and RawArchive objects.
- memory.ts: search (personal, workspace, all, global), frames list, write,
edit and delete, stats and quick capture on the contract. Ids are strings.
The access-count route is gone. New GET /api/memory/capabilities and
PUT /api/memory/settings { extraction } for background fact extraction.
- memory-center.ts: list, get, create, patch, archive, confirm, trace,
delete, erase and merge on the contract. Archive sets importance
'temporary' (skipped by recall) and remembers the old importance; confirm
stamps metadata.confirmedAt; 'unreviewed' means extracted in the
background and not confirmed. Erase forgets one memory or every memory of
a chat session. The original-source and suppression routes are removed:
there is no raw archive and no harvest to re-import from.
- knowledge.ts returns an empty graph (not part of v1).
- export.ts writes memories/personal.json and memories/workspace-<id>.json
from the contract.
- identity.ts loses a dead resolver; the erase safety check recognizes
waggle.db.
- memory-records.ts holds the scope, status and creation-time helpers.
- normalizeToMemory stays in memory-center-legacy.ts until home.ts and
artifacts.ts read memory through the contract.
- @waggle/shared MemoryKind follows the contract's kinds; Memory gains
origin and sessionId.
Tests: new memory-routes and memory-center tests on the in-memory store;
local-mode and data-export tests seed memory through the contract; tests of
removed behaviour (source, suppression, sticky erasure, graph projection,
legacy normalizer, old erase and stats) are deleted.
- Workspace sessions, fleet runs, agent groups, loops, the file indexer,
external tool runs, chat and the health endpoint are checked against the
memory store instead of .mind files. Assertions on mind-cache pins and
releases go with the pins; the drain and cancellation checks stay.
- Delete the sticky-erasure test (harvest import was removed) and the
session-distillation test (distillation on workspace activation was
removed).
- The saved-history retry test checks the conversation only: the failed
user turn is kept in workspace memory by design (#3).
Chat collaboration writes run results to memory in the background and
records the memory refs when the writes finish. That update recomputed the
parent Room, so a workflow Room turned 'completed' while its synthesis step
was still running and could no longer be cancelled. A memory-refs update
never changes a run's status, so it no longer recomputes the parent.
The collaboration tests use an in-memory memory store and wait for the
background writes before reading memory refs.
- Artifact Center related search lists personal and workspace memories
through server.memory and finds related chat sessions in the session
files (UF-034).
- /api/agent/run searches the requested workspace's memory, or personal
memory when no known workspace is given.
- Executor briefs search only the workspace's own memory and leave out
temporary memories in the query; route proposals no longer borrow a
mind from the cache.
- Onboarding treats any personal memory as evidence of prior use.
- The service no longer creates personal.mind on a fresh install, and
isFirstRun also looks for waggle.db.
- 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).
- 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.
- 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.
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).
KVARK is the commercial enterprise product and is not part of the community
edition. The agent's KVARK tools were never wired into the server, so
removing them changes no runtime behaviour beyond the routes listed here.
- agent: delete kvark-tools; CombinedRetrieval and formatCombinedResult now
merge workspace and personal memory only (no KVARK lane, no source
conflict note); connector substrate is always 'waggle'
- agent: promote_skill stops at workspace scope; team and enterprise scopes
answer "not available in this edition" instead of an upgrade prompt
- server: delete src/kvark and GET /api/marketplace/enterprise-packs
- marketplace: delete ENTERPRISE_PACKS
- compliance (EU AI Act dashboard, its templates and the KVARK template
seeded on every boot): delete core/src/compliance, the /api/compliance/*
routes, agent compliance-pdf and the Cockpit compliance panel. The
ai_interactions table lives in the memory substrate and goes with P1.5.
The community edition has no monetization (ADR-0001). Remove the tier
model (packages/shared/src/tiers.ts), the requireTier middleware and every
tier gate, GET/PATCH /api/tier and the trial start, and the Stripe
integration, which depends on the tier model.
Personal features a tier used to limit are open to everyone: unlimited
workspaces and connectors, every embedding provider including LiteLLM,
per-workspace costs, Approvals. The workspace session cap is one constant
(100). Team and enterprise surfaces are hidden instead of unlocked (team
dock zone, Settings Team/Enterprise/Plan tabs, workspace Team tab);
cloud sync reports unavailable, as it did for free users.
The sidecar ignores the tier keys in config.json but does not delete them:
both editions may still share ~/.waggle.
Web billing UI is deleted: plan cards, upgrade and trial modals, payment
success route, the KVARK sales block, tier 403 handling.
A non-streaming /api/pull holds the response headers until the download
ends, and Node fetch gives up on headers after five minutes, cancelling
every larger model pull. Request stream:true and read the NDJSON progress,
failing on an in-stream error or a missing success status (UF-008).