Skip to content

[Resource]: claude-ops bash dashboard #778

@sarob

Description

@sarob

Display Name

claude-ops bash dashboard for managing Claude Code's operational files

Category

Tooling

Sub-Category

Tooling: Config Managers

Primary Link

https://github.com/sarob/claude-ops

Author Name

sarob

Author Link

https://github.com/sarob

License

MIT

Other License

No response

Description

Zero-dependency bash dashboard for managing Claude Code's operational files across all projects. Shows where CLAUDE.md, MEMORY.md, and conversation logs live, tracks memory coverage per project, and provides interactive log cleanup with safety checks. Single script, no install required.

Validate Claims

Download the script and run ./claude_ops.sh status to see a summary of all Claude Code projects with memory coverage indicators and log sizes. Run ./claude_ops.sh files to see the full path of every CLAUDE.md and MEMORY.md file across your projects. Run ./claude_ops.sh clean --dry to preview log cleanup without deleting anything.

Specific Task(s)

Run ./claude_ops.sh with no arguments to see the full dashboard report covering project status, file locations, and conversation log details across all Claude Code projects on your machine.

Specific Prompt(s)

No Claude Code prompts needed — this is a standalone bash script. Run ./claude_ops.sh in your terminal to see the dashboard. Run ./claude_ops.sh files to list all CLAUDE.md and MEMORY.md locations. Run ./claude_ops.sh clean --dry to preview log cleanup.

Additional Comments

Built to solve the problem of Claude Code scattering files across ~/.claude/ with no easy way to see what exists where. Particularly useful when managing multiple projects. macOS only currently (uses stat -f for file sizes) — Linux PR welcome.

Recommendation Checklist

  • I have checked that this resource hasn't already been submitted
  • My resource provides genuine value to Claude Code users, and any risks are clearly stated
  • All provided links are working and publicly accessible
  • I am submitting only ONE resource in this issue
  • I understand that low-quality or duplicate submissions may be rejected

Metadata

Metadata

Assignees

No one assigned

    Labels

    resource-submissionThis Issue submits a new resource to the listvalidation-passedResource has passed initial validation

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions