Planned Telegram-First Access
The product direction proposes Telegram as the main assistant interface. Today Telegram is only a project contact; this page documents the intended experience.
Planned Telegram Interface
The planned product would use Telegram for its main interactions. No assistant bot or management service is generally available today.
- ✓ Telegram bot - PRIMARY interface (main entry/exit/management)
- ✓ Website - SECONDARY interface (informational only)
- ✓ REST API for future integrations
- ✓ WebSocket for real-time updates
- ✓ Consistent experience through Telegram
Access Methods
Main interface - all interactions and management through Telegram
Informational only - learn about capabilities
Standard HTTP endpoints for future integrations
Real-time bidirectional communication
Telegram Bot (PRIMARY)
Intended as the main interface for future interactions and chat commands.
Website (SECONDARY)
Informational interface for learning about the planned capabilities; no management service is live.
Future API Access
Possible future REST API and WebSocket integrations for custom applications.
Consistent Experience
Telegram-First Experience
The intended capabilities would be available through a Telegram interface. The website currently documents that direction.
- ✓ All interactions through Telegram
- ✓ Synchronized across all life aspects
- ✓ Access from anywhere via Telegram
- ✓ Real-time updates and notifications
Developer Direction
Possible future API documentation and SDKs for application integrations.
- RESTful API design
- WebSocket support
- OpenAPI documentation
- SDKs for popular languages
Interested in the Direction?
Discuss the proposed access model with the project