Inkore’s first product candidate
Inkore Cue brings text conversation, voice, local memory, governed actions, and extensions into one desktop application. This page presents the product and its real limits while the alpha is being hardened.
No sale, subscription, or remote AI call is active today.
One interface, four capabilities
The alpha’s goal is to turn a powerful open-source foundation into a product that is installable, understandable, and governed by its user.
Text chat is the main interface, and local voice output (Piper) works when its model is already installed. A real-time LiveKit voice mode does exist: its server ships in the Windows bundle, pinned by a SHA-256 fingerprint, and the client opens the microphone continuously there rather than on a key press. That mode is not started by the normal launch, it is not finished, and local speech recognition has no model in the bundle.
Inspectable persistent memory kept on the machine instead of hidden behind a remote interface.
PC control stays bounded: read system status and open allowlisted applications with permission and approval. The main free-form command surface is neutralised; other shell surfaces remain to be closed before any distribution.
The extension catalog will have to be pinned, verified, and staged before activation.
Secure by default
Inkore Cue is not called secure because of a promise. Every critical boundary must be backed by code, tests, and reproducible installation evidence.
Requirements before any launch:
Current alpha status
The candidate’s verified, dated state is published on the Progress page; this table summarises what is open and what stays closed.
| Component | State | Required evidence |
|---|---|---|
| Inkore Cue identity and local interface | Partially implemented | Partial rebrand: upstream licence and copyright kept, upstream name still present in the code |
| Local authentication and WebSockets | Hardening in progress | Denial, session, and non-disclosure tests |
| Extension catalog | Remote install suspended | Remote installation stays closed: the human security audit of the native modules has not taken place |
| PC control | Limited scope | Applications permission is off by default and approval is required before action |
| Remote AI engine | Not configured | BYOK API key or dedicated provider account at launch |
| Public Windows archive | Not published | Windows CI, checksum, signature, and clean-machine test |
| Payments and subscriptions | Not enabled | Pricing, entitlements, billing, and support validated separately |
Two planned editions
Both offers keep the same local core and safety boundaries. They differ in how AI usage is supplied and funded, not through a promise of unrestricted PC control.
Users buy the distribution once and connect their own API key. AI calls are billed directly by the selected provider and are not included in the Inkore purchase.
Not for sale yet: the signed installer, update path, and support process still need proof.
“Lifetime” means a perpetual right to use the major version purchased; it promises neither free updates nor free support for life. The duration of those services will be shown before any sale.
Inkore supplies AI access within plan limits, with quotas, usage metering, and cost guardrails. A personal key is not required while the plan quota covers usage.
No subscription is open: Cue Plus is postponed by decision until the first Lifetime payment proof; provider service, billing, quotas, and revocation still need implementation and verification.
No pricing is published at this stage. A ChatGPT Pro subscription is not used as a shared API key. It is a development tool only, not a resold component or API credit for users.
Transparent provenance
Inkore Cue is a fork of Jarvis OS, distributed under AGPL-3.0-or-later: the upstream licence and original copyright notices are kept, and Inkore does not claim the upstream code as an exclusive creation. The dated modification notices the licence requires are being added on a private branch, pending human legal review: they are not merged. The rebrand is partial — the upstream name still appears in the code.
No external access is open: the candidate stays private until the human decisions — code signing, legal review and a trial on a clean Windows PC among them — are taken. The verified, dated state is published on the Progress page.