forked from retoor/devplacepy
retoor
6ceca3d0d4
- Add comprehensive documentation for backend content rendering in AGENTS.md, detailing the new `render_content` and `render_title` Jinja globals built on mistune with media processing, emoji shortcodes, and XSS protection
- Document the `X-Response-Time` header and bottom-left render time indicator in README.md
- Update bot token pricing documentation to clarify fallback vs gateway cost headers
- Add `email_accounts` to soft-delete tables and `idx_users_role` composite index in database schema
- Implement `telegram_pairings` and `telegram_links` table creation with column migration and indexes
- Add `/profile/{username}/telegram` endpoint to docs API with request/unpair actions
- Register `TelegramService` in main.py lifespan and add `response_timing` middleware emitting `X-Response-Time` header
- Introduce `TelegramPairForm` model and `guard_public_host_sync` synchronous host validation function
40 lines
1.9 KiB
HTML
40 lines
1.9 KiB
HTML
<div class="docs-content" data-render>
|
|
# Devii on Telegram
|
|
|
|
Chat with your own Devii assistant from Telegram. Once you connect your Telegram account, the
|
|
DevPlace bot talks to the same Devii that runs in the web terminal: it operates your DevPlace
|
|
account through your API key, answers in markdown, shows a typing indicator while it works,
|
|
updates a single message as it thinks instead of flooding the chat, and can read images you send.
|
|
|
|
## Connect your account
|
|
|
|
1. Open your [profile](/profile) and find the **Telegram** card in the sidebar.
|
|
2. Click **Request pairing code**. A four digit code appears. It is valid for a limited time
|
|
(one hour by default).
|
|
3. Open the DevPlace bot in Telegram and send it the four digit code.
|
|
4. The bot replies confirming the connection. You can now chat with Devii directly.
|
|
|
|
The code is single use. If it expires or you lose it, request a fresh one from your profile. To
|
|
disconnect, click **Disconnect** on the same card, which unlinks the Telegram chat from your
|
|
account.
|
|
|
|
## What you can do
|
|
|
|
- Ask Devii anything you would ask in the web terminal: it can read your feed, manage posts,
|
|
projects, gists and files, search the documentation, and more, all on your own account.
|
|
- Send a photo and Devii can see it and respond to it.
|
|
- Long answers are split automatically so they always fit Telegram's message limits.
|
|
- Markdown in Devii's replies is rendered with Telegram formatting (bold, italics, code,
|
|
links and code blocks).
|
|
|
|
## Privacy and limits
|
|
|
|
Your Telegram conversation is a separate thread from the web terminal, but it shares the same
|
|
Devii memory, tools, and your rolling 24 hour AI usage limit. Only private chats are supported,
|
|
and the bot only ever acts for the account that paired with it. Disconnecting removes the link
|
|
immediately.
|
|
|
|
If the bot does not respond, the Telegram service may be turned off for this deployment. The
|
|
service is managed by administrators and is not enabled by default.
|
|
</div>
|