PostHog.AI - general availability

Open
#224 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
csharp

Research direction

Start by reading src/PostHog.AI and compare its raw OpenAI HTTP handling with the Python and Node SDK approaches. Review Microsoft.Extensions.AI and the OpenAI Responses API mentioned in the issue. The issue does not define a settled implementation or acceptance criteria, so completion depends on first deciding the long-term abstraction and required provider coverage.

Written by the indexing model from the issue text.

Description

enhancement team/llm-analytics
Description

https://github.com/PostHog/posthog-dotnet/tree/main/src/PostHog.AI
this is in an experimental state and was donated by the community

we are not convinced the approach is the right long-term solution. It hooks the raw HTTP calls to OpenAI and parses the JSON instead of wrapping the client like our Python/Node SDKs do. That seems brittle. Its OpenAI-only, tags Azure as “openai”, grabs nothing from OpenAI’s new Responses API.

it seems the .NET community is consolidating on Microsoft.Extensions.AI for this sort of thing. Its a standard set of abstractions

Before going GA, we might want to address those issues

Dominant language
C#
Stars
47
Forks
23
Avg merge
2d 12h
Merged PRs (30d)
30

Getting set up

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.

More from PostHog/posthog-dotnet

All issues in PostHog/posthog-dotnet

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.