From 03e030ca5cd90c65c837cbc58ad76bcaa87e308c Mon Sep 17 00:00:00 2001 From: Jacob Stephens Date: Sun, 27 Sep 2026 16:35:05 +0000 Subject: [PATCH] README: say which copy runs when a build from source sits beside the installer's Drop the sudo /usr/local/bin install: it is always behind ~/.local/bin on PATH, and thirdshift update can't touch it. Co-Authored-By: Claude Opus 5.5 --- README.md | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index d22ca1d75..cb54ace0d 100644 --- a/README.md +++ b/README.md @@ -192,13 +192,20 @@ git checkout main && git pull cargo install --path . ``` -To install it system-wide instead, build it and copy it into place: +If the shell installer also put a copy in `~/.local/bin`, typing `thirdshift` runs whichever copy comes first on your `PATH`, and the installer's copy often does. To see every copy, in the order the shell tries them: ```sh -cargo build --release -sudo install -m 755 target/release/thirdshift /usr/local/bin/thirdshift +type -a thirdshift ``` +To run the build from source, give its path, as in `~/.cargo/bin/thirdshift `, or put `~/.cargo/bin` first on your `PATH`, for example in `~/.bashrc`: + +```sh +export PATH="$HOME/.cargo/bin:$PATH" +``` + +`thirdshift version` can't tell the two apart: a build from `main` reports the last released version until the next release bumps it. + Editing a skill in `skills/` has no effect until you rebuild and reinstall ([ADR-0001](docs/adr/0001-rust-binary-with-embedded-skills.md)). The [Prompts and skills page](https://thirdshift.app/prompts/) is generated from the prompts, the `claude` arguments and the skills, and `cargo test` fails until it is regenerated after a change to any of them. Regenerate it with `UPDATE_PROMPTS_PAGE=1 cargo test prompts_page`.