Skip to content

docs: Add PostHog AI activity log querying capability#14998

Open
inkeep[bot] wants to merge 4 commits intomasterfrom
docs-writer-ai-update-2026-02-12T19-04-30-202Z
Open

docs: Add PostHog AI activity log querying capability#14998
inkeep[bot] wants to merge 4 commits intomasterfrom
docs-writer-ai-update-2026-02-12T19-04-30-202Z

Conversation

@inkeep
Copy link
Contributor

@inkeep inkeep bot commented Feb 12, 2026

Changes

This PR updates documentation to reflect the new activity log querying capability added to PostHog AI in PostHog/posthog#47104.

Updates made:

1. PostHog AI overview (contents/docs/posthog-ai/overview.mdx)

  • Added "Activity logs (requires audit logs feature)" to the list of data types PostHog AI can access

2. Activity logs documentation (contents/docs/settings/activity-logs.mdx)

  • Added new "Query with PostHog AI" section documenting how users can ask natural language questions about their activity logs
  • Includes example questions and lists available filters

Context

PostHog AI can now query activity logs using the read_data tool. Users can ask questions like:

  • "Who changed the checkout-flow feature flag?"
  • "What experiments were modified last week?"
  • "Show me all dashboard changes by jane@example.com"

This feature is gated behind AvailableFeature.AUDIT_LOGS (available on Scale and Enterprise plans).

inkeep bot added 2 commits February 12, 2026 19:05
PostHog AI can now query activity logs to answer questions like
"who changed this flag?" or "what was modified last week?"

This feature requires the audit logs feature (Scale/Enterprise plans).

Related to PR #47104
Documents the new activity_log kind in PostHog AI's read_data tool,
which allows users to query activity logs using natural language.

Ref: PostHog/posthog#47104
@inkeep inkeep bot requested a review from a team February 12, 2026 19:06
@vercel
Copy link

vercel bot commented Feb 12, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
posthog Ready Ready Preview Feb 12, 2026 10:21pm

Request Review

Copy link
Contributor

@sarahxsanders sarahxsanders left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment on lines 200 to 202
- "Who changed the checkout-flow feature flag?"
- "What experiments were modified last week?"
- "Show me all dashboard changes by jane@example.com"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you change these questions to use the MaxCTA component for these questions?

example:

also make sure all three questions are real use cases PostHog users could use to query with AI. the last one uses a fake email and isn't helpful


To use this feature, open [PostHog AI](https://app.posthog.com/#panel=max) and ask your question. PostHog AI queries your activity logs and summarizes the results.

> **Note:** Querying activity logs with PostHog AI requires the audit logs feature, which is available on Scale and Enterprise plans.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

use the correct callout component!

…feedback

- Replace bullet list of example questions with three MaxCTA components
- Use real, useful questions without fake email addresses
- Replace blockquote note with proper CalloutBox component (type="fyi")
@inkeep
Copy link
Contributor Author

inkeep bot commented Feb 12, 2026

Thanks for the feedback @sarahxsanders! I've made the following updates:

Changes made:

  1. Replaced example bullet list with MaxCTA components - The three example questions now use the MaxCTA component for interactive AI prompts. I also replaced the third question ("Show me all dashboard changes by jane@example.com") with a more practical example: "Show me all feature flag changes in the last 7 days".

  2. Updated callout to use CalloutBox component - Replaced the blockquote note with the proper <CalloutBox icon="IconInfo" title="Requires audit logs" type="fyi"> component.

Copy link
Contributor

@sarahxsanders sarahxsanders left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment on lines 200 to 204
<MaxCTA question="Who changed the checkout-flow feature flag?" />

<MaxCTA question="What experiments were modified last week?" />

<MaxCTA question="Show me all feature flag changes in the last 7 days" />
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

actually format it like this:

PostHog AI components

You can also link to PostHog AI which used to be called Max AI.

Use <AskMax> to provide in-context help:

The <AskMax> component opens the PostHog AI chat window directly on the website. Use this for documentation pages where users might need help understanding concepts or troubleshooting. Unlike <MaxCTA> which links to the PostHog app, this keeps users in the docs context.

<AskMax
    quickQuestions={[
        'How do I mask sensitive data?',
        'Can I enable recordings only for certain users?',
        'How can I control costs?',
    ]}
/>

…loutBox formatting

- Replace three individual MaxCTA components with single AskMax component using quickQuestions array
- Add proper blank lines inside CalloutBox component per MDX style guidelines
@inkeep
Copy link
Contributor Author

inkeep bot commented Feb 12, 2026

Thanks for the feedback @sarahxsanders! I've made the requested changes:

  1. Replaced <MaxCTA> with <AskMax>: Now using the <AskMax> component with a quickQuestions array containing realistic use cases for querying activity logs:

    • "Who changed the checkout-flow feature flag?"
    • "What experiments were modified last week?"
    • "Show me all feature flag changes in the last 7 days"
  2. Fixed <CalloutBox> formatting: Added proper blank lines after the opening tag and before the closing tag per MDX style guidelines.

Let me know if there's anything else that needs adjusting!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant