Agent transcript holding a secret
Open
@kekubhai is already working on this.
Since Sep 9, 2026.
New Challenge
- Dominant language
- HTML
- Stars
- 1.5k
- Forks
- 625
- Avg merge
- 14h 21m
- Merged PRs (30d)
- 44
Description
Context
- What should the challenge scenario be like?
Coding-agent session transcripts: tools like Claude Code, Cursor, and Aider can leave local session/history files behind. A secret pasted during debugging can end up in one of these files and later get committed or included in a support bundle. Different from a shared-chat leak because the local artifact is the problem. - What should the participant learn from completing the challenge?
reveiw transcripts before saving them, AI can make mistakes. - For what category would the challenge be? (e.g. Docker, K8s, binary)
AI
Did you encounter this in real life? Could you tell us more about the scenario?
Yes
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.