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

ozaiya-cli

v0.10.4

Published

Ozaiya agent daemon - server management and terminal

Readme

Ozaiya CLI

Control Claude Code remotely from your mobile device.

Free. Open source. Code anywhere.

Installation

npm install -g ozaiya-cli

Quick Start

# Authenticate
ozaiya auth login

# Start daemon
ozaiya daemon start

# Check status
ozaiya daemon status

This will:

  1. Authenticate with your Ozaiya account
  2. Start the background daemon
  3. Register your machine with the Ozaiya server
  4. Allow remote control from the Ozaiya mobile app

Commands

Authentication

ozaiya auth login          # Authenticate with Ozaiya server
ozaiya auth login --force  # Force re-authentication
ozaiya auth status         # Check authentication status

Daemon Management

ozaiya daemon start    # Start background daemon
ozaiya daemon stop     # Stop background daemon
ozaiya daemon status   # Check daemon status

Session Management

ozaiya                 # Start an interactive Claude session
ozaiya --help          # Show available options

Configuration

Environment Variables

  • OZAIYA_SERVER_URL - Server URL (default: https://api.ozaiya.dev)
  • OZAIYA_HOME_DIR - Home directory for Ozaiya data (default: ~/.ozaiya)
  • OZAIYA_WEBAPP_URL - Web app URL (default: https://app.ozaiya.dev)

Local Development Setup

For local development with a local server:

Option 1: Shell Configuration (Recommended)

Add to your ~/.zshrc or ~/.bashrc:

# Ozaiya CLI - Use local development server
export OZAIYA_HOME_DIR=~/.ozaiya-dev
export OZAIYA_SERVER_URL=http://localhost:3007

Then reload your shell:

source ~/.zshrc  # or source ~/.bashrc

Now you can use commands normally:

ozaiya daemon start
ozaiya daemon status
ozaiya auth login

Option 2: Per-Command Configuration

Use environment variables for individual commands:

OZAIYA_HOME_DIR=~/.ozaiya-dev OZAIYA_SERVER_URL=http://localhost:3007 ozaiya daemon start

Option 3: Using .env File

The CLI supports --env-file flag:

node --env-file=.env.dev-local-server ./bin/ozaiya.mjs daemon start

Example .env.dev-local-server:

OZAIYA_HOME_DIR=~/.ozaiya-dev
OZAIYA_SERVER_URL=http://localhost:3007
OZAIYA_WEBAPP_URL=http://localhost:8081

Development vs Production

| Configuration | Data Directory | Server URL | |--------------|----------------|------------| | Production (default) | ~/.ozaiya | https://api.ozaiya.dev | | Local Development | ~/.ozaiya-dev | http://localhost:3007 |

Important: Always use the same configuration for authentication and daemon commands. If you authenticate with local server config, you must start the daemon with the same config.

Troubleshooting

Daemon Won't Start

Check if daemon is already running:

ozaiya daemon status
ps aux | grep "ozaiya.*daemon"

If zombie process exists, kill it:

kill <PID>

Authentication Issues

Clear credentials and re-authenticate:

ozaiya auth login --force

Machine Not Showing in App

  1. Check daemon is running: ozaiya daemon status
  2. Check server URL matches: echo $OZAIYA_SERVER_URL
  3. Check daemon logs: ~/.ozaiya-dev/logs/ or ~/.ozaiya/logs/

Requirements

  • Node.js >= 20.0.0
  • Claude CLI installed & logged in (claude command available in PATH)

Development

See CLAUDE.md for detailed development documentation.

Credits

Based on happy by Happy Coder Contributors.

License

MIT