hermes-admin/hermes-agent
1
0
Fork 0
Code Issues Pull Requests Actions 28 Packages Projects Releases Wiki Activity

fix(dev): bind hermes to the active worktree after activation

Browse Source 
Activation defined PATH and PYTHONPATH, but `hermes` still resolved to a
global command or an MSIX alias. The shell now defines `hermes` as a
function for this worktree. It runs this checkout's CLI only while the
shell is inside the tree, and it refuses outside it. The prompt gains a
branch prefix and drops it outside the tree. `deactivate` removes the
function and the prefix.
This commit is contained in:
ethernet
2026-09-22 12:21:25 -04:00
parent a9b931585b
commit 012bc02af1
8 changed files with 206 additions and 46 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
website/docs/reference/package-management.md
View File

@@ -325,10 +325,16 @@ rebuild. A setup failure returns an error before changing the activated shell
environment, including when re-sourcing an already active environment.
After sync, activation prepends installed PM tools to `PATH` and sets
`PYTHONPATH` to this checkout and its selected dependency tree. It does not
change an OS-wide PATH or activate a conventional venv prompt.
`PYTHONPATH` to this checkout and its selected dependency tree. It also
defines `hermes` as a shell function for this worktree. The function runs
this checkout's CLI and hides the installed command, including an MSIX alias.
It runs only while the shell is inside this worktree and refuses outside it,
so a sibling worktree does not inherit the command. The prompt gains a prefix
naming the branch, and drops it outside the tree. It does not
change an OS-wide PATH or install a conventional venv prompt.
Start in a clean shell rather than nesting this inside another venv.
`deactivate` restores the environment values captured by the activation script.
`deactivate` restores the environment values captured by the activation script,
and removes the function and the prompt prefix.
It does not uninstall packages or stop processes that you started.
Verify the interpreter and source before doing work:
@@ -338,7 +344,7 @@ python -c "import sys, pm; print(sys.executable); print(pm.__file__)"
python -c "import httpx; print(httpx.__file__)"
node --version
npm --version
python hermes --version
hermes --version
```
`python` must resolve to the PM store interpreter. `pm.__file__` must point
@@ -348,13 +354,14 @@ attention, even if `source ./activate` itself returned successfully.
### Work on this source tree
Use checkout-qualified commands so a global `hermes` command or MSIX alias
cannot run a different installation:
`hermes` is this worktree's CLI while the shell is inside it. Outside the
worktree the function refuses, so it cannot run another checkout's tree or
fall through to an installed command:
```bash
python hermes setup
python hermes
python hermes --tui
hermes setup
hermes
hermes --tui
python -m pm.cli status
```