v0.5.0

Changes since v0.4.3

• chore(release): v0.5.0
• chore(deps): bump the cargo group, and port catalog and update to ureq 3 (#2)
• feat(tui): a slot machine for anyone who cannot decide (#9)

Install

Download the file for your platform, make it executable and put it on your PATH.
Every binary is signed with the project's minisign key; the signatures are in
SIGNATURES.json and SHA256SUMS.txt covers the same files.

An existing install updates itself with fastpick --update, which checks the
signature before replacing anything.

v0.4.3

Before you update

System prompt files are no longer matched against the model's name. A model launches with a
prompt only when its config names one, and any file in the folder can be named by any model:

[[provider.model]]
id = "acme-orca-v4-pro"
prompt = "house-style"      # the .md is optional, the case does not matter

A model that named nothing used to be handed the file whose stem matched its id. It now
launches with no system prompt, silently. Add prompt to the models that were relying on
that. A prompt naming a file the folder does not hold is reported, in the options panel and
on stderr at launch.

The a key, which listed every file rather than only the matching ones, is gone: the whole
folder is the list now.

--json output carries schema: 4. A model's prompts array became a single prompt
string, absent when the model names no file or names one that is missing.

Changes since v0.4.2

• chore(release): v0.4.3
• fix(catalog): a private endpoint over http is not a key on the wire (#8)
• feat(prompts): every prompt in the folder, for every model (#7)
• chore: bump the actions group across 1 directory with 3 updates (#1)
• feat(pi): a fourth harness, and the endpoint it has no variable for (#6)
• feat(tui): the search that was always there, now on screen (#5)
• feat(prompts): a model can say which prompt file it wants (#4)

Install

Download the file for your platform, make it executable and put it on your PATH.
Every binary is signed with the project's minisign key; the signatures are in
SIGNATURES.json and SHA256SUMS.txt covers the same files.

An existing install updates itself with fastpick --update, which checks the
signature before replacing anything.

v0.4.2

Changes since v0.4.1

• chore: 0.4.2, and let the GitHub release push the crate
• fix(tui): a part-cached site says how much it knows
• fix(tui): refuse a --model id that two keys both serve
• feat(cli): --key names the credential a launch spends
• fix(config): refuse two routes that answer to the same id
• feat(config): let one provider hold several keys

Install

Download the file for your platform, make it executable and put it on your PATH.
Every binary is signed with the project's minisign key; the signatures are in
SIGNATURES.json and SHA256SUMS.txt covers the same files.

An existing install updates itself with fastpick --update, which checks the
signature before replacing anything.

v0.4.1

Changes since v0.4.0

• chore(meta): name the harnesses where search looks
• docs: cargo install is a real channel now

Install

Download the file for your platform, make it executable and put it on your PATH.
Every binary is signed with the project's minisign key; the signatures are in
SIGNATURES.json and SHA256SUMS.txt covers the same files.

An existing install updates itself with fastpick --update, which checks the
signature before replacing anything.

v0.4.0

Changes since v0.3.0

• feat: one signature manifest instead of a .minisig per binary
• chore: let dependabot watch the crates and the actions

Install

Download the file for your platform, make it executable and put it on your PATH.
Every binary is signed with the project's minisign key; the signatures are in
SIGNATURES.json and SHA256SUMS.txt covers the same files.

An existing install updates itself with fastpick --update, which checks the
signature before replacing anything.

v0.3.0

Changes

• fix: the MSRV is 1.88, and one more Windows-only field
• fix: make the checks pass on the platforms this was never built on
• feat: sign releases with a real key, and shorten the README
• chore: 0.3.0
• feat: CI, signed releases, and an updater that refuses what it cannot verify
• fix: stop credentials from reaching an endpoint that did not earn them
• feat: detect installed harnesses, manage keys, options as a side panel
• feat(json): machine-readable --list and --dry-run
• feat: fastpick, a picker for coding agent, provider and model

Install

Download the file for your platform, make it executable and put it on your PATH.
Every asset is signed; SHA256SUMS.txt covers the same files.

An existing install updates itself with fastpick --update, which checks the
signature before replacing anything.