groove-dev 0.27.26 → 0.27.28

package/packages/gui/src/components/marketplace/marketplace-card.jsx

@@ -4,42 +4,7 @@ import { cn } from '../../lib/cn';
 import { Badge } from '../ui/badge';
 import { fmtNum } from '../../lib/format';
 
-// Well-known integration logos via CDN (simple-icons on cdn.simpleicons.org)
-export const INTEGRATION_LOGOS = {
-  'google-workspace': 'https://cdn.simpleicons.org/google/white',
-  github:      'https://cdn.simpleicons.org/github/white',
-  stripe:      'https://cdn.simpleicons.org/stripe/635BFF',
-  gmail:       'https://cdn.simpleicons.org/gmail/EA4335',
-  'google-calendar': 'https://cdn.simpleicons.org/googlecalendar/4285F4',
-  'google-drive':    'https://cdn.simpleicons.org/googledrive/4285F4',
-  'google-docs':     'https://cdn.simpleicons.org/googledocs/4285F4',
-  'google-sheets':   'https://cdn.simpleicons.org/googlesheets/34A853',
-  'google-slides':   'https://cdn.simpleicons.org/googleslides/FBBC04',
-  'google-maps':     'https://cdn.simpleicons.org/googlemaps/4285F4',
-  postgres:    'https://cdn.simpleicons.org/postgresql/4169E1',
-  notion:      'https://cdn.simpleicons.org/notion/white',
-  linear:      'https://cdn.simpleicons.org/linear/5E6AD2',
-  'brave-search': 'https://cdn.simpleicons.org/brave/FB542B',
-  'home-assistant': 'https://cdn.simpleicons.org/homeassistant/18BCF2',
-  sentry:      'https://cdn.simpleicons.org/sentry/362D59',
-  elevenlabs:  'https://cdn.simpleicons.org/elevenlabs/white',
-  hubspot:     'https://cdn.simpleicons.org/hubspot/FF7A59',
-  jira:        'https://cdn.simpleicons.org/jira/0052CC',
-  sendgrid:    'https://cdn.simpleicons.org/sendgrid/1A82E2',
-  resend:      'https://cdn.simpleicons.org/resend/white',
-  replicate:   'https://cdn.simpleicons.org/replicate/white',
-  vercel:      'https://cdn.simpleicons.org/vercel/white',
-  supabase:    'https://cdn.simpleicons.org/supabase/3FCF8E',
-  mixpanel:    'https://cdn.simpleicons.org/mixpanel/7856FF',
-  datadog:     'https://cdn.simpleicons.org/datadog/632CA6',
-  airtable:    'https://cdn.simpleicons.org/airtable/18BFFF',
-  zendesk:     'https://cdn.simpleicons.org/zendesk/03363D',
-  intercom:    'https://cdn.simpleicons.org/intercom/6AFDEF',
-  twilio:      'https://cdn.simpleicons.org/twilio/F22F46',
-  telnyx:      'https://cdn.simpleicons.org/telnyx/00C08B',
-  aws:         'https://cdn.simpleicons.org/amazonaws/FF9900',
-  plaid:       'https://cdn.simpleicons.org/plaid/white',
-};
+import { INTEGRATION_LOGOS } from '../../lib/integration-logos';
 
 function ItemIcon({ item, size = 40 }) {
   const logoUrl = INTEGRATION_LOGOS[item.id];

package/packages/gui/src/lib/integration-logos.js

@@ -0,0 +1,39 @@
+// FSL-1.1-Apache-2.0 — see LICENSE
+
+export const INTEGRATION_LOGOS = {
+  'google-workspace': 'https://cdn.simpleicons.org/google/white',
+  slack:       'https://cdn.simpleicons.org/slack/E01E5A',
+  discord:     'https://cdn.simpleicons.org/discord/5865F2',
+  github:      'https://cdn.simpleicons.org/github/white',
+  stripe:      'https://cdn.simpleicons.org/stripe/635BFF',
+  gmail:       'https://cdn.simpleicons.org/gmail/EA4335',
+  'google-calendar': 'https://cdn.simpleicons.org/googlecalendar/4285F4',
+  'google-drive':    'https://cdn.simpleicons.org/googledrive/4285F4',
+  'google-docs':     'https://cdn.simpleicons.org/googledocs/4285F4',
+  'google-sheets':   'https://cdn.simpleicons.org/googlesheets/34A853',
+  'google-slides':   'https://cdn.simpleicons.org/googleslides/FBBC04',
+  'google-maps':     'https://cdn.simpleicons.org/googlemaps/4285F4',
+  postgres:    'https://cdn.simpleicons.org/postgresql/4169E1',
+  notion:      'https://cdn.simpleicons.org/notion/white',
+  linear:      'https://cdn.simpleicons.org/linear/5E6AD2',
+  'brave-search': 'https://cdn.simpleicons.org/brave/FB542B',
+  'home-assistant': 'https://cdn.simpleicons.org/homeassistant/18BCF2',
+  sentry:      'https://cdn.simpleicons.org/sentry/362D59',
+  elevenlabs:  'https://cdn.simpleicons.org/elevenlabs/white',
+  hubspot:     'https://cdn.simpleicons.org/hubspot/FF7A59',
+  jira:        'https://cdn.simpleicons.org/jira/0052CC',
+  sendgrid:    'https://cdn.simpleicons.org/sendgrid/1A82E2',
+  resend:      'https://cdn.simpleicons.org/resend/white',
+  replicate:   'https://cdn.simpleicons.org/replicate/white',
+  vercel:      'https://cdn.simpleicons.org/vercel/white',
+  supabase:    'https://cdn.simpleicons.org/supabase/3FCF8E',
+  mixpanel:    'https://cdn.simpleicons.org/mixpanel/7856FF',
+  datadog:     'https://cdn.simpleicons.org/datadog/632CA6',
+  airtable:    'https://cdn.simpleicons.org/airtable/18BFFF',
+  zendesk:     'https://cdn.simpleicons.org/zendesk/03363D',
+  intercom:    'https://cdn.simpleicons.org/intercom/6AFDEF',
+  twilio:      'https://cdn.simpleicons.org/twilio/F22F46',
+  telnyx:      'https://cdn.simpleicons.org/telnyx/00C08B',
+  aws:         'https://cdn.simpleicons.org/amazonaws/FF9900',
+  plaid:       'https://cdn.simpleicons.org/plaid/white',
+};

package/MUST_FIX_ISSUES.md

@@ -1,305 +0,0 @@
-LAYER 1: ELECTRON SHELL (packages/desktop/main.js) ----------------------------------------------------
-
-The desktop app itself creates memory pressure before any agent work begins:
-
-CRITICAL - Daemon heap capped at 512MB (line 178) The daemon process managing ALL agents, the GUI server, WebSocket broadcasts, journalist synthesis, token tracking, and state persistence gets only 512MB. When GC hits this ceiling, the event loop blocks for 100-300ms. The Electron app freezes waiting for daemon responses. This is why button clicks take 5s to register.
-
-CRITICAL - Listener accumulation on window reuse (lines 862-914) When reopening a project, the home window is reused. Lines 872-873 remove close/closed listeners, but console-message, render-process-gone, and permission handlers are re-registered without removing the old ones. Each reuse adds duplicate listeners. N window reuses = N duplicate handlers firing per event.
-
-CRITICAL - IPC broadcast flooding (process.js lines 926-950) Every agent output is broadcast to all Electron windows. Throttled to 4/sec per agent, but with 4+ agents that's 16+ JSON serializations per second over IPC with no backpressure. The renderer can't keep up, and the IPC message queue grows unbounded in the main process.
-
-HIGH - Subscription polling on every window focus (lines 301, 886) Every time you click the Electron window, it triggers a subscription check to the daemon. With multiple windows, this creates constant HTTP traffic even when idle.
-
-HIGH - stdout buffer string operations (process.js lines 844-854) Per-agent stdout buffer grows to 1MB, then the "oldest half" is discarded via .indexOf() and .slice() on a multi-MB string. This runs on EVERY chunk. With streaming agents, it's constant multi-MB string allocations and GC pressure.
-
-LAYER 2: PROCESS MANAGER (packages/daemon/src/process.js) -----------------------------------------------------------
-
-HIGH - Stream throttle timers leak (lines 928-948) Each agent gets a throttle object in a Map. If agent crashes or is killed while a timer is pending, the callback still fires, broadcasting to a dead agent ID. The closure over output data never gets GC'd. Long sessions with many spawns = unbounded map growth.
-
-HIGH - Resume doesn't clean up maps (lines 1251-1367) When resuming a completed agent, peakContextUsage, pendingMessages, and _streamThrottle entries from the old agent ID are never cleared. These maps grow with every resume cycle.
-
-HIGH - Log stream file descriptor leaks (lines 545, 1284) Each spawn creates a write stream. On exit, logStream.end() is called but file descriptors aren't guaranteed released if I/O is slow. Resume creates new streams for the same agent. Long sessions accumulate hundreds of open .log file descriptors.
-
-LAYER 3: JOURNALIST (packages/daemon/src/journalist.js) ---------------------------------------------------------
-
-This is where "infinite sessions" should work. It doesn't fully deliver.
-
-CRITICAL - 40K char budget is actually 3-5K tokens (line 10) The comment says "~10k tokens budget" but 40,000 UTF-8 chars of chat-style logs is closer to 3-5K tokens. The synthesis prompt can only fit the last 20-30 agent events. In active sessions, 60-70% of recent activity is dropped from synthesis.
-
-CRITICAL - Exploration tools excluded from synthesis (lines 211-218) Read, Glob, and Grep events are filtered into a separate explorationEntries array and never included in the synthesis prompt. New agents don't know what files were examined. They re-explore the same files, wasting tokens.
-
-HIGH - Handoff brief is only 7K tokens total (lines 706-784) The brief pulls from 9 sources, each truncated:
-
--
-Errors: 10 entries x 300 chars = 3K chars
--
-Results: last 3 joined = 3K chars
--
-File changes: 20 files = 2K chars
--
-Discoveries: 10 entries = 2K chars
--
-Constraints: 2K chars
--
-User feedback: 5 x 500 = 2.5K chars
--
-Recent tools: 5 x 80 = 400 chars
--
-Rotation history: 3K chars
--
-Original task: 2K chars
-Total ~22K chars = ~7K tokens. The original agent had full context. The new agent gets a structured digest. Nuance, intermediate reasoning, and failed experiments are gone.
-
-HIGH - Only last 5 tool calls in rotation history (lines 755-760) A complex multi-file refactor needs 10-20 tool calls for context. Only the last 5 survive, each truncated to 80 chars. The handoff says "agent was editing files" but not "agent tried approach A, it failed because X, then tried B."
-
-MEDIUM - Synthesis cycle is 2 min, rotation check is 15 sec (lines 9, rotator.js:11) Rotations can happen 8x per synthesis cycle. Agent rotates at 0:15, journalist doesn't synthesize until 2:00. New agent has 1:45 of unsynthesized activity.
-
-LAYER 4: ROTATOR (packages/daemon/src/rotator.js) ---------------------------------------------------
-
-CRITICAL - 5-minute cooldown prevents fast recovery (line 16) After rotation, the new agent is locked in for 5 minutes regardless of quality. If the handoff was bad and the new agent is immediately degraded, nothing can be done until cooldown expires. Total degradation window: 8-10 minutes (3 min to detect + 5 min cooldown).
-
-HIGH - No post-rotation validation (lines 233-237) Pre-rotation session is scored and recorded. But there is NO measurement of post-rotation quality. System assumes rotation improved things without verifying. Could be making things worse.
-
-HIGH - Kill+respawn loses in-flight state (lines 278-301) Between kill and respawn: in-flight variables, cached results, classifier window, score history, and live quality tracking are all destroyed. New agent starts from the 7K-token brief only. This is a warm start, not zero cold start.
-
-HIGH - Idle check blocks quality rotation (lines 201-213) Quality rotation only fires if agent is idle 10+ seconds. If user is actively sending messages, an agent scoring 30/100 won't rotate because it's "busy." Planner agents producing bad plans while user reads output = degradation that the system ignores.
-
-MEDIUM - Handoff chain keeps only 10 rotations (memory.js line 18) At 5-minute rotations, 10 rotations = 50 minutes of history. Multi-hour tasks lose their full lineage. Agent #11 can't see what agent #1 learned.
-
-LAYER 5: ADAPTIVE THRESHOLDS (packages/daemon/src/adaptive.js) ----------------------------------------------------------------
-
-HIGH - Session scoring baseline is arbitrary (line 96) Score starts at 70. Errors cost 5 points each, repetitions cost 6. But these weights have no empirical calibration. A fatal error and a benign warning both cost 5 points. The scoring doesn't distinguish.
-
-HIGH - Asymmetric drift (+2%/-5%) (lines 8-9) Good sessions nudge threshold up slowly (+2%). Bad sessions yank it down fast (-5%). Over many sessions, thresholds oscillate unpredictably rather than converging.
-
-HIGH - Convergence detection is set but never read (lines 139-149) The profile.converged flag is computed and stored. The rotator never checks it. It's dead data.
-
-MEDIUM - No per-role quality thresholds (rotator.js line 12) QUALITY_THRESHOLD=40 applies to all roles. Planners naturally have higher error rates (exploring, revising). Backend agents on stable code have lower rates. Same threshold for both.
-
-LAYER 6: TOKEN TRACKER (packages/daemon/src/tokentracker.js) --------------------------------------------------------------
-
-HIGH - Planner token ceiling is 50M tokens (rotator.js lines 111-112) Role multiplier for planner is 10x the 5M base = 50M tokens. That's ~180K output tokens. Degradation happens long before 50M, but the safety ceiling never triggers. Planners can burn 50M tokens of garbage before forced rotation.
-
-MEDIUM - Cache hit rate is global, not per-agent (lines 205-216) If planner has 80% hit rate and fullstack has 20%, global rate is ~50%. Can't detect which agents benefit from caching.
-
-MEDIUM - Cold-start savings estimation is inflated (lines 8-14, 182-187) Per-file cost is flat (15 tokens). A 50-line config and a 10K-line monolith cost the same. Reported savings are overstated.
-
-MEDIUM - Journalist synthesis cost not tracked separately (lines 237-258) Internal overhead is tracked by __ prefix IDs, but journalist synthesis tokens may not be properly attributed.
-
-LAYER 7: MEMORY (packages/daemon/src/memory.js) -------------------------------------------------
-
-CRITICAL - Layer 7 skips first-generation agents (process.js line 431) Discoveries and handoff history are only injected when hasTask=true. hasTask = !!config.prompt. Agents spawned with just a role and no prompt never receive prior discoveries. They repeat mistakes that Layer 7 already captured.
-
-HIGH - Specializations recorded but never used (lines 310-389) Quality profiles per agent/role are stored. They are NEVER read for routing decisions. The router doesn't check "which agent specialization scores best for this file domain." It's write-only data.
-
-HIGH - Handoff briefs degrade over generations (lines 154-219) By rotation 5-10, the brief is summarizing summaries. Content degradation compounds. There's no quality scoring to flag "this was a clean rotation" vs "this was an emergency rotation."
-
-MEDIUM - No mid-session memory injection (introducer.js lines 345-381) Memory is injected once at spawn. If journalist discovers a critical fix during the agent's session, the running agent never learns it. Only the next rotated agent sees it.
-
-LAYER 8: ROUTER + CLASSIFIER (router.js, classifier.js) ---------------------------------------------------------
-
-CRITICAL - Classifier and Router are disconnected (entire design) Classifier produces tier classifications (light/medium/heavy). Router makes model decisions. But router.recommend() is called ONCE at spawn. Classifier broadcasts updates to UI only. There is NO feedback loop from classifier to router mid-session. An agent can drift from heavy to light work and stay on the expensive model for the entire session.
-
-HIGH - Default routing mode is FIXED, not AUTO (router.js line 73) Unless explicitly set, agents spawn in FIXED mode with no adaptive routing. Most agents never get auto-routing.
-
-HIGH - Cost tracking is dead code (router.js lines 125-136) recordUsage() is called, costLog accumulates data, but nothing reads the cost log. Cost data exists but never feeds back into routing decisions.
-
-MEDIUM - 200-event classifier window averages away trends (classifier.js line 39) If task complexity changes at event 190, classifier still averages across events 1-189. Recent changes are diluted.
-
-BACKBONE: API + REGISTRY + STATE (api.js, registry.js, state.js, timeline.js) -------------------------------------------------------------------------------
-
-HIGH - O(n^2) broadcast on every registry change (api.js line 224) Every agent spawn/update/remove triggers enrichAgents() on ALL agents, then broadcasts full state to ALL WebSocket clients. With 10 agents and frequent updates, this is expensive.
-
-HIGH - State saved every 30 seconds (index.js lines 518-521) If daemon crashes 29 seconds after an agent spawn, that agent is lost. State persistence should be 5s max for critical data.
-
-HIGH - Synchronous state write blocks event loop (state.js line 24) writeFileSync on every save. Blocks all other operations for the duration of the write.
-
-MEDIUM - Timeline caps at 16.7 hours (timeline.js lines 8-10) 2000 snapshots x 30s = 16.7 hours. After that, oldest snapshots are silently deleted. For multi-day sessions, early history is gone.
-
-MEDIUM - AGENTS_REGISTRY.md rewritten every 2 seconds (index.js lines 210-220) On every registry change, debounced to 2s. Also rewrites the GROOVE section of CLAUDE.md. Constant file I/O.
-
-THE DEGRADATION CASCADE -------------------------
-
-Here's what actually happens when a planner agent runs for 30+ minutes:
-
-T=0:00 - Agent spawns with role only, no prompt
-
--
-hasTask=false, so Layer 7 discoveries are SKIPPED
--
-Router defaults to FIXED mode, no auto-routing
--
-Agent starts blind to all prior learnings
-T=0:30 - Agent reads files, builds mental model
-
--
-Exploration events (Read, Glob, Grep) are filtered OUT of
-journalist synthesis
-
--
-Classifier window starts filling (200-event buffer)
-T=2:00 - First journalist synthesis cycle
-
--
-Only captures 3-5K tokens of activity (40K char budget)
--
-Exploration context excluded
-T=5:00 - Agent is productive but context window filling
-
--
-Quality score: 65 (decent but in dead zone 40-70)
--
-No rotation triggered (quality threshold is 40)
--
-No model downshift (classifier needs 40+ events)
--
-Adaptive threshold nudges up (+2%)
-T=10:00 - Context usage at 40-50%
-
--
-Agent slowing down, re-reading files
--
-Quality score drops to 55 (still in dead zone)
--
-Classifier broadcasts tier update to UI only
--
-Router does nothing (FIXED mode, no mid-session routing)
--
-Token velocity increasing but below 1.5M/5min spike
-T=15:00 - Quality score drops to 38 (below threshold!)
-
--
-But agent is "active" (user reading output), idle check fails
--
-Rotation blocked because agent isn't idle 10+ seconds
--
-Agent continues degrading
-T=18:00 - Agent finally idle, quality rotation fires
-
--
-40K char synthesis captures last 20-30 events
--
-Exploration context lost
--
-Handoff brief generated: 7K tokens
--
-Old agent killed, state destroyed
-T=18:30 - New agent spawns with brief
-
--
-Gets discoveries this time (hasTask=true from brief)
--
-But only last 10 discoveries, 4K chars
--
-Doesn't know what files previous agent explored
--
-Spends first 2-3 turns re-reading same files
--
-Cooldown: can't rotate for 5 minutes even if degraded
-T=20:00 - New agent productive but missing context
-
--
-Doesn't have previous agent's intermediate reasoning
--
-Doesn't know which approaches were tried and failed
--
-Quality score defaults to 70 (not enough data yet)
-T=30:00 - Second rotation
-
--
-Handoff brief now summarizes a summary
--
-3K chars of rotation history (3 briefs compressed)
--
-Context loss compounds
-This cycle repeats. Each rotation loses ~50-70% of useful context. By rotation 5 (roughly 90 minutes), the agent is working with heavily compressed summaries and repeating exploration the first agent already did.
-
-PRIORITY FIXES FOR TRUE INFINITE SESSIONS -------------------------------------------
-
-TIER 1 - IMMEDIATE (stop the bleeding)
-
-1.
-Increase daemon heap to 2048MB (main.js line 178)
-Change: --max-old-space-size=2048 Impact: Eliminates GC-induced freezes, fixes desktop lag
-
-1.
-Force Layer 7 injection regardless of hasTask (process.js line 431)
-Change: Always pass hasTask=true to generateContext, or remove the gate Impact: First-generation agents get prior discoveries immediately
-
-1.
-Include exploration events in synthesis (journalist.js lines 211-218)
-Change: Don't filter Read/Glob/Grep into separate array; include in main entries with lower priority Impact: New agents know what files were examined
-
-1.
-Lower planner token ceiling from 50M to 10M (rotator.js)
-Change: Reduce ROLE_MULTIPLIERS.planner from 10 to 2 Impact: Planners rotate before burning excessive tokens
-
-1.
-Clean up maps on agent removal (process.js)
-Change: Clear peakContextUsage, pendingMessages, _streamThrottle when registry.remove() is called Impact: Stops unbounded memory growth
-
-TIER 2 - HIGH PRIORITY (fix the feedback loops)
-
-1.
-Connect classifier to router mid-session
-Change: When classifier detects tier change, call router.recommend() and auto-apply if confidence is high Impact: Agents auto-downshift to cheaper models when task simplifies
-
-1.
-Reduce rotation cooldown from 5 min to 2 min for quality rotation
-Change: Separate QUALITY_COOLDOWN_MS = 2 * 60 * 1000 Impact: Degraded agents recover faster
-
-1.
-Remove idle check for severe degradation
-Change: If quality score < 25, rotate immediately regardless of idle Impact: Severely degraded agents don't persist
-
-1.
-Increase synthesis budget to 100K chars (~25K tokens)
-Change: MAX_LOG_CHARS = 100_000 Impact: Captures 80-90% of recent activity instead of 30-40%
-
-1.
-Add post-rotation validation
-Change: Compare first-10-events quality of new agent vs last-10 of old agent. If worse, flag as cold start. Impact: System knows when rotation helped vs hurt
-
-TIER 3 - MEDIUM PRIORITY (optimize the flow)
-
-1.
-Delta-only WebSocket broadcasts (api.js line 224)
-Change: Send only changed agent data, not full state Impact: Reduces IPC pressure by 80%+
-
-1.
-Use specializations for routing
-Change: When task involves files agent previously excelled at, prefer that agent Impact: Agents build on proven strengths
-
-1.
-Increase handoff chain from 10 to 25 rotations
-Change: MAX_HANDOFF_ROTATIONS = 25 Impact: 2+ hours of causal history preserved
-
-1.
-State save every 5 seconds instead of 30
-Change: setInterval at 5000 Impact: Max 5s of data loss on crash instead of 30
-
-1.
-Pre-compile minimatch patterns (lockmanager.js)
-Change: Use minimatch.makeRe() at registration, cache compiled Impact: O(n*m) regex compilation per check reduced to O(n) lookup
-
-1.
-Fix listener cleanup on window reuse (main.js)
-Change: Remove all webContents listeners before re-registering Impact: Stops listener accumulation, reduces memory pressure
-
-TIER 4 - ARCHITECTURAL (true infinite sessions)
-
-1.
-Implement incremental context patching at rotation
-Instead of regenerating full context from scratch, patch only what changed since last rotation
-
-1.
-Add mid-session memory injection
-When journalist discovers new fix, inject into running agent via instruct endpoint
-
-1.
-Implement per-role quality baselines
-Calibrate scoring weights and thresholds per role type
-
-1.
-Add degradation cascade detection
-Track if downstream agents inherit errors from upstream rotations