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

@olivierbelaud/claude-copilote

v0.7.0

Published

Autonomous product copilote for Claude Code — one CLI, N projects, self-healing.

Downloads

832

Readme

@olivierbelaud/claude-copilote

Autonomous product copilote for Claude Code. One CLI, N projects, self-healing.

Philosophy

  • Claude Code runs continuously on a project, owns it, ships real user-value only.
  • You (the human) do product vision, nothing else.
  • One persistent session per project, orchestrated via filesystem state.
  • A meta-Claude on top orchestrates all projects from a single window.

Install

npm install -g @olivierbelaud/claude-copilote
# or
bun install -g @olivierbelaud/claude-copilote

Quick start

cd /path/to/your/project
copilote init --kind code     # or orga, mixed
copilote install              # registers a launchd/systemd service
# That's it — the daemon ticks autonomously from here.

copilote logs                 # follow the journal
copilote digest               # latest daily report
copilote proposals            # pending actions awaiting your OK

Provision a fresh VPS

Idempotent bootstrap of Bun + Node + claude CLI + Bitwarden CLI + ufw + fail2ban:

# Source repo is private — copy the script from your local clone:
scp ~/path/to/claude-copilote/scripts/provision-vps.sh user@vps:~/
ssh user@vps 'bash ~/provision-vps.sh'

Commands

| Command | Purpose | |---|---| | init [--name <slug>] | Register the current directory as a copilote project | | start [--force] [--effort <level>] | Launch (or force-launch) the autonomous session | | stop | HALT the runner (kill switch) | | status [project] | Show current state (one project, or all) | | cost [project] [--top N] | Per-action cost breakdown | | logs [project] [--tail] | Tail the journal | | list | List all registered projects | | meta | Launch meta-Claude (single conversational window across N projects) | | install-cron | Install the platform scheduler (launchd on mac, systemd on linux) | | uninstall-cron | Remove the scheduler |

Cross-platform

  • macOS: launchd agents at ~/Library/LaunchAgents/copilote.*.plist
  • Linux (VPS): systemd user timers at ~/.config/systemd/user/copilote-*.timer

The CLI detects the platform and generates the right unit. No manual config.

State layout

~/.claude-copilote/
├── engine/                    # shared runtime (runner, watchdog, cost, …)
├── templates/                 # prompt + actions defaults
├── projects/
│   ├── <project-slug>/
│   │   ├── config.json        # budget, code_path, stop window, session_id
│   │   ├── system-prompt.md   # copilote's identity (editable per project)
│   │   ├── actions.md         # action menu (editable)
│   │   ├── state.md           # live working memory
│   │   ├── inbox/ outbox/ journal/ budget/
│   │   └── ...
└── meta/                      # meta-Claude's workspace
    ├── CLAUDE.md
    ├── inbox/ outbox/
    └── state.md

Nothing from this package ever lands in your project's git. The only touch is adding a short snippet to your project's CLAUDE.md explaining how to invoke the CLI — purely documentation.

Status

V0.1 — scaffold / WIP. Wraps the bash engine proven on PALAS OMS (24h of autonomous shipping, 25 commits). Progressive TS port planned.

Architecture

See ARCHITECTURE.md (TBD).