Repository navigation
docs: interface routing, local shell path rewrite, claude CLI, unfilled $ARGUMENTS; release 0.16.1 - #15
Merged
Conversation
…ed $ARGUMENTS From claude-code-internals findings of 2026-10-02/03 (Desktop 2.19675.0, agents 2.1.286/2.1.287), reviewed by that project before applying. - Choosing Cowork in the Chat/Cowork picker ran locally when "Only on this computer" was on (Team n=5, Personal 2/2) and in the cloud when it was off; the merged composer ran in the cloud even with it on. 0.16.0 said the picker starts a cloud session. Quote the in-app deprecation notice shown on local tasks. - Local sessions: Desktop rewrites plugin and skill paths inside shell commands to the VM mounts (measured n=4, in the asar from 1.40609.0; onset between agent 2.1.246 and 2.1.260), so the "VM shell cannot resolve it" sentence was stale. The shell then prints VM paths, which the file tools refuse; say not to hand those to file tools. CLAUDE_PLUGIN_DATA and the outputs path are not rewritten. - README: `claude` was found at /usr/local/bin/claude in the local VM shell (n=4); other runtimes unchecked. Gate on `command -v claude`. - $ARGUMENTS is left unfilled when a cloud skill is invoked before the session exists (positional placeholders untested); fall back to the user's message. Also soften the claude-cli-dependency lint message, the module docstring and SKILL.md: absence of `claude` from the chat runtime was never measured (claude-code-internals has no evidence, even relayed; the cloud agent itself runs as /opt/node22/bin/claude).
Bump the version, date the changelog, and re-record the no-trigger cassette (the bump re-stales it).
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.
Corrections from claude-code-internals findings of 2026-10-02/03 (Desktop 2.19675.0). That project reviewed the wording before it was applied.
claudeCLI. It was found in a local session's shell, and its absence from the chat runtime was never measured. The README,SKILL.mdand theclaude-cli-dependencylint message now say it may be off the PATH outside Claude Code, so gate oncommand -v claude. The rule fires on the same inputs as before.$ARGUMENTScan arrive unfilled when a cloud skill is invoked before the session exists. Fall back to the user's message.Local checks: 182 tests OK, quick_validate valid, check_portability rule set unchanged (4), harness static lane clean.
🤖 Generated with Claude Code