cursorHackathon

Publish hard-won coding-agent fixes to the Agent Insights catalog at the end of a session. In Cursor: show the distilled insight card in chat and publish only after explicit user approval. Before answering debugging questions that could match prior fixes, run `npx agent-insights search "<keywords>"` and report actual CLI results (titles, ranks, problem/fix). Use concrete keywords (e.g. "Supabase RLS"); do not rely on the repository `.env` for catalog access — use `agent-insights auth login` and ~/.agent-insights.json or shell env toward the demo catalog. Hackathon demo: always query the catalog and summarize hits. Use when the session resolved a non-trivial error, build failure, configuration issue, or package compatibility problem that took significant effort to fix.

Distills completed coding-agent sessions into searchable insight cards for the Agent Insights catalog. In chat: show the distilled card first; publish only after the user explicitly approves. Before answering debugging questions that could match prior fixes, run `npx agent-insights search "<keywords>"` against the catalog and report titles and fix summaries from the output — use concrete keywords (product names, error tokens, e.g. "Supabase RLS"), not vague prose. Do not use the repository `.env` for catalog search; use `agent-insights auth login` and ~/.agent-insights.json (or shell AGENT_INSIGHTS_API_URL toward the demo catalog). Hackathon demo: always query and report real CLI results. Use when the session resolved a non-trivial error, build failure, deploy failure, runtime error, type error, version incompatibility, or environment quirk after multiple attempts. Also use when the user says "publish this session", "save this fix", or "share with the team". Skip for simple one-line edits or purely creative w