Repository navigation
v2.0.30
HomeGenie v2.0.30
This release consolidates Gemini Genie and Lailama around shared AI services and brings provider selection to scheduled Genie actions.
Shared AI services
- Centralized response handling, capability checks, chat persistence and execution metrics.
- Shared recovery for confirmed compilation failures, without repeating completed actions or actions with uncertain outcomes.
- Independent settings and chat history for each provider.
Background requests
The common AI Genie service now provides:
- Request.Generate — generate text without executing actions.
- Request.Execute — process a request and execute permitted actions.
- Request.Status — retrieve request state and results.
- Request.Cancel — cancel a background request.
Requests can select a provider explicitly or use the default configured in AI Genie settings. They run independently of the interactive chat and respect the selected provider’s context and capability permissions.
Common endpoint prefix: System.Utility/AiGenie/.
Scheduler integration
- Select Gemini Genie, Lailama, or Default for each Genie action.
- Wait for the request to complete before continuing with subsequent commands.
- Report failed or cancelled requests to the scheduler.
- Cancel an active request when its scheduled execution is stopped. Cancellation does not undo actions already performed.
Interface and translations
- Completed translations for the new AI and scheduler settings across all 91 supported languages.
- Fixed the missing SVG favicon and updated frontend cache assets.
Upgrade notes
Update AI Genie, Gemini Genie, and Lailama before using the new scheduler integration.
Reopen and save existing schedules containing Genie actions to regenerate their scripts. Custom integrations using the following removed endpoints require migration:
- Gemini
Prompt.Ask→Request.Generate - Gemini/Lailama
Prompt.Schedule→Request.Execute - Gemini
Task.Status→Request.Status - Lailama
AI.IntentHandlers/Lailama→AI.Genies/Lailama
The removed endpoints have no compatibility aliases. Interactive chat cancellation remains separate from background request cancellation.
Validation
Validated with 493 backend regression tests, frontend checks, and live tests covering both providers, scheduler execution, cancellation, provider recovery and chat history isolation.