Skip to content

Discord component callback TTL should be configurable #84184

@100menotu001

Description

@100menotu001

Summary

Discord component callback registry entries currently use a fixed 30-minute TTL with no account-level configuration escape hatch.

Current behavior

The component registry accepts a TTL parameter internally, but normal Discord component sends do not expose a supported configuration field to change it. Workflows that need longer-lived review buttons must fit into the hard-coded default.

Expected behavior

Discord config should support a bounded agentComponents.ttlMs value, preserve the current 30-minute default when unset, and pass the configured TTL into component registry registration for sends and edits.

Why this matters

Some action-card workflows are intentionally asynchronous and may be reviewed well after the first 30 minutes. A bounded configuration field gives operators an explicit, documented choice without changing defaults.

Suggested scope

Keep this focused:

  • Add config type/schema support for a bounded TTL.
  • Add a UI hint for the setting.
  • Pass the resolved account TTL into component registration.
  • Cover config validation and send-path propagation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.clawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.issue-rating: 🌊 off-meta tidepoolIssue quality rating does not apply to this item.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions