The Companion

Why it's ranked here

The repository supports a serious operations workflow, not merely a chat front end. Deterministic resource addresses, drift reporting, guarded deletion, provider validation, and plan-before-apply behavior make deployments understandable. Its narrow infrastructure choices and credential requirements limit its fit, but the safety model is unusually concrete.

What's good

Plans distinguish creation, updates, deletion, drift, and no-op resources before mutation. Protected resources require explicit destruction, while persistent data adds backup confirmation. Secrets stay outside desired configuration and plan output exposes names rather than values. Failed console edits roll back workspace changes after validation errors.

Tradeoffs

Live operation depends on configured Fly, Tailscale, and OpenRouter credentials. The default architecture also brings Hermes, Granite, and Open WebUI into the operating model. Users must maintain TOML configuration, an environment file, generated artifacts, and SQLite state together. Applying a plan mutates remote infrastructure.

How to use it well

Use it when a solo operator, internal team, or consultant needs repeatable fleets with distinct identities, models, memory, tools, and private access. Keep one workspace as each fleet's operating home, validate edits, inspect the plan, then apply. It does not replace general cloud orchestration or eliminate provider accounts and credentials.

Observed

Primary language

Go

Packaging

Install script places the companion CLI binary in ~/.local/bin by default

Interfaces

CLI, local status dashboard, JSON status routes, and console API

Configuration and state

TOML workspaces define desired state; SQLite records operational evidence

Provider surface

Fly runtime, Tailscale private networking, and OpenRouter model routing

Testing structure

Repository includes CLI and Fly provider test files