@hienlh/ppm 0.8.1 → 0.8.2

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## [0.8.2] - 2026-03-23
+
+### Fixed
+- **Heartbeat during SDK connection**: Keep "Connecting... (Xs)" indicator alive until real content arrives — previously stopped by `account_info` event, causing misleading "thinking" state during 3-minute SDK failures
+- **Unknown API error hint**: "API error: unknown" now shows actionable guidance (check connectivity, re-add account, new session)
+
 ## [0.8.1] - 2026-03-23
 
 ### Fixed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hienlh/ppm",
-  "version": "0.8.1",
+  "version": "0.8.2",
   "description": "Personal Project Manager — mobile-first web IDE with AI assistance",
   "author": "hienlh",
   "license": "MIT",

package/src/providers/claude-agent-sdk.ts

@@ -797,6 +797,7 @@ export class ClaudeAgentSdkProvider implements AIProvider {
               rate_limit: "Rate limited by the API. Please wait and try again.",
               invalid_request: "Invalid request sent to the API.",
               server_error: "Anthropic API server error. Try again shortly.",
+              unknown: "API connection failed. Possible causes: network unreachable, expired OAuth token, or API outage. Try: 1) Check connectivity (`curl -s https://api.anthropic.com`), 2) Re-add account in Settings, 3) Create a new chat session.",
             };
             const hint = errorHints[assistantError] ?? `API error: ${assistantError}`;
             console.error(`[sdk] session=${sessionId} assistant error: ${assistantError}`);

package/src/server/ws/chat.ts

@@ -146,8 +146,12 @@ async function runStreamLoop(sessionId: string, providerId: string, content: str
       const ev = event as any;
       const evType = ev.type ?? "unknown";
 
-      // First event received — stop heartbeat, switch to streaming status
-      if (!firstEventReceived) {
+      // First content event — stop heartbeat, switch to streaming status.
+      // Skip metadata events (account_info, streaming_status) that arrive before
+      // the SDK subprocess actually produces output — keeps heartbeat + "connecting"
+      // indicator alive until real content flows.
+      const isMetadataEvent = evType === "account_info" || evType === "streaming_status";
+      if (!firstEventReceived && !isMetadataEvent) {
         firstEventReceived = true;
         const waitMs = Date.now() - startTime;
         console.log(`[chat] session=${sessionId} first SDK event after ${waitMs}ms: type=${evType}`);