Files
kandev/apps/web/lib/ws
João Salavisa 159f98efe6 feat(web): File browser with syntax-highlighted viewer (#13)
* feat(web): add file browser with syntax-highlighted viewer

- Add file browser component in right panel to browse workspace files
- Open files in left panel tabs alongside Notes/Changes/Chat
- Color-coded dots for file types (TS, JS, Go, Python, etc.)
- Visual separator between main tabs and file tabs
- Folders sorted to top in file tree view
- LRU eviction for max 4 open file tabs
- Backend handlers for workspace file tree and content via WebSocket

* fix(web): refresh file tree on filesystem changes via fsnotify

- Subscribe to file change notifications from agentctl's fsnotify watcher
- Backend lifecycle manager now connects to file changes stream
- Publishes FileChangeNotified events to event bus
- WebSocket broadcasts workspace.file.changes to task subscribers
- Frontend file browser refreshes tree when changes detected

* perf(agentctl): use fsnotify instead of polling for git status

- Replace 2-second polling with fsnotify-triggered updates
- Add debouncing (300ms) to batch rapid file changes
- Git status updates now triggered by actual filesystem changes
- More efficient and responsive than periodic polling

* refactor(agentctl): consolidate fs events into single debounced trigger

- Single fsChangeTrigger channel for all filesystem events
- After 300ms debounce: update git status, files, and notify subscribers
- Removed per-file notifications in favor of single 'refresh' event
- Simpler and more efficient than separate triggers

* refactor(agentctl): simplify file API - use HTTP for tree/content

- Remove unused filesConn, fileTreeConn, fileContentConn from Client struct
- Convert RequestFileTree and RequestFileContent from WebSocket to HTTP GET
- Remove StreamFiles and CloseFilesStream (redundant with file changes stream)
- Keep only fileChangesConn for the debounced refresh notification

HTTP is simpler than WebSocket for request/response patterns.

* feat(web): switch to CodeMirror for file viewer

- Replace react-syntax-highlighter with @uiw/react-codemirror
- Add language extensions for JS/TS, Python, Go, Rust, Java, C++, CSS, HTML, JSON, Markdown, YAML
- Use VS Code dark theme for consistent look
- Enable code folding and read-only mode
- Better performance and features than syntax highlighter

* refactor: consolidate duplicated types and extract shared constants

- Re-export file types from process package in agentctl/client.go instead of duplicating
- Move OpenFileTab type to lib/types/backend.ts (shared by file-browser and page-client)
- Extract FILE_EXTENSION_COLORS constant for file type color indicators
- Remove console.log statement and unused imports in file-browser.tsx
- Add 'refresh' operation to FileChangeNotificationPayload type

* refactor(agentctl): move Close() method from acp.go to client.go

Close() is a general client cleanup method that closes all streams
(ACP, permissions, git status, file changes). It belongs in client.go
since acp.go should only contain ACP-specific communication logic.

* fix(web): remove unused cn import in file-browser

* refactor(agentctl): consolidate duplicated types into process/types.go

- Create process/types.go with all workspace-related types
- Remove duplicate GitStatusUpdate, FileInfo from workspace_tracker.go
- Remove duplicate GitStatusUpdate, FileInfo from api/workspace.go
- Re-export all types from agent/agentctl/client.go for convenience

Types are now defined once and imported everywhere.

* chore: remove package-lock.json, add to .gitignore

Project uses pnpm (pnpm-lock.yaml), not npm.

* fix(orchestrator): probe agent before returning stale execution state

When checking task.execution, the backend now probes the actual agent:
- For tracked instances: health check via agentctl
- For Docker: verify container is running

If the agent is not running but DB says 'running', the session is
marked as stopped and false is returned. This fixes the UI showing
agents as running after backend restart when they're actually dead.

Changes:
- Add IsAgentRunningForTask to AgentManagerClient interface
- Add IsContainerRunning to docker client
- Update GetExecution to verify agent is actually running
- Clean up stale sessions in database when agent not found

* fix(orchestrator): use agentctl status to verify agent is running

Simplified approach - probe agentctl's /api/v1/status endpoint to check
if agent process is running. Same check for both Docker and standalone.

- Add IsAgentRunning() helper to StatusResponse
- Simplify IsAgentRunningForTask to just use agentctl.GetStatus()

* fix(orchestrator): also verify agent running for in-memory executions

The previous fix only checked agent status when loading from DB. But if
an execution is cached in memory and the agent process stops (while
agentctl stays running), the stale state was still returned.

Now both paths verify the agent is actually running by probing agentctl.
If agent stopped, clean up in-memory state and update DB session.

* chore(web): remove unused react-syntax-highlighter

Switched to CodeMirror for code viewing, no longer needed.

* fix(tests): add IsAgentRunningForTask to mock agent managers

Add the new interface method to test mocks:
- mockAgentManager in scheduler_test.go
- SimulatedAgentManagerClient in orchestrator_test.go

---------

Co-authored-by: Kandev Agent <kandev@example.com>
2026-01-14 01:24:05 +00:00
..
2026-01-11 12:55:50 +00:00

WebSocket Client with Auto-Reconnect

This directory contains the WebSocket client implementation with automatic reconnection capabilities.

Features

1. Automatic Reconnection

  • Exponential Backoff: Reconnection delays increase exponentially to avoid overwhelming the server
  • Configurable Retry Limits: Set maximum number of reconnection attempts
  • Graceful Degradation: Properly handles connection failures and notifies the UI

2. Connection State Management

The client tracks the following connection states:

  • idle: Initial state before any connection attempt
  • connecting: Actively establishing a connection
  • open: Successfully connected and ready to send/receive messages
  • reconnecting: Attempting to reconnect after a disconnect
  • closed: Connection closed (intentionally or after max retries)
  • error: Connection failed and won't retry

3. Message Queue

  • Messages sent while disconnected are queued
  • Queued messages are automatically sent when connection is restored
  • Prevents message loss during brief disconnections

4. Subscription Management

  • Tracks task subscriptions across reconnections
  • Automatically re-subscribes to all tasks when reconnected
  • Provides subscribe() and unsubscribe() methods for easy subscription management

5. Pending Request Handling

  • Properly cleans up pending requests on disconnect
  • Rejects pending promises with appropriate error messages
  • Prevents memory leaks from abandoned requests

Configuration

Reconnect Options

interface ReconnectOptions {
  enabled?: boolean;           // Enable/disable auto-reconnect (default: true)
  maxAttempts?: number;        // Maximum reconnection attempts (default: 10)
  initialDelay?: number;       // Initial delay in ms (default: 1000)
  maxDelay?: number;           // Maximum delay in ms (default: 30000)
  backoffMultiplier?: number;  // Exponential backoff multiplier (default: 1.5)
}

Default Configuration

const DEFAULT_RECONNECT_OPTIONS = {
  enabled: true,
  maxAttempts: 10,
  initialDelay: 1000,      // 1 second
  maxDelay: 30000,         // 30 seconds
  backoffMultiplier: 1.5,
};

Usage

Basic Usage

import { WebSocketClient } from '@/lib/ws/client';

const client = new WebSocketClient(
  'ws://localhost:8080/ws',
  (status) => {
    console.log('Connection status:', status);
  }
);

client.connect();

Custom Reconnect Configuration

const client = new WebSocketClient(
  'ws://localhost:8080/ws',
  (status) => {
    console.log('Connection status:', status);
  },
  {
    enabled: true,
    maxAttempts: 5,
    initialDelay: 2000,
    maxDelay: 60000,
    backoffMultiplier: 2,
  }
);

Subscribing to Tasks

// Subscribe to task updates
client.subscribe('task-id-123');

// Unsubscribe when done
client.unsubscribe('task-id-123');

Sending Messages

// Send a message (queued if not connected)
client.send({ type: 'request', action: 'some.action', payload: {} });

// Send a request and wait for response
const response = await client.request('task.get', { id: 'task-123' });

Listening to Events

const unsubscribe = client.on('task.updated', (message) => {
  console.log('Task updated:', message.payload);
});

// Clean up when done
unsubscribe();

Reconnection Behavior

Exponential Backoff Example

With default settings:

  • Attempt 1: 1 second delay
  • Attempt 2: 1.5 seconds delay
  • Attempt 3: 2.25 seconds delay
  • Attempt 4: 3.375 seconds delay
  • ...
  • Attempt 10: 30 seconds delay (capped at maxDelay)

What Happens on Disconnect

  1. Connection closes (network issue, server restart, etc.)
  2. Client sets status to closed
  3. If not an intentional disconnect and reconnect is enabled:
    • Calculate delay using exponential backoff
    • Set status to reconnecting
    • Schedule reconnection attempt
  4. On successful reconnection:
    • Reset reconnect attempt counter
    • Set status to open
    • Flush queued messages
    • Re-subscribe to all tasks
  5. If max attempts reached:
    • Set status to error
    • Clean up pending requests
    • Stop reconnection attempts

Integration with React

The useWebSocket hook automatically sets up the client with reconnection:

import { useWebSocket } from '@/lib/ws/use-websocket';

export function MyComponent() {
  const store = useAppStoreApi();
  useWebSocket(store, 'ws://localhost:8080/ws');
  
  // Connection status is automatically synced to store
  const status = useAppStore((s) => s.connection.status);
  
  return <div>Status: {status}</div>;
}

Testing

To test reconnection behavior:

  1. Start the application
  2. Open browser DevTools → Network tab
  3. Observe WebSocket connection
  4. Stop the backend server
  5. Watch the client attempt to reconnect with increasing delays
  6. Restart the backend server
  7. Verify the client reconnects and re-subscribes to tasks

Best Practices

  1. Always use the provided methods: Use subscribe()/unsubscribe() instead of sending raw messages
  2. Handle connection states in UI: Show appropriate feedback for connecting, reconnecting, and error states
  3. Clean up subscriptions: Always unsubscribe when components unmount
  4. Configure appropriately: Adjust reconnect settings based on your use case
  5. Monitor console logs: Reconnection attempts are logged for debugging