More useful.
More personal.

Text conversations, model selection and local SQLite conversation history are implemented. Responses use OpenAI; EVIE is not an entirely offline assistant.

The interface supports English and Greek. Conversation history is separate from the planned personal-memory system.

Native voice foundations and isolated microphone/playback tests exist. Natural voice quality and complete live voice conversations have not passed full acceptance.

Saved conversations exist. Persistent personal memory and richer contextual assistance remain planned.

A local wake word is planned. No working always-listening activation or continuous iOS background listening is promised.

EVIE aims to help with permitted actions. The current AI chat has no execution tools; manual device controls do not mean the AI can operate them.

Conversation data is stored locally and API credentials use macOS Keychain. A broader hybrid architecture is in development. Cloud requests still leave the device.

An iPhone companion, supported Bluetooth audio and permitted hands-free requests are planned. Compatibility and background behavior are not finalized.

General computer control, project integrations and scheduled automations remain future work. They are not available through the current chat or this website.

Proactive assistance and advanced cross-device intelligence are research directions without a delivery commitment.

Rooms, scenes and the home interface combine demonstrations with real Hue-backed paths. Demo controls stay separate from connected hardware.

Discovery, pairing, lighting controls and state readback are implemented locally. Controls depend on reported hardware capabilities. Physical-action acceptance remains limited.

Local adapters provide read-only monitoring. They do not establish unrestricted management, configuration changes or AI control of network devices.

130 entries cover 97 brand records and 12 categories. Three entries have adapters; 127 are planned. Shelly and broad entertainment support remain planned.

Detection and diagnostic inputs have documented physical acceptance. Navigation is implemented locally but still needs physical acceptance. Adaptive triggers and haptic output are unavailable.

Overview, wallets, assets and activity help organize public-address information. This is not a custodial wallet or transaction service.

The registry contains 27 networks. Read adapters exist for Solana, Bitcoin and seven EVM networks; their token, balance and history coverage differs.

Selected token and market-data paths exist. USD valuation may be partial, stale or unavailable. Unknown values are not presented as zero; a currency preference does not perform FX conversion.

The Store has 16 listings. Crypto is the first functional opt-in local development plugin. The other 15 listings are not executable plugins.

Local install, enable, disable and removal foundations exist, with scoped permissions and entitlement checks. A subscription does not itself grant device or data access.

Trusted subscription and entitlement foundations are tested locally. Public subscriptions, checkout, payment collection and trial activation are unavailable.

Unified identity is in active development. Public registration and sign-in are Coming Soon. This website does not create accounts or call authentication services.

Passkey/session foundations and server-side OWNER checks exist in local development. Documented local native/Admin acceptance does not establish public Account readiness.

Shared settings, regional date/time/number formatting, appearance and accessibility preferences are implemented locally. Some platform-dependent settings remain unavailable.

Usage records and token/cost views exist. Cost estimates are not provider invoices or a guarantee of final charges. Missing provider usage must remain unknown.