Repository navigation
ChatGPT sign-in, model controls close to the message, and a smaller, cleaner composer.
ChatGPT on desktop
- Choose ChatGPT (subscription) and Continue with ChatGPT in settings. Fetch the models available to your account, then pick a model and reasoning effort. Effort is remembered per model and applies to the next request.
- Requests use your eligible ChatGPT plan or available credits. There is no automatic paid API fallback and no Fast mode. Account, workspace, regional and app-specific restrictions still apply.
- Credentials are encrypted with the operating system through Electron safeStorage, outside the vault. There is no plaintext fallback. Sign-in does not import conversations, assistant memory or a personal assistant identity.
- Model responses stream through the Responses route. A failed or incomplete response is not treated as a completed note edit.
The ChatGPT provider is desktop-only. The existing API providers remain available on desktop and mobile.
Allowance, when you ask for it
The optional Refresh allowance control reads the shared Codex/ChatGPT Work allowance through an installed, already signed-in official Codex CLI. The account email must match. There is no background polling or inference request.
This is not the plugin's app-specific cap, and matching email does not establish matching workspace. Old snapshots are marked stale and hidden at their reported reset. API credits are not displayed.
The message box
The input, attachment button and send/stop button now share one border. Model, effort and allowance controls sit in a compact toolbar that wraps on narrow sidebars. The extra bottom gap is removed without changing other Obsidian views. Keyboard focus, IME composition and a draft typed during generation are preserved.
Build and verification
The release workflow now runs the complete offline regression suite before publishing. Local checks cover subscription transport, synthetic-token authentication, quota handling, composer behavior and light/dark responsive layouts.
A normal build never deploys to a vault. Explicit deployment requires an existing absolute destination in AI_ASSIST_VAULT_PLUGIN and npm run build:deploy. User settings, conversations, credentials and local deployment backups are not release assets.
Install main.js, manifest.json and styles.css from this release into .obsidian/plugins/ai-assist/, then reload the plugin. See setup and security for details.