Skip to content

Let agents run index, and keep skill replies as envelopes - #62

Merged
VirtualMachinist merged 2 commits into
mainfrom
feat/w15-followup
Nov 16, 2026
Merged

VirtualMachinist merged 2 commits into
mainfrom
feat/w15-followup

Conversation

@VirtualMachinist

Copy link
Copy Markdown
Member

Lets agents keep their own index current, and tidies two skill replies.

What changes

  • index needs no human request. Agents may run index whenever the index is missing or stale, or to bring it up to date. It writes only to Phantom's own data directory, never to the repository. The skill, the README and the MCP instructions and index_repo description now say so. index still takes one path and no flags, and no read command ever sends it.
  • The count-mode note appears on success replies only, never on a not_found or error reply. A failed --rust query keeps its hint, because that hint says what to do next.
  • where always returns a reply envelope. If a show success comes back without a symbol, where now returns a one-line error envelope (exit 1), not a raw Nushell error.

Checks

The skill tests pass on nu 0.115.1 and 0.116.1, and the CLI tests and clippy pass. Only MCP description and instruction text changed; no reply key or tool schema changed.

🤖 Generated with Claude Code

VirtualMachinist and others added 2 commits November 16, 2026 05:45
…a nu error

`index` may run at any time: the human-ask wording is gone from SKILL.md,
the script's header and its help table. It still takes one path and no
flag, and no read command sends it; skill_nu proves both against a fake
binary that records argv.

The raw-count note now rides only on a successful `cochange` count. A
`not_found` or other failure envelope carries the CLI's fields unchanged;
`--rust` keeps its note on a failure, since that note says to drop
`--rust`.

`where` checks that a `show` success holds a symbol record. Without one
it answers an error envelope (exit 1) instead of a nu error, and it skips
any match or find hit that is not a record.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The README and the MCP text no longer ask an agent to wait for a person
before indexing. The skill list says index may run whenever the index
is missing or stale, or to make it current, and that it writes only to
Phantom own data directory, never to the repository. The pasteable MCP
block, the server instructions and the index_repo description say the
same: refresh with index_repo where offered, or phantom-fractal index.
A tree outside the roots still needs the server started with --root.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@VirtualMachinist
VirtualMachinist merged commit 8676aef into main Nov 16, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant