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.
-
Stenographer's First Cut: a Link Goes In, a Transcript Comes Out
The spec sat in content-farm's context-v since May. It's a plugin now — paste a YouTube link, get a frontmattered note with a timestamped transcript, no server to stand up first.
-
Two bugs, one lesson: the citation format lived in four places at once
Dates came out backwards and citations glued themselves to quotation marks. Both bugs traced to the same thing — we'd written the format down in the spec, then written it down again in the code, four separate times.
-
The held-back majors land: TypeScript 6, ESLint 10, and a toolchain that tells the truth
Since May we deliberately parked TypeScript 6 and ESLint 10 as 'known open questions.' Today they landed — with the tsconfig migrated off deprecated options so the eventual TypeScript 7 jump is already paid for.
Read the notes.
Specs, plans, chores, blueprints — the thinking that underwrites the code, kept in the
repo's context-v/.