npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

renard

v1.0.8

Published

Sync LLM CLI interactions

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

neekunjchaturvedineekunjchaturvedi

Keywords

llmcliclaudeopenaigeminideveloper-toolsai

Readme

Renard CLI 🦊

Renard tracks your LLM CLI interactions, giving you visibility into how you work with AI coding assistants.

Quick Start

# Install globally
npm install -g renard

#Test run in terminal to check if renard was installed
renard

# Login to your Renard account
renard login

# Hook supported CLI tools
renard install

#If cli tool is installed globally use
sudo renard install

That's it! Your Claude, Codex, and Gemini sessions are now tracked automatically.

Supported Tools

| Tool | Package | Status | | -------------- | -------------------------- | --------------- | | Claude | @anthropic-ai/claude-cli | ✅ Full support | | Codex (OpenAI) | @openai/codex | ✅ Full support | | Gemini | @google/gemini-cli | ✅ Full support |

Commands

Authentication

renard login          # Authenticate with Renard
renard logout         # Clear authentication

Installation

sudo renard install   # Hook CLI tools (requires sudo for global installs)
sudo renard uninstall # Restore original CLIs
renard status         # Show which CLIs are tracked

Logs

renard logs           # View collected logs
renard logs --last 20 # View last 20 entries
renard clear          # Clear all local logs

Upload

renard upload         # Upload pending logs to server

Use this if your session expired during a CLI session. Renard saves logs locally and you can upload them after re-authenticating.

Workspaces

renard workspace      # List all workspaces
renard workspace 2    # Switch to workspace #2

How It Works

  1. Install hooks your CLI tools by replacing them with lightweight shims
  2. Shims intercept CLI launches and notify Renard
  3. On exit, Renard reads conversation history directly from each tool's storage:
    • Claude: ~/.claude/projects/ and ~/.claude/history.jsonl
    • Codex: ~/.codex/history.jsonl and ~/.codex/sessions/
    • Gemini: ~/.gemini/tmp/*/chats/
  4. Upload sends only new messages to the Renard backend
  5. Local logs are kept in ~/.renard/logs.jsonl

Handling Expired Sessions

If your auth token expires while using a CLI tool:

[Renard] Session expired. Please run 'renard login' to re-authenticate.
[Renard] Your logs are saved. Run 'renard upload' after logging in.

Your logs are safe in ~/.renard/logs2upload.jsonl. Just run:

renard login    # Re-authenticate
renard upload   # Upload pending logs

Troubleshooting

"Permission denied" during install

CLI tools installed globally (with npm install -g) require sudo:

sudo renard install

Tool shows "not found in PATH"

Make sure the CLI tool is installed:

npm install -g @anthropic-ai/claude-cli   # Claude
npm install -g @openai/codex              # Codex
npm install -g @google/gemini-cli         # Gemini

Different tools need different permissions

  • Tools in /usr/local/bin/ (global installs) → need sudo
  • Tools in ~/.local/bin/ (user installs) → no sudo needed

Run renard install without sudo first, then sudo renard install for global tools.

Privacy

  • Only developer-context data (prompts, responses, tool metadata) is captured
  • Sensitive or unrelated data is automatically rejected by the backend
  • Local logs are stored in ~/.renard/ and you control what gets uploaded

Links