lfg

Run AI coding agents on your own machine, from anywhere.

lfg turns a Linux box or macOS workstation into a private control plane for Claude Code, Codex, and opencode. It starts each agent in a long-lived tmux session, streams the transcript to a web UI, and lets you answer prompts or steer work from your phone or laptop.

Website: lfg.apps.omg.dev

Why lfg?

• Run agents where your code lives. Sessions execute on your machine, in your repos, with your local CLIs and credentials.
• Use a real web UI. Launch sessions, watch output, answer permission prompts, switch projects, and resume work from an installable PWA.
• Keep it private. The server binds to loopback by default and is designed to be exposed through Tailscale, not the public internet.
• Automate repo checks. Optional markdown-defined agents can collect git, repo, GitHub, model, or security context and produce reports.

Screenshots

The images are stored in this repo instead of hotlinked, so the README renders reliably on GitHub.

Requirements

• Bun
• tmux
• git
• At least one supported agent CLI on PATH:
  • claude
  • codex
  • opencode
• Optional: Tailscale for private remote access

Quick Start

Install on an Ubuntu/Debian VPS or macOS workstation:

curl -fsSL https://raw.githubusercontent.com/BennyKok/lfg/main/scripts/setup.sh | bash

For a non-interactive Tailscale setup:

curl -fsSL https://raw.githubusercontent.com/BennyKok/lfg/main/scripts/setup.sh \
  | TS_AUTHKEY=tskey-auth-xxxx bash

The setup script downloads the latest release, installs production dependencies, writes .env, starts the server as a user service, and configures tailscale serve when Tailscale is available.

One-click Launch

Railway is useful for a hosted demo, but lfg works best on the machine that has your repos, tmux, and authenticated agent CLIs. See deploy/railway for details.

The shared Dockerfile also works as the base for Fly.io, Render, DigitalOcean, and Koyeb. These PaaS targets are best for demos or private-network deployments; a VPS remains the cleanest production-style target. Because the Vibes SDK path is not live for source installs yet, the Dockerfile installs the published bundled release (lfg-bundle.tar.gz) instead of building from the GitHub source tree. Publish a bundle with scripts/release.sh <tag> before relying on one-click cloud deploys.

For Hetzner, use the cloud-init template in deploy/hetzner. Hetzner's official deploy button only preselects Hetzner App images, so the repo ships a first-boot installer instead.

Railway user requirements:

• Railway account and GitHub access to this repo.
• Keep Public Networking disabled unless you put auth in front of lfg.
• For Tailscale access, add Railway's Tailscale router as a second service and put TS_AUTHKEY on that router service.
• Optional provider keys in Railway variables, such as ANTHROPIC_API_KEY, OPENAI_API_KEY, or ELEVENLABS_API_KEY.

Hetzner user requirements:

• Hetzner Cloud account, SSH public key, and either the hcloud CLI or Console.
• Tailscale account plus an ephemeral/preauthorized auth key for unattended setup. The installer joins the server with tailscale up --authkey ... and exposes the loopback-only UI through tailscale serve.
• After boot, authenticate claude, codex, or opencode on the server, or configure API-key based providers in .env.

Local Development

git clone https://github.com/BennyKok/lfg.git
cd lfg
bun install
cp .env.example .env
bun run serve

Open http://127.0.0.1:8766.

Authenticate the agent CLI you want to use, for example by running claude once and completing OAuth, or by setting the required API key in .env.

Commands

bun run serve                  # web UI + control server
bun run agents -- list         # list markdown-defined agents
bun run agents -- run <name>   # run an insight agent
bun run whatsapp -- run        # optional WhatsApp sidecar
bun run setup                  # rerun provisioning/update flow

Installed release builds expose the same commands through lfg.

Configuration

Configuration lives in .env; see .env.example.

Common settings:

Security

lfg launches AI agents with shell access on your machine. The control API is unauthenticated by design because it is meant to run on loopback and be accessed privately through Tailscale.

Do not expose lfg directly to the public internet. Read SECURITY.md before sharing access.

Project Layout

src/                 CLI, server, sessions, tmux, agents, integrations
web/                 React/Vite PWA
agents/              Example markdown-defined insight agents
scripts/setup.sh     Installer/provisioning script
scripts-internal/    Operator-only helpers (gitignored — see CONTRIBUTING.md)
deploy/              Optional voice, STT, Modal, and ops deployments
docs/                Notes, designs, and future public images

Contributing

Issues and pull requests are welcome. Please read CONTRIBUTING.md and SECURITY.md first.

License

MIT