PostHog agent platform
"Live" demo
Dylan Martin
AI product engineering lead, PostHog
Describe an agent. Ship it live in minutes.
❯ Create and deploy a live agent called repo-explorer-demo: an assistant that answers questions about any public GitHub repo's architecture using the DeepWiki remote MCP server (https://mcp.deepwiki.com/mcp — public, no auth).
An agent is a versioned spec
Authors
MCP · console · Claude Code
Triggers
chat · webhook · Slack · cron · MCP
Control plane — author & promote
Django REST
agent-janitor
bundle CRUD · freeze · validate
Data plane — run
agent-ingress
auth · route slug → live revision
agent-runner
model loop · tool dispatch
applications · revisions (spec + bundle)
bundle store · S3
session queue
draft → freeze → promote
Authors
MCP · console · Claude Code
Triggers
chat · webhook · Slack · cron · MCP
Control plane — author & promote
Django REST
agent-janitor
bundle CRUD · freeze · validate
Data plane — run
agent-ingress
auth · route slug → live revision
agent-runner
model loop · tool dispatch
applications · revisions (spec + bundle)
bundle store · S3
session queue
One agent, five front doors
Authors
MCP · console · Claude Code
Triggers
chat · webhook · Slack · cron · MCP
Control plane — author & promote
Django REST
agent-janitor
bundle CRUD · freeze · validate
Data plane — run
agent-ingress
auth · route slug → live revision
agent-runner
model loop · tool dispatch
tool calls can be gated behind human approval
applications · revisions (spec + bundle)
bundle store · S3
session queue
Ask it anything with a repo.
> how does posthog/posthog handle session replay ingestion?
⚙ deepwiki · ask_question(repo: "posthog/posthog", ...)
live demo →
Spec in. Agent out.
Built live from a single prompt
Versioned by default; rolling back is one command
Reachable from chat, Slack, webhooks, cron, and MCP