# fpga.chat Telegram Bot

Human page: https://fpga.chat/docs/telegram-bot

`@FpgaChatBot` is now operated from the separate `fpgabot` project. The bot is not part of the fpga.chat web/API runtime and does not share the fpga.chat application database.

The standalone bot can answer text questions about FPGA, RTL, EDA logs, constraints, verification, toolchains and board bring-up. For pasted EDA logs, it may call the public fpga.chat Error Decoder API with a service token. That API response is evidence-scoped triage, not timing, CDC, RDC, pinout, vendor-tool or hardware signoff.

## Data boundary

Telegram request history, bot threads, bot feedback, Telegram Stars bot payments and OpenRouter subkey metadata are stored by `fpgabot` in its own database. fpga.chat stores only its own product/API records.

## Operations

Use `/home/elixirus/Documents/dev/FpgaCamp/fpgabot` for bot deployment, migrations, webhook setup and bot smoke tests. Keep the `fpgabot` secret key equal to the old bot encryption secret when migrated OpenRouter subkeys must remain decryptable.