🦔 PostHog provides open-source web & product analytics, session recording, feature flagging and A/B testing that you can self-host. Get started - free.
When a conversation has more than two messages, we output all previously generated schemas. In practice, it doesn't make sense because it doesn't provide any context but rather pollutes if previous steps have weirdness (excessive breakdowns or filters).
Changes
Append only the last schema to the schema generator step.
Add tests checking that the message history is correctly constructed.
Does this work well for both Cloud and self-hosted?
Problem
When a conversation has more than two messages, we output all previously generated schemas. In practice, it doesn't make sense because it doesn't provide any context but rather pollutes if previous steps have weirdness (excessive breakdowns or filters).
Changes
Does this work well for both Cloud and self-hosted?
No
How did you test this code?
Unit tests, manual testing.