JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 309
  • Score
    100M100P100Q90991F
  • License MIT

Ozaiya agent daemon - server management and terminal

Package Exports

  • ozaiya-cli
  • ozaiya-cli/codex/ozaiyaMcpStdioBridge
  • ozaiya-cli/lib
  • ozaiya-cli/socket-worker

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

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