slicc-agent adds ChatGPT, xAI and Kimi sign-ins to its browser-based pi agent

slicc-agent can now connect ChatGPT, xAI and Kimi For Coding accounts through device-code sign-in flows. The community project’s October 20 version 6.16.0 brings pi-ai’s authentication routes into its browser-worker agent core, while keeping an API-key alternative for xAI and Kimi.

The distinction matters: slicc-agent is built on pi’s durable harness and runs beside slicc-kernel, with slicc-spectrum providing its interface. It is not a new model, an official provider app or a standalone browser extension. The new release changes how an existing SLICC environment connects accounts; it does not include a subscription or remove provider usage limits.

Sign in through the host vault

The documented flow opens a provider authentication page and displays a device code, with a copyable code and link if the browser blocks the popup. A successful flow passes the provider grant to the host vault. The maintainers describe tokens as excluded from replicated settings and transcript state, with subsequent model calls using credential placeholders that the vault fills. AITrending has reviewed that documentation and the implementation change, not independently audited the credential boundary.

ChatGPT is represented internally as openai-codex and shown as ChatGPT. The provider description names ChatGPT Plus or Pro access. Users still need an eligible account with access to the selected model.

Browser connectivity also differs by provider. Kimi’s inference API and ChatGPT’s API need the host’s CORS-free transport. xAI’s API can answer browser requests, but its device authentication endpoints need that transport for sign-in. The README explains that a connected account can remain visible while its models are unavailable until the required route returns.

A package release for a compatible host

The release is served on npm as @ai-ecoverse/slicc-agent@6.16.0. Existing host installations use the documented pnpm upgrade @ai-ecoverse/slicc-agent route. Package metadata declares Node.js 24+, slicc-kernel >=1.110.0 <2 and slicc-spectrum ^1.98.0; sign-in additionally needs a compatible host vault. Installing the agent package alone does not provide that complete environment.

The code is Apache-2.0-licensed. The release’s certification record concerns its package and project checks, while the README says a downstream host boot is not yet part of its certification workflow. Treat the sign-in support as a documented, shipped component integration, rather than proof that every provider account has been tested end to end in the full application.