Reference on Unbound Force

uf CLI Reference

Sat, 02 May 2026 00:00:00 +0000

This page reflects uf v0.12.0. Run uf --help for the latest.

Overview

uf [command] [flags]

The uf CLI (alias for unbound-force) manages the full Unbound Force toolchain. Each command group handles a distinct concern — from project scaffolding to containerized development sessions.

Configuration

Sat, 02 May 2026 00:00:00 +0000

Overview

The uf CLI uses a unified configuration system. All settings live in .uf/config.yaml at the repository root. The file is optional — when absent, compiled defaults apply with no error. You never need to create this file manually; uf config init generates it with all values commented out so you can see what’s available and uncomment what you want to change.

Sandbox

Sat, 02 May 2026 00:00:00 +0000

Overview

uf sandbox provides containerized development sessions for AI agents. Instead of running OpenCode directly on your host, the sandbox creates a Podman container with your project mounted, OpenCode installed, and API keys forwarded. The agent works inside the container where file changes are isolated (or directly applied, depending on mount mode).

Gateway

Sat, 02 May 2026 00:00:00 +0000

Why a Gateway?

Running AI agents inside containers creates a credential isolation problem. The agent needs to call the Anthropic Messages API, but the cloud credentials (Google Cloud OAuth tokens, AWS session credentials, or Anthropic API keys) live on the host machine. Forwarding credentials into containers is fragile and insecure — credential files change location across platforms, tokens expire, and mounting secret directories creates attack surface.