Building an AUTORESEARCH for Cribble to use local AI when the system is Idle.
lmk what are the things I should be including/have clear thoughts about:
I'm not doing web search for now, but will include it later.
--- How it works ---
Your notes/code/diffs/highlights/reading trails
↓
local deterministic analysis local LLM passes
↓
virtual research artifacts and insight cards
↓
you review, ask follow-ups, save/publish only if useful
---
for the first version, it should be local workspace research.
Examples:
> “these two notes are about the same topic but are not linked.”
> “this code module and this design note describe the same concept.”
> “this file changed recently, but the architecture summary still describes the old behavior.”
...now the question maybe, how is it different from Chat HUD?
> Chat is reactive: you ask, it answers.
> Autoresearch is proactive: Cribble notices useful relationships or open questions while idle.
But it should still be controlled:
> runs locally,
> waits for idle/thermal/battery-safe conditions,
> stores results as virtual artifacts first,
> cites source files/lines/commits,
> never edits your Markdown unless you explicitly save or approve.
For the product, autoresearch is the thing that makes Cribble feel like a second brain instead of just a Markdown reader with AI chat.
What else should i consider?