Skip to content

Centralize chat-session naming; define subagent session lifetime & cross-channel persistence #103067

Description

@karkarl

Summary

Centralize chat-session naming and define the lifetime + persistence model for agent-created (ACP/subagent) sessions.

Problems observed

  • Naming: ACP / Copilot sessions are not getting meaningful titles. Session naming is not centralized, so titles are inconsistent or absent.
  • Subagent lifetime: The lifetime of agent-created subagent sessions is undefined — when they should live, persist, or be cleaned up is unclear.
  • Cross-channel/session persistence: There is no defined model for how an agent's identity/state persists across channels and across sessions.

Goals / acceptance criteria

  • Sessions receive meaningful, consistent titles via a centralized naming mechanism.
  • Documented lifetime policy for agent-created subagent sessions.
  • Defined persistence model for an agent across channels and sessions.

Related

Context

Surfaced during chat-session review (2026-07-08). Filed on core/gateway because session identity, naming, and persistence are owned here (ACP session management), while the display surfaces in the Windows companion app.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.clawsweeper:needs-live-reproClawSweeper needs live local, crabbox, or manual validation to confirm this issue.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.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.impact:session-stateSession, memory, transcript, context, or agent state can drift or corrupt.impact:ux-frictionUser-facing flow adds avoidable confusion or support burden without fully blocking progress.issue-rating: 🐚 platinum hermitGood issue quality with a plausible reproduction path needing some confirmation.maturity:stableIssue affects a taxonomy feature currently scored M4/M5.staleMarked as stale due to inactivity

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions