# Anthropic Recruiter Reply + Browser Agent Public Release

**Date:** 2026-04-10
**Duration:** ~45 minutes
**Repos touched:** assortedLLMTasks, claude-browser-agent (new)

## Context & Motivation

Laura Small (Anthropic recruiter) reached out about the PM Consumer role referral. The HM had already reviewed Nick’s profile and leaned toward candidates with more founder experience, so the reply needed to hedge toward other roles while demonstrating deep product usage.

Session evolved from drafting the email reply into creating a public-ready version of the browser-agent repo to strengthen the project portfolio shared with the recruiter.

## Decisions Made

### 1. Email Positioning Strategy
– **Decision:** Lead with PM Consumer excitement but prominently hedge toward “exploring where I’d be the best fit”
– **Alternatives:** (a) Go all-in on PM Consumer, (b) Ask about specific other roles
– **Rationale:** HM already soft-passed for founder experience. The real play is keeping Laura engaged as a router to other roles. Being explicitly open makes her job easy without signaling desperation.
– **Trade-offs:** Slight risk of seeming unfocused, mitigated by the strong project list anchoring Claude expertise.

### 2. Project List Format
– **Decision:** Bullet points with plain descriptions + GitHub links, no inline repo name parentheticals
– **Rationale:** Recruiter audience — scannable > technical. GitHub link lets her dig deeper if she wants.

### 3. Browser Agent Public Release
– **Decision:** Create a fresh `claude-browser-agent` repo from a scrubbed copy rather than making the existing repo public or using GitHub fork
– **Alternatives:** (a) Make browser-agent public directly, (b) GitHub fork
– **Rationale:** Git history in the private repo contains hardcoded SSH credentials, Discord webhooks, VM paths. Fresh repo with clean history is the only safe option.

### 4. Userscript Configuration Approach
– **Decision:** Use `GM_getValue(“BROWSER_AGENT_API”)` with localhost default instead of hardcoded domain
– **Alternatives:** Build-time injection, separate config file
– **Rationale:** Tampermonkey scripts don’t have a build step. GM_getValue is the standard TM storage mechanism and can be set from browser console. Simplest approach.

## What Was Built / Changed

