TensorPass

Blog

AI Connect 0.1.0 is on npm

Since 16 November 2026 the four AI Connect packages install from npm under the scope @tensorpass, with provenance from 0.1.1. A fresh Next.js 16 app built on them passed 12 of 12 visitor checks against the live sign ins.

Published on

On 16 November 2026 TensorPass published version 0.1.0 of the AI Connect SDK on npm. A website installs it with one command and answers its visitors on their own AI accounts, through the AI Wallet extension or through a sign in with OpenRouter or the TensorPass plan.

npm install @tensorpass/aiconnect @tensorpass/aiconnect-react

The four packages

PackageWhat it holdsPacked sizeFiles
@tensorpass/aiconnectThe client, the conversation loop, the MCP client, the guards, the sign ins without AI Wallet and the aiconnect command135.2 kB124
@tensorpass/aiconnect-reactThe provider, useAiChat, the connect window and the five interface modules101.2 kB123
@tensorpass/aiconnect-elementsThe modules as the custom elements <aiconnect-chat> and <aiconnect-search>, in one script1.1 MB8
@tensorpass/aiconnect-designThe design tokens and the marks, which the React package installs70.3 kB17

Each package carries the Apache License 2.0. The elements package holds a script of 707 KB, 201 KB compressed with gzip, and its source map, and jsDelivr serves the script at https://cdn.jsdelivr.net/npm/@tensorpass/[email protected]/dist/aiconnect-elements.js for a page with no build step.

What 0.1.0 holds since the notes of 12 November

The release notes of 12 November list the client, the guards and the modules. Four parts joined the release before publication:

How the packages were checked

Three fixes came before the upload. The design package exported TypeScript files, which a Next.js app could not compile from node_modules, so it now ships JavaScript with its types. The source maps named a src folder the packages left out, so each map now carries its source. The elements package listed React and the other packages as dependencies of a script that already holds them, so they became build inputs.

On 16 November a fresh app installed the packages from npm with the command above, on Next.js 16.4.6 and React 19.3.1, with no transpilePackages setting. Its build passed, and a visitor without AI Wallet passed 12 of 12 checks against the live services: the connect card with both sign ins, the TensorPass sign in accepting the site key on localhost, the OpenRouter popup returning to the app's own page, which closed it, and the page calling OpenRouter's real key exchange with its PKCE verifier. The elements script from jsDelivr drew its chat on a plain HTML page. Before the upload, the same files built a Vite app and imported in Node.

What comes next

Version 0.1.0 carries no npm provenance, since it was published from a computer, and npm signs provenance only for a package built by a workflow of a public repository. Version 0.1.1 followed the same day at 02:22 UTC with the same code, published by the release workflow of the SDK's public repository, https://github.com/tensorpass/aiconnect, with provenance on each package. AI Wallet waits on the Chrome Web Store's review, and visitors install it by hand from the AI Wallet page meanwhile. The changelog lists everything 0.1.0 contains.

Sources

Read the quickstartRead the changelog