ozaiya-cli
v0.10.4
Published
Ozaiya agent daemon - server management and terminal
Maintainers
Readme
Ozaiya CLI
Control Claude Code remotely from your mobile device.
Free. Open source. Code anywhere.
Installation
npm install -g ozaiya-cliQuick Start
# Authenticate
ozaiya auth login
# Start daemon
ozaiya daemon start
# Check status
ozaiya daemon statusThis will:
- Authenticate with your Ozaiya account
- Start the background daemon
- Register your machine with the Ozaiya server
- 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 statusDaemon Management
ozaiya daemon start # Start background daemon
ozaiya daemon stop # Stop background daemon
ozaiya daemon status # Check daemon statusSession Management
ozaiya # Start an interactive Claude session
ozaiya --help # Show available optionsConfiguration
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:3007Then reload your shell:
source ~/.zshrc # or source ~/.bashrcNow you can use commands normally:
ozaiya daemon start
ozaiya daemon status
ozaiya auth loginOption 2: Per-Command Configuration
Use environment variables for individual commands:
OZAIYA_HOME_DIR=~/.ozaiya-dev OZAIYA_SERVER_URL=http://localhost:3007 ozaiya daemon startOption 3: Using .env File
The CLI supports --env-file flag:
node --env-file=.env.dev-local-server ./bin/ozaiya.mjs daemon startExample .env.dev-local-server:
OZAIYA_HOME_DIR=~/.ozaiya-dev
OZAIYA_SERVER_URL=http://localhost:3007
OZAIYA_WEBAPP_URL=http://localhost:8081Development 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 --forceMachine Not Showing in App
- Check daemon is running:
ozaiya daemon status - Check server URL matches:
echo $OZAIYA_SERVER_URL - Check daemon logs:
~/.ozaiya-dev/logs/or~/.ozaiya/logs/
Requirements
- Node.js >= 20.0.0
- Claude CLI installed & logged in (
claudecommand available in PATH)
Development
See CLAUDE.md for detailed development documentation.
Credits
Based on happy by Happy Coder Contributors.
License
MIT
