Debugs why session recordings aren't appearing in the local dev environment.
$ npx skills add PostHog/posthog-foss --skill debugging-local-replay -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog-foss debugging-local-replay --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/PostHog/posthog-foss.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/debugging-local-replay .claude/skills/debugging-local-replay && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "debugging-local-replay" agent skill from https://github.com/PostHog/posthog-foss/tree/master/.agents/skills/debugging-local-replay into .claude/skills/debugging-local-replay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-local-replay", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/PostHog/posthog-foss/tree/master/.agents/skills/debugging-local-replayType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add PostHog/posthog-foss --skill debugging-local-replay -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog-foss debugging-local-replay --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog-foss.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/debugging-local-replay .agents/skills/debugging-local-replay && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "debugging-local-replay" agent skill from https://github.com/PostHog/posthog-foss/tree/master/.agents/skills/debugging-local-replay into .agents/skills/debugging-local-replay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-local-replay", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PostHog/posthog-foss --skill debugging-local-replay -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog-foss debugging-local-replay --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog-foss.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/debugging-local-replay .cursor/skills/debugging-local-replay && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "debugging-local-replay" agent skill from https://github.com/PostHog/posthog-foss/tree/master/.agents/skills/debugging-local-replay into .cursor/skills/debugging-local-replay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-local-replay", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/PostHog/posthog-foss.git --path .agents/skills/debugging-local-replay--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add PostHog/posthog-foss --skill debugging-local-replay -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog-foss debugging-local-replay --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog-foss.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/debugging-local-replay .gemini/skills/debugging-local-replay && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "debugging-local-replay" agent skill from https://github.com/PostHog/posthog-foss/tree/master/.agents/skills/debugging-local-replay into .gemini/skills/debugging-local-replay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-local-replay", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install PostHog/posthog-foss debugging-local-replayInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add PostHog/posthog-foss --skill debugging-local-replay -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/PostHog/posthog-foss.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/debugging-local-replay .github/skills/debugging-local-replay && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "debugging-local-replay" agent skill from https://github.com/PostHog/posthog-foss/tree/master/.agents/skills/debugging-local-replay into .github/skills/debugging-local-replay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-local-replay", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PostHog/posthog-foss --skill debugging-local-replay -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install PostHog/posthog-foss debugging-local-replay --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog-foss.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/debugging-local-replay .opencode/skills/debugging-local-replay && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "debugging-local-replay" agent skill from https://github.com/PostHog/posthog-foss/tree/master/.agents/skills/debugging-local-replay into .opencode/skills/debugging-local-replay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-local-replay", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
debugging-local-replayDebugs why session recordings aren't appearing in the local dev environment.
Debugging Local Replay is an agent skill from PostHog/posthog-foss, published by the product's own GitHub organization. Debugs why session recordings aren't appearing in the local dev environment. Use when a developer reports that local replay ingestion isn't working, recordings aren't showing up despite /s calls, or the replay pipeline seems broken after hogli start. Covers the full local pipeline: SDK capture, Caddy proxy, capture-replay (Rust), Kafka, ingestion-sessionreplay (Node), recording-api (Node), SeaweedFS, and common failure modes like orphaned processes, stuck phrocs workers, and trigger misconfiguration.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/common-failures.md`).
It sits in Backend & APIs, covering Event-driven systems and Debugging. It works with Apache Kafka and Rust. The repository describes itself as: PostHog FOSS is a read-only mirror of PostHog, with all proprietary code removed. NOTE: This repo is synced automatically from the main PostHog repo. Please raise any issues and… The licence is MIT.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 2c48221. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
pnpmdockerclickhousecurltsxFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use pnpm, docker and curl, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Debugging Local Replay loads about 1.9k tokens when it runs, and up to ~3.3k if it reads all its reference files. Until then it costs about 132 tokens; SKILL.md has 748 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from PostHog/posthog-foss at commit 2c48221, republished under its MIT licence (© PostHog). 748 words, ~1,874 tokens.
.claude/skills/debugging-local-replay/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.When a developer says "local replay isn't working" or "recordings aren't showing up", work through these layers in order. The local replay pipeline has several moving parts and failures are usually silent.
| Symptom | Likely cause |
|---|---|
No /s calls in Network tab | SDK not recording — triggers, settings, or recorder script issue (Step 1) |
/s calls return 200 but no recordings in list | Ingestion pipeline broken — capture-replay, Kafka, or ingestion-sessionreplay (Steps 2-3) |
| Recordings listed but playback stuck on "Buffering..." | recording-api (port 6741) not running (Step 2) |
| Recorder script MIME type or CORS error in console | Frontend build stale — need pnpm build + pnpm copy-scripts (Step 1) |
Browser SDK → /s endpoint (Caddy proxy :8000)
→ capture-replay (Rust, :3306)
→ Kafka (session_recording_snapshot_item_events topic)
→ ingestion-sessionreplay (Node, :6740, PLUGIN_SERVER_MODE=recordings-blob-ingestion-v2)
→ SeaweedFS (blob storage, :8333)
→ recording-api (Node, :6741, PLUGIN_SERVER_MODE=recording-api)
→ FrontendA break at any point in this chain means no recordings in the UI. The diagnostic approach is to find where the chain breaks.
Ask the developer to open browser DevTools Network tab and filter for /s.
If no /s calls at all:
The SDK isn't attempting to send recording data. Investigate client-side causes:
$replay_sample_rate is < 1.0, sessions may be sampled out.session_recording must not be explicitly disabled.http://localhost:8000 (or wherever
the local Caddy proxy is running)./s endpoint.MIME type ('text/html') is not executable for posthog-recorder.js or a CORS error for
lazy-recorder.js. This means Django is serving an HTML page (usually the login redirect)
instead of the JS file — the static recorder scripts are stale or missing.
See recorder script build failure.If /s calls are happening with 200 responses:
The SDK is recording and capture is receiving data. The break is downstream — proceed to Step 2.
If /s calls are returning errors (4xx/5xx):
The capture service may be down or misconfigured. Check capture-replay in phrocs.
Check that these phrocs processes are running and healthy.
A "running" process that never produced output after tsx watch src/index.ts is effectively dead.
| Process | Port | What it does |
|---|---|---|
capture-replay | 3306 | Rust service receiving /s, writes to Kafka |
ingestion-sessionreplay | 6740 | Node consumer processing recordings from Kafka |
recording-api | 6741 | Node service serving replay data to the frontend |
Verify with:
lsof -nP -i :3306 -i :6740 -i :6741If ports are not listening: The processes haven't started or are stuck. See common failures.
If ports are listening: The pipeline processes are running. Proceed to Step 3.
These Docker containers must be running and healthy:
| Container | Purpose |
|---|---|
posthog-kafka-1 | Message bus for recording events |
posthog-db-1 | Postgres for metadata |
posthog-redis7-1 | Redis for state |
posthog-clickhouse-1 | ClickHouse for session data |
seaweedfs-main | Blob storage for recording data |
Check with:
docker ps --format "table {{.Names}}\t{{.Status}}" | grep -E "kafka|db|redis7|clickhouse|seaweed"All should show (healthy) except seaweedfs which doesn't have a health check.
If seaweedfs-main is missing, the replay Docker profile may not be active —
check the docker-compose phrocs process output for --profile replay.
If capture-replay is running and receiving /s calls, data should land on the
session_recording_snapshot_item_events Kafka topic. Check the Kafka UI at
http://localhost:8080 (if the debug_tools intent is enabled) or use kcat:
kcat -b localhost:9092 -t session_recording_snapshot_item_events -C -c 5 -eIf the topic is empty or doesn't exist: capture-replay isn't writing to Kafka. Check its phrocs logs for Kafka connection errors.
If data is on the topic but recordings don't appear: ingestion-sessionreplay isn't consuming. Check if it's stuck, crashed, or if an orphaned process is holding the consumer group (see common failures).
Ingestion writes recording blobs to SeaweedFS. Verify it's accessible:
curl -s http://localhost:8333/ | head -5The SESSION_RECORDING_V2_S3_ENDPOINT env var must be set correctly.
In bin/start, this defaults to http://seaweedfs:8333 (the Docker hostname).
Host processes resolve this via Docker networking.
See common failures for detailed diagnosis of:
bin/wait-for-docker© PostHog, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file (references) in .agents/skills/debugging-local-replay of PostHog/posthog-foss.
Open the folder on GitHubat commit 2c48221
Debugging Local Replay next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Debugging Local Replay this skillPostHog/posthog-foss | 721 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Flowfile Frame And CodegenEdwardvaneechoud/Flowfile | 370 | — | ~12k | Automated safety check: Pass | MIT | |
| Windmill Trigger Type Checklistwindmill-labs/windmill | 18k | — | ~4.7k | Automated safety check: Pass | Custom licence | |
| Opensource Guide Coachcalf-ai/calfkit-sdk | 149 | 1 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| 123 Java Design Patternsjabrena/plinth | 445 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| MQTTX CLIemqx/MQTTX | 5.1k | — | ~1.9k | Automated safety check: Pass | Apache-2.0 |
Edwardvaneechoud/Flowfile
Deep dive into flowfileframe — the Polars-LazyFrame-shaped Python API that builds an in-process flowfilecore FlowGraph as a side effect of every method call — covering the FlowFrame/Expr internals…
windmill-labs/windmill
Checklist of every backend, frontend, CLI and capture change needed to add a new TriggerCrud-based trigger type, such as Azure, GCP or Kafka, to Windmill.
calf-ai/calfkit-sdk
A skill your agent uses when a user wants guidance on starting, contributing to, growing, governing, funding, securing, or sustaining an open source project, or asks about contributor onboarding…
jabrena/plinth
A skill your agent uses when you need to select, review, or implement Java design and integration patterns — including classic Java design patterns, REST API patterns, Kafka and event-driven…
emqx/MQTTX
Operates the `mqttx` command line client to connect, publish, subscribe, benchmark and simulate data against an MQTT broker, with TLS and MQTT 5 support.
FoundatioFx/Foundatio
A skill your agent uses when working with Foundatio infrastructure abstractions for .NET -- caching, queuing, messaging, file storage, distributed locking, or background jobs.
PostHog/posthog-foss
Author useful, low-noise log alerts on services in a PostHog project.
PostHog/posthog-foss
Operating procedure for the conflict-autoresolver agent: sweep open PostHog/posthog PRs that conflict with master, resolve the trivial conflicts (generated artifacts deterministically, source…
PostHog/posthog-foss
Help users debug PostHog Error Tracking stack-trace symbolication for any supported platform — JavaScript/TypeScript web, React Native (Hermes), Android (Proguard / R8), or iOS / macOS (dSYM).
PostHog/posthog-foss
Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP.
PostHog/posthog-foss
Debug and inspect LLM/AI agent traces using PostHog's MCP tools.
PostHog/posthog-foss
Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.
Works with
Categories
Debugs why session recordings aren't appearing in the local dev environment. Debugging Local Replay is an agent skill from PostHog/posthog-foss, published by the product's own GitHub organization. Debugs why session recordings aren't appearing in the local dev environment.
Debugging Local Replay fits situations like: A developer reports that local replay ingestion isnt working; recordings arent showing up despite /s calls; the replay pipeline seems broken after hogli start; misconfiguration.
Run `npx skills add PostHog/posthog-foss --skill debugging-local-replay -a claude-code`. Or copy the skill folder (.agents/skills/debugging-local-replay in PostHog/posthog-foss) into .claude/skills/debugging-local-replay in your project. Claude Code loads it when a task matches its description.
Run `npx skills add PostHog/posthog-foss --skill debugging-local-replay -a codex`. Or copy the skill folder (.agents/skills/debugging-local-replay in PostHog/posthog-foss) into .agents/skills/debugging-local-replay in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add PostHog/posthog-foss --skill debugging-local-replay -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debugging-local-replay, .gemini/skills/debugging-local-replay, .github/skills/debugging-local-replay and .opencode/skills/debugging-local-replay in your project.
Going by SKILL.md and its folder, Debugging Local Replay needs the command-line tools its instructions call (pnpm, docker, clickhouse, curl and tsx). Our summary lists: Docker.
SKILL.md contains no URLs. Its commands use docker and curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Debugging Local Replay is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.9k tokens (SKILL.md is roughly 7.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.5k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Debugging Local Replay: Flowfile Frame And Codegen (Edwardvaneechoud/Flowfile, 370 stars), Windmill Trigger Type Checklist (windmill-labs/windmill, 18k stars), Opensource Guide Coach (calf-ai/calfkit-sdk, 149 stars) and 123 Java Design Patterns (jabrena/plinth, 445 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog-foss, which has 721 GitHub stars. The repository holds 213 skills in this directory. The repository was last updated on October 7, 2026.
Source: PostHog/posthog-foss on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
