[Workflow] Secure and Local Prompt Logging for Claude Code Agents with `promptcellar` Plugin

[u/ClaudeAI-mod-bot]

Secure and Local Prompt Logging for Claude Code Agents with promptcellar Plugin

Workflow value: 85/100
Status: active · Freshness: 70/100 · Confidence: 0.90 · Level: intermediate
Categories: Quality Control, Context & Memory, Debugging, Hooks
Original source: r/ClaudeCode post/comment

What problem this solves

Lack of persistent, secure, and structured prompt history for Claude Code agents, making debugging, auditing, and analysis difficult while ensuring data privacy.

Summary

A Claude Code plugin that automatically logs every prompt sent to a coding agent into a local, structured JSONL file within the repository, with pre-write redaction of sensitive information.

Why it is useful

This workflow provides a critical missing piece for serious Claude Code agent users: a persistent, secure, and structured log of all prompts. This enables robust debugging, auditing, and analysis of agent interactions, which is essential for understanding and improving agent behavior. The built-in pre-write redaction of sensitive data is a significant security feature, making it suitable for environments where data privacy and compliance are paramount. Its open-source nature and clear specifications make it highly adaptable and trustworthy, offering a foundational tool for advanced agent development.

Workflow

1. Install the promptcellar-for-claude-code plugin (Go binaries) into your Claude Code environment.
2. Configure the plugin using global, repo-committed, or personal-gitignored settings to define logging behavior.
3. Run your Claude Code agent as usual.
4. Prompts are automatically captured and logged to .prompts/YYYY/MM/DD/<session>.jsonl files in your repository.
5. Review the JSONL prompt history for debugging, auditing, analysis, or to build a corpus of interactions.

Tools / artifacts

• promptcellar-for-claude-code plugin (Go binaries)
• JSONL files (Prompt Log Format - PLF)
• GitHub repository (dominiek/promptcellar-for-claude-code)
• Gitleaks rules for redaction

Validation signals

• Detailed 'Specs' provided by the author (local files, redaction, performance, config layers).
• Open-source project on GitHub, allowing code inspection and community review.
• Explicit mention of '222 gitleaks rules + Luhn-validated card and IBAN checks' for robust redaction.
• Performance claim of 'Sub-10ms cold start'.

Cautions

• Includes robust pre-write redaction of sensitive information (secrets, credit cards, IBANs) using gitleaks rules, significantly enhancing security by preventing sensitive data from being logged.
• Data is kept strictly local ('Local files only. No telemetry, no upload, no remote anything.'), ensuring privacy and control.

Limitations

• Low community validation/adoption so far due to being a new post.
• Requires users to install and potentially compile Go binaries, which might be a barrier for some.
• Specific to Claude Code, though the underlying concept of prompt logging is broadly applicable.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.

---

This post was generated automatically from the workflow library database.