Bitter Frontier What coding agents just made possible, where the bottleneck moved, and what deserves attention.

Evidence record / flue

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

Automatic .env loading and dev reload on config changes

What Changed

Flue now automatically loads project-root .env file before configuration resolution (can be overridden with --env <path>). Additionally, flue dev now restarts when auto-discovered flue.config.* files are created, edited, or deleted; explicit --config <path> files are also watched.

Operator Implication

Operators can now rely on automatic .env loading for local development without explicit flags, and benefit from automatic dev server restart when configuration changes.

Receipt

Finding metadata

Confidence
high
Actionability
observe
Accessibility impact
low

Run: 2026-06-03-weekly-digest-2026-05-28_2026-06-03-frontier-v0

Finding ID: 2026-06-01-flue-v090-env-config-reload

Source links

Primary links, including exact changelog lines when available.

  1. Flue
    release noteFrom CHANGELOG.md v0.9.0 (2026-06-02): 'Load local environment values before configuration. Flue application commands load project-root `.env` values automatically...' and 'Restart `flue dev` after cowithastro/flue / CHANGELOG.md

Versioned source: run artifact