Slack-compatible ingestion
Stores the raw payload and replies in ~10 ms; a queue inside SQLite itself processes it afterwards.
Lets you adopt it without touching application code or slowing down the sender.
A production error archive, read by AI with your system's context.
An early-stage project. The idea: the error that today becomes a Slack message and scrolls away gets stored, grouped and searchable by meaning — and the AI analyses each group with the business context you wrote about the system. The core flow already works end to end; what's left is maturing operations and widening the set of recognised stacks.
A regular tracker says "QueryException on line 88". log-ai aims to say "the checkout queue retry reached an order that was already cancelled". Adoption is a one-line change: the endpoint accepts the same Slack webhook the app already uses. The AI is the last resort — structured payloads and regex handle almost everything for free, and only the unrecognised case reaches the model.
Captured from the running product.




Stores the raw payload and replies in ~10 ms; a queue inside SQLite itself processes it afterwards.
Lets you adopt it without touching application code or slowing down the sender.
Pydantic schema, then regex per known stack, and only last an LLM extracting into the same schema.
Keeps AI cost to the rare case — and records which rung resolved each event.
A fingerprint that ignores line numbers, local embeddings and vector search inside the same SQLite file.
Lets "payment problem" find a GatewayTimeoutException without the word appearing.
Free-text notes about the system, read by the AI, and a read-only MCP server for Claude Code and Cursor.
Lets you ask "why is checkout failing?" from inside the editor.