Overview

This week’s posts were tightly focused on multi-tenant support. The channel shared a technical snapshot of the implementation approach, plus a short milestone update, with a light joke about Codex’s “sense of humor.”

Key Themes

• Multi-tenant implementation progress
  • Work is moving toward a tenant-aware webhook/event pipeline.
• Routing via webhook secret
  • The shared screenshot describes using Telegram’s secret header for tenant selection instead of building a more complex router.
• Schema and event changes
  • `tenant_id` is being added to the relevant `PostEvent` structures and carried through the webhook flow.
• Data consistency
  • Both `posts.tenant_id` and `chats.tenant_id` need to stay aligned to avoid mismatches.
• Compatibility
  • Existing bot behavior is described as remaining compatible, while new tenants can be onboarded with `webhook_secret`.

Notable Posts

• “codex现在幽默细胞满满啊😂”

Posted with a screenshot showing implementation notes for multi-tenant support, including:

• `webhook_secret -> tenant_id` mapping
• adding `tenant_id` to event structures
• webhook events now carrying `tenant_id`
• a planned API-side shift from “guessing tenant” to trusting the event payload

A short milestone update marking progress on the multi-tenant work.

Watchlist

• API consumer changes: switching from inferred tenant logic to event-provided `tenant_id`
• Tenant ID consistency: making sure both post and chat records are updated together
• Onboarding flow: continued use of `webhook_secret` as the tenant association mechanism