Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial
Home / Reference / Settings keys

next.to

setting never mined JSON

A Claude Code settings key, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.

Hooks/plugin runtime gains a 'to' messaging function, a 'surface' concept, and table-resolution requests

Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.267.

First seen — never in a mined build
Last seen — never in a mined build
Builds0 / 159on this box, as of v2.1.319
Written about v2.1.267 first named in a changelog, 9 Sep 2026

In the changelogs

4

Releases whose published page names next.to.

  1. v2.1.305
    Plugin hooks modules now have the floors they hand back checked

    When a plugin hooks module calls next(), Claude Code now checks the floors handed back and refuses ones the plugins cannot reach

    found in this entry's text

  2. v2.1.269
    Plugin hooks-module scan enforces that next.to() targets be statically discoverable

    Plugins that call next.to() with a hooks module name Claude Code can't find in the code are now rejected

    found in this entry's text, named in this entry

  3. v2.1.267
    Hooks plugin API gains a 'to' messaging primitive, 'surface' concept, and table resolution

    Hooks/plugin runtime gains a 'to' messaging function, a 'surface' concept, and table-resolution requests

    found in this entry's text

  4. v2.1.267
    Plugin hook modules gain a resolved 'tier' controlling next.to() ordering

    Plugin hooks can now be assigned a resolved ordering tier that next.to() calls are validated against

    found in this entry's text

First cited

3

The earliest release whose published evidence quoted next.to was v2.1.267, 9 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

ReleaseDateThe span that was quoted
v2.1.2679 Sep 2026next.to always next.to(e, "<tier>")
v2.1.2679 Sep 2026next.to("${d}") skips nothing from ${r}
v2.1.30520 Oct 2026next refused: the floors handed back are not ones a next.to of these plugins leaves (host rule)

Presence across releases

0

The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.

Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the settings key does. All settings keys.

Feedback