ADR-0010 records that the marketplace catalog holds package metadata
only (names, authors, licenses, short descriptions, links, install
instructions), like any package index, and needs no licensing review.
The pending licensing row of the ADR index keeps only the copyright
holder in LICENSE; the settled items (Apache-2.0 files in core, the
notices and the LGPL terms, the catalog) are listed below the table.
The README names the Apache-2.0 files of packages/core.
The notices now carry the LGPL-3.0 and GPL-3.0 texts from
scripts/license-texts (the LGPL text byte-identical to gnu.org's, the GPL
text as the Rust toolchain ships it), whatever the dependencies ship.
The LGPL section names each component with its exact version, says it
ships unmodified as a separate library, and gives the upstream source
release of that version: sharp-libvips v1.3.2 and libvips v8.18.3 for
the libvips packages, sharp v0.35.3 for @img/sharp-win32-x64, the npm
package of node-webpmux 3.2.1. The libraries built into libvips are
listed with their versions from versions.json. Versions and repository
URLs come from the lockfile and the installed packages.
The LGPL exceptions of the license gate are no longer pending: the
project owner left these items to us. A test checks the texts, the LGPL
rows and the Apache-2.0 files against the committed notices. UF-059 is
fixed.
The logger, injection scanner, ingress guard, WorkspaceManager, embedders,
recall helpers and execution traces came from @waggle/hive-mind-core
(Apache-2.0); awareness, identity and parts of WaggleDB were adapted from
it. They keep Apache-2.0: an SPDX header with the original copyright line
and the source file, packages/core/LICENSE.md listing them,
LICENSE-APACHE with the full text, and "MIT AND Apache-2.0" in
package.json. A test keeps the list and the headers in step. No code
changes.
Logs UF-069: the hive-mind-core LICENSE is an abridged Apache text.
exceljs 4.4.0 pulled unzipper 0.10, which depends on binary and through
it on buffers 0.1.1, a package with no license grant. An npm override
moves exceljs to unzipper 0.12.3, the version whatsapp-web.js already
uses, so binary, buffers, chainsaw and traverse leave the installers.
Waggle only writes workbooks and loads them through JSZip; both still
work. The license gate drops the two exceptions it no longer needs.
ADR-0005's open item is closed: the installed Chrome or Edge first, a
downloaded Chrome for Testing only when none is found. The v1 platform
list is confirmed and leaves the pending table. ADR-0005 no longer
mentions install.sh or an npm install on the user's machine.
Records the decision not to generate marketplace.db at build time or ship
it as a release artifact (P1.6), and adds the catalog's third-party
descriptions to the pending licensing review.
The SDK reads pack manifests and starter skills next to its own module,
which in the bundle is service.js, and no build step copied them there:
installed builds showed no packs and no starter skills. build-sidecar now
copies both folders next to service.js and Tauri bundles them (UF-066).
GET /api/agent/status returned the configured model even when it had no
key, so the status bar named Claude while chats ran on the local model.
It now resolves the model the way the chat route does (UF-067).
The release publishes the server archive and the desktop installers under
one tag, and the installer looks for the release named after its own
version, so both now carry 1.0.0.
The architecture guide, AGENTS.md and the threat model said releases were
built by hand or Windows-first; ADR-0009 still listed the release
workflow as future work. The Windows build guide named the missing
Settings > API Keys tab.
- Key messages named a Settings > API Keys tab that does not exist; they
now point at Settings > Models (UF-061).
- The connector suggestion looked for vault.db, which never exists; it
now checks the vault for a connector entry (UF-062).
- /config and /preferences were registered with a leading slash and
never matched (UF-063).
- Pins and documents were written under ~/.waggle whatever the data
directory; they now use the server's data directory (UF-064).
- The Windows uninstaller named a Data & Privacy page that does not
exist (UF-065).
The guide now says the release workflow builds Windows on windows-latest
with NSIS and MSI, and shows how to pack the server archive and run the
installer and desktop smoke tests locally.
Developer ID and notarization on macOS (including the bundled node and
native libraries), the owner's existing Azure Artifact Signing on Windows
with SignPath Foundation or a CA certificate as alternatives, and signed
checksums on Linux. Lists the decisions the owner has to make.
The launcher is now a self-contained installer with install, run, update,
doctor and uninstall. Install downloads waggle-server-<version>-<target>
.tar.gz, checks its SHA-256, unpacks it into a per-user program directory
and writes a waggle-server command that runs the tool on the archive's own
Node. Nothing is built on the user's machine and the data directory stays
WAGGLE_DATA_DIR or ~/.waggle.
scripts/build-server-archive.mjs packs the staged desktop sidecar payload
with the built web UI and a manifest. The download location waits for the
repository decision; until then install takes --from or
WAGGLE_RELEASE_BASE_URL (ADR-0009).
Removes install.sh, scripts/waggle-server.sh and their CI job, which the
installer replaces, and the bin name clash with @waggle/cli.
Sample data in tests, prompts and UI placeholders uses Alex Morgan
instead of the maintainer's name; decision attributions say "owner".
Personal details in two test fixtures are replaced. Local paths
(D:/Projects/...) and paths into the maintainer's planning repository
are reworded. Clone and install URLs in CONTRIBUTING.md and the getting
started guide use placeholders until the public repository location is
decided (Q9). The Benchmarks page no longer names the maintainer's
hive-mind repository, and the upstream fixes log names the main Waggle
repository instead of an internal git host.
When no embedding provider answers, the banner told users to set
HIVE_MIND_EMBEDDING_PROVIDER, which only the hive-mind CLI read; Waggle
reads EMBEDDING_PROVIDER. A test checks the banner text.
The bench compared mem0 with MindDB, FrameStore and HybridSearch from
the hive-mind substrate, which @waggle/core no longer exports and which
left the repository. It now runs mem0, mem0-rerank and cosine; the
recorded comparison stays in docs/oss/research/memory-search-quality.md.
scripts/generate-third-party-notices.mjs works offline: it lists the npm
packages of the sidecar and web UI closures from package-lock.json, the
Node.js runtime and npm that bundle-node.mjs stages, and the Rust crates of
the desktop shell from `cargo metadata --offline`, and reproduces each
distinct license text once. A section covers the LGPL (libvips,
node-webpmux), MPL (servo crates), OFL (fonts) and unlicensed components
and what their licenses ask.
The Windows and Linux crates are not in the local cargo cache, so this
first file covers the macOS crates and says so; regenerate after
`cargo fetch` before a release.
Log UF-058 (installers ship third-party code without notices) and UF-059
(buffers 0.1.1 has no license) in the upstream fixes.
The first start copied Waggle's tables and the memories of the commercial
edition's .mind files into waggle.db and mem0. The product is still in
development and nobody has data to bring over, so both copies, their tests
and the legacy creation-time field are gone. ADR-0007 records the change.
A provider without its key lists no models, so Model Pilot could not tell
the primary needed a key, and it compared a prefixed active id with a bare
one. The provider now also comes from the id's prefix or family name, and
prefixed and bare ids count as the same model. The account row's fallback
initial is A for Account, not W.
At 375px the 64px icon rail took a fifth of the screen and Home's heading
wrapped over five lines. Below sm the rail hides, a bottom bar carries the
five places plus More (⌘K), and Home tightens its padding and heading.
Home and the sidebar read the user's name from the identity row, which the
sidecar fills with the assistant's identity named Waggle. Both now use the
profile name, with the identity name as a fallback that skips the default.
Settings showed the configured primary while the status bar showed the
model new chats fall back to, so the two screens disagreed. Model Pilot now
says the primary needs a key and names the model in use.
"Pick up where you left off" listed every recent workspace, including the
one the Start here card already offers. The list now leaves it out and
hides when nothing else is left.
Only a successful recall reported its outcome, so an empty or failed
recall left "Recalling relevant memories..." as the last step after the
answer. Both cases now send a closing step and the turn goes on.
The card headline was a fixed "Worked across your memory, web & files".
It is now built from the turn: memory, web and file tools it called and
the memory steps the server reported, or a plain Working / Done.
The title carries a framer-motion layoutId for the card-to-header hero morph,
which also animates any change of its box. With a short workspace name the
title is as wide as the subtitle row; hiding that row on the Chat tab changed
the width, and framer animated it as a horizontal scale (2.9x for "Eng").
Both titles now use layout="position": only the position animates, and the
hero morph still moves the name into place. The hero-morph test checks it.
The ⌘K search input had no padding but drew its own focus ring with an
offset, so the ring ran right against the text. It now has inner padding
and no offset, so the ring reads as the field's outline; the palette test
checks both.
The sidebar account row had 8px above its content and 22px below, because
its bottom padding added to the nav's own. It now has 14px above and none
below, matching the nav padding underneath.
On macOS and Linux the shell stopped the sidecar with Child::kill(), which is
SIGKILL, so the sidecar never ran its shutdown: the processes it started (MCP
servers, a managed Ollama, the WhatsApp browser) kept running. After an app
restart the orphaned WhatsApp browser still held the session profile, and the
channel failed with "The browser is already running".
The shell now sends SIGTERM, waits up to 5 seconds for the sidecar to exit,
then sends SIGKILL; Windows keeps its kill-on-close job. For crashes, where no
shutdown runs, the WhatsApp channel stops a browser left over from an earlier
run before starting its own. It only stops a process whose command line uses
this profile and whose parent is gone; a browser another running Waggle server
owns is left alone, and the channel says so instead of retrying.
POST /api/personas/generate posted to /api/anthropic/v1/messages, a route
that does not exist, with no session token and a port built from
address().toString(), so the URL did not even parse. It also pinned
claude-sonnet-4-6, which needs an Anthropic key.
The route now calls the built-in proxy through self-request.ts, reads the
OpenAI-format reply, and picks the model from the user's default with the
same fallback chat uses, so a local Ollama model works too. An end-to-end
test with localhost trust off checks the generated persona comes back.
Since the server stopped trusting loopback callers, the built-in model proxy
needs the session token like every other route, but the sidecar's own calls
to it sent none. The Models key check read the proxy's 401 as a rejected key,
so a working Anthropic key showed "Key found but not responding". Scheduled AI
tasks and loops, the dream diary narrative and the profile calls failed the
same way; the profile calls also built the port from address().toString(),
and the scheduled tasks used the configured port, which the desktop app's
port fallback can leave pointing at another Waggle server.
self-request.ts now builds the address from the bound port and adds the
session token; all these calls and command.ts use it, and the token is never
sent to Ollama. An end-to-end test runs the key check through the real
middleware and proxy with localhost trust off; it fails without the fix.
UF-045 records the persona generator, which posts to a route that does not
exist; it is left open.
The composer textarea drew its own focus ring inside the rounded box, which
already turns amber on focus-within. The ring is gone; the box's border stays
the focus indicator (8.14:1 dark, 4.92:1 light against the composer).
With the full-width sidebar every item showed a hover hint that repeated its
visible label, and the part of the hint that reached past the sidebar was
hidden wherever the main area had content: the hint rendered inside the nav,
and the nav and <main> are sibling z-10 layers.
Sidebar hints now show only on the icon rail below lg, where they are the
only label, and render in document.body through a new opt-in `portal` flag
on HintTooltip. Other hints keep rendering in place, since several sit in
overlays above z-50 where a portaled hint would end up underneath.
The OAuth routes started a module-level cleanup interval that was never
cleared or unref'd. The service's SIGTERM/SIGINT handler closes the server
and relies on the event loop going empty, so the process kept running: a
first Ctrl+C in `npx waggle` or `npm run dev:server` left it alive, and
SIGTERM never ended it. The interval is now unref'd.
The launcher tests left two `waggle` processes behind on every run: they
stopped `npx` but not the waggle process it started. They now start it in
its own process group and stop the whole group, with a SIGKILL fallback,
and a new test checks that the built CLI exits by itself after SIGTERM.
Core keeps only shared infrastructure, so InstallAuditStore leaves it and
lives in packages/server/src/local/install-audit.ts. The trail itself stays:
the Audit and Activity tabs, the extend and export routes, and the threat
model entry keep working on the same waggle.db table.
- @waggle/shared gets RecordAuditInput and the narrow InstallAuditRecorder
(record only), which the agent's skill tools now depend on.
- The server creates the audit table before the one-time legacy copy, which
no longer constructs it in core.
- UF-040: GET /api/debug/logs called prepare() on the store's private db
wrapper, which has none, so the support bundle never carried recent
installs. It now reads them through getRecentSummary().
- The packaged macOS app stayed on "Starting Waggle…": the shell looked
for node, service.js, native/ and node_modules/ next to the executable,
the Windows layout, while a macOS bundle keeps them in
Contents/Resources/resources. bundled_resources_dir() checks both.
- The startup screen used min-height 100vh on an unstyled body, which
showed scroll bars, and a fixed light text colour that is invisible in
the light theme. It is now styled from index.html, fixed to the window,
with a dark text colour for the light theme.
POST /api/memory/frames, /api/quick-capture and the Memory Center's
POST /api/memory saved a memory meant for an unknown workspace into
personal memory, which every workspace reads. They now answer 404
workspace_not_found and write nothing; a request without a workspace
still goes to personal memory.
AGENTS.md no longer describes memory as half-migrated or asks for
build:packages before running the sidecar, lists the tsc -b build and the
test typecheck among the checks, and drops the removed weaver package.
ADR-0007 and ADR-0008 record that core no longer re-exports the legacy
substrate and that sqlite-vec is gone.
- adapter: memory ids are strings; single-memory calls take only the id
(no ?mind= disambiguation). searchMemory takes the workspace as its own
parameter. New getMemoryCapabilities / setMemoryExtraction. Removed:
incrementFrameAccess, getMemoryOriginalSource, listSuppression,
allowReimport, getWeaverStatus, and the dead importPreview, importCommit
and getWikiWatermark. eraseMemory takes { id } or { sessionId }.
- memory-features reads GET /api/memory/capabilities for the knowledge
graph; history import, wiki, hooks, Room and the memory MCP stay hidden
(ADR-0002). useMemoryCapabilities re-renders the Memory screens.
- Settings > General has a Memory toggle for background fact extraction.
- Memory Center: the confidence filter, the erased-sources panel, the
original-source view and the Deprecated chip are gone; Erase forgets
every memory saved from the chat a memory came from and is offered only
for memories with a chat session. Memory kinds follow the contract.
- Trust views show short memory labels for the new string ids and drop the
per-row "not scored yet" badge (v1 stores no confidence).
- The Weaver maintenance view and the Cockpit weaver card are removed
(the weaver package and its routes are deleted).
- Timeline uses the contract kinds and maps important/temporary
importance.
Logs UF-033 (search scope sent as the workspace id), UF-034 (importance
mapping) and UF-035 (restore over open databases, open).
- 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).