What is UFO?

UFO is a thin communication layer over Claude Code. It lets you dispatch AI agents from a chat interface -- web, mobile, any browser -- while your machine at home does the actual work.

Think of it as a remote control for your development environment. You talk, agents execute. Your existing Claude Code setup -- CLAUDE.md, custom agents, skills -- works without modification.

Screenshot
UFO main workspace -- channel list on the left, chat area with streaming AI output

Why not Telegram or Discord?

Generic chat apps aren't built for AI workflows. No real-time token streaming, no agent management, no file context, no scheduled tasks. UFO is purpose-built for human-AI collaboration -- every design decision came from 6+ months of daily production use.

Key principles

Installation

Prerequisites

Install

# Download and install UFO
curl -fsSL ufo.alienz.ooo/install.sh | sh

Configure

# Set up your workspace (API keys, Claude Code path, etc.)
ufo install

The installer will walk you through connecting to your Claude Code setup. It detects your existing configuration and uses it as-is.

Screenshot
ufo install terminal flow -- API key input, workspace path detection

Run as a service

# Install as a system service (auto-start on boot)
ufo service install

This registers UFO as a launchd service on macOS. It starts automatically on boot and restarts on crash. Your agents stay online 24/7.

Quick Start

Once UFO is running, open ufo.alienz.ooo from any device and log in.

# 1. Install
curl -fsSL ufo.alienz.ooo/install.sh | sh

# 2. Configure
ufo install

# 3. Run as service
ufo service install

# 4. Open from any device
open https://ufo.alienz.ooo
Screenshot
First login experience -- empty workspace, creating your first channel

Send your first message

Create a channel and type a message. UFO forwards it to Claude Code running on your machine. Watch the response stream back in real-time.

Screenshot
First message being sent and AI streaming a response

Architecture

UFO has a deliberately simple architecture. There is no cloud compute. Your machine does everything.


[ Your Browser / Phone ]
        |
        | WebSocket (messages only)
        v
[ UFO Server (relay) ]
        |
        | Bot API
        v
[ Your Computer ]
[ Claude Code + UFO Daemon ]

The server only relays messages. It never sees your code, files, or conversation content. All AI processing happens on your machine.

Components

Channels

Channels are the core organizational unit in UFO. Each channel is an independent conversation with its own Claude Code session and context.

Screenshot
Channel list sidebar with multiple channels

One channel, one context

Each channel maintains its own Claude Code session. This means separate conversation history, separate file context, separate working directory. You can have one channel for backend work, another for frontend, another for DevOps -- all running in parallel on your machine.

Channel badges

Badges show the current state of a channel at a glance. For example, which AI model is active, whether it's in a special mode, or if a long task is running.

Screenshot
Channel with badges showing mode and status

Agents

Claude Code supports custom agents -- specialized AI personas with specific roles. UFO inherits all of them. Your agents defined in .claude/agents/ work automatically.

Built-in agent examples

These are just examples. You define your own agents based on your workflow.

Screenshot
Agent being dispatched in a channel

Claude Code Integration

UFO doesn't replace Claude Code. It extends it with remote access and multi-channel management.

What works automatically

What UFO adds

No migration needed. If Claude Code works on your machine, UFO works too. Just install and go.

Mobile & Remote Access

UFO's interface is designed to work on phones and tablets. Open ufo.alienz.ooo on your phone, log in, and you have full control over your development machine.

Screenshot
UFO on mobile -- sending a message, viewing streaming response

Use cases

Screenshot
Mobile view of channel list and chat

Real-Time Streaming

AI responses stream token-by-token through WebSockets. You see the agent thinking and working in real-time, just like watching Claude Code in your terminal.

Video
Token-by-token streaming in action

What streams

Scheduled Jobs

Set up recurring tasks that run automatically. Your agents work 24/7, even when you're not watching.

# Example: check build status every 5 minutes
Schedule: */5 * * * *
Prompt: Check if there are any failed builds in the pipeline

Common patterns

Screenshot
Scheduled jobs management interface

Multi-AI Support

While Claude Code is the primary engine, UFO can dispatch tasks to other AI providers when it makes sense.

Examples

Your agents decide which AI to use based on the task. You configure the APIs, and agents call them when needed.

Custom Skills

Skills are reusable prompt templates that extend what agents can do. Define them once, invoke them from any channel.

# Skill directory structure
.claude/skills/
  deploy/
    SKILL.md     # name, description, instructions
  test/
    SKILL.md
  review/
    SKILL.md

Skills are automatically detected by Claude Code and available in all channels. No UFO-specific configuration needed.

Harness Mode

Harness mode activates a Generator-Evaluator pattern for high-quality output. When you say "make it properly" or "team effort", UFO chains multiple agents in sequence.

Game development harness

[planner] --> PLAN.md + Sprint Contract
        |
[creator] <--> [qa-tester]    # Code QA loop (max 3 rounds)
        |
[designer] <--> [ui-evaluator]  # UI quality loop (max 5 rounds)
        |
        v
       Done

Web service harness

[developer] <--> [qa-tester]    # API + page + DB validation
        |
[designer] <--> [ui-evaluator]  # UI quality loop
        |
        v
       Done

Each stage has clear pass/fail criteria. Failed stages loop back with feedback until quality is met or max retries are exhausted.

Privacy & Data

UFO was designed from day one to minimize data on our servers. Here's exactly what happens with your data.

What stays on your computer

What passes through the server

We can't see your code. We can't read your conversations. Honestly, we don't want to -- keeping servers minimal keeps our costs down. Your hardware does the work.

Why this architecture?

It's not just about privacy. Using your compute means zero usage-based cloud bills. The server only relays messages -- it does almost nothing. That's why UFO can stay free.