fix(tools): find turso in ~/.turso instead of reporting it missing - #135
Merged
Conversation
The official turso installer unpacks to $HOME/.turso and only appends that dir to your shell profile, so the binary is on PATH for the NEXT shell. moshcode resolves tools against PATH alone, so right after `/install turso` the pit still showed turso as "not installed" and `/turso` failed with "turso isn't on PATH" — in the session that installed it, and in every already-running one. Tool specs can now declare `binDirs`: extra directories searched after PATH when resolving the executable. turso points at ~/.turso, so both the status list and the passthrough launch find the binary the vendor script just dropped. PATH still wins when a real turso is on it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
vu1nz Security Review0 finding(s) in PR #? No security issues found. |
ralyodio
marked this pull request as ready for review
July 31, 2026 07:38
Merged
ralyodio
added a commit
that referenced
this pull request
Jul 31, 2026
Cuts a release off main so the fixes merged after v0.13.1 actually reach installs. v0.13.1 shipped before #135, so re-running the installer still handed you a moshcode that reported turso as missing. Included since v0.13.1: - #135 fix(tools): find turso in ~/.turso instead of reporting it missing - #134 fix(tui): stop styling the agent-view notice as an error - #133 fix(runtime): deliver fire-and-forget notify() when the script throws Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
/install tursosucceeded, then/toolslisted turso asnot installedand/tursodied withturso isn't on PATH.The official turso installer unpacks to
$HOME/.tursoand only appends that dir to your shell profile — so the binary is on PATH for the next shell. moshcode resolves every tool against PATH alone, so the session that just installed it (and every already-running one) can't see it.Fix
Tool specs can now declare
binDirs— extra directories searched after PATH when resolving the executable:executableCandidates/resolveExecutable/isInstalled/spawnSpectake optional extra dirsopenPassthroughreadstarget.binDirs, so the launch path is fixed too, not just the status dottoolStatus()passestool.binDirsthroughbinDirs: [~/.turso]Searching after PATH means a real
tursoon PATH still wins; the fallback only kicks in when PATH misses.Verification
~/.turso/tursounder a fake$HOME:installed: true,/tursolaunchok: true, code: 0🤖 Generated with Claude Code