Delight

Delight is a small stack for running agent sessions on your computer and viewing/controlling them from an iOS app.

Delight is experimental and intended primarily for personal use.

At a high level:

• The CLI runs an agent backend (Codex, Claude, etc) in a local terminal directory and streams encrypted events.
• The server stores metadata, fans out updates over WebSockets, and coordinates pairing/authentication (it cannot read end-to-end encrypted message content).
• The iOS app pairs to a terminal, shows the transcript, and can request remote control depending on the agent + permission mode.

This repo contains all three pieces, plus shared protocol/logger libraries.

Project Goals

• Go end-to-end: keep as much of the stack as possible in Go (CLI, server, SDK bindings) for a small, auditable surface area.
• Mobile remote control: pair a terminal session to a phone UI with a tight focus on session visibility and operator control.
• AI-engineered: this project is built end-to-end with AI agents (the goal is to stay fast and iterative, not to be a polished product).

Components

• cli/README.md - CLI usage, commands, development
• server/README.md - Server configuration, local run, public hosting
• ios/README.md - iOS app build + simulator workflow

Quick Start (Local Dev)

1. Start the server:

cd server
make secret
cat > .env <<EOF
PORT=3005
DELIGHT_MASTER_SECRET=<paste-secret-from-make-secret>
DATABASE_PATH=./delight.db
DEBUG=true
EOF
make run

2. Authenticate the CLI once and start a session:

cd cli
make build
./delight auth --server-url=http://localhost:3005
./delight run --server-url=http://localhost:3005

3. Build and run the iOS app in the simulator:

make ios-run

Notifications (Pushover)

Delight can send Pushover notifications when a turn finishes or when the app needs attention (e.g. permission prompts). Notifications are emitted by the CLI, not the server, so nothing is revealed to the server: the CLI has the local context (agent, machine, directory) and the server remains blind to end-to-end encrypted payloads.

Enable Pushover by setting these environment variables:

export DELIGHT_PUSHOVER_TOKEN=your_app_token
export DELIGHT_PUSHOVER_USER_KEY=your_user_key

Optional settings:

# Comma-separated list: turn-complete, attention
export DELIGHT_PUSHOVER_EVENTS=turn-complete,attention

# Cooldown in seconds (per alert type)
export DELIGHT_PUSHOVER_COOLDOWN_SEC=60

# Pushover priority (-2..2)
export DELIGHT_PUSHOVER_PRIORITY=0

You can also control notifications with a CLI flag:

./delight run --pushover=auto   # default: only when creds are set
./delight run --pushover=on     # force enable (requires creds)
./delight run --pushover=off    # disable

Public Hosting (HTTPS)

For public hosting, use the included Caddy + Docker Compose deployment. Caddy automatically provisions and renews Let's Encrypt certificates.

./deploy/delight-server.sh init
${EDITOR:-vi} ./deploy-data/.env
./deploy/delight-server.sh up

See server/README.md for details and troubleshooting.

Origins

This project is inspired by (and was originally prototyped by analyzing) the Happy ecosystem:

• https://github.com/slopus/happy
• https://github.com/slopus/happy-cli
• https://github.com/slopus/happy-server

Delight is not compatible with Happy. The protocol and implementation here are private-to-this-repo and may change freely.

The name "Delight" is a deliberate, fun reference to "Happy".

License

MIT. See LICENSE.