Conversation summary is persisted outside the workspace in an OS temporary directory
Source references: 3The Skill explicitly writes the current conversation to a file in the operating system's temporary directory. Although it requires redaction of API keys, passwords, and personally identifiable information, the conversation may contain confidential business details, internal paths, or artifact URLs that are not covered by those examples or are not recognized correctly. The supplied source does not specify the file's exact location, access permissions, or cleanup time.
After invocation, project context may remain somewhere the user would not normally review or clean with the project. If another local process or user can read the temporary file, or if it is retained, information in the summary could be exposed.
The Skill requires explicit invocation, but once invoked it writes a summary of the current conversation to the OS temporary directory rather than the workspace. The summary may also reference artifact paths or URLs. Although API keys, passwords, and personally identifiable information must be redacted, the source does not specify the exact file location, permissions, retention period, or protection for other business-confidential material. This creates a plausible risk that another local user or later process could read the residual summary. A user can ask the author to document permissions and automatic cleanup, or restrict included content and require a controlled destination.
Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the temporary directory of the user's OS - not the current workspace.Show 2 other places
Do not duplicate content already captured in other artifacts (specs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.Redact any sensitive information, such as API keys, passwords, or personally identifiable information. short_description: "Compact a conversation into a handoff"policy: allow_implicit_invocation: false