2026-03-03T11-41-54_auto_memory/memories.db-wal, memory/memories.db-wal, me

memory/2026-03-03-bug-triage-agent-deployment.md

@@ -0,0 +1,36 @@
+# 2026-03-03 Session Notes
+
+## Bug Triage & Agent Deployment
+
+Nicholai identified five critical bugs/issues in Signet requiring parallel investigation and fixes:
+
+1. **Dashboard version display** — Version number in bottom-left corner doesn't update after software updates
+2. **Config persistence** — Changes made in the dashboard config editor don't persist/save
+3. **Auto-update system** — Update mechanism is broken
+4. **Agent update knowledge** — Agents don't know how to update Signet; documentation contains hallucinated commands
+5. **Install command contamination** — Repository contains wrong install commands (`npx signet`, etc.) everywhere; only two valid methods exist
+
+## Signet Installation Workflow
+
+Nicholai clarified the only two supported installation flows:
+- `bun add -g signetai` (one word, no space)
+- `npm install -g signetai` (one word, no space)
+
+Followed by:
+- `signet daemon restart`
+- `signet daemon sync`
+
+All other commands (e.g., `npx signet`) are non-functional and confuse users and agents alike.
+
+## Documentation & Agent Observability
+
+Agents need visibility into proper Signet update workflows. Documentation must be corrected across:
+- skill.md files on the website
+- Session start hook documentation
+- All agent-facing documentation
+
+Nicholai emphasized agents need clear, simple, and correct information about updates to prevent installation failures.
+
+## Actions Taken
+
+Spawned parallel explore agents to map the codebase for each of the five issues before planning fixes.