### 1. Recruiter Reply Draft (`assortedLLMTasks`)
– Created `applications/anthropic/pm_consumer/recruiter_reply_draft.md`
– Structured to hedge toward other roles while showcasing Claude Code depth
– Committed: [f046e39](https://github.com/npezarro/assortedLLMTasks/commit/f046e39)

### 2. Public Browser Agent Repo (`claude-browser-agent`)
– Created fresh repo: https://github.com/npezarro/claude-browser-agent
– Scrubbed 6 files from the private `browser-agent` repo:
– `deploy.sh` — SSH creds → env vars (`VM_USER`, `VM_HOST`, `VM_KEY`, `VM_PATH`)
– `agent-server.js` — Hardcoded VM paths → `process.cwd()` fallback; removed GitHub clone URL
– `browser-cli.sh` — Removed WSL paths, SCP credentials, cowork-sync/capture-daemon commands
– `browser-agent.user.js` — Hardcoded `pezant.ca` → configurable `GM_getValue` with localhost default; removed `@updateURL`/`@downloadURL`
– `install.html` — Cleaned to only show browser agent (removed freeGames scripts)
– Excluded: `context.md`, `progress.md`, `.env` (internal notes / secrets)
– Added: `.env.example`, `README.md` with full setup guide
– Security verification: `grep -rn` for all sensitive patterns returns zero matches
– Committed: [e1b5d5a](https://github.com/npezarro/claude-browser-agent/commit/e1b5d5a)

## Learnings Captured

– `.env.*` in gitignore catches `.env.example` — use `!.env.example` negation pattern when standardizing gitignore
– For public forks of private repos: always fresh-init rather than filter-branch. Cleaner and less error-prone.

## Open Items & Follow-ups

1. **Rotate credentials** — `BROWSER_AGENT_KEY` and Discord cowork webhook should be rotated (they were in `.env` which is gitignored, but the values existed in the private repo’s working copy)
2. **Send the email** — Draft is ready in `applications/anthropic/pm_consumer/recruiter_reply_draft.md`, needs final review and send
3. **Add browser-agent line to email** — User has the suggested line; needs to add it before sending
4. **claude-tray-notifier** — Identified as another potential repo to highlight but not added to the email draft

## Key Files

– [Recruiter reply draft](https://github.com/npezarro/assortedLLMTasks/blob/main/applications/anthropic/pm_consumer/recruiter_reply_draft.md)
– [claude-browser-agent repo](https://github.com/npezarro/claude-browser-agent)
– [claude-browser-agent README](https://github.com/npezarro/claude-browser-agent/blob/main/README.md)

Context

Browser-agent TM userscript was causing Edge to hang during extended sessions. Root cause: aggressive DOM polling (two uncoordinated loops at 2s and 3s), accumulated timeout timers, and server-side memory leaks from orphaned state.

Fixes (v1.8.0)

• Merged polling loops: Two separate timers to single 3s tick(). Cuts DOM polling ~40%.
• Cached getPageState(): 2s TTL cache prevents redundant DOM traversal on heartbeats.
• Command timeout cleanup: Promise.race timers now cleared on completion via finally block.
• Circular console buffer: O(1) ring buffer replaces O(n) .shift() on every log entry.
• Server cleanup routines: 30s interval prunes dead tabs, expired resultWaiters (10min TTL), and orphaned command queues.

Key Decisions

• Single 3s polling interval is sufficient — SPA navigation detection latency goes from 2s to 3s, negligible for the use case.
• Heartbeat page state can be up to 2s stale (cached). Explicit getState commands still return fresh data.
• Server cleanup runs every 30s automatically, no longer depends on /health endpoint being hit.

Deployment

Deployed via SCP to VM (browser-agent directory is not a git repo). PM2 restarted. TM script hosted at pezant.ca/browser-agent.user.js for auto-update.

Open Items

• Monitor Edge stability over next few sessions
• If still hanging: consider requestIdleCallback wrapper, MutationObserver for SPA detection, or increasing POLL_MS to 5s

Commit 8645c0a | Repo

# Auto Shorts: Analytics, Learning Agent & Experimentation Framework
**Date:** 2026-04-09
**Duration:** ~4 hours
**Repos touched:** auto-shorts, shorts-pipeline

## Context & Motivation
The Auto Shorts system generates YouTube Shorts from long-form cooking videos for the Chef Agathe channels (EN + FR) but had zero visibility into performance. The user wanted to:
1. Measure how different titles, descriptions, and cutting approaches perform
2. Build a system that learns per-channel what resonates and applies those learnings automatically
3. Create an experimentation framework to test new approaches, measure results, and graduate winners

The goal is to maximize a mix of views, watch completions, and shares.

## Decisions Made

### Analytics via YouTube APIs (not scraping)
– **Decision:** Use YouTube Data API v3 for basic stats + YouTube Analytics API for watch completion
– **Alternatives:** YouTube Studio scraping, manual data entry
– **Rationale:** API is reliable, automated, and gives per-video granularity
– **Trade-offs:** Analytics API requires separate OAuth scope (yt-analytics.readonly) — needed GCP Console changes and channel re-auth

### Server-side token exchange (not worker-dependent)
– **Decision:** OAuth callback exchanges tokens directly via Google’s token endpoint in Node.js
– **Alternatives:** Original design delegated to Python worker for token exchange
– **Rationale:** Worker wasn’t running on VM; server-side exchange is self-contained
– **Trade-offs:** Token files stored on VM in data/tokens/ rather than in shorts-pipeline repo

### Learnings injected via instructions field (zero pipeline changes)
– **Decision:** Channel learnings and experiment instructions are prepended to the job’s `instructions` field at poll time
– **Alternatives:** Modify pipeline.py to read learnings directly, add a new field to the job schema
– **Rationale:** The worker’s `auto_select_preset()` and `analyze_transcript()` already read instructions — prepending context is invisible to the pipeline
– **Trade-offs:** Instructions can get long with many learnings; capped at top 10

### Experiments seed jobs immediately by default
– **Decision:** Creating an experiment pulls unprocessed videos from the library and creates jobs right away
– **Alternatives:** Wait for auto-poll to find new uploads (could take days)
– **Rationale:** User wanted experiments to start producing results quickly; existing library has 140+ EN and 66+ FR unprocessed videos
– **Trade-offs:** Uses existing library videos rather than only new uploads. “Wait for next auto-generate” is available as opt-out

## What Was Built / Changed

### Phase 1: YouTube Analytics Dashboard
– **New tables:** `clip_analytics_snapshots` (per-clip stats over time), `analytics_fetch_log`
– **Migrations:** `shorts_clips.channel_id`, `shorts_channels.analytics_scope`, `shorts_channels.last_analytics_fetch`
– **8 analytics query functions** in shorts-queue.js including preset comparison, channel summaries, snapshot history
– **Python fetcher** (`shorts-pipeline/fetch_analytics.py`): pulls stats from YouTube Data API, batches 50 videos per request, posts to server. Auto-syncs tokens from server for scope changes
– **3 dashboard views:** main overview (preset comparison bar chart, top performers), channel detail (sortable table), clip detail (growth chart with deltas)
– **Nav update:** Analytics link added to all 7 existing EJS views
– 12 new tests

### Phase 2: Deep Analytics (YouTube Analytics API)
– GCP Console: YouTube Analytics API enabled, yt-analytics.readonly scope added to OAuth consent screen (done manually via Cowork)
– OAuth auth-url route supports `?analytics=1` to request extended scope
– Settings UI shows “Enable Deep Analytics” / “Re-authenticate Analytics” button per channel
– `auth_channel.py –analytics` flag for CLI re-auth
– `fetch_analytics.py –mode full` pulls averageViewDuration, averageViewPercentage, shares
– Both Chef Agathe channels re-authed with analytics scope, initial data seeded (20 clips)

### Server-Side Token Exchange
– Replaced worker-dependent exchange with direct Node.js exchange via Google’s token endpoint
– Tokens saved to `data/tokens/` on VM
– New `GET /worker/token` route lets local fetcher pull tokens remotely
– `fetch_analytics.py` auto-syncs tokens from server when running in full mode

### Learning Agent
– **New file:** `lib/shorts-learning-agent.js` — periodic script that reviews per-channel analytics, sends data to Claude, extracts structured insights
– **New table:** `channel_learnings` (category, insight, confidence, sample_size, source, active)
– Claude prompt includes all clip data, preset comparison, and current learnings for refinement
– Insights categorized: duration, content_type, style, timing, general
– Confidence tied to sample size: low (<15), medium (15-30), high (>30)
– Can be triggered manually via POST /learnings/:channelId/run or run as standalone script
– Initial run produced 10 EN insights and 8 FR insights

### Experimentation Framework
– **New table:** `channel_experiments` (name, hypothesis, instructions, target_count, produced_count, status)
– **New table:** `experiment_suggestions` (persisted AI-generated suggestions)
– **Migration:** `shorts_clips.experiment_id` tags clips to experiments
– **Experiment lifecycle:** active → completed → graduated/rejected. Queued experiments auto-activate when current completes
– **Worker integration:** `/worker/poll` injects learnings + experiment instructions into job’s instructions field. `/worker/update` tags clips with experiment_id and increments produced_count
– **Auto-poll awareness:** New jobs check for active experiments and attach experimentId in metadata
– **Job seeding:** `seedExperimentJobs()` creates jobs from existing library videos immediately
– **Results comparison:** `getExperimentComparison()` compares experiment cohort vs baseline metrics
– **Graduation:** Converts experiment instructions into permanent channel learnings
– **AI suggestions:** POST `/experiments/:channelId/suggestions` generates 3 experiment ideas via Claude, persisted for later use. “Start This” / “Start All” buttons
– **UI:** Experiments page with active experiment progress bar, create form (Start Now vs Wait), queued experiments section, past experiments with status badges, suggestion cards with prior suggestions collapsible

### Weekly Learnings Summary
– **New file:** `lib/shorts-weekly-summary.js` — builds per-channel digest
– Sends email via SMTP (pezant.projects@gmail.com) to channel owner emails
– Posts to Discord #shorts-learnings channel (webhook created)
– Includes learnings, experiment status, and how-to guide
– Cron: every Monday at 9:03am on VM

### Operational Improvements
– **Stale job sweeper:** Runs every poll cycle, marks jobs stuck >2 hours as failed
– **Channel switcher:** Dropdown on all per-channel pages (analytics, learnings, experiments)
– **Auto-generate toggle:** Replaced checkbox with clear ON/OFF button + confirmation dialog
– **Static index.html fix:** Removed `public/index.html` that was overriding the EJS dashboard route
– **Channel lookup fix:** Routes use `getChannelById()` instead of filtering by logged-in email

## Architecture & Design

“`
┌─────────────────┐
│ YouTube APIs │
│ Data + Analytics│
└────────┬────────┘
│
┌──────────────┐ poll/update ┌────────┴────────┐ fetch_analytics.py
│ Python Worker │◄──────────────────►│ auto-shorts │◄───────────────────
│ (local WSL) │ learnings + │ server (VM) │ posts snapshots
│ pipeline.py │ experiment │ :3007 │
│ │ injected into ├─────────────────┤
│ │ instructions │ SQLite DB │
└──────────────┘ │ ├ shorts_jobs │
│ ├ shorts_clips │ ┌─────────────┐
┌──────────────┐ │ ├ clip_analytics│───►│ Dashboard │
│ Learning │ Claude analysis │ ├ channel_ │ │ /analytics │
│ Agent │◄──────────────────►│ │ learnings │ │ /learnings │
│ (6h cron) │ extract insights│ ├ channel_ │ │ /experiments│
└──────────────┘ │ │ experiments │ └─────────────┘
│ └ experiment_ │
┌──────────────┐ │ suggestions │ ┌─────────────┐
│ Weekly │ └─────────────────┘───►│ Email + │
│ Summary │ │ Discord │
│ (Mon 9am) │ └─────────────┘
└──────────────┘

Feedback loop:
Analytics fetched → Learning agent analyzes → Insights stored →
Worker poll injects learnings into prompt → Better clips produced →
Analytics measured → Cycle repeats
“`

## Learnings Captured

| Learning | Location |
|———-|———-|
| Test before asking user (channel lookup email mismatch, static index.html) | memory/feedback_test_before_asking.md (updated) |
| OAuth scope mismatch causes RefreshError when tokens have different scope | shorts-pipeline fix in fetch_analytics.py |
| duration_seconds is NULL for synced videos (playlistItems API doesn’t return it) | auto-shorts getUnprocessedVideos fix |

## Open Items & Follow-ups

1. **Worker rate limiting:** Currently processes back-to-back. Could add configurable delay between jobs to prevent YouTube 429 errors on large batches
2. **Learning agent cron:** Not yet set up as PM2 cron on VM — currently manual or via API trigger. Should be every 6 hours
3. **Queued experiments:** 6 experiments queued across both channels — will auto-activate as current ones complete
4. **Analytics fetch cron:** Should set up periodic `fetch_analytics.py –all –mode full` to keep stats current
5. **yt-dlp deprecation:** Worker logs warn about missing JS runtime — may need `deno` installed
6. **Experiment results review:** Once the 2 active experiments complete their 5 shorts each, results should be reviewed and graduated/rejected

## Key Files

### auto-shorts (Node.js server)
– `lib/shorts-queue.js` — All DB tables, migrations, query functions
– `lib/shorts-routes.js` — All routes (analytics, learnings, experiments, worker)
– `lib/shorts-auto-poll.js` — Auto-generation, experiment seeding, stale job sweeper
– `lib/shorts-learning-agent.js` — Periodic Claude-based analysis
– `lib/shorts-weekly-summary.js` — Weekly email + Discord digest
– `views/auto-shorts-analytics.ejs` — Main analytics dashboard
– `views/auto-shorts-analytics-channel.ejs` — Channel detail with sort/filter
– `views/auto-shorts-analytics-clip.ejs` — Clip detail with growth chart
– `views/auto-shorts-learnings.ejs` — Per-channel learnings management
– `views/auto-shorts-experiments.ejs` — Experiment creation, suggestions, results
– `ANALYTICS_SETUP.md` — Setup guide and cowork handoff instructions

### shorts-pipeline (Python worker tools)
– `fetch_analytics.py` — YouTube stats fetcher with token sync
– `auth_channel.py` — OAuth management with –analytics flag

Context & Motivation

Before fully transitioning Discord request handling from the existing debate/direct-execution path to the CLI mirror streaming approach, we needed to run both in parallel to evaluate CLI mirror’s real-world performance and catch any bugs.

The CLI mirror approach provides 1.5s streaming updates with visible tool calls in Discord threads — a significantly better UX than the current batch-response model.

What Was Built

Every fresh request in #requests now also fires a shadow run through #cli-mirror (fire-and-forget). Both the existing debate/direct path and the CLI mirror streaming path execute simultaneously.

Key Details

• Shadow mirrors don’t count against activeJobs concurrency limits
• Thread names suffixed with (mirror) for easy identification
• Metrics source tagged as cli-mirror-shadow
• Only fresh requests mirrored (not session resumes/replies)
• Fire-and-forget: if the mirror fails, the original request still completes

Architecture

User posts in #requests
    |
index.js request handler
    |-- [fire-and-forget] mirrorRequestToCliMirror() --> #cli-mirror thread (streaming)
    |                                                     --> 1.5s polling, tool call display
    |
    +-- [awaited] existing path (debate/handleRequest) --> #requests reply (batch)

Decisions

• Fire-and-forget shadow rather than replacing the existing path — zero risk, easy to remove
• No concurrency tracking for shadows — prevents false blocking of real requests
• Only fresh requests — session continuity (–resume) is path-specific

Files Changed

• src/bot/cliMirror.js — Added mirrorRequestToCliMirror() (+128 lines)
• src/bot/index.js — Shadow trigger in request handler (+8 lines)

Open Items

1. Monitor resource usage (two Claude processes per request during testing)
2. Compare quality and latency between both paths
3. Once satisfied, remove shadow and switch #requests to CLI mirror as primary

Repo: centralDiscord | Commit: faff71f

Summary

Built and shipped a live audio PM interview practice tool at pezant.ca/interview/. Claude CLI (Max subscription) as interviewer, browser SpeechSynthesis for TTS with 50+ voice options, Web Speech API for STT with auto voice activity detection. Loads 7+ interview prep files as context. Structured scoring rubric (5 categories, advance decision). All loose ends resolved: PM2 for server persistence, autossh for tunnel, 9 company prep mappings + auto-scan, clickable session review page with full transcripts.

Architecture

Browser (STT+TTS) ↔ WebSocket ↔ Express:3456 (WSL) ↔ autossh tunnel ↔ pezant.ca Apache /interview/ (HTTPS). Claude CLI via stdin pipe, sonnet model, Max OAuth.

Key Decisions

• Claude CLI over API — user requested leveraging Max subscription, zero marginal cost
• Browser SpeechSynthesis over Edge TTS — user tested Edge TTS, said terrible; browser voices much better
• 15s silence timeout — original 1.8s too aggressive for PM interview answers
• Settings panel with Save button — user explicitly requested explicit save vs live-apply

Commits

• c82aeb0 — Initial implementation
• 6aed990 — Context/progress files
• 67290f3 — Loose ends: PM2, autossh, company mappings, session review
• f115f67 — Final context update

Learnings

• Edge TTS npm broken on Node 22 (TypeScript in node_modules)
• ngrok now requires account; Cloudflare quick tunnel API unreliable
• Web Speech API not-allowed error creates infinite retry loops without denial tracking
• Claude CLI large prompts must pipe via stdin, not -p argument

Repo: npezarro/pm-interview-practice

Context

Built a live audio PM interview practice tool. Claude CLI as interviewer, browser SpeechSynthesis for TTS, Web Speech API for STT. Accessible at pezant.ca/interview/.

Key Decisions

• Claude CLI via stdin — zero cost on Max sub
• Browser SpeechSynthesis over Edge TTS — better voices
• 15s silence timeout, user-configurable
• SSH tunnel + Apache proxy for public HTTPS

What Was Built

• Express + WS server with Claude CLI orchestration
• Context loader reads 7 interview prep files
• Settings panel with voice picker, text-only mode
• Structured scoring rubric (5 categories, 1-5 scale)

# Deep Closeout: Discord Reliability Overhaul + CLI Mirror

**Date:** 2026-04-06 to 2026-04-07
**Duration:** ~3 hours
**Repos touched:** centralDiscord (12 commits), buying-assistant (2 commits), agentGuidance (1 commit), privateContext (1 commit)

## Context & Motivation

A buying guide request via Discord failed to read a Gemini share link (JS-rendered SPA). Investigation revealed a cascade of quality issues explaining why Discord sessions feel “dumber” than CLI sessions. The user asked for a root cause analysis, fixes, and ultimately a CLI-like interactive experience through Discord.

## What Was Built

### Phase 1: Root Cause Analysis & URL Pre-Fetching

**Problem:** WebFetch silently fails on JS-rendered SPAs (Gemini, React apps). Agents proceed without the context, producing lower-quality results.

**Fixes across 3 repos:**
– `contextFetcher.js`: Auto-detects external URLs in request text, pre-fetches via page-reader (headless Chromium), injects content into prompts
– `contextFetcher.js`: `stripBotOutput()` for retry detection in #buying-guides
– `executor.js` + `jobRequest.js`: Page-reader fallback instruction in all Discord directives
– `routeClassifier.js`: URL-dominated messages (>40% URL chars) classify as TASK, skip debate
– `buying-assistant/CLAUDE.md`: Explicit page-reader fallback instructions
– `agentGuidance/agent.md`: Page-reader fallback as a Core Principle

### Phase 2: Pre-Job Repo Sync

**Problem:** Pushing CLAUDE.md or agent.md changes from local had no effect on Discord agents because VM repos were never pulled.

**Fix:** `preJobSync()` in executor.js does `git pull –ff-only` on agentGuidance and the job’s working directory before every Claude spawn. 8s timeout, fire-and-forget.

Also synced page-reader on VM (was 5 commits behind, missing `–stealth`).

### Phase 3: Interactive Sessions ([WAITING_FOR_INPUT])

**Problem:** Discord sessions are single-shot with `clarifyAmbiguous: ‘best-effort’`. Agents can never ask clarifying questions.

**Solution:** Pause-and-resume protocol:
1. Agent outputs `[WAITING_FOR_INPUT]` + question, then stops
2. Bot detects marker, posts question to Discord, parks session
3. User replies with answer
4. Bot resumes with `–resume ` + answer
5. 30-minute timeout auto-resumes with “proceed with best judgment”

**Files:** sessionPool.js (waiting state management), claudeReply.js (detection + handling in all 3 execution paths), index.js (reply routing for waiting answers), jobRequest.js + executor.js (directive update)

### Phase 4: CLI Mirror Channel

**Problem:** Even with [WAITING_FOR_INPUT], Discord sessions lack the real-time visibility of the CLI.

**Solution:** New `#cli-mirror` channel with streaming output:
– Thread per conversation
– Live message edited every 1.5s with text + tool call indicators (`> Read package.json`)
– Messages freeze at 1800 chars, continue in new messages
– Session continuity via thread replies (`–resume`)
– `[WAITING_FOR_INPUT]` support for mid-task questions

**Files:** New `cliMirror.js` (250 lines), executor.js (configurable `pollIntervalMs`/`progressIntervalMs`, enriched `onProgress` with `textDelta`/`toolEvents`)

### Phase 5: Bug Fixes Found During Testing

1. **`fetchAttachments` return type mismatch** (from auto-merged PR #134): Early return `[]` vs normal return `{ results, mediaTempDir }`. Every text-only message in #requests was crashing. Fixed the early return.

2. **Raw NDJSON posted to Discord**: `local-worker.sh` had `2>&1` merging stderr into the NDJSON stream, corrupting JSON parsing. `extractFinalText()` returned empty, fallback posted raw JSON. Fixed: `2>/dev/null` + removed raw fallback.

3. **CLI mirror sessions lost on bot restart**: In-memory session pool wiped on restart. Fixed: session ID embedded in footer messages + thread message scanning fallback.

4. **`runClaudeRemote` missing poll interval params**: CLI mirror sessions routed to local worker used default 5s/15s intervals instead of 1.5s. Fixed: forwarded params through `runClaudeRemote`.

5. **Error serialization**: Pino’s `logger.error(‘msg:’, err)` didn’t serialize error objects. Fixed with `logger.error({ err, stack }, msg)`.

## Decisions Made

### Decision: Server-side URL pre-fetching + agent-side fallback (belt and suspenders)
– **Rationale:** Pre-fetching handles URLs in the initial request. Directive + CLAUDE.md handle URLs discovered during execution.
– **Trade-off:** 3-20s latency per pre-fetched URL. Acceptable for the quality improvement.

### Decision: [WAITING_FOR_INPUT] as text marker, not tool interception
– **Alternatives:** Stdin pipe injection, MCP server bridge, AskUserQuestion tool interception
– **Rationale:** Claude in `-p` mode finishes its turn and exits normally. No process killing, no stream interception, no architecture change. Just detect the marker in output, park the session, resume on reply.

### Decision: Enhanced polling for CLI mirror (not pipe-based streaming)
– **Alternatives:** Non-detached process with pipe-based streaming (true real-time)
– **Rationale:** Keeps the detached process model (survives bot restarts). 1.5s poll interval is imperceptible in Discord. Upgrade path to pipes exists for v2 if needed.

### Decision: Fix `local-worker.sh` stderr with `2>/dev/null` not `2>errfile`
– **Rationale:** Stderr from Claude sessions is mostly hook noise and debug output. The VM bot captures stderr separately via its own file descriptors. Discarding it on the local side is safe.

## Architecture

“`
User posts in Discord
|
v
index.js message router
|
+–> #cli-mirror ———> cliMirror.js
| |
| +–> StreamingDisplay (edit msg every 1.5s)
| +–> runClaude(pollIntervalMs: 1500)
| +–> sessionPool.registerSession(threadId)
| +–> [WAITING_FOR_INPUT] detection
|
+–> #requests ———–> debate/handleRequest
| |
| +–> buildRequestContext()
| | +–> prefetchExternalUrls() [NEW]
| | +–> stripBotOutput() [NEW]
| +–> runClaude/runClaudeRemote
| | +–> preJobSync() [NEW]
| +–> [WAITING_FOR_INPUT] detection [NEW]
|
+–> #buying-guides ——> executeRequest (buying-assistant cwd)
“`

## Learnings Captured

| Learning | Where Saved |
|—|—|
| Page-reader fallback for JS SPAs | agentGuidance/agent.md, buying-assistant/CLAUDE.md, executor.js directives |
| VM repos must be synced before jobs | executor.js preJobSync() |
| fetchAttachments return type contract | Fixed in contextFetcher.js |
| local-worker.sh must not merge stderr into stdout | Fixed in local-worker.sh |
| In-memory session pool doesn’t survive restarts | cliMirror.js now embeds session ID in messages + scans on fallback |
| Pino error serialization needs object form | Fixed in index.js + claudeReply.js |

## Commits (This Session)

### centralDiscord
| Commit | Description |
|—|—|
| `c86983c` | URL pre-fetch, retry detection, page-reader fallback, route classifier |
| `144b251` | context.md update |
| `d62f04c` | Pre-job repo sync |
| `de44ffe` | Pre-fetch timing logs |
| `b7e695f` | Interactive sessions: [WAITING_FOR_INPUT] |
| `0706525` | Fix WAITING_FOR_INPUT multiline regex |
| `b76c48b` | Fix fetchAttachments early return type |
| `130f95a` | Improve error serialization |
| `86625d7` | CLI mirror: streaming interactive sessions |
| `a1863a4` | Forward poll intervals through runClaudeRemote |
| `7d8ae06` | Fix raw NDJSON posted to Discord |
| `37ce053` | Fix CLI mirror session loss on restart |

### buying-assistant
| Commit | Description |
|—|—|
| `31f1f92` | Page-reader fallback in CLAUDE.md |
| `178493f` | Hard wax oil buying guide |

### agentGuidance
| Commit | Description |
|—|—|
| `902cf41` | Page-reader fallback as core principle |

## Open Items

1. **Test [WAITING_FOR_INPUT] end-to-end in #requests** — the fetchAttachments bug was blocking all tests. Now fixed, needs a clean test.
2. **CLI mirror streaming latency** — currently 1.5s poll. Could go to pipe-based for sub-second in v2.
3. **CLI mirror thread cleanup** — threads auto-archive after 24h but old sessions pile up. Consider a janitor sweep for CLI mirror threads.
4. **SKIP_DOMAINS tuning** — URL pre-fetch skips Discord/YouTube/GitHub. May need adjustment based on real usage.
5. **Buying guide: hard wax oil** — complete guide written from the originally-failed Gemini link. Best pick: General Finishes HWO 8oz ($26).

## Key Files

| File | Purpose |
|—|—|
| `centralDiscord/src/bot/cliMirror.js` | CLI mirror channel: streaming display, session handling, thread replies |
| `centralDiscord/src/bot/contextFetcher.js` | URL pre-fetching, bot output stripping |
| `centralDiscord/src/bot/executor.js` | Pre-job sync, configurable poll intervals, NDJSON safety, error serialization |
| `centralDiscord/src/bot/sessionPool.js` | Waiting-for-input state management |
| `centralDiscord/src/bot/claudeReply.js` | [WAITING_FOR_INPUT] detection and handling |
| `centralDiscord/src/bot/routeClassifier.js` | URL-dominated task classification |
| `centralDiscord/src/bot/index.js` | CLI mirror dispatch, waiting reply routing |
| `buying-assistant/CLAUDE.md` | Shared link handling instructions |
| `agentGuidance/agent.md` | Page-reader core principle |
| `~/local-worker.sh` | Fixed stderr contamination |

# Deep Closeout: Discord Quality Gap Fix — URL Pre-Fetching, Retry Detection, Page-Reader Fallback

**Date:** 2026-04-06
**Duration:** ~45 minutes
**Repos touched:** centralDiscord, buying-assistant, agentGuidance

## Context & Motivation

The user reported that a buying guide request dispatched through Discord failed to read a shared Gemini link (`gemini.google.com/share/1692639e3f4d`). The agent used WebFetch, which returned empty content (JS-rendered SPA), then proceeded without the context. The user’s original requirements (hard wax oil for a pine nightstand) were in that Gemini link, so the agent produced a generic USB-C hub guide from web search alone.

A retry attempt also failed: the user pasted the prior bot output back with a correction (“use the page-reader util”), but the agent saw the pasted output and said “I don’t see a specific task.”

The user also asked: “Why do my requests made through Discord seem to be dumber and less successful than requests made directly here?”

## Root Cause Analysis

1. **WebFetch silently fails on JS SPAs.** Gemini, React apps, modern forums return empty/broken HTML without JavaScript execution. The buying-assistant CLAUDE.md had no instructions about fallback tooling.

2. **No URL pre-fetching in the Discord pipeline.** Unlike the interactive CLI where the user can redirect on tool failure, Discord’s single-shot execution means the agent has to discover, attempt, fail, and recover from link-reading failures on its own. Most don’t.

3. **No retry detection.** When users paste prior bot output back with corrections, the bot passes the entire mess (bot output + user correction) as the query. The agent sees a completed report and gets confused.

4. **Structural quality gap (Discord vs CLI):**
– `planMode: ‘skip’` and `clarifyAmbiguous: ‘best-effort’` means no interactive recovery
– No feedback loop when tools fail mid-execution
– Prompt wrapping dilutes original user intent
– Route classifier sent URL-only messages to debate instead of direct execution

## Decisions Made

### Decision: Pre-fetch URLs server-side in contextFetcher
– **Alternatives considered:** (a) Only add page-reader instructions to agent directives, (b) Build a dedicated URL proxy service, (c) Pre-fetch only for specific channels
– **Rationale:** Server-side pre-fetch solves the problem for ALL agents without relying on each agent knowing how to use page-reader. The content is injected into the prompt before the agent even starts. Falls back gracefully if page-reader isn’t available.
– **Trade-offs:** Adds 3-20 seconds latency per URL. Max 3 URLs pre-fetched. 6000 char budget per URL.

### Decision: Belt-and-suspenders approach (pre-fetch + directive + CLAUDE.md)
– **Alternatives considered:** Only pre-fetching (single layer)
– **Rationale:** Pre-fetching handles URLs in the initial request, but agents discover new URLs during execution (e.g., following links in pre-fetched content). The directive and CLAUDE.md instructions cover those cases.
– **Trade-offs:** Slight prompt bloat from the directive instruction (~1 sentence).

### Decision: Bot output stripping at handler level, not buildRequestContext
– **Alternatives considered:** Strip in buildRequestContext (affects all channels)
– **Rationale:** Retry-with-paste is specific to channel watchers (buying-guides, job-search) where the same channel holds both the original request and bot responses. The #requests channel has session chaining for follow-ups. Stripping at handler level is more targeted.

### Decision: URL-dominated messages classify as TASK
– **Alternatives considered:** Keep fail-open to debate
– **Rationale:** Users dropping links expect action. A message that’s >40% URL with no debate signals (no “should we”, “vs”, “tradeoffs”) is almost certainly a task. Debate adds 30-60s of unnecessary overhead.

## What Was Built / Changed

### centralDiscord (commit c86983c)

**`src/bot/contextFetcher.js`** (184 lines added):
– `stripBotOutput(text)` — Detects “Actions Taken”, “Session: UUID”, “Summary, Recommendation:” patterns and extracts user intent from retry messages
– `extractExternalUrls(text)` — Finds URLs in text, filters out Discord/media/GitHub domains
– `prefetchUrl(url, readerPath)` — Runs page-reader CLI on a single URL with 20s timeout, stealth mode, 3s wait
– `prefetchExternalUrls(text)` — Orchestrates parallel pre-fetch of up to 3 URLs
– `getPageReaderPath()` — Resolves page-reader location (VM vs local WSL)
– Pre-fetch integrated into `buildRequestContext()` — runs after attachments, before reply context. Injects `— PRE-FETCHED URL CONTENT —` blocks into the prompt.

**`src/bot/index.js`**:
– Buying-guide handler now calls `stripBotOutput()` on the raw query
– If retry detected, adds `IMPORTANT: The user is retrying…` note to the prompt
– Imported `stripBotOutput` from contextFetcher

**`src/bot/executor.js`**:
– `EXECUTE_DIRECTIVE` now includes page-reader fallback instruction

**`src/bot/jobRequest.js`**:
– `buildDirective()` now appends page-reader fallback instruction to all structured directives

**`src/bot/routeClassifier.js`**:
– Added URL-dominated message detection (>40% URL chars, no debate signals = TASK)

### buying-assistant (commit 31f1f92)

**`CLAUDE.md`**:
– Added “Handling Shared Links” section between Phase 1 and Phase 2
– Instructions: try WebFetch first, fall back to page-reader, never skip shared links
– Explicit command syntax for page-reader with stealth mode

### agentGuidance (commit 902cf41)

**`agent.md`**:
– Added page-reader fallback as a Core Principle (line 29)
– All agents now pick up the rule, not just buying-assistant

### buying-assistant (commit 178493f)

**`guides/hard-wax-oil/recommendation.md`**:
– Full buying guide produced from the Gemini link content that originally failed
– Corrected Gemini’s oversized Rubio recommendation ($63 for 390ml -> $32 for 130ml)
– Found General Finishes HWO ($26) as best value, which Gemini missed entirely
– Verdict: GF HWO 8oz for best overall, Rubio 130ml for purist, Fiddes 250ml for budget

## Learnings Captured

| Learning | Where Saved |
|—|—|
| Page-reader fallback for JS SPAs | agentGuidance/agent.md (Core Principles), buying-assistant/CLAUDE.md, centralDiscord executor.js + jobRequest.js directives |
| URL pre-fetching for Discord pipeline | centralDiscord/src/bot/contextFetcher.js (implementation) |
| Bot output stripping for retries | centralDiscord/src/bot/contextFetcher.js + index.js |
| URL-dominated messages are tasks | centralDiscord/src/bot/routeClassifier.js |

## Open Items & Follow-ups

1. **Monitor page-reader latency in production.** Pre-fetching adds 3-20s per URL. If this becomes a bottleneck, consider caching or a dedicated pre-fetch worker.
2. **VM needs page-reader deployed.** The bot runs on the VM; `getPageReaderPath()` checks both `~/page-reader/` and `~/repos/page-reader/`. Verify the VM path exists and has Playwright dependencies installed.
3. **Other channel watchers.** Job-search handler could also benefit from bot-output stripping if users retry there.
4. **Test the full pipeline end-to-end.** Drop a Gemini link in #buying-guides after the restart and verify pre-fetching works.
5. **SKIP_DOMAINS list may need tuning.** Currently skips Discord, YouTube, Twitter, GitHub. May want to add or remove domains based on real usage patterns.

## Key Files

– `centralDiscord/src/bot/contextFetcher.js` — URL pre-fetch + bot output stripping (the core change)
– `centralDiscord/src/bot/executor.js:189` — EXECUTE_DIRECTIVE with page-reader fallback
– `centralDiscord/src/bot/routeClassifier.js` — URL-dominated task classification
– `centralDiscord/src/bot/index.js:430-443` — Buying-guide retry handling
– `buying-assistant/CLAUDE.md` — Shared link handling instructions
– `agentGuidance/agent.md:29` — Page-reader core principle
– `buying-assistant/guides/hard-wax-oil/recommendation.md` — The guide that should have been produced originally