Commit Graph

71 Commits

Author SHA1 Message Date
shumeiko.it
0e2f3197eb docs: describe the release workflow now that it is merged
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.
2026-11-01 02:21:20 +01:00
shumeiko.it
608c804482 Merge P2.4: README and documentation for the community edition 2026-11-01 02:20:13 +01:00
shumeiko.it
10c013efcd Merge P1.3d: unsigned release workflow for three systems 2026-11-01 02:20:13 +01:00
shumeiko.it
74200d46e8 fix: five defects found while rewriting the docs (UF-061 to UF-065)
- 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).
2026-11-01 02:08:57 +01:00
shumeiko.it
e34f95ec3c docs(oss): describe the release workflow in the Windows build guide (P1.3d)
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.
2026-11-01 02:08:36 +01:00
shumeiko.it
87c1d398f9 docs: add desktop app update and uninstall steps to the install guide (P2.4) 2026-11-01 02:02:50 +01:00
shumeiko.it
dd6564451a docs: bring the command and local API references up to date (P2.4)
commands.md lists all 23 registered slash commands with their working
aliases and drops the FTS5 and two-mind wording. api.md explains the
bearer session token and that the API is internal, fixes the session
route parameters, lists the memory routes served through the memory
contract, the current chat stream events and the permissions body, and
removes the team, import and KVARK enterprise-pack routes.
2026-11-01 02:01:57 +01:00
shumeiko.it
94d54c4188 docs: rewrite the troubleshooting guide for this edition (P2.4)
Cover the unsigned installers, the server installer's error messages,
the desktop startup log, ports, models, memory on mem0 (including the
embedder mismatch) and the data directory. Drop team mode, the .mind
files, FTS5, docker compose for LiteLLM, the Node-on-PATH requirement
of the old desktop app and the invented cost per conversation.
2026-11-01 01:59:25 +01:00
shumeiko.it
834096146e docs: update the capabilities and connectors guides for this edition (P2.4)
Remove KVARK enterprise connectors, the 120+ package count and the
curl examples, which no longer work without the session token. Describe
Skills Hub, the marketplace scan as the code applies it, MCP Hub, the
30 native connectors, the approval modes, and the messaging channels
with the whatsapp-web.js warnings and browser download.
2026-11-01 01:58:42 +01:00
shumeiko.it
eca050328b docs: merge the two getting-started pages and update the workspaces guide (P2.4)
docs/GETTING-STARTED.md and docs/guides/getting-started.md covered the
same ground; keep one guide in docs/guides that follows the current
setup flow, the two model paths, memory on mem0 and the real keyboard
shortcuts. Drop the product tiers, the signed-Windows-only install, the
.mind files, install.sh and the external coding-agent sign-in.

The workspaces guide loses team workspaces, the .mind files, FTS5 search
and the knowledge graph, and describes virtual and local storage, the
shipped personas and what deleting a workspace removes.
2026-11-01 01:57:12 +01:00
shumeiko.it
06a0df73b5 docs: rewrite the architecture overview for the community edition (P2.4)
Describe the web UI, the sidecar, the Tauri shell, waggle.db, the
memory contract and mem0, models, the server installer and archive,
and the staging chain that builds the desktop packages and the server
archive. Drop the removed packages, KVARK, team mode, the .mind files
and the knowledge graph.
2026-11-01 01:53:53 +01:00
shumeiko.it
4377096495 docs: move CONTRIBUTING.md to the root and rewrite it for this edition (P2.4)
Point contributors to AGENTS.md for the rules, list the current setup
and check commands (no build:packages step, no Docker), and drop the
team-mode test setup and the stale test counts. docs/CONTRIBUTING.md
keeps a one-line pointer because the pull request template links it.
2026-11-01 01:53:53 +01:00
shumeiko.it
491df50a59 docs: add the install guide and the memory guide (P2.4)
docs/install.md covers both ways to install (the Tauri desktop
packages and the server installer), the unsigned-installer warnings
on each system, first launch, the data directory, update and
uninstall. docs/memory.md describes the memory contract, its mem0
implementation, where mem0 keeps its files, recall and background
fact extraction.
2026-11-01 01:50:35 +01:00
shumeiko.it
9806afbced docs(oss): propose how to sign the installers (P2.5)
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.
2026-11-01 01:39:49 +01:00
shumeiko.it
3a426a5423 feat(launcher): install the server from a prebuilt archive (P1.3c)
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.
2026-11-01 01:35:54 +01:00
shumeiko.it
86ea0d7529 Merge P2.3: license gate and third-party notices
# Conflicts:
#	docs/oss/upstream-fixes.md
2026-11-01 01:17:28 +01:00
shumeiko.it
16eaf01e14 chore: scrub personal names, maintainer URLs and local paths (P2.2)
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.
2026-11-01 00:50:13 +01:00
shumeiko.it
72a2a895a5 docs: drop references to the removed packages (P2.2)
AGENTS.md records that the excluded packages left in P2.2. SECURITY.md
scopes memory to memory-contract and memory-mem0. THREAT_MODEL.md points
the injection scanner at @waggle/core, marks the MCP tool scope gate as
removed with the memory MCP servers, and drops the hive-mind copy of the
URL egress guard. docs/ARCHITECTURE.md lists the memory packages instead
of the hive-mind substrate. docs/methodology.md, the LoCoMo write-up of
the hive-mind engine whose reproduction steps pointed at the
maintainer's hive-mind repository, is removed.
2026-11-01 00:50:06 +01:00
shumeiko.it
9276723f25 fix(core): name EMBEDDING_PROVIDER in the mock-embedding warning (UF-058)
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.
2026-11-01 00:43:05 +01:00
shumeiko.it
613b23be17 refactor(memory-mem0): drop the old engine from the search-quality bench (P2.2)
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.
2026-11-01 00:42:47 +01:00
shumeiko.it
8a308aac01 docs: generate THIRD_PARTY_NOTICES.md for the shipped components (P2.3)
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.
2026-11-01 00:31:26 +01:00
shumeiko.it
a8250cb375 refactor: drop the one-time copy of legacy .mind data
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.
2026-10-28 12:35:41 +01:00
shumeiko.it
fb3697ca6c fix(web): find a keyless primary's provider from the model id (UF-054, UF-055)
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.
2026-10-27 14:56:30 +01:00
shumeiko.it
3ae3cc81fc fix(web): give phones a bottom navigation bar instead of the rail (UF-057)
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.
2026-10-27 14:36:35 +01:00
shumeiko.it
22846e4131 fix(web): label the Home activity summary as the last 24 hours (UF-056)
The summary always covers the last 24 hours, but it read "While you slept"
and "A calm night" at any time of day.
2026-10-27 14:24:44 +01:00
shumeiko.it
659c84bee2 fix: never greet the user by the assistant's default name (UF-055)
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.
2026-10-27 14:24:35 +01:00
shumeiko.it
c2998f1a6b fix(web): say when the primary model has no key and which model chats use (UF-054)
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.
2026-10-27 14:20:05 +01:00
shumeiko.it
f3c48e6f19 fix(web): square the user's chat bubble at the top right (UF-053)
User messages sit on the right, but the bubble's one square corner was the
top left, pointing away from the sender.
2026-10-27 13:15:57 +01:00
shumeiko.it
ef99f04c5b fix(web): stop offering the Start here workspace twice on Home (UF-052)
"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.
2026-10-27 12:54:54 +01:00
shumeiko.it
b3b61e14c9 fix(server): close the memory recall step when nothing is found or recall fails (UF-051)
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.
2026-10-27 12:54:51 +01:00
shumeiko.it
06d267dec8 fix(web): name only what a chat turn touched in the activity card (UF-050)
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.
2026-10-27 12:54:45 +01:00
shumeiko.it
711c37358a fix(web): keep the workspace title from stretching between tabs (UF-049)
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.
2026-10-26 21:22:32 +01:00
shumeiko.it
3d1d07bd50 fix(web): pad the command palette search field and center the account row (UF-047, UF-048)
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.
2026-10-26 21:16:20 +01:00
shumeiko.it
1e826aa220 fix(desktop): stop the sidecar with SIGTERM first, and free a stale WhatsApp profile (UF-046)
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.
2026-10-26 12:03:31 +01:00
shumeiko.it
48bdab8087 fix(server): generate personas through the built-in proxy (UF-045)
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.
2026-10-26 01:50:47 +01:00
shumeiko.it
d6217ad7c2 fix(server): send the session token on the sidecar's calls to its own proxy (UF-044)
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.
2026-10-26 01:46:29 +01:00
shumeiko.it
5268881f46 docs(oss): how to build the Windows desktop installer 2026-10-26 00:43:43 +01:00
shumeiko.it
ae8233b8f6 fix(web): give the chat composer a single focus outline (UF-043)
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).
2026-10-26 00:32:11 +01:00
shumeiko.it
efcb19e682 fix(web): show sidebar hints only on the icon rail, above the main area (UF-042)
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.
2026-10-25 23:37:20 +01:00
shumeiko.it
07a529512c fix(server): let the CLI server exit on Ctrl+C and SIGTERM (UF-041)
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.
2026-10-25 23:01:05 +01:00
shumeiko.it
2e08f2ae96 refactor(server): move the install audit trail from core to the server (P1.2, UF-040)
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().
2026-10-25 21:32:38 +01:00
shumeiko.it
3befcd8e9b docs: how to build the desktop app, and the packaged macOS launch 2026-10-24 19:18:02 +02:00
shumeiko.it
1f536151d8 fix(desktop): find the sidecar in a macOS app bundle and fit the startup screen (UF-004, UF-017)
- 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.
2026-10-24 19:10:23 +02:00
shumeiko.it
276808cd69 docs(oss): record the end-of-week-2 checkpoint 2026-10-24 18:27:12 +02:00
shumeiko.it
8a9ba09ad9 fix(server): refuse memory writes for a workspace that does not exist (UF-039)
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.
2026-10-24 18:09:43 +02:00
shumeiko.it
4dbab2cb8b docs: describe the community edition after the move to mem0 and the unified build
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.
2026-10-24 17:56:20 +02:00
shumeiko.it
2c376f21cf docs(oss): log the Marketplace hot-reload notification that never reaches the sidecar (UF-038) 2026-10-24 17:39:20 +02:00
shumeiko.it
d433dca857 refactor(web): move the Memory screens onto the memory contract API (P1.5)
- 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).
2026-10-24 13:19:37 +02:00
shumeiko.it
f310333970 refactor(server): search memory through the contract in artifacts, agent runs, route proposals and onboarding (P1.5)
- 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.
2026-10-24 13:19:06 +02:00
shumeiko.it
e9ed8c0765 refactor(server): read workspace state, briefings and workspaces from the memory contract (P1.5)
- 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.
2026-10-24 13:19:06 +02:00