[wizard-ci-bot]

Automated wizard CI run

Source: wizard-pr
Trigger ID: 69eeefc
App: groq/node-chat
App directory: apps/groq/node-chat
Workbench branch: wizard-ci-69eeefc-groq-node-chat
Wizard branch: posthog/functional-a1-min
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-09-22T15:55:22.753Z
Duration: 213.4s

YARA Scanner

✓ 35 tool calls scanned, 0 violations detected

No violations: ✓ 35 clean scans

[wizard-ci-bot]

---

PR Evaluation Report

Summary

This PR instruments a Groq-powered Node.js chat CLI with PostHog AI observability using the @posthog/ai OpenAI-compatible wrapper. It swaps the OpenAI import for the PostHog wrapper, passes per-call identity (posthogDistinctId, posthogTraceId, , ) through every generation, and flushes events before exit. The implementation is clean and precisely matches the app's expected structure.

Files changed	Lines added	Lines removed
5	+80	-11

Confidence score: 4/5 👍

• No critical or medium issues found. The implementation correctly addresses every expected outcome from the README.

---

File changes

Filename	Score	Description
src/index.ts	5/5	Swaps OpenAI import for @posthog/ai/openai wrapper, initializes PostHog client at module scope, threads userId/threadId/traceId through complete(), sets `` and : 'groq' per call, adds `posthog.shutdown()` in finally block
package.json	5/5	Adds @posthog/ai and posthog-node dependencies alongside existing openai
.gitignore	5/5	Excludes .env from version control
.posthog-wizard-cache/.posthog-ai.json	5/5	Wizard cache metadata recording Groq provider and wrapper package
posthog-ai-observability-report.md	5/5	Thorough report documenting what was implemented and how to verify

---

App sanity check ✅

Criteria	Result	Description
App builds and runs	Yes	Report confirms tsc --noEmit passes
Preserves existing env vars & configs	Yes	GROQ_API_KEY and baseURL untouched; no pre-existing PostHog client
No syntax or type errors	Yes	TypeScript compilation successful
Correct imports/exports	Yes	@posthog/ai/openai and posthog-node are real, published modules
Minimal, focused changes	Yes	Only AI observability instrumentation; moderate() left untouched, control flow preserved
Pre-existing issues	None

Issues

• No .env.example: New environment variables POSTHOG_PROJECT_TOKEN and POSTHOG_HOST are documented in the report but no .env.example file was created. The base app also lacked one. [LOW]

Other completed criteria

• All changes are relevant to AI observability instrumentation
• Correct files modified (entry point, dependency manifest, gitignore)
• App's tool-dispatch loop and LLM request shape are unchanged — same messages construction, same model, same control flow
• Code follows existing codebase patterns (naming, structure, indentation)
• Dependency versions (@posthog/ai ^8.13.1, posthog-node ^5.52.5) are plausible and resolve to releases with the APIs used
• posthog.shutdown() called in finally block before CLI exit

---

PostHog implementation ✅

Criteria	Result	Description
PostHog SDKs installed	Yes	@posthog/ai and posthog-node added
PostHog client initialized	Yes	Module-scope singleton with env vars for token and host
capture()	Yes	Generations captured automatically via @posthog/ai/openai wrapper
identify()	N/A	CLI app; identity passed per-call via posthogDistinctId
Error tracking	Yes	enableExceptionAutocapture: true configured
Reverse proxy	N/A	Server-side Node.js CLI

Issues

No issues.

Other completed criteria

• Instrumentation initialized exactly once at module scope
• `` events will be produced by the @posthog/ai/openai wrapper for every `chat.completions.create` call
• Shared posthogTraceId (via randomUUID()) within each ask() turn groups all generations of a single request into one trace
• set using the app's own `Thread.threadId` (`thread_abc`), spelled with the exact key
• Session cardinality correct: one thread_abc shared across all traces
• Identity scope correct: per-call posthogDistinctId for a CLI app is fine
• No hand-authored spans; moderate() left as a plain guard function
• No pre-existing PostHog instrumentation to modify; additive only
• : 'groq' explicitly set, preventing OpenAI misattribution
• baseURL preserved pointing to api.groq.com

---

PostHog insights and events ✅

Filename	PostHog events	Description
src/index.ts	`` (×3 per run)	Three generations across two traces: first ask produces 1 generation (reply), second ask produces 2 generations (condense + reply). All grouped under session thread_abc, attributed to user_123, provider groq.

Issues

No issues.

Other completed criteria

• Events form the exact tree described in README: 1 session → 2 traces → (1 gen, 2 gens)
• Person attribution uses the app's stable user_123 from Thread.userId
• No fabricated structure: all traces/sessions derive from natural app concepts
• No credentials or secrets in event properties; and are appropriate metadata

---

Reviewed by wizard workbench PR evaluator