Skip to main content
The main happy command starts Claude Code with mobile control capabilities, allowing you to interact with Claude from your mobile device and manage sessions remotely.

​
Syntax

happy [options]

​
Description

Happy wraps Claude Code to enable:
  • Remote control from mobile devices
  • Session persistence and resumption
  • Background daemon management
  • Mobile notifications
  • End-to-end encrypted communication
Happy supports ALL Claude Code options! Any flag you can use with claude works with happy.

​
Options

​
--help
flag
Show help information including both Happy and Claude Code options
​
--version
flag
Display Happy CLI version information
​
--yolo
flag
Shortcut for --dangerously-skip-permissions. Bypasses all permission prompts (use with caution)
​
--chrome
flag
Enable Chrome browser access for this session. Allows Claude to control your browser
​
--no-chrome
flag
Disable Chrome even if it’s enabled by default in settings
​
--no-sandbox
flag
Disable Happy sandbox for this session. Useful when you need unrestricted file system access
​
--js-runtime
string
JavaScript runtime to use for spawning Claude Code. Options: node (default) or bun
happy --js-runtime bun
​
--claude-env
string
Pass environment variables to Claude in KEY=VALUE format. Can be used multiple times
happy --claude-env ANTHROPIC_BASE_URL=http://127.0.0.1:3456
​
--happy-starting-mode
string
Internal flag for Happy daemon. Options: local or remote. Not typically used directly by users
​
--started-by
string
Internal flag indicating session origin. Options: daemon or terminal. Not typically used directly by users
The --settings flag is reserved by Happy for session tracking. Your custom settings file will be ignored. Configure Claude via ~/.claude/settings.json instead.

​
Claude Code Options

Happy passes all unknown flags directly to Claude Code. Popular options include:
​
--resume
string
Resume a previous Claude session by session ID
happy --resume aada10c6-9299-4c45-abc4-91db9c0f935d
​
--dangerously-skip-permissions
flag
Skip all permission prompts (use --yolo for short)
​
--print
flag
Print mode for non-interactive usage
​
--output-format
string
Output format for print mode. Options: stream-json, text
​
--verbose
flag
Enable verbose logging from Claude Code

​
Examples

​
Start a Basic Session

happy
Starts Claude Code with mobile control enabled.

​
Start with Permission Bypass

happy --yolo
Starts Claude without permission prompts (equivalent to --dangerously-skip-permissions).

​
Enable Browser Access

happy --chrome
Allows Claude to interact with your Chrome browser.

​
Use Custom API Endpoint

happy --claude-env ANTHROPIC_BASE_URL=http://127.0.0.1:3456
Useful for routing Claude requests through a local proxy or custom endpoint.

​
Resume Previous Session

happy --resume aada10c6-9299-4c45-abc4-91db9c0f935d
Continues a previous Claude session. The session ID can be found in Claude’s session files.

​
Use Bun Runtime

happy --js-runtime bun
Spawns Claude Code using Bun instead of Node.js for potentially faster startup.

​
Disable Sandbox

happy --no-sandbox
Disables Happy’s OS-level sandboxing for this session.

​
Combine Multiple Options

happy --chrome --yolo --js-runtime bun
Starts Claude with browser access, no permission prompts, using Bun runtime.

​
Output

When you start Happy, you’ll see: 
Authentication Status
✓ Authenticated

Daemon Status
✓ Daemon is running

Starting Claude Code session...
[Claude Code interface appears]
The Happy daemon runs in the background and automatically manages:
  • Session persistence
  • Mobile notifications
  • Remote control connections
  • Keep-alive signals

​
Session Files

Claude sessions are stored in:
  • ~/.claude/projects/<project-hash>/<session-id>.jsonl
Happy configuration is stored in:
  • ~/.happy/ (production) or ~/.happy-dev/ (development)

​
Background Daemon

The Happy daemon automatically starts when you run any Happy command. To manage it manually: 
happy daemon start   # Start daemon
happy daemon stop    # Stop daemon
happy daemon status  # Check daemon status
See happy daemon for more details.
Happy requires authentication before starting sessions. Run happy auth login if you haven’t authenticated yet.