Skip to content

OpenClaw: Rosie/Lenny Telegram host aliases and claimable work #3

Description

@mfethe1

What to build

Add a single-Telegram-service routing path where @rosie and @lenny explicitly target host aliases, while untagged actionable Telegram messages become claimable work that exactly one eligible host can claim and execute.

Acceptance criteria

  • Explicit @rosie and @lenny messages route through Fleet Controller host alias resolution.
  • Untagged actionable Telegram messages can be claimed by one eligible host.
  • Rosie and Lenny cannot start simultaneous Agent Runs for the same message.
  • Existing command-ref signing, delivery records, and task leases remain the authoritative execution fences.

Blocked by

None - can start immediately.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-triageMaintainer needs to evaluate this issue

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions