Fabian Samson57 downloadsLook up Japanese words locally and insert configurable vocabulary notes.
Kotoba Insert is an English-language Obsidian plugin for quickly inserting Japanese vocabulary from an offline JMdict-derived dictionary.
{word|reading} source is shown.The default template is:
{{word_with_furigana}} — {{english_definitions}}
Kotoba Insert renders {word|reading} itself, so no separate Furigana plugin is required. When the installed dictionary contains an exact JmdictFurigana match for the selected written form and reading, {{word_with_furigana}} uses aligned segments instead: {食|た}べる. It otherwise safely falls back to {食べる|たべる}.
Configure the AI API base URL, model, API-key secret, and prompt folder in Settings → Kotoba Insert → AI lookup. The default base URL is OpenAI's https://api.openai.com/v1 and the default model is gpt-5.6-luna, but any provider compatible with the Chat Completions API can be configured.
API keys are selected by name through Obsidian's SecretStorage and are not saved in Kotoba Insert's plugin data. Create the default prompt in the configured kotoba-insert-prompt folder, or add your own Markdown prompt files. Choose a prompt for each AI lookup. The existing dictionary command opens the Dictionary tab; Kotoba Insert: Ask AI and insert Japanese study note opens the AI tab directly.
word, reading, word_with_furigana, english_definitions, english_definition_1, part_of_speech, alternate_forms, priority, commonness, cross_references, antonyms, field_tags, usage_tags, and sense_notes.
Multi-sense values are semicolon-separated. An absent optional field becomes an empty string.
Dictionary lookups are local after installation. AI lookups send the entered term and selected prompt to the AI provider configured by the user; they can incur charges. The plugin does not send note content. See PRIVACY.md and NOTICE.md.
If Kotoba Insert is useful to you, you can support its development through Buy Me a Coffee.
npm install
npm run dev
For a production bundle, run npm run build.
The release workflow runs when you push a Git tag. Before tagging, update manifest.json and versions.json, commit the version change, and verify npm run check, npm test, and npm run build. The tag must exactly match manifest.json (for example, 0.1.0, not v0.1.0). The workflow creates a GitHub release with main.js, manifest.json, and styles.css attached.