'hyve config'

The hyve config command group reads and updates hyve.yaml at the root of your state repository — the same object GET/PATCH /config exposes over HTTP, and that Hyve Studio’s Configuration section reads and writes through.

Commands

hyve config get

Print the resolved hyve.yaml as YAML. If the file doesn’t exist yet, prints the defaults hyve would otherwise fall back to.

hyve config get

Example:

hyve config get

Output:

reconcile:
  mode: local
  strictDelete: false
  strictResourceDelete: false
server:
  port: 8080
env:
  file: local.env

---

hyve config set

Set a single field in hyve.yaml by dotted key, save it, then commit and push — mirroring PATCH /config’s behavior exactly, including its soft-fail commit (a failed push is logged, not fatal — your local hyve.yaml is already updated and usable regardless).

hyve config set <key> <value>

key string required

Dotted path to the field to set. See the supported keys below.

value string required

The new value. Booleans and integers are parsed from plain text (true/false, 8080) — there’s no separate --type flag.

Supported keys:

Key	Type	Description
env.file	string	Path, relative to the repo root, to a local env file — see Configuration
reconcile.mode	string	local or cicd
reconcile.strictDelete	bool	Warn about untracked cloud clusters
reconcile.strictResourceDelete	bool	Auto-prune orphaned spec.resources entries
server.port	int	Port hyve serve listens on
server.frontendUrl	string	URL hyve serve --open navigates to
server.auth.mode	string	none or forward
server.auth.forward.validateUrl	string	Forward-auth validator endpoint
server.auth.forward.timeout	string	Forward-auth timeout (Go duration string, e.g. 3s)

Example:

# Point reconciles/workflows at a local env file
hyve config set env.file local.env

# Switch to CI/CD mode
hyve config set reconcile.mode cicd

# Change the server port hyve serve listens on
hyve config set server.port 9090

Output:

Set env.file = local.env

Note

Setting env.file automatically appends it to .gitignore (idempotent — safe to run repeatedly, never duplicates an existing entry) before saving, so a locally-configured env file can’t ship to your remote by omission. See Configuration.

Caution

Changes to server.* only take effect on the next hyve serve restart — hyve config set writes hyve.yaml, it doesn’t reach into an already-running server process.

---

Related Commands

• hyve serve — reads server.* and env.file from hyve.yaml at startup
• hyve reconcile — reads reconcile.* and env.file from hyve.yaml on every run