Dazzle Claude Plugins
Add hook-based session logging, auto-named sesslog folders, transcript symlinks, and slash commands so you can audit what Claude Code did across runs.
Overview
dazzle-claude-plugins is a plugin marketplace for the Build phase that adds Claude Code session logging, transcript symlinks, and session management commands.
What is this marketplace?
- Hook-based persistent tool-call logs per session under ~/.claude/sesslogs/
- Auto session naming from working directory plus /renameAI for AI-assisted titles
- transcript.jsonl symlinks inside sesslog folders for fast transcript discovery
- Run markers and task-operation logging for TaskCreate, TaskUpdate, and TaskList
- /sessioninfo command to inspect current session state from Claude Code
- Marketplace bundle lists 1 plugin (claude-session-logger)
- Logs stored under ~/.claude/sesslogs/ per README
- GPL v3 licensed; Python 3.9+ stated platform requirement
Community signal: 4 GitHub stars.
What problem does it solve?
Agent sessions vanish into opaque transcripts and unnamed runs, making it hard for a solo builder to replay tool history, compare attempts, or prove what shipped in a review.
Who is it for?
Builders who run long or repeated Claude Code sessions and want local, file-based session forensics without a separate SaaS logger.
Skip if: Teams that require centralized cloud audit with RBAC or who never revisit past agent transcripts after a task completes.
What do I get? / Deliverables
You get named sesslog directories with tool logs, run tracking, and symlinked transcripts plus /sessioninfo and /renameAI for repeatable session hygiene.
- Per-session tool-call log files with auto-derived session names
- transcript.jsonl symlinks co-located with session log directories
- Slash commands /renameAI and /sessioninfo for naming and inspection
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Build is the canonical shelf because the extension installs Claude Code hooks and commands that shape how you work in-repo day to day, before you rely on logs for post-ship forensics. Agent-tooling captures sesslogs under ~/.claude/sesslogs/, TaskCreate logging, /renameAI, and /sessioninfo—infra around the agent, not your product binary.
How it compares
Hook-based Claude Code logging marketplace, not a hosted analytics dashboard or generic note-taking skill.
Common Questions / FAQ
Who is Dazzle Claude Plugins for?
It is for developers on Claude Code who need persistent sesslogs, transcript links, and commands to rename or inspect sessions during indie shipping workflows.
When should I use Dazzle Claude Plugins?
Use it when you run multi-run sessions, task lists via Claude tools, or pre-merge reviews where a local JSONL trail saves debugging time.
How do I add Dazzle Claude Plugins to my agent?
Follow the GitHub quick start: add the DazzleML marketplace plugin bundle, install claude-session-logger hooks per README, and confirm logs appear under ~/.claude/sesslogs/.