Adding Telegram cloud agents (chat bots over Telegram) surfaced that workforce's consumed catalogs don't know telegram yet. The telegram adapter, trigger/scope/writeback catalogs, and generated client all live in relayfile-adapters (tracked in AgentWorkforce/relayfile-adapters#222) — workforce just needs to pick them up.
What's missing today
packages/persona-kit pins @relayfile/adapter-core: ^0.3.60, and the installed adapter-core has no telegram in its trigger/scope catalogs (grep telegram node_modules/@relayfile/adapter-core/dist → empty). So KNOWN_TRIGGER_CATALOG / KNOWN_SCOPE_KEY_CATALOG (re-exported by persona-kit) don't include telegram.- Downstream consumers therefore treat telegram as unknown:
packages/cli/src/invoke-command.ts:467-479 warns provider "telegram" is not in KNOWN_TRIGGER_CATALOG … scaffolding anyway and can't validate the event name.packages/deploy/src/integrations-list.ts:231,413 won't surface telegram triggers in the integrations list.- persona authoring (
triggers.telegram, integrations.telegram.scope) only type-checks via persona-kit's [provider: string] index-signature fallback — no real validation/autocomplete.
Ask
Once relayfile-adapters#222 publishes telegram in @relayfile/adapter-core (+ the generated telegramClient in @relayfile/relay-helpers):
- Bump
@relayfile/adapter-core (and @relayfile/relay-helpers if pinned) across persona-kit / deploy / cli / runtime to the telegram-aware version.
- Verify the catalogs propagate:
KNOWN_TRIGGER_CATALOG.telegram (message/edited_message/callback_query/…), telegram scope keys, and the messages/reactions writeback resources resolve.
- Re-run the trigger-autocomplete coverage / drift check (persona-nango-integrations) so telegram is covered.
No new telegram-specific code is expected in workforce — it's a catalog/dependency cutover (same shape as prior adapter-core cutovers). Blocked on relayfile-adapters#222.
Context: adding Telegram variants of inbox-buddy / joke-bot / spotify-releases / hn-monitor in AgentWorkforce/agents.
Adding Telegram cloud agents (chat bots over Telegram) surfaced that workforce's consumed catalogs don't know telegram yet. The telegram adapter, trigger/scope/writeback catalogs, and generated client all live in relayfile-adapters (tracked in AgentWorkforce/relayfile-adapters#222) — workforce just needs to pick them up.
What's missing today
packages/persona-kitpins@relayfile/adapter-core: ^0.3.60, and the installed adapter-core has no telegram in its trigger/scope catalogs (grep telegram node_modules/@relayfile/adapter-core/dist→ empty). SoKNOWN_TRIGGER_CATALOG/KNOWN_SCOPE_KEY_CATALOG(re-exported by persona-kit) don't include telegram.packages/cli/src/invoke-command.ts:467-479warnsprovider "telegram" is not in KNOWN_TRIGGER_CATALOG … scaffolding anywayand can't validate the event name.packages/deploy/src/integrations-list.ts:231,413won't surface telegram triggers in the integrations list.triggers.telegram,integrations.telegram.scope) only type-checks via persona-kit's[provider: string]index-signature fallback — no real validation/autocomplete.Ask
Once relayfile-adapters#222 publishes telegram in
@relayfile/adapter-core(+ the generatedtelegramClientin@relayfile/relay-helpers):@relayfile/adapter-core(and@relayfile/relay-helpersif pinned) acrosspersona-kit/deploy/cli/runtimeto the telegram-aware version.KNOWN_TRIGGER_CATALOG.telegram(message/edited_message/callback_query/…), telegram scope keys, and themessages/reactionswriteback resources resolve.No new telegram-specific code is expected in workforce — it's a catalog/dependency cutover (same shape as prior adapter-core cutovers). Blocked on relayfile-adapters#222.
Context: adding Telegram variants of inbox-buddy / joke-bot / spotify-releases / hn-monitor in AgentWorkforce/agents.