Niplex Research AI 0.1.23

Standalone release: removes companion-plugin installers, update checks, ecosystem extension hosting, and companion-dependent onboarding. Adds MCP-compatible tool schema normalization and a streamable HTTP JSON-RPC client. Research AI remains independently usable with Gemini, Agnes, local bounded vault tools, local skills, MOCs, approvals, and mobile-first UX.

Niplex Research AI 0.1.22

Stops repeated overlapping reads of the same bounded Markdown window, terminates pathological reread loops, clarifies continuation evidence reuse, keeps Markdown notes out of Assets/, and creates missing parent folders for generated notes.

Niplex Research AI 0.1.21

Compatibility patch: exposes the Niplex ecosystem host bridge under the documented and legacy discovery aliases so enabled companion plugins can connect after load-order changes. Includes the existing bounded-context, consent, mobile UX, and provider setup fixes.

0.1.20

Fix missing provider-key handling, reduce repeated MOC failure diagnostics, simplify the narrow mobile view, and clarify settings descriptions.

0.3.2 — Codex privacy and companion lifecycle fixes

What changed

This patch addresses privacy and reliability edge cases found in the ecosystem review.

• Companion reminders and restart-time release checks remain off for upgraded installations until the user explicitly confirms first-time companion setup. After confirmation, the intended user-controlled maintenance defaults are enabled.
• Failed or below-target release lookups stay visible in the companion manager instead of being mistaken for an up-to-date installation.
• Companion files now use the vault’s configured Obsidian config directory, including custom configDir values.
• Stable releases correctly supersede prerelease versions during update checks.
• Host-side context normalization now preserves explicit zero and small item/character budgets.
• The protocol documentation now matches the runtime extension contract.

How this affects you

Nothing is silently downloaded or enabled. Existing users may see the companion setup panel before maintenance checks begin. If you confirm setup, reminders and restart checks can run according to the Settings toggles. If a release service is unavailable, the manager now shows that it could not verify the companion and offers the visible manual Community-plugin route instead of claiming that no action is needed. Your preserved 0.1.19 release remains available as a rollback point.

Release assets are exactly main.js, manifest.json, and styles.css.

Niplex Research AI 0.3.1

Fixes the Settings action for installed-but-disabled companion plugins by opening Obsidian Community plugins instead of rendering an inactive installer control. The consent-based first-install flow, allowlisted restart update checks, release-note impact explanations, exact asset verification, and rollback-aware replacement remain unchanged.

Niplex Research AI 0.3.0

Adds the versioned Niplex ecosystem host, deny-by-default extension permissions, bounded Research Brain and Writing Insights context, read-only companion actions, transparent first-install companion confirmation, allowlisted restart update checks, rollback-aware replacement, and expandable release notes explaining user impact. Existing 0.1.19 remains available as a rollback point.

Niplex Research AI 0.1.19

Community review warning cleanup\n\n- Removed the unsafe-looking activity lookup flagged by the source review.\n- Replaced the CSS column-gap/row-gap pair with a standard grid gap declaration.\n- Removed placeholder-style installation wording from the README.\n- Retained the Community-safe manifest description from 0.1.18.

Niplex Research AI 0.1.18

Community manifest validation repair\n\n- Removed the redundant product-name word from the Community manifest description after the automated validator rejected 0.1.17.\n- Retained the current mobile runtime, bounded vault research, chat-window sizing, inline commands, and skill controls.\n- Network and runtime functionality are unchanged.

Niplex Research AI 0.1.17

User-controlled chat window size\n\n- Added Compact, Comfortable, and Spacious chat-window profiles under Actions → Chat window size.\n- Persisted the choice locally and apply it immediately to the current view.\n- Reduced mobile card/composer density in Compact mode and expanded readable answer/composer space in Spacious mode.\n- Kept runtime history scrollable and secondary tools behind Actions.