docs: record timmy openclaw telegram path
This commit is contained in:
@@ -181,6 +181,26 @@ Interpretation:
|
||||
- they can post into the group successfully
|
||||
- the group now contains a real multi-bot discussion among Timmy, Ezra, and Bezalel
|
||||
|
||||
### Timmy streamlined channel note
|
||||
|
||||
Timmy now wears OpenClaw on the local Telegram path.
|
||||
|
||||
Proof:
|
||||
- `openclaw channels add --channel telegram ...` succeeded and added the Timmy bot to OpenClaw config
|
||||
- `openclaw channels status --json --probe` now reports Telegram as:
|
||||
- `configured: true`
|
||||
- `running: true`
|
||||
- probe `ok: true`
|
||||
- bot username `TimmysNexus_bot`
|
||||
- OpenClaw logs show:
|
||||
- Telegram provider start for `@TimmysNexus_bot`
|
||||
- a DM pairing request from Alexander's Telegram user (`7635059073`)
|
||||
- pairing approval recorded after explicit approval
|
||||
|
||||
Important behavior note:
|
||||
- OpenClaw is now the streamlined DM path for Timmy
|
||||
- group replies are still blocked by OpenClaw's current group policy (`reason: not-allowed`), so DM is the clean path until group policy is deliberately relaxed
|
||||
|
||||
Four-party discussion proof:
|
||||
- Alexander posted into the group during validation, including messages:
|
||||
- `255` — greeting / roll call
|
||||
|
||||
Reference in New Issue
Block a user