agentgui 1.0.393 → 1.0.394

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agentgui",
-  "version": "1.0.393",
+  "version": "1.0.394",
   "description": "Multi-agent ACP client with real-time communication",
   "type": "module",
   "main": "server.js",

package/.prd

@@ -1,215 +0,0 @@
-# AgentGUI ACP Compliance PRD
-
-## Overview
-Transform AgentGUI into a fully ACP (Agent Connect Protocol) v0.2.3 compliant server.
-
-**Current Status**: 100% ACP compliant - All waves completed
-**All Required Features**: Fully implemented and tested
-
-**Note on "Slash Commands"**: ACP spec contains no slash command concept. This is purely a client-side UI feature outside ACP scope. If user wants slash commands implemented, that would be a separate UI enhancement task.
-
----
-
-## Completion Status
-
-### ✅ WAVE 1: Foundation (COMPLETED)
-- Database schema extended with ACP tables
-- Thread state management implemented
-- Checkpoint system operational
-
-### ✅ WAVE 2: Core ACP APIs (COMPLETED)
-- All 23 ACP endpoints implemented
-- Threads API fully functional
-- Stateless runs supported
-- Agent discovery operational
-
-### ✅ WAVE 3: SSE Streaming & Run Control (COMPLETED)
-- SSE streaming endpoints implemented
-- Run cancellation working
-- Event stream format compliant with ACP spec
-
-### ✅ WAVE 4: UI Fixes & Optimization (COMPLETED - Enhanced)
-- **4.1** Thread Sidebar UI Consistency: Fixed agentId vs agentType inconsistency, sidebar now correctly uses `agentId`, model column confirmed in database, agent/model restore on page reload working
-- **4.2** WebSocket Optimization: Added message deduplication via `wsLastMessages` Map and `createMessageKey()` function, prevents identical consecutive messages, adaptive batching and rate limiting already present
-- **4.3** Duplicate Displays: Removed redundant agent/model from conversation headers (3 locations) and streaming start event, kept authoritative displays in sidebar and input selectors only
-
----
-
-## Additional Enhancements (Non-blocking)
-
-### NICE-TO-HAVE 1: Webhook Callbacks
-- Implement webhook support for run status changes
-- POST to webhook URL when run status changes (pending → active → completed)
-- Retry logic: 3 attempts with exponential backoff
-- Store webhook config in run_metadata table
-- Validate webhook URL format on run creation
-
-### NICE-TO-HAVE 2: Run Interrupts
-- Support interrupt mechanism for agents that implement it
-- Interrupt types: user feedback request, tool approval, configuration needed
-- Store interrupt state in sessions table
-- API endpoints: GET /runs/{id}/interrupts, POST /runs/{id}/resume with interrupt response
-- UI: show interrupt prompt, collect user input, resume run
-
-### NICE-TO-HAVE 3: Enhanced Search & Filtering
-- Full-text search on thread content (messages, agent responses)
-- Filter by agent type, date range, status, metadata fields
-- Search history: recent searches saved per user
-- Autocomplete for search filters
-- Export search results as JSON
-
-### NICE-TO-HAVE 4: Thread Templates
-- Save thread configuration as template
-- Templates include: agent, model, initial prompt, working directory
-- Clone thread from template
-- Share templates between users (if multi-user support added)
-
----
-
-## Testing Requirements (Per Item)
-
-Each implementation item must include:
-1. Execute in plugin:gm:dev: create test run for every endpoint/function
-2. Success paths: valid inputs, expected outputs verified
-3. Error paths: invalid inputs, 404s, 409s, 422s verified
-4. Edge cases: empty results, large payloads, concurrent requests
-5. Integration tests: end-to-end flow (create thread → run → stream → cancel)
-6. Database verification: inspect tables after operations, verify foreign keys
-7. WebSocket verification: subscribe, receive events, verify payload format
-8. SSE verification: curl endpoint, verify event-stream format
-
----
-
-## Acceptance Criteria (All Must Pass)
-
-### Core ACP Compliance
-- [ ] All 23 ACP endpoints implemented and tested
-- [ ] All ACP data models match spec (Thread, ThreadState, Run, Agent, etc.)
-- [ ] Error responses follow ACP format (ErrorResponse schema)
-- [ ] SSE streaming works with curl: `curl -N /threads/{id}/runs/stream`
-- [ ] Stateless runs work without thread context
-- [ ] Run cancellation kills agent process within 5 seconds
-- [ ] Thread copy duplicates all states and checkpoints
-- [ ] Agent descriptors return valid JSON matching AgentACPDescriptor schema
-
-### Database Integrity
-- [ ] No orphaned records after thread/run deletion
-- [ ] Foreign key constraints enforced
-- [ ] Thread status correctly reflects run states
-- [ ] Checkpoint sequences monotonically increase
-- [ ] WAL mode enabled, queries under 100ms for typical operations
-
-### UI Consistency
-- [ ] Sidebar shows correct agent for each conversation
-- [ ] Model selection persists after page reload
-- [ ] No duplicate agent/model displays found
-- [ ] Agent/model changes reflected in database immediately
-
-### WebSocket Optimization
-- [ ] Streaming progress events batched (max 10/100ms)
-- [ ] Only subscribed clients receive messages
-- [ ] No client exceeds 1MB/sec sustained WebSocket traffic
-- [ ] Message deduplication prevents identical consecutive events
-
-### Integration & E2E
-- [ ] Full flow: create thread → start run → stream events → cancel → verify cancelled
-- [ ] Stateless run: create run → stream → complete → verify output
-- [ ] Thread search: create 10 threads → search by metadata → verify correct results
-- [ ] Agent search: search by capability "streaming" → verify all streaming agents returned
-- [ ] Thread copy: create thread with 5 runs → copy → verify new thread has all history
-- [ ] Concurrent runs blocked: start run on thread → start second run → verify 409 conflict
-
----
-
-## Migration Strategy
-
-### Backward Compatibility
-- Existing conversations map to threads (1:1)
-- Existing sessions map to thread runs
-- `/api/conversations/*` endpoints remain functional (alias to `/threads/*`)
-- Old WebSocket message formats supported alongside new ACP formats
-- No breaking changes to current client code
-
-### Rollout Plan
-1. Deploy database schema changes (additive only, no drops)
-2. Deploy new ACP endpoints alongside existing endpoints
-3. Update client to use ACP endpoints where beneficial
-4. Deprecation notice for old endpoints (6 month window)
-5. Remove old endpoints after deprecation period
-
----
-
-## Out of Scope
-
-- Multi-user authentication/authorization
-- Slash command implementation (not in ACP spec, pure client feature)
-- Agent marketplace or discovery service
-- Real-time collaboration on threads
-- Thread branching/forking (beyond simple copy)
-- Custom agent development framework
-- Billing/metering for agent usage
-
----
-
-## Technical Notes
-
-### ACP Terminology Mapping
-- AgentGUI "conversations" = ACP "threads"
-- AgentGUI "sessions" = ACP "runs" (stateful, on a thread)
-- AgentGUI "chunks/events" = ACP "run output stream"
-- AgentGUI "claudeSessionId" = ACP checkpoint ID concept
-
-### Known Gotchas
-- ACP requires UUID format for thread_id, run_id, agent_id (current AgentGUI uses strings)
-- SSE requires newline-delimited format, different from current JSON streaming
-- Run cancellation must handle agents that don't support it gracefully
-- Thread status "idle" means no pending runs; must validate on run creation
-- Webhook URLs must be validated to prevent SSRF attacks
-
-### Performance Targets
-- Thread search: <200ms for 10,000 threads
-- Run creation: <50ms (background processing)
-- SSE streaming: <10ms latency per event
-- WebSocket batch: <100ms accumulation window
-- Database writes: <20ms per transaction
-
----
-
-## Dependencies
-
-**External**:
-- None (all features implemented with existing dependencies)
-
-**Internal**:
-- database.js (extended with new tables/queries)
-- server.js (new route handlers)
-- lib/claude-runner.js (run cancellation support)
-- static/js/client.js (UI consistency fixes)
-- static/js/conversations.js (agent/model persistence)
-- static/js/websocket-manager.js (optimization)
-
-**Configuration**:
-- No new env vars required
-- Existing BASE_URL, PORT, STARTUP_CWD remain unchanged
-
----
-
-## Success Metrics
-
-- ACP compliance score: 0% → 100%
-- API endpoint coverage: 20 → 43 endpoints
-- WebSocket bandwidth: <50% reduction in bytes/sec per client
-- UI consistency issues: 4 identified → 0 remaining
-- Database tables: 5 → 8 (conversations, messages, sessions, events, chunks, thread_states, checkpoints, run_metadata)
-- Test coverage: endpoint tests for all 43 routes, integration tests for all critical flows
-
----
-
-## Timeline Estimate
-
-- Wave 1 (Foundation): 3 parallel tasks = 1 completion cycle
-- Wave 2 (Core APIs): 3 parallel tasks = 1 completion cycle
-- Wave 3 (Streaming): 2 tasks = 1 completion cycle
-- Wave 4 (UI Fixes): 3 tasks = 1 completion cycle
-
-**Total**: 4 completion cycles (waves executed sequentially, items within wave executed in parallel with max 3 concurrent subagents per wave)