zhang-guiping 0ad58848b3 fix(telegram): stop duplicate fallback when dispatch fails after final reply ...

Telegram no longer sends a generic "Something went wrong" fallback after a
final answer was already delivered and a later dispatch/cleanup step failed.
Failures with only partial or no visible output still send the error fallback
and stay retryable.

Related: #87299
Closes #90152

2026-07-03 09:37:48 -07:00

..

src

fix(telegram): stop duplicate fallback when dispatch fails after final reply

2026-07-03 09:37:48 -07:00

account-inspect-api.ts

…

AGENTS.md

docs(telegram): document group history removal

2026-07-02 09:22:59 -07:00

allow-from.ts

…

api.test.ts

…

api.ts

…

channel-config-api.test.ts

…

channel-config-api.ts

…

channel-plugin-api.ts

…

CLAUDE.md

docs(telegram): move maintainer decisions into scoped AGENTS.md

2026-07-01 17:19:16 -07:00

config-api.ts

…

configured-state.ts

…

contract-api.ts

…

directory-contract-api.ts

…

doctor-contract-api.ts

…

index.test.ts

…

index.ts

…

legacy-state-migrations-api.ts

…

openclaw.plugin.json

…

package.json

chore(release): close out 2026.6.11 on main

2026-06-30 11:31:08 -07:00

runtime-api.ts

…

runtime-setter-api.ts

…

secret-contract-api.ts

…

security-audit-contract-api.ts

…

session-binding-contract-api.ts

…

session-key-api.ts

…

setup-entry.ts

…

setup-plugin-api.ts

…

test-api.ts

…

tsconfig.json

…

update-offset-runtime-api.ts

…