Current development dependencies are SDK 0.22.2, Kit/native 0.22.1, App Tools 0.14.0 and Nimi Coding 0.7.0. The checked-in pnpm lock resolves these packages from the public registry. Run pnpm install --frozen-lockfile, pnpm exec nimi-app check, then pnpm dev with a matching source-built Nimi Runtime and Home. App versions and published App releases are unchanged. Earlier versioned notes retain their original acceptance scope. Home uses the App-owned root NIMI_APP.md; this README remains developer documentation.
Upgrade verification: public-registry installation, frozen-lockfile installation, App Tools checks and the applicable type/Host build checks passed. Desktop-supervised macOS development opened the research workspace and Nimi AI configuration. New model-output journeys and packaged installation were not rerun; earlier evidence below retains its stated versions and scope.
Fixes the citation display failure observed during real web research. The previous Markdown parser misread an inline Windows backslash, and the App's pre-parse HTML replacement could expose internal citation tags or rewrite code and link labels. The updated parser and post-parse React citation rendering preserve code, ordinary links and unresolved references without interpolating source URLs into HTML. Stored model answers and source records are unchanged.
Type checking and all 21 App tests pass, including six regressions for backslashes, inline/fenced code, links, missing references and quoted URLs. Through the existing Desktop-supervised CDP target, the original saved web answer now displays its backslash and citation links correctly with no exposed tag. The previous document answer still opens the actual uploaded source passage from its numbered citation. Windows production build/pack and the packaged Electron native, canvas and document-extraction checks pass.
On October 14, installed Nimi 0.2.4-rc.1 updated the Imported Windows App from
0.1.7 to 0.1.8, preserving the original document chat and source passage.
Opening its numbered citation still displayed the uploaded text. The retained
Web source option was initially off; direct official-page reading passed in
that mode. After enabling Web, one ai-output-invalid request and two search
engine failures remained recorded. The local SearxNG service was tuned through
its documented engine settings
and outgoing timeouts:
Bing enabled, Brave and DuckDuckGo disabled after repeated rate-limit/CAPTCHA
responses, request timeout 10 seconds and maximum 15 seconds. This only changes
the local acceptance service; the App still uses its configured service URL.
The subsequent installed research task ran three real queries, found 60
results, read one source and returned a Chinese comparison with numbered
official Python citations and intact Windows-backslash code. Normal close and
Home relaunch restored all four chats, including the successful answer and
earlier failures. The successful chat is
61049960-574a-4e7f-92b9-0b4fa7646da3. The Home news widget still reported an
upstream loading failure; news availability is not claimed. The annotated
v0.1.8 tag points to tested source 0b38230. The immutable release
is published for both targets, and exact packages, licenses and build provenance
passed Registry preparation. Candidate #102
replaces withdrawn #94. The user approved the existing dual-platform stable
candidate on October 14; finalization passed and #102 merged. The superseded
0.1.4 safety candidate #62 was closed. The slow Catalog download subsequently
completed and installed the original 0.1.8 Windows package on Nimi 0.2.4.
Home launched its distinct Catalog release-directory Host. A fresh document
upload used text-embedding-v4, and qwen3.8-flash returned the correct Lin Lan,
Runtime Bridge, six-observation and no-zero-fill facts with file citations.
Opening a numbered citation displayed the actual uploaded source passage.
The first request correctly refused Web research because the new Catalog
workspace had no SearxNG URL; disabling Web for this document-only task allowed
the next request to complete. That prerequisite failure remains recorded.
Home's account session later expired, interrupting the App connection. After
the user signed in again, Home relaunched the same Catalog instance and its
Library restored the answer, source and citations without regeneration. The
successful chat is 0bfed5ca-d2ba-4592-a113-842e83651e33. Fresh Windows Catalog
download/install, document research and reopen therefore pass. The prior
Imported update and Web-research evidence retain their separate scopes;
Catalog N-to-N+1 update and Web search in this new workspace were not run.
Uses published SDK 0.21.0, Kit/native 0.19.3, App Tools 0.12.2 and Nimi Coding 0.6.5. Type checking and 15 tests pass. Research uses automatic tool choice with the existing no-action rejection; submission waits for attachment processing. Both Windows supervised development and local imported installation completed document research. Against Nimi 0.2.3-rc.2, the installed release-directory Host uploaded and embedded windows-acceptance.txt, then used qwen3.8-flash and text-embedding-v4 to return a cited Chinese answer identifying Lin Lan, Runtime Bridge, six observations and the rule against replacing missing data with zero. Normal close, relaunch from Home's Imported source, and opening the Library restored the same attachment and answer. Installed interaction used native UI without production CDP.
The first MiMo v2.6 Flash research attempt returned ai-text-behavior-unsupported; its failure remains in the conversation. Vane requires tools and structured output, so that unsupported combination is not counted as model-quality acceptance. Catalog installation of this new version remains a separate delivery step. Earlier macOS evidence below keeps its original version and scope.
Additional Windows supervised-development acceptance against Nimi 0.2.3 used Vane's own loopback CDP and a local SearxNG 2026.10.13 service with JSON enabled. The App's connection test returned 27 results after initial engine timeouts. With qwen3.8-flash and text-embedding-v4, the real research flow searched two queries, found 53 results, read the Python pathlib documentation and produced a Chinese answer with working official-document links. Normal App close, resume of the same development registration and opening the Library restored that answer and its sources. One inline citation marker remained visible as raw text; this presentation limitation is recorded separately from successful search and AI execution. Installed-package web search remains NOT-VERIFIED. SearxNG remains a separately configured service, not a bundled or promised default endpoint.
This release resolves public npm Kit/native 0.19.2 in the frozen lockfile, with SDK 0.21.0 and App Tools 0.12.0. Launch the installed Catalog App through Nimi Home in either the supported production environment or the macOS source-development environment. The App always loads its own packaged native carrier. Source Runtime peer identity and installed-App/session admission remain verified; no workspace carrier replacement or trust-check bypass is used.
Catalog AI acceptance passed on macOS arm64 using the actual 0.1.6 Release admitted by Registry PR #73, downloaded and launched through source Nimi Home. Uploaded and embedded a new text document, obtained a cited answer identifying Runtime Bridge, BLUEBIRD-743 and Kit 0.19.2, then quit and relaunched from Home and reopened the saved chat and file. The configured Deepseek model first rejected the requested text behavior; selecting Gemma 4 through the App AI settings completed the same workflow.
Local screenshots and exported results are in .nimi/local/released-dependencies-20261012/. Windows interactive acceptance and other unrun AI modalities remain NOT-VERIFIED. These results supersede the earlier Catalog limitation; historical results below retain their stated versions.
This fork adapts Vane into a Nimi ecosystem App. The standalone Nimi App targets Windows x64 and Apple Silicon macOS. Availability in the Nimi catalog requires a separately approved Registry entry.
Vane owns research steps, web tools, document retrieval and answer presentation. Nimi owns account binding, App authorization, model configuration and AI consumption. Chat history, uploaded documents and search settings use Nimi managed App storage.
The release target is installation and launch from Nimi. Once installed, sign in to Nimi and open Vane:
- Open Settings → AI models and use Nimi's model configuration panel. Research needs a text model with tools and structured output support; document indexing and search ranking also use text embeddings.
- Open Settings → Search, enter a SearxNG service address, test it and save. The service must allow JSON searches. This App does not bundle a SearxNG server or promise a default public endpoint.
- Ask a question, choose web/academic/social sources and a research mode, or attach a PDF, DOCX or plain text document. Documents are limited to 20 MiB each, with at most 20 selected documents.
Settings are entered inside the App. End users do not edit repository files, install Node.js or run a Vane web server. Search queries go to the configured search service; AI execution follows the configuration owned by Nimi.
Search-engine outages are reported with a retry or service-selection action. Quality mode uses deeper research while keeping the answer length appropriate to the question.
Research can be stopped. Reopening a chat within the running Host observes its current progress without repeating tools. After a Host exit, an unfinished saved request is shown as interrupted; it is not automatically resumed.
Changing text-generation settings does not require re-uploading documents. If the embedding model changes, clear the old attachments and upload them again to rebuild their indexes. Interrupted answers remain incomplete; a connection failure never confirms that unsaved progress was stored.
Upstream is ItzCrazyKns/Vane, with baseline
348feca3e378fb4157b217724ed508dc707f853f before the Nimi adaptation. The downstream
App mainline is nimi, independent of upstream release tags. Select an exact
upstream revision when updating and review the affected product, dependency,
license, CI and agent-entry changes together; do not automatically import tags
or restore retired provider/account paths.
Use Node.js 24 and pnpm 10.34.5. Version 0.1.5 selects the published npm SDK 0.21.0, Kit/native 0.19.0, App Tools 0.12.0 and Nimi Coding 0.6.5. The frozen pnpm lock records registry integrity and contains no Nimi local package override. Electron uses the supported 44 series.
The public macOS native carrier uses the production Runtime trust profile. Platform-source experiments use Nimi's separately documented development carrier/profile and remain private validation. A matching version number alone does not make the two native profiles interchangeable.
The project uses the managed engineering surface and is maintained with nimi-app sync. App Tools also supports nimi-app init --adopt for first-time adoption of an existing project. This fork has no fresh scaffold intent or lock; do not fabricate them.
pnpm install --frozen-lockfile
pnpm exec nimi-app check
pnpm exec nimi-app test
pnpm run typecheck
pnpm devpnpm dev is the official App Tools entrypoint. Run a matching installed Nimi,
sign in and enable developer mode. App Tools asks Desktop to supervise the
Electron Host and prints its loopback CDP endpoint. Nimi's source-development
Runtime is a separate native trust profile; follow the platform's development
instructions when working on that profile.
A new development registration has its own managed storage identity. To rebuild and reopen the same App data, run pnpm exec nimi-app dev --list-registrations, select the existing registration for this project, then use pnpm dev -- --resume <selector>. Selectors belong to the current Desktop session; list again after restarting Nimi. Plain pnpm dev requests an explicit selection when registrations exist. Renderer reload reconnects within the existing Host. A real session invalidation
retires its business clients, cancels old work and replaces the renderer; the
ready callback supplies fresh clients. Development registration is separate from
installed App lifecycle acceptance.
pnpm exec nimi-app check checks the managed authoring contract and public
dependency lock. Run it after synchronization and dependency changes, and before
packaging. Verify real App behavior separately through the supervised Host.
Research model steps use the public synchronous carrier so classification, structured extraction and function tools can use resources that support those behaviors in SYNC mode. Vane continues to own its research loop and progress events. The selected resource must support the complete request; a catalog row or a ready text resource alone does not establish support for every behavior. The Host configures the technical profile supplied by Desktop before loading the rest of Kit. The macOS public-package upgrade passes production preflight, 14 tests, TypeScript, production build/pack and the packaged native/canvas/PDF/DOCX check. Real document upload, retrieval with source citations and saved-result reload were exercised through Desktop-supervised development. Catalog installation and Windows user journeys require their own verification.
Before the first release, follow the app-tools publishing setup.
Configure NIMI_REPOSITORY_ADMIN_TOKEN in this repository's Actions secrets with
Administration: Read-only. It only checks tag protection and Release
immutability; actual Release uploads use GitHub's built-in token. Local
development does not need this credential. A secret in another App repository
is not inherited.
For an App release, keep the public component combination and lockfile aligned, then run the managed lifecycle:
pnpm exec nimi-app sync
pnpm exec nimi-app check
pnpm exec nimi-app test
pnpm exec nimi-app build --target macos-aarch64 --production
pnpm exec nimi-app pack --target macos-aarch64 --productionRun the commands above on Apple Silicon macOS. On Windows x64, use --target windows-x86_64 for both build and pack. The managed workflow builds both targets on their native runners and aggregates their packages into one Release. Every build executes the packaged Electron binary to check protected-native loading, canvas and real PDF/DOCX extraction; this dependency check does not establish Desktop/Runtime or GUI acceptance.
The --production flag supplies the native execution metadata required by Nimi installation; it does not publish anything. For local installation testing, use Nimi → Apps → Add app → Import local package.
The .gitattributes rule preserves LICENSE bytes on Windows. Registry compares the packaged license with the exact tagged source file; a checkout line-ending conversion also fails this check.
The generated .github/workflows/nimi-app-release.yml owns GitHub package publication. Registry admission and installation through Nimi are separate acceptance steps and remain unverified until actually exercised. No test requires publishing a package, pushing a tag or merging a release PR.
The former Next.js server, direct model provider setup, SQLite and Docker deployment are removed from this fork. Upstream documentation under docs/ describes the original project; it is not the integration contract for this Nimi App.
Vane is MIT licensed. See LICENSE. Original project and contributors: ItzCrazyKns/Vane.
Report the App version, failed operation, Runtime status and error message through this fork’s GitHub issue tracker. Remove credentials, session tokens, document contents and private search queries from reports. Restart Vane from Nimi after checking model and search settings; an interrupted request is not automatically resumed.
0.1.5 is published through the managed immutable-release workflow and admitted to the Registry. The App consumes released SDK 0.21.0, Kit/native 0.19.0, App Tools 0.12.0 and Nimi Coding 0.6.5 through public npm locks, with no local Nimi dependency override.
Document upload, embedding retrieval, cited answers and saved-result reload passed. Catalog 0.1.5 downloaded, installed and launched; its AI connection returned runtime-service-untrusted in the current source-development Runtime topology. These business checks used the actual Desktop-supervised development Host. Catalog AI acceptance remains NOT-VERIFIED; the user authorized publication and admission with that limitation recorded. Windows package production tests, build and provenance passed; Windows interactive use remains NOT-VERIFIED.