suggest using eval_path if path isn't found in llm-step's resolve (used by ls and read) - #308
Merged
Merged
Conversation
`read caos-std/README.md` failed with `caos resolve <tree> caos-std/README.md /cas/resolved-1 exited with exit status: 1` and nothing else. caos-std/ is a mount that exists only in the evaluated tree, so the answer was eval_path then `read` with its hash as `root` -- but nothing a model could see said so, and a cloud session concluded the std index was unreadable. resolve() now runs `caos resolve` with its output captured. A path missing from the conversation tree, with no `root`, says what to do instead; any other failure carries caos' own reason rather than an exit status. The lookup still never evaluates: it names the tool that does, since evaluating can build. read, ls and grep's help name eval_path as a source of `root`. Two stale descriptions of the registry go with it: MCP.md listed `bash` and the caos build/test tools among llm-step's tools, and llm-step's .caos-expr said it binds bash-tool, caos-build and caos-test. Since 90dc0f5 those are reached by path, as `caos-std/<name>`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
nishu-builder
changed the title
llm-step's resolve (used by ls and read)
nishu-builder
changed the title
llm-step's resolve (used by ls and read)llm-step's resolve (used by ls and read)
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
2 participants
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.
read caos-std/README.mdfailed with onlycaos resolve <tree> caos-std/README.md /cas/resolved-1 exited with exit status: 1.caos-std/exists only in the evaluated tree, so the fix was to calleval_path, thenreadwith the hash it returns asroot. Nothing the model could see said that, and a cloud session concluded the std index couldn't be read.llm-stepresolve()(shared byreadandls) now runscaos resolvewith its output captured. If the path is missing from the conversation tree and norootwas given, the error says to useeval_pathand pass its hash asroot. Any other failure carries caos's own reason instead of an exit status. The lookup still never evaluates; it names the tool that does, because evaluating can start a build.read,lsandgrepnow nameeval_pathas a source ofroot.MCP.mdandstd/llm-step/.caos-exprstill saidbash,caos-buildandcaos-testare registered tools. Since90dc0f55they're reached by path, ascaos-std/<name>.Tested:
llm-stepunit tests: 49 pass, including 2 new ones for the message.caos-cli talkconversation pinned to this branch got the new error fromread caos-std/README.md, followed it (eval_path, thenreadwithroot), and returned the README.caos-testsuite was not run.Changing
std/llm-stepre-keys it, so the first session on the next pin rebuildsllm-steponce.🤖 Generated with Claude Code