AI Translate

AI Translate is a multi-platform toolkit for dictionary lookup and selected-text translation. It provides extensions for Chrome, Edge, Firefox, VS Code, and Obsidian, with shared vocabulary request behavior across all supported platforms.

Simplified Chinese | Documentation index | Architecture | VS Code documentation | Obsidian documentation | Releases

Platform Overview

Platform	Primary workflow	Package
Chrome	Translate selected words, sentences, and paragraphs on web pages.	dist/<version>/AI-Translate-chrome.zip
Edge	Uses the Chrome feature set with Edge-compatible packaging and TTS fallback.	dist/<version>/AI-Translate-edge.zip
Firefox	Uses the same translation workflow through a Manifest V2-compatible package.	dist/<version>/AI-Translate-firefox.zip
VS Code	Shows dictionary and translation results while reading English Skill documents.	dist/<version>/ai-translate-hover-<version>.vsix
Obsidian	Looks up English words, translates selected note text, and optionally saves vocabulary.	dist/<version>/main.js, manifest.json, styles.css, and the matching ZIP

All plugins use the same release version. A release is valid only when Chrome, Edge, Firefox, VS Code, and Obsidian match exactly.

Features

Browser extensions

• Detect a selected word, sentence, or paragraph and open the matching result view.
• Switch between selection, sentence, and paragraph modes without repeating completed requests.
• Look up English words with phonetics, definitions, examples, synonyms, antonyms, and pronunciation.
• Configure multiple OpenAI-compatible model profiles with priority-based fallback.
• Use automatic Chinese-English direction detection or explicit source and target languages.
• Keep recent results locally and prevent stale requests from replacing the current view.
• Optionally save successful English lookups to an external vocabulary API.

VS Code extension

• Look up selected English words from hover or command-based workflows.
• Prefer built-in Youdao dictionary and translation services, with an OpenAI-compatible fallback.
• Play available UK and US pronunciation audio inside VS Code.
• Cache translation and dictionary results with bounded retention.
• Save vocabulary automatically or through a command link when manual mode is enabled.

Obsidian plugin

• Run AI Translate: Lookup or translate from the Command Palette.
• Run AI Translate: Look up selected text from the editor menu or Command Palette.
• Show phonetics, Chinese and English definitions, and available pronunciation audio for English words.
• Use built-in Youdao mobile services first and an OpenAI-compatible endpoint as fallback.
• Support Obsidian 1.12.2 and later through one settings implementation shared by all supported app versions.
• Send vocabulary requests independently so a vocabulary API failure does not break lookup or translation.

See AI Translate - Obsidian Plugin for the complete Obsidian installation, settings, privacy, and request-template reference.

Installation

Browser development packages

1. Download the ZIP for your browser from GitHub Releases.
2. Extract the ZIP.
3. Open the browser's extension management page.
4. Enable developer mode and load the extracted directory.

Store installation should use the platform listing when one is available. Do not upload an extracted development package to an untrusted service.

VS Code

1. Download the .vsix file from the matching release.
2. Open the Extensions view in VS Code.
3. Select Install from VSIX... and choose the downloaded file.

Obsidian

After Community plugins approval, open Settings > Community plugins, search for AI Translate, and install it.

For manual installation, download main.js, manifest.json, and styles.css from the release whose tag exactly matches the manifest version. Copy the files to:

<vault>/.obsidian/plugins/ai-translate/

Release tags do not use a v prefix. For example, version 7.0.9 must use release tag 7.0.9, not v7.0.9.

Configuration

Translation services

Browser and VS Code model profiles support OpenAI-compatible base URLs, endpoint paths, model IDs, authentication, timeouts, priorities, prompts, and optional extra request fields.

The Obsidian plugin uses built-in Youdao services by default. Its fallback translation settings contain an API base URL, endpoint path, model, and target language.

External vocabulary API

Vocabulary integration is disabled by default. When enabled, successful English word lookups can be saved automatically or manually.

Supported request options include:

• POST with a JSON body or GET with encoded query parameters.
• Bearer, Basic, or no built-in authentication.
• A masked authentication credential and custom JSON headers.
• Custom request templates using headword, US/UK phonetics, and Chinese/English definitions.
• An Idempotency-Key for each actual write unless the user supplies one.
• Concurrent request merging for the same normalized word.

The shared protocol implementation is in src/vocabulary.js. Platform-specific code owns only transport, logging, and UI feedback.

Privacy and Security

• Translation text is sent only to the enabled built-in service or the endpoint configured by the user.
• Vocabulary data is sent only when vocabulary integration is enabled and configured.
• Request logging is disabled by default and may contain selected text or provider responses when enabled.
• Browser request logs redact authentication-related headers before storage.

Review the privacy behavior of every endpoint you configure. Local endpoints remain local only when the configured service itself does not forward requests.

Development

Requirements

• Node.js 18.17.0 or later. CI and release workflows currently use Node.js 22.
• npm with the repository lockfiles.
• No Python dependency is required for browser or Obsidian release builds.

Install dependencies

npm ci
npm --prefix obsidian-plugin ci
npm --prefix vscode-extension ci

Run checks

Build all browser packages and run the browser/shared tests:

npm test

Build, type-check, and test the Obsidian plugin:

npm --prefix obsidian-plugin run check

Check and package the VS Code extension:

npm --prefix vscode-extension run check
npm --prefix vscode-extension run package

The browser build writes browser-specific directories under browser-extensions/ and writes the three distributable ZIP files to dist/. ZIP creation runs in Node.js and keeps manifest.json as the first archive entry.

Release Process

Full multi-platform release

A full release requires matching versions for every plugin and an exact, unprefixed release tag.

npm run release:all -- --tag <version>

This command builds Chrome, Edge, Firefox, VS Code, and Obsidian. All release assets are written directly to dist/<version>/. GitHub Release tags always use the exact version without a v prefix.

Release assets

The complete release command verifies all plugin versions, runs every plugin check, and writes these Obsidian assets alongside the browser and VS Code packages:

dist/<version>/main.js
dist/<version>/manifest.json
dist/<version>/styles.css
dist/<version>/ai-translate-obsidian-<version>.zip

Pushing a numeric tag such as 7.0.9 triggers .github/workflows/release-all.yml, which rebuilds every plugin with the actual tag, creates artifact attestations, and publishes the complete GitHub Release. See the Obsidian release and review guide for Obsidian-specific requirements, known scanner findings, fixes, and post-release verification.

Repository Layout

Path	Purpose
src/	Shared browser extension source.
browser-extensions/	Browser-specific manifests, static icons, and generated Chrome, Edge, and Firefox package directories.
src/vocabulary.js	Cross-platform vocabulary request implementation.
vscode-extension/	VS Code extension source, tests, and package configuration.
obsidian-plugin/	Obsidian source, bundle, styles, tests, and dedicated documentation.
scripts/	Browser and release build scripts.
test/	Browser, VS Code, Obsidian, shared regression tests, and browser compatibility fixtures.
website/	Project website source.
docs/	Architecture, development, release, and store documentation.

Contributing and Support

Before submitting a change, run the checks for every affected platform and include focused regression coverage. Start with the documentation index; architecture and behavior constraints are documented in Development Guidelines.

• Report reproducible defects or request features through GitHub Issues.
• Download signed release assets from GitHub Releases.
• Review project and support information on GitHub Pages.

License

This project is licensed under the terms in LICENSE.