About
I prepare guides explaining internal procedures.
Badges
Forums
AI apps are no longer apps. They are attachments to surfaces you already use.
Last week, six AI products launched on Product Hunt that share one move. None of them ask users to open a new app. They embed into surfaces people already touch.
Hardware: Dune Keypad (46 upvotes) sits next to your keyboard with Claude integration. Video calls: Mina Meeting Assistant (47 upvotes). Text threads: folk (51 upvotes). Chat windows: Databox MCP (39 upvotes) plugs business data into Claude via Model Context Protocol. Mac autocomplete: Typeahead (22 upvotes).
The pattern is clear: shipping AI as a new app is the slow path. The fast path is grafting onto a surface the user already touches. The cost of building a standalone AI app dropped 90%+. The cost of getting it noticed did not. Surface integration sidesteps the noticing problem because the surface already has users.
The enterprise question isn’t capture. It’s control.
On a Tuesday, the first enterprise question is usually not can you capture AI code? It s who can see the records, how long do they live, and what happens when a policy blocks a change?
That s the part LineageLens is built for. Base gives you local capture. Lite gives a shared team record. Plus and Max move the data into a backend where auth, permissions, retention, and policy live next to the provenance records instead of around them.
The useful thing here is not another dashboard. It s a self-hosted record of prompt, model, tool, file, and outcome that engineering, security, and platform teams can actually govern on their own infrastructure.
I keep seeing AI governance tools start with visibility, then discover that the real enterprise questions are identity, retention, and review. If the record cannot be scoped, retained, and exported on your side, it is not really governable.
Just shipped v1.1.5: Why text-scraping AI code is a dead end (and what we built instead)
Thanks for the massive support on the last update! I ve been heads-down rewriting the core engine of LineageLens, and I'm stoked to share the v1.1.5 release.
When building an audit trail for AI-generated code, the default approach is to try and regex markdown blocks out of the LLM s text response. It is incredibly brittle. For this release, we ripped that out entirely.
The LineageLens proxy now natively parses the underlying structured protocols:
Anthropic s tool_use blocks (handling the streaming JSON assembly)
OpenAI s apply_patch DSL (via the newer Responses API)
Gemini s functionCall arrays