Item detail
github.com

Ar9av/obsidian-wiki

Ar9av/obsidian-wiki is a agent memory framework in RepoRadar's Developer Tools section, holding Gold tier and a 'try now' verdict. Its strongest signal is workflow potential, scored 10.0 out of 10.

Score8.5
Popularity1.0
Riskconditional
TierGold
Score breakdown
Usefulness9.0
Novelty8.0
Momentum8.0
Maturity6.6
Open-source/build8.4
Evidence7.2
Workflow potential10.0
Setup ease6.4

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for builders who want agent memory to live in owned markdown files instead of disappearing into chat scrollback or a hosted memory layer.

Who should use it

Developers who already keep notes or project context in ObsidianTeams that want agent memory to survive model, tool, and session changesBuilders testing Karpathy-style LLM wiki workflows on real reposOperators who want a human-readable memory layer instead of another hosted dashboard

Who should skip it

Consider Ar9av/obsidian-wiki lower priority if you already have a working solution in this category.

About this signal

Ar9av/obsidian-wiki is tracked by RepoRadar as a agent memory framework in the Developer Tools section. It was first seen on 2026-06-30 and last updated on 2026-06-30. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Ar9av/obsidian-wiki leads on workflow potential (10.0) and practical usefulness (9.0); its lowest signal is setup ease (6.4), so factor that in before investing setup time. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.

How this item is evaluated

RepoRadar assigned Ar9av/obsidian-wiki a composite score of 8.5 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.

Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.

Risk explanation

It can ingest transcripts, plans, and research notes into a long-lived vault, so scrub secrets before aiming it at sensitive sessions; It writes and reorganizes markdown inside your Obsidian vault, so test the workflow on a non-critical notebook before making it part of your main project memory.

Evidence links
Closest alternatives / related signals
obsidianmemoryknowledge-baseclaude-codecodexdeveloper-toolsmit