Allow session archive/pin/move actions to be permission-scoped (not per-call approval)

Status Open
Maintainer reply None cached
Activity 0 comments · opened Sep 10, 2026

Problem

Session-management tools (archive_session, and pin/move-to-folder where they exist) require an
approval dialog on every single call, with no way to allow-list them — even for calls a Claude
session is making on the user's own explicit, standing instruction (e.g. an automation the user
asked for).

This makes any "clean up my sessions" workflow impractical at scale. Concretely: I run scheduled
automations that create a new sidebar session on every run (e.g. a Discord monitor firing every
15–60 min). Over a few days this produces hundreds of sessions. I asked Claude to have each one
archive itself when done — but archiving prompts every time, no bypass. In one real case the user
had to manually approve ~15 archive prompts in a row and said it wasn't sustainable. The workaround
that exists today is a blunt, global "auto-archive after N days of inactivity" setting — it works,
but it's a timer, not a decision, and it can't selectively pin, rename-and-file, or archive based on
content the way an agent reasonably could.

Ask

Allow session management actions — archive, pin/unpin, move to folder — to be permission-scoped
like other tool calls: allow-listable in settings.json, or auto-approved in an unattended/automation
context the same way other tool calls can be. At minimum, a batch/bulk variant that asks once for N
sessions instead of N times.

Why it matters

Without this, the only two options are (a) manually approve every single archive click, which does
not scale past a handful of sessions, or (b) leave the sidebar to accumulate hundreds of stale
sessions until a blunt time-based sweep clears them. Neither is a real "manage my own sessions"
workflow — it's either constant manual approval or no real control at all.

View original on GitHub ↗