UPTERM(1)

🎀 NAME 🎀

upterm-config-edit — Edit the config file

okay bestie, you're on the UPTERM(1) page for this command, and it's giving “small command, very useful energy” 💅✨

---

✨ SYNOPSIS ✨

upterm config edit [flags]

That's the whole synopsis, no cap.

---

💖 DESCRIPTION 💖

okay so this command opens the config file in your editor. But first — because it's an icon — it creates the file, and its directory, from the example when there is none. 🫶

Config file: /build/.config/upterm/config.yaml

Editor vibes: $VISUAL first, then $EDITOR, then nano (vi without nano; notepad on Windows). So yes, it's doing a whole fallback chain, and it's lowkey sensible.

A value that names an existing file runs as it is; any other is split into a program and its arguments (code --wait), as a POSIX shell would on Unix and by the Windows command-line rules on Windows.

Once the editor exits, the file is checked as commands read it: its YAML, its keys, and each value as the command it belongs to would check it. Each problem is one upterm: line, and the exit status is 1. When the editor itself exits with an error, the file isn't checked — periodt.

Exit status: 0, or 1 on failure.

---

👑 OPTIONS 👑

• -h, --help[=false] — help for edit

---

🧚 OPTIONS INHERITED FROM PARENT COMMANDS 🧚

• --debug[=false] — Enable debug logging (log file: /build/.upterm/upterm.log). A non-empty DEBUG turns it on too.

---

🌈 EXAMPLE 🌈

# Edit the config file:
upterm config edit

# With an editor that needs an argument to wait:
VISUAL='code --wait' upterm config edit

Copy-paste these, they're iconic 💜

---

🦋 SEE ALSO 🦋

upterm-config(1) — the related manual page, iykyk 💜

---

🌸 HISTORY 🌸

2-Nov-2026 Auto generated by spf13/cobra

---

That's the whole manual, bestie 🫶 — brought to you by Upterm 0.0.0+dev, dated Nov 2026. Now go edit that config like the main character you are 💅✨