ObsidiAI 0.1.2

ObsidiAI 0.1.2

New

• Chat permission modes: Read-only, Ask before changes (default), and Auto-approve notes. Plugin lifecycle changes still require individual approval. New and reopened conversations reset to Ask; automatic note approval never bypasses path, current-run read, conflict, or cancellation checks.
• Persistent chat history with native Open and Delete controls. Restore prior messages and tool context after reload; continued requests use the currently selected provider/model, as disclosed in the dialog.
• @ note and folder suggestions in the composer, including nested permitted Markdown files, duplicate handling, and visible attachment failures.
• / skill suggestions with keyboard and mouse selection. Manual-only skills remain selectable; user-invocable: false excludes explicit invocation. Selection does not send automatically.
• Subtle chat, tool-card, and control animations, respecting reduced-motion preferences.

Fixed

• Native provider requests no longer inherit incompatible browser timers, performance APIs, or response streams inside Obsidian. The bundled HTTP client uses dependency-scoped Node bindings without changing host/UI globals. This fixes connection failures, stalled response bodies, and cancellation hangs observed with NVIDIA.
• Provider failures now display safe, actionable authentication/access, unavailable-model, quota, and service categories without exposing upstream response bodies.
• Failed history saves retain the current conversation and report the problem; retry can save it before starting a new chat. Deletion does not resurrect a saved conversation on unload.
• Attachment status clears after submission, and late attachment reads cannot add context to a closed view.

Important: history storage

Saved chats can contain sent note excerpts, skill instructions, and tool results. They are stored separately from credentials in .obsidian/plugins/obsidiai/history.json by default, or under your custom vault configuration folder. The plugin does not encrypt this file; sync and backups may copy it. Unsent drafts and elevated permission modes are not stored. Deleting removes the plugin's saved copy, not existing backups or remote copies.

Install or update

1. Download obsidiai-0.1.2.zip, not GitHub's automatic source archive.
2. Extract the included obsidiai/ folder into <test-vault>/.obsidian/plugins/. When updating, replace only main.js, manifest.json, and styles.css; preserve existing data.json and history.json if present.
3. Reload Obsidian or disable/re-enable ObsidiAI. Conversations from 0.1.1 were memory-only and cannot be recovered after reload; finish or copy them before updating.

The three individual plugin files are also attached. Requirements remain Obsidian desktop 1.11.4+ and embedded Node 22.19.0+.

Verification and limits

• 113 tests pass locally, including real local HTTP streaming/abort with renderer-like globals, permission boundaries, history persistence and failure recovery, and credential privacy. The release workflow repeats checks on Node 22.19.0 and Node 24 before publication.
• Native checks used Obsidian 1.13.7 in disposable vaults: automatic note edits, read-only rejection, plugin approval, permission resets, @// interaction, IME/dismissal, narrow panes, reduced motion, history reload/resumption/deletion, and failed-save recovery.
• A real NVIDIA openai/gpt-oss-20b request returned a response through the production plugin; Stop settled correctly. Some models advertised by NVIDIA returned HTTP 404 for the test account. Catalog visibility is not proof of endpoint availability or account access.
• Successful OAuth login and actual third-party plugin-manager lifecycle effects remain unverified. No scripted preview provider or test credential is shipped.

Start in a disposable vault. Community plugins execute unsandboxed code; uninstall can remove their saved data. Stop is not rollback.