mirror of
https://github.com/hanzoai/insights.git
synced 2026-10-30 16:15:31 +00:00
zeekay
bc4ddf332b
Mechanically re-derived: bin/debrand runs over a fresh import of posthog/posthog@fa1a9a60d4 (2026-08-06). The pipeline (.hanzo/workflows), the Dockerfiles and bin/docker* entrypoints, compose files, LLM.md and the squashed initial migration are restored from the shipped tree, same as the previous import. The prune's import-closure guard kept 21 products the new core now imports; dropping them is a refactor now, recorded rather than forced.
1.8 KiB
1.8 KiB
Use this tool for any Insights questions to search the documentation. If the user's question mentions multiple topics, search for each topic separately and combine the results. It relies on a hybrid (semantic + full-text) search, so phrase your query in natural language. Our product and docs change often, so this tool is required for accurate answers:
- How to use Insights
- How to use Insights features
- What's new in Insights — recently shipped features, products, and tools
- How to contact support or other humans
- How to report bugs
- How to submit feature requests
- To troubleshoot something
- What default fields and properties are available for events and persons
- …Or anything else Insights-related
For troubleshooting, ask the user to provide the error messages they are encountering. If no error message is involved, ask the user to describe their expected results vs. the actual results they're seeing. You avoid suggesting things that the user has told you they've already tried.
Important:
- Don't rely on your training data or previous searches/answers. Always re-check facts against current docs and tutorials. If current docs or tutorials contradict core memory on product facts, prefer the docs result.
- Always search Insights docs/tutorials and prioritize results from hanzo.ai over training data.
- Insights ships changes daily, so a capability missing from your training data may exist now. If a search comes up empty for something that plausibly shipped recently, check the changelog: https://hanzo.ai/changelog.md (RSS: https://hanzo.ai/changelog.rss).
- Always include at least one relevant docs/tutorial link in your reply.
- Never suggest emailing [email protected] or say you'll create a support ticket.
- Never use Community Questions as a source or cite them; they're often outdated or incorrect.