Greptile Summary

Fixes a regression introduced between 2026.4.5 and 2026.4.8 where Telegram multi-account configs using agentId were rejected by schema validation. The fix adds agentId?: string to both TelegramAccountConfig and TelegramAccountSchemaBase, aligning the account-level schema with the already-supported topic-level field.

Confidence Score: 5/5

Safe to merge — targeted schema fix with regression test coverage and no behavioral side effects.

The only finding is a P2 style issue (new test placed in the wrong describe block). The core fix is minimal, correct, and type-consistent with the existing topic-level agentId pattern.

src/config/config.telegram-topic-agentid.test.ts — the account-level agentId regression test belongs in its own describe block.

This is a comment left during a code review.
Path: src/config/config.telegram-topic-agentid.test.ts
Line: 238-266

Comment:
**New test placed in wrong describe block**

The "accepts agentId in telegram account config (multi-account routing)" test (line 238) is nested inside `describe("telegram disableAudioPreflight schema")` (line 137), which is semantically unrelated. Consider moving it to the existing `describe("telegram topic agentId schema")` block or a dedicated new block such as `describe("telegram account agentId schema")`.

```suggestion
describe("telegram account agentId schema", () => {
  it("accepts agentId in telegram account config (multi-account routing)", () => {
```

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "fix(telegram): add agentId field to acco..." | Re-trigger Greptile}

Addressed the account-level agentId follow-up.

• route channels.telegram.accounts.<id>.agentId when no explicit binding matches
• keep explicit bindings and topic-specific agentId overrides ahead of the account default
• reject top-level channels.telegram.agentId so only per-account config accepts this field

Validated with:

• OPENCLAW_VITEST_INCLUDE_FILE=/tmp/openclaw-tests.json node scripts/run-vitest.mjs run --config test/vitest/vitest.unit-fast.config.ts

Addressed the remaining Telegram agentId type mismatch follow-up.

• keep channels.telegram.accounts.<id>.agentId in TelegramAccountConfig
• exclude agentId from the top-level TelegramConfig type so channels.telegram.agentId no longer type-checks

Validated with:

• OPENCLAW_VITEST_INCLUDE_FILE=/tmp/openclaw-tests.json node scripts/run-vitest.mjs run --config test/vitest/vitest.unit-fast.config.ts
• pnpm exec tsc -p tsconfig.telegram-types.tmp.json