Skip to content

Scan session content for secrets before share and export #190

Description

@samzong

Not urgent. Tracked after a competitor pass: AgentsView persists secret_findings on the archive; Recall publishes selected sessions to Cloudflare Pages via recall session share and can emit full transcripts with recall export / session export.

Why

Share and export already send session text off the local index. Transcripts routinely contain pasted tokens, .env fragments, and hook output. A scan here is a liability gate, not a new security product.

Scope (when we pick this up)

  • Run a small local pattern scan on the selected session (and export batch) before publish/write.
  • On a hit: refuse, or redact and report the hit class in the command JSON. Do not upload raw secrets.
  • Apply on the share path first (src/share/publish.rs / session share). Export is the same gate if the scan stays cheap.
  • Keep it deterministic and offline. No cloud classifier.

Out of scope

  • A standalone recall secrets product or persisted findings table.
  • Claiming the output is scrubbed for forwarding to other people.
  • Changing share target / Pages setup.

Notes

docs/trace.md Privacy section says personal-only surfaces should not pretend to redact. That still holds for recall trace / session show. This issue is only about leaving the machine (Pages publish and files written for export).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions