`fluffbuzz sessions`

List stored conversation sessions.

fluffbuzz sessions
fluffbuzz sessions --agent work
fluffbuzz sessions --all-agents
fluffbuzz sessions --active 120
fluffbuzz sessions --verbose
fluffbuzz sessions --json

Scope selection:

default: configured default agent store
--verbose: verbose logging
--agent <id>: one configured agent store
--all-agents: aggregate all configured agent stores
--store <path>: explicit store path (cannot be combined with --agent or --all-agents)

fluffbuzz sessions --all-agents reads configured agent stores. Gateway and ACP session discovery are broader: they also include disk-only stores found under the default agents/ root or a templated session.store root. Those discovered stores must resolve to regular sessions.json files inside the agent root; symlinks and out-of-root paths are skipped. JSON examples: fluffbuzz sessions --all-agents --json:

{
  "path": null,
  "stores": [
    { "agentId": "main", "path": "/home/user/.fluffbuzz/agents/main/sessions/sessions.json" },
    { "agentId": "work", "path": "/home/user/.fluffbuzz/agents/work/sessions/sessions.json" }
  ],
  "allAgents": true,
  "count": 2,
  "activeMinutes": null,
  "sessions": [
    { "agentId": "main", "key": "agent:main:main", "model": "gpt-5" },
    { "agentId": "work", "key": "agent:work:main", "model": "claude-opus-4-6" }
  ]
}

Cleanup maintenance

Run maintenance now (instead of waiting for the next write cycle):

fluffbuzz sessions cleanup --dry-run
fluffbuzz sessions cleanup --agent work --dry-run
fluffbuzz sessions cleanup --all-agents --dry-run
fluffbuzz sessions cleanup --enforce
fluffbuzz sessions cleanup --enforce --active-key "agent:main:telegram:direct:123"
fluffbuzz sessions cleanup --json

fluffbuzz sessions cleanup uses session.maintenance settings from config:

Scope note: fluffbuzz sessions cleanup maintains session stores/transcripts only. It does not prune cron run logs (cron/runs/<jobId>.jsonl), which are managed by cron.runLog.maxBytes and cron.runLog.keepLines in Cron configuration and explained in Cron maintenance.
--dry-run: preview how many entries would be pruned/capped without writing.
- In text mode, dry-run prints a per-session action table (Action, Key, Age, Model, Flags) so you can see what would be kept vs removed.
--enforce: apply maintenance even when session.maintenance.mode is warn.
--fix-missing: remove entries whose transcript files are missing, even if they would not normally age/count out yet.
--active-key <key>: protect a specific active key from disk-budget eviction.
--agent <id>: run cleanup for one configured agent store.
--all-agents: run cleanup for all configured agent stores.
--store <path>: run against a specific sessions.json file.
--json: print a JSON summary. With --all-agents, output includes one summary per store.

fluffbuzz sessions cleanup --all-agents --dry-run --json:

{
  "allAgents": true,
  "mode": "warn",
  "dryRun": true,
  "stores": [
    {
      "agentId": "main",
      "storePath": "/home/user/.fluffbuzz/agents/main/sessions/sessions.json",
      "beforeCount": 120,
      "afterCount": 80,
      "pruned": 40,
      "capped": 0
    },
    {
      "agentId": "work",
      "storePath": "/home/user/.fluffbuzz/agents/work/sessions/sessions.json",
      "beforeCount": 18,
      "afterCount": 18,
      "pruned": 0,
      "capped": 0
    }
  ]
}

Session config: Configuration reference

CLI commands

RPC and API

Templates

Technical reference

Concept internals

Project

Release policy

Sessions

`fluffbuzz sessions`

Cleanup maintenance

​fluffbuzz sessions

​Cleanup maintenance

`fluffbuzz sessions`

Cleanup maintenance