v3.18.1

fastf 3.18.1: your agent starts from the app menu

Opened from the app menu, fastf could not start an agent installed in
~/.local/bin, which is where Claude Code's own installer puts claude.
X, x and fastf agent all stopped at sh: line 1: claude: command not found. The same thing happened to a template's commands, the editor and a
terminal installed there. From a terminal everything worked, which is what
made it look random.

Why

A desktop session's PATH is the one it started with, before any shell
read ~/.bashrc. The folders your rc file adds were missing from every
program fastf started.

What fastf does now

fastf asks your shell which PATH it builds, the way a terminal tab starts
it, and starts the program with that one:

• Opened from the app menu or a terminal emulator, the agent, the editor
  and every post-create command get your shell's PATH.
• Typed into a shell, fastf's PATH already is your shell's, so it asks
  only when it cannot find the program itself.

It asks once per run, and for five seconds at most. It never asks without a
display, over ssh, or with $SHELL unset. fastf's own environment never
changes, only the program's. While it asks, FASTF_ASKING_SHELL=1 is set,
so an rc that does slow work can skip it.

Quotes around the agent

An agent typed into Settings with quotes around the whole of it,
"claude --dangerously-skip-permissions", used to be stored with them, so
the shell would look for one program with that entire name. Now fastf
treats it as the command inside the quotes. That applies when you set it,
and when it reads a value an earlier fastf already stored. The editor
setting gets the same treatment.

Nothing else changed.

How a program is found: docs/cli.md

What's Changed

• packaging: bump both AUR packages to 3.18.0-1 by @cristocola in #130
• fastf 3.18.1: a program you name is found where your shell finds it by @cristocola in #131

Full Changelog: v3.18.0...v3.18.1