How the JARVIS AI interface works.

The system is a composition, not one model

The framework separates the visual scene, spoken voice, language-model brain, briefing script, and live data feeds. Each capability has its own contract. A developer can replace one plugin without rewriting the rest of the assistant.

This matters because an AI experience is larger than its model. The scene controls what appears, the voice controls what is heard, the brain produces responses, the script shapes a briefing, and feed adapters bring in changing data.

• ScenePlugin controls the 3D scene and visual phases.
• VoiceAdapter turns text into speech and can stop playback.
• BrainAdapter accepts a request and can optionally stream a response.
• BriefingScript defines ordered beats, pauses, and visual phases.
• FeedAdapter fetches or subscribes to data such as news, trading, or social feeds.

The briefing engine connects the parts

The repository describes a briefing engine that moves through scripted beats while coordinating visual phases and speech. The heads-up display renders the experience around that flow.

The full reference build uses Electron for the desktop shell and Three.js for the visual scene. It supports clap or spacebar wake triggers and several local or cloud brain adapters.

Local-first is a design choice

The project documentation says JARVIS has no analytics or telemetry. Prompts leave the machine only when the user chooses a cloud service and provides that service's key. A local Ollama adapter is listed alongside cloud adapters.

That does not make every configuration private by default. Privacy depends on which voice, brain, and feed adapters a user enables. The repository remains the source for current setup and security details.

What the project does not claim

JARVIS is an early-stage open-source framework, not a claim that a fictional all-knowing assistant exists. Its current value is an inspectable architecture for composing an AI desktop experience.

The repository marks the project as version 0.1 building. Roadmap items should not be described as already shipped unless the repository later confirms them.