image-gin
Beta
Community Plugin
Generate, search, and place AI images without leaving Obsidian.
A pseudomonorepo of Obsidian plugins · The Lossless Group
A small farm of writing tools.
Nine Obsidian plugins, one vault, working in chorus. AI-assisted drafting, citations, image generation, search-augmented enhancement, and the connective tissue to keep them all in step.
We invite contributors and idea-generators and complainers. At this point, we're vibe-coding (agentic-engineering) all this, too. Submit ideas or look for contributions to make on our project board or make discussions, reach out!
- 10 Plugins in the farm
- 1 Vault, many surfaces
- ∞ Workflows downstream
What's growing
The plugins
Each plugin is its own repo, included here as a git submodule. Cards link to the source.
Cards with the
Community Plugin pill are live in Obsidian's directory — install them from
inside Obsidian via Settings → Community Plugins → Browse. The others are
either dev-only (run from a symlinked checkout) or submitted-but-not-yet-accepted.
Standing on shoulders
Inspirational plugins by others
Vendored as study references — community plugins that informed how the farm's plugins are shaped. Cards link to the upstream source.
Why this exists
A pseudomonorepo, on purpose.
Not a monorepo. Not loose repos. A parent that hosts cross-cutting context so the plugins stay aware of each other.
Built where writing happens.
Obsidian is where the drafts live. Tooling that asks you to leave the editor loses the moment. Every plugin here lands inside the vault, inside the modal, inside the flow.
Many small tools, one shared shape.
A unified wide-modal pattern across plugins. Same header, same submit gesture (Cmd/Ctrl+Enter), same temperature slider when temperature is a thing. Fewer surprises, more reuse.
AI as ingredient, not destination.
Local models via LM Studio. Hosted models via Perplexica, Recraft, Ideogram. The plugin asks; you decide. The note remains the source of truth.
In public, on purpose.
Specs, plans, and chores live in the repo's context-v/. The work and the writing are the same activity. This splash page is one of those artifacts.
Latest from the field
Recent ship notes
What we shipped lately, with links back to the spec or blueprint that led to it.
-
Twelve repos back at parity — and the release the marketplace couldn't see
metafetch 0.1.7 was tagged, released, and attested. Obsidian's directory still read 0.1.6, because it reads the default branch and the default branch was six commits behind. Every repo in the family is now development = main = master.
-
A cosmetic quoting bug was sitting on top of silent data loss
Metafetch was wrapping every tag in quotes. Annoying, but harmless. Chasing it turned up two bugs underneath that weren't harmless at all — one of which was quietly destroying inline tag arrays on every fetch.
-
Metafetch reads papers now — any URL property, and all six authors
A note about an arXiv paper keys its link as `arxiv:`, not `url:` — so metafetch couldn't see it at all. Now it shows you every URL in your frontmatter and lets you pick, comes back with the whole author list when the source is scholarly, and can stamp a stable code so the note is referenceable anywhere.
Read the notes.
Specs, plans, chores, blueprints — the thinking that underwrites the code, kept in the
repo's context-v/.