Use Case
Knowledge bases are passive — they only surface knowledge when you search. Forest should push relevant nodes to you based on what you're working on, recent captures, and temporal patterns.
No competitor does this. Obsidian, Notion, Logseq all require you to remember to search. Forest should be the knowledge base that finds you.
Current Workaround
Manual search via forest search or asking Jack. No proactive suggestions.
Proposed Solution
- Jack watches context signals: current project, recent captures, time patterns
- Periodically surfaces related nodes via Telegram: "You captured X yesterday — here are 3 related nodes you might want to revisit"
- Could run on a schedule (morning briefing, end-of-day review) or event-triggered (new capture → show connections)
- Forest CLI could support
forest suggest or forest related <ref> as the underlying command
Context
- Forest node:
d653 (roadmap), 8e3e (competitive analysis)
- Competitive edge: no PKM tool does proactive surfacing
Use Case
Knowledge bases are passive — they only surface knowledge when you search. Forest should push relevant nodes to you based on what you're working on, recent captures, and temporal patterns.
No competitor does this. Obsidian, Notion, Logseq all require you to remember to search. Forest should be the knowledge base that finds you.
Current Workaround
Manual search via
forest searchor asking Jack. No proactive suggestions.Proposed Solution
forest suggestorforest related <ref>as the underlying commandContext
d653(roadmap),8e3e(competitive analysis)