osborn 0.9.54 → 0.9.55

package/.claude/skills/bug-reporter/SKILL.md

@@ -0,0 +1,129 @@
+---
+name: bug-reporter
+description: |
+  File a bug report or feature request when the user describes a problem with
+  Osborn itself (voice glitches, agent freezes, audio echo, session crashes,
+  interrupt issues) or asks for a new Osborn feature. Posts to a local agent
+  endpoint that hands the report off to the frontend, which writes it to
+  Supabase. Use whenever the user describes something wrong with Osborn —
+  NOT for questions about their own project code.
+---
+
+# Bug Reporter Skill
+
+File bug reports and feature requests from inside a voice session, without
+breaking the conversation. Reports land in the dev team's Supabase table for
+triage from a separate Claude Code session.
+
+## When to use this
+
+Trigger when the user describes any of these (or similar):
+
+**Bugs:**
+- Voice quality issues — "the audio cut out", "I can't hear you", "you keep echoing", "you interrupted yourself"
+- Agent malfunctions — "the agent froze", "it crashed", "it stopped responding", "you're stuck"
+- Session issues — "session disconnected", "the room keeps closing", "I had to restart"
+- Memory/state issues — "you don't remember", "you lost context"
+- Interrupt problems — "you keep cutting yourself off", "the interrupt isn't working"
+- Direct asks — "this is a bug", "file this", "report this", "let me know when it's fixed"
+
+**Feature requests:**
+- "I wish Osborn could…", "can you add…", "it would be nice if…", "feature request:"
+
+## When NOT to use
+
+- The user has a coding question about THEIR project — that's normal research/coding work
+- The user mentions an error in code they're writing — not an Osborn bug
+- The user is debugging their own logs — they're working, not reporting
+
+## How to file
+
+### Step 1 — confirm with the user
+
+Don't silently file. Say something brief like:
+
+> "Sounds like a real bug — want me to file it so the team can dig in? I'll
+> include the recent logs."
+
+If they say yes, proceed. If unsure, ask whether it's worth filing.
+
+### Step 2 — POST to the local agent endpoint
+
+```bash
+curl -sS -X POST http://localhost:8741/report-bug \
+  -H "Content-Type: application/json" \
+  -d @- <<'JSON'
+{
+  "type": "bug",
+  "severity": "medium",
+  "title": "Voice cuts out mid-sentence in pipeline mode",
+  "description": "User reported that the agent stops speaking mid-sentence and resumes 5 minutes later. Happens repeatedly. Started after migrating to user_state_changed handler (May 21, 0.9.39).",
+  "reproduction_notes": "Speak to the agent, then go silent — audio cuts off at a sentence boundary and won't resume until mic is muted for ~2 seconds.",
+  "tags": ["voice-quality", "interrupt", "echo"]
+}
+JSON
+```
+
+The agent endpoint:
+- Generates a `reportId`
+- Tails `/workspace/osborn.log` (last 500 lines)
+- Pulls the last few turns from the current JSONL session
+- Sends everything to the frontend via the LiveKit data channel
+- Returns `{ reportId, status: "submitted" }` to you
+
+You don't need to attach logs yourself — the agent does that automatically.
+
+### Step 3 — confirm to the user
+
+Briefly:
+
+> "Filed. Bug `f4a2…` — the team will look. Want me to log anything else?"
+
+Use the first 4 chars of the returned `reportId` as a short reference.
+
+## Choosing severity
+
+- `critical` — voice completely unusable, session crashes immediately, data loss
+- `high` — major friction (voice keeps cutting, frequent crashes, can't connect)
+- `medium` — annoying but workable (echo, occasional drops, minor UI glitches)
+- `low` — nice-to-have polish, edge cases, documentation gaps, feature requests
+
+Feature requests default to `low` unless the user describes blocking workflows.
+
+## Title writing
+
+Short, present-tense, specific. 6–10 words.
+
+Good:
+- "Voice cuts out mid-sentence in pipeline mode"
+- "Agent echoes own speech as user interrupt"
+- "Session orphaned after machine OOM auto-restart"
+
+Bad:
+- "voice bug" (too vague)
+- "When I was talking the agent stopped responding and I had to..." (use description)
+
+## What NOT to include in the description
+
+- Don't dump the full transcript — the agent attaches a `transcript_excerpt` automatically
+- Don't paste log lines — the agent attaches the `log_excerpt` automatically
+- Don't speculate about the fix unless the user explicitly suggested one
+- Don't include the user's API keys, OAuth tokens, or PII
+
+## Tags vocabulary
+
+Pick from these rough buckets (one or more):
+`echo, interrupt, crash, freeze, memory, voice-quality, audio, mode-specific,
+direct, pipeline, realtime, ui, sessions, fly, recall, meeting, deepgram, tts, stt`
+
+## Reading existing reports
+
+You don't query, list, or close reports from inside a voice session — that's
+the dev team's job from their own Claude Code session. If the user asks "is
+that bug fixed yet?", say "let me check" and use the same endpoint with `GET`:
+
+```bash
+curl -sS "http://localhost:8741/report-bug?id=${REPORT_ID}"
+```
+
+But typically the user won't ask, and you don't need to volunteer the status.

package/dist/index.js

@@ -14,6 +14,7 @@ import { existsSync, readdirSync, readFileSync, mkdirSync, writeFileSync, mkdtem
 import { dirname, join } from 'node:path';
 import { fileURLToPath } from 'node:url';
 import { spawn } from 'node:child_process';
+import { randomUUID } from 'node:crypto';
 import { homedir, tmpdir } from 'node:os';
 import { PassThrough } from 'node:stream';
 import { createGunzip } from 'node:zlib';
@@ -189,6 +190,14 @@ const livekitState = {
 let intentionalLeave = false;
 let connectRoomHook = null;
 let leaveRoomHook = null;
+// Hook for the bug-reporter skill. The /report-bug HTTP endpoint validates the
+// payload + generates the reportId in the module-level handler, then delegates
+// to this hook which lives in main() (where sendToFrontend, currentVoiceMode,
+// and currentSession are in scope). The frontend listens for the data channel
+// message type 'bug_report' and writes the row to Supabase — same architecture
+// as the existing fetch-log/save-log flow so we don't ship Supabase credentials
+// to the Fly machine.
+let bugReportHook = null;
 function startApiServer(workingDir, port) {
     const server = createServer(async (req, res) => {
         // CORS headers for cloud frontend
@@ -332,6 +341,67 @@ function startApiServer(workingDir, port) {
             }
             return;
         }
+        // POST /report-bug — invoked by the bug-reporter skill (running inside Claude
+        // Code on this same machine) when the user describes an Osborn bug or
+        // requests a feature. We validate the payload, generate a reportId, and emit
+        // a data channel message via bugReportHook → sendToFrontend. The frontend
+        // owns the actual Supabase write (it already has the keys for the log-upload
+        // flow, no need to ship them to the Fly machine).
+        if (req.method === 'POST' && url.pathname === '/report-bug') {
+            let body = '';
+            req.on('data', (chunk) => { body += chunk.toString(); });
+            req.on('end', () => {
+                try {
+                    const parsed = JSON.parse(body || '{}');
+                    const errors = [];
+                    if (parsed.type !== 'bug' && parsed.type !== 'feature')
+                        errors.push('type must be "bug" or "feature"');
+                    if (!parsed.title || typeof parsed.title !== 'string' || parsed.title.length < 3)
+                        errors.push('title required (>= 3 chars)');
+                    if (!parsed.description || typeof parsed.description !== 'string')
+                        errors.push('description required');
+                    const sev = parsed.severity || 'medium';
+                    if (!['low', 'medium', 'high', 'critical'].includes(sev))
+                        errors.push('severity invalid');
+                    if (errors.length) {
+                        res.writeHead(400, { 'Content-Type': 'application/json' });
+                        res.end(JSON.stringify({ error: 'invalid payload', details: errors }));
+                        return;
+                    }
+                    const reportId = randomUUID();
+                    const payload = {
+                        type: parsed.type,
+                        severity: sev,
+                        title: parsed.title.trim().slice(0, 200),
+                        description: parsed.description.trim().slice(0, 8000),
+                        reproduction_notes: typeof parsed.reproduction_notes === 'string'
+                            ? parsed.reproduction_notes.trim().slice(0, 4000)
+                            : undefined,
+                        tags: Array.isArray(parsed.tags)
+                            ? parsed.tags.filter((t) => typeof t === 'string').slice(0, 20)
+                            : undefined,
+                    };
+                    res.writeHead(200, { 'Content-Type': 'application/json' });
+                    res.end(JSON.stringify({ reportId, status: 'submitted' }));
+                    if (bugReportHook) {
+                        try {
+                            bugReportHook(reportId, payload);
+                        }
+                        catch (e) {
+                            console.error('❌ bugReportHook threw:', e);
+                        }
+                    }
+                    else {
+                        console.warn('⚠️ /report-bug fired but no bugReportHook registered (frontend may not receive)');
+                    }
+                }
+                catch (e) {
+                    res.writeHead(400, { 'Content-Type': 'application/json' });
+                    res.end(JSON.stringify({ error: 'invalid JSON', details: e.message }));
+                }
+            });
+            return;
+        }
         // POST /restart — graceful process restart (process manager will restart)
         if (req.method === 'POST' && url.pathname === '/restart') {
             res.writeHead(200, { 'Content-Type': 'application/json' });
@@ -2069,11 +2139,22 @@ async function main() {
                 // transcripts AND speechDuration updates), which is the path that was firing
                 // even after our user_state_changed handler skipped the trigger.
                 interruption: {
-                    minDuration: 750, // 500 → 750: require 750ms of sustained audio activity
-                    minWords: 2, // 0 → 2: require ≥2 transcript words (filters single-word echo blips)
-                    // SDK defaults kept: enabled=true, resumeFalseInterruption=true,
-                    // falseInterruptionTimeout=2000ms (that 2s timer is what resumed your audio
-                    // exactly where it stopped — confirmed working as designed).
+                    // SDK auto-interrupt fully DISABLED (0.9.55). Even with minDuration:750
+                    // and minWords:2 in 0.9.54, the SDK's onInterimTranscript path bypasses
+                    // duration gating (it fires on first interim text) and minWords gates
+                    // against accumulated transcript wordcount — so once a real user utters
+                    // ≥2 words, every subsequent echo passes. Worse: double-fires within
+                    // 200ms corrupt SegmentSynchronizerImpl state (pushAudio called after
+                    // close → markPlaybackFinished before input done → playback hangs).
+                    // With enabled:false the SDK won't fire interruptByAudioActivity at all;
+                    // our user_state_changed handler at index.ts:3162 with the self-echo
+                    // guard (lastRemoteSpeakerAt + ActiveSpeakersChanged) becomes the SOLE
+                    // interrupt path. We control timing, deduplication, and identity.
+                    enabled: false,
+                    // The values below have no effect with enabled:false but kept for
+                    // documentation in case enabled is flipped back on for testing.
+                    minDuration: 750,
+                    minWords: 2,
                 },
             },
         });
@@ -3009,8 +3090,16 @@ async function main() {
                         return;
                     }
                     try {
-                        console.log('🎤 user_state_changed=speaking + agent speaking + remote-speaker confirmed → interrupting TTS');
-                        currentSession?.interrupt();
+                        // force:true bypasses the SpeechHandle's allowInterruptions check
+                        // (speech_handle.js:93-99). Required because turnHandling.interruption.enabled=false
+                        // sets allowInterruptions=false on every SpeechHandle (agent_activity.js:329-331),
+                        // which is what blocks the SDK's auto-interrupt path — but without
+                        // force:true, this manual call from our handler would also throw
+                        // "This generation handle does not allow interruptions". Combined,
+                        // they let US interrupt (with self-echo guard already verified above)
+                        // while keeping the SDK's auto-trigger off.
+                        console.log('🎤 user_state_changed=speaking + agent speaking + remote-speaker confirmed → interrupting TTS (force)');
+                        currentSession?.interrupt({ force: true });
                     }
                     catch (err) {
                         console.warn('⚠️ user-state interrupt failed:', err instanceof Error ? err.message : err);
@@ -4282,6 +4371,40 @@ async function main() {
             console.error('leave-room room.disconnect failed:', e);
         }
     };
+    // bug-reporter skill hook — forwards a validated bug payload to the frontend
+    // via the LiveKit data channel. Frontend (which holds the Supabase keys for
+    // the existing log-upload flow) is responsible for the actual Supabase write.
+    // Enriches with the agent-side facts the frontend doesn't already have on
+    // hand (voice_mode + sandbox_id from FLY_MACHINE_ID — version it can read
+    // from /health, session_id it tracks via preSelectedSessionId).
+    bugReportHook = (reportId, payload) => {
+        const sandboxId = process.env.FLY_MACHINE_ID || null;
+        let osbornVersion;
+        try {
+            for (const rel of ['../package.json', '../../package.json']) {
+                try {
+                    const pkg = JSON.parse(readFileSync(join(__dirname, rel), 'utf8'));
+                    if (pkg.name === 'osborn' && pkg.version) {
+                        osbornVersion = pkg.version;
+                        break;
+                    }
+                }
+                catch { /* try next */ }
+            }
+        }
+        catch { /* version optional */ }
+        console.log(`🪲 Bug report ${reportId.slice(0, 8)} (${payload.type}/${payload.severity}): ${payload.title}`);
+        sendToFrontend({
+            type: 'bug_report',
+            reportId,
+            payload,
+            context: {
+                voice_mode: currentVoiceMode,
+                sandbox_id: sandboxId,
+                osborn_version: osbornVersion,
+            },
+        }).catch((e) => console.error('❌ bugReportHook sendToFrontend failed:', e));
+    };
     // Fire and forget; the retry loop keeps the process alive on its own (so
     // we don't need the explicit `new Promise(() => {})` keepalive anymore).
     // Errors that escape the retry loop should never happen, but if they do,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "osborn",
-  "version": "0.9.54",
+  "version": "0.9.55",
   "description": "Voice AI coding assistant - local agent that connects to Osborn frontend",
   "type": "module",
   "bin": {