PostHog / PostHog/posthog

feature request (posthog-ai): add a tool to draft a github issue (feature request or bug) from conversation context

Open
#59,449 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement team/posthog-ai
Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
6h 51m
Merged PRs (30d)
232

Description

Is your feature request related to a problem?

PostHog AI users encounter rough edges (missing features, unexpected behavior, etc.) during conversations with the assistant but have no in-flow way to capture them as a GitHub issue. Today the only path is to navigate to the Share feedback panel and open the GitHub feature request form manually, which loses the conversation context that made the issue obvious in the first place.

Describe the solution you'd like

Add a PostHog AI tool that drafts a feature-request or bug-report body from the current conversation context, then opens a pre-filled github.com/PostHog/posthog/issues/new URL the user can review and submit. The tool should not file issues directly via the GitHub API in a first version, to avoid spam and abuse concerns: the user submitting under their own GitHub identity is the right access control.

Important nuance: PostHog AI often categorizes normal product behavior as "bugs". The tool prompt and UX should bias toward feature requests and confirm with the user before producing a body, so it doesn't turn into a noise source for the team.

Describe alternatives you've considered

The existing Share feedback side panel already links to the GitHub feature request URL but doesn't carry over conversation context: https://github.com/PostHog/posthog/blob/master/frontend/src/layout/navigation-3000/sidepanel/panels/support/SidePanelSupport.tsx

A more ambitious API-submitting tool was considered but rejected for v1 due to spam and abuse concerns.

Additional context

PostHog AI tools currently number 49 (see AssistantTool enum at https://github.com/PostHog/posthog/blob/master/posthog/schema.py). None of them file issues. MaxTool base class for new tools: https://github.com/PostHog/posthog/blob/master/ee/hogai/tool.py

Reported by a Technical Support Engineer working with customer feedback who saw the value of capturing in-flow rough edges with their context preserved.

Debug info

  • PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables]
  • PostHog Hobby self-hosted with docker compose, version/commit: [please provide]
  • PostHog self-hosted with Kubernetes (deprecated, see Sunsetting Kubernetes support), version/commit: [please provide]

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the AssistantTool enum in posthog/schema.py and the MaxTool base class in ee/hogai/tool.py; review SidePanelSupport.tsx for the existing feedback URL flow. Define the tool and UX behavior around conversation context, confirmation, and feature-request bias, then verify that it produces a reviewable pre-filled GitHub issue URL without submitting through the API.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, python, typescript
Domain
ai, backend, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.