TELEGRAM_BOT_TOKEN
set
Connects the private bot.
Paste BotFather token into .env.
Personal Operating Agent
Telegram-first operating console with an auditable ledger, approval gates, and external writes disabled.
Telegram Readiness
3 / 3
required settings present
Storage
JSON
C:\server\repos\personal-operating-agent\data\ledger.json
Execution
Blocked
approval and policy scaffolds are active
Setup Checklist
| Setting | Status | Purpose | Next action |
|---|---|---|---|
| TELEGRAM_BOT_TOKEN | set | Connects the private bot. | Paste BotFather token into .env. |
| TELEGRAM_ALLOWED_USER_IDS | set | Restricts access to approved Telegram accounts. | Add your numeric Telegram user ID. |
| TELEGRAM_WEBHOOK_SECRET | set | Verifies webhook requests came through the expected Telegram route. | Add a random secret string. |
| OPENAI_API_KEY | optional | Enables real model-backed agent work after mock flow is approved. | Fill after Telegram is proven. |
| DATABASE_URL | planned | Moves the ledger from local JSON to Postgres. | Future hardening step. |
| REDIS_URL | planned | Runs scheduled jobs, retries, and background queues. | Future hardening step. |
TELEGRAM_ALLOWED_USER_IDS
set
Restricts access to approved Telegram accounts.
Add your numeric Telegram user ID.
TELEGRAM_WEBHOOK_SECRET
set
Verifies webhook requests came through the expected Telegram route.
Add a random secret string.
OPENAI_API_KEY
optional
Enables real model-backed agent work after mock flow is approved.
Fill after Telegram is proven.
DATABASE_URL
planned
Moves the ledger from local JSON to Postgres.
Future hardening step.
REDIS_URL
planned
Runs scheduled jobs, retries, and background queues.
Future hardening step.
Operational Views
Local Telegram Simulation
Use this after TELEGRAM_ALLOWED_USER_IDS is filled and the API is restarted.
Invoke-RestMethod http://localhost:4200/dev/command -Method Post -ContentType 'application/json' -Body '{"text":"/status","userId":123}'