Catalog/Goose

Transcripts

Goose

Goose records agent sessions as JSONL under its config directory (secrets default to the OS keyring, not a file).

Block Linux · macOS · Windows files

Exposure

High
Stores found
1
Holds
personal data · source code
Confidence
likely

Where it writes

1 store in the current signature database. Paths shown for a typical macOS install.

Transcripts high

files may hold personal data · source code

  • all OSes ~/.config/goose/sessionsdir
  • all OSes ~/.local/share/goose/sessionsdir

Goose records agent sessions as JSONL under its config directory (secrets default to the OS keyring, not a file).

  • Prune ~/.config/goose/sessions to limit local retention.

Source: goose-docs.ai

What to do about it

PromptDust flags these stores and leaves them in place; cleanup is your call. If a store holds a live secret, rotate the secret first, since deleting the file won’t un-leak a key that already sat in plain text.

For ongoing work, keep sensitive material out of sessions where you can, and prune old transcripts and caches now and then.

This describes where Goose stores data. Metadata only, never your content. Confidence: likely. Spot a mistake? Tell us.

See if this one’s on your machine.

One pass finds every store, for this tool and the other 51.