feat(registry): add tool options support for http backend

[jdx]

Summary

• Add options field to RegistryTool struct with platform support
• Create jq.rs module for JSON path extraction (e.g., .[].version)
• Create version_list.rs for fetching/parsing version lists from URLs
• Update http backend to use version_list_url option
• Merge registry options with user-provided options in BackendArg
• Add claude-code entry using http backend with version list endpoint
• Update registry.toml schema to allow options field

This enables tools to specify version list URLs and platform-specific configurations directly in the registry, reducing reliance on npm/other backends for simple binary downloads.

Example registry.toml entry:

[tools.claude]
aliases = ["claude-code"]
backends = ["http:claude", "npm:@anthropic-ai/claude-code"]

[tools.claude.options]
version_list_url = "https://storage.googleapis.com/claude-code-dist-.../stable"
bin = "claude"

[tools.claude.options.platforms.macos-arm64]
url = "https://storage.googleapis.com/.../{version}/darwin-arm64/claude"

Test plan

• mise ls-remote claude returns version from version_list_url
• mise install [email protected] installs from http backend
• mise exec [email protected] -- claude --version outputs correct version
• Unit tests pass for jq.rs, version_list.rs, and backend integration
• Lint passes

🤖 Generated with Claude Code

---

Note

Adds HTTP backend remote version listing (regex/jq path parsing) with registry-backed options and introduces claude tool via HTTP; updates docs/schema/tests.

• Backend:
  • HTTP: Implement remote version listing from version_list_url, supporting version_regex and version_json_path.
  • New Modules: Add backend/jq.rs (jq-like JSON extraction) and backend/version_list.rs (fetch/parse versions), with unit tests.
  • Options Merge: BackendArg::opts() now merges registry backend options with user options (user takes precedence).
• Registry/Build:
  • Schema: Extend schema/mise-registry.json to allow per-backend options (including nested platforms).
  • Codegen: build.rs generates backend options; introduce raw_string_literal for safe string embedding.
  • Runtime: RegistryBackend gains options; add accessors get_backend and backend_options.
  • Tool: Update registry.toml to add tools.claude HTTP backend with version_list_url, bin, and platform-specific URLs; restrict OS; keep npm as alternate.
• Docs/Tests:
  • Docs: Expand HTTP backend docs with version_list_url, version_regex, and version_json_path usage.
  • E2E: Add e2e/backend/test_http_version_list_slow validating ls-remote and install for claude.

^{Written by Cursor Bugbot for commit 7cb7c3e. This will update automatically on new commits. Configure here.}

[Copilot]

Pull request overview

This PR adds support for tool-specific options in the registry, enabling HTTP backend tools to fetch version lists from URLs without relying on npm or other package managers. The implementation includes a custom JQ-like JSON path extractor for parsing various version list formats.

Key changes:

• Added options field to registry tool definitions with platform-specific configuration support
• Implemented JSON path extraction and version list parsing utilities
• Modified HTTP backend to fetch versions from configurable URLs

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/registry.rs	Adds options field to RegistryTool struct and tool_options() method to convert registry options
src/cli/args/backend_arg.rs	Merges registry options with user-provided options, giving user options precedence
src/backend/version_list.rs	New module for fetching and parsing version lists from URLs with multiple format support
src/backend/jq.rs	New module implementing simplified JQ-like JSON path extraction
src/backend/http.rs	Updates HTTP backend to use version_list_url option for remote version listing
src/backend/mod.rs	Registers new jq and version_list modules
schema/mise-registry.json	Adds options field schema with platform-specific configuration support
registry.toml	Adds claude-code tool configuration using HTTP backend with version list URL
build.rs	Updates registry codegen to serialize options field from TOML

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The clone() is unnecessary here. Since opts.get() returns Option<&String>, you can use as_str() to get &str and pass it directly to fetch_versions without cloning.

Suggested change

	let version_list_url = match opts.get("version_list_url") {
	Some(url) => url.clone(),
	None => return Ok(vec![]),
	};
	// Get optional version regex pattern or JSON path
	let version_regex = opts.get("version_regex").map(|s| s.as_str());
	let version_json_path = opts.get("version_json_path").map(|s| s.as_str());
	// Use the version_list module to fetch and parse versions
	version_list::fetch_versions(&version_list_url, version_regex, version_json_path).await
	let version_list_url = opts.get("version_list_url").map(|s| s.as_str());
	if version_list_url.is_none() {
	return Ok(vec![]);
	}
	// Get optional version regex pattern or JSON path
	let version_regex = opts.get("version_regex").map(|s| s.as_str());
	let version_json_path = opts.get("version_json_path").map(|s| s.as_str());
	// Use the version_list module to fetch and parse versions
	version_list::fetch_versions(version_list_url.unwrap(), version_regex, version_json_path).await

[Copilot]

[nitpick] These two lines extract options that are already being extracted from opts. Consider extracting all three options (version_list_url, version_regex, version_json_path) consistently at the same location for better code organization.

Suggested change

	// Get version_list_url from options
	let version_list_url = match opts.get("version_list_url") {
	Some(url) => url.clone(),
	None => return Ok(vec![]),
	};
	// Get optional version regex pattern or JSON path
	// Get version_list_url and related options from options
	let version_list_url = match opts.get("version_list_url") {
	Some(url) => url.clone(),
	None => return Ok(vec![]),
	};

[Copilot]

[nitpick] The field name \"v\" is a single letter which could match unintended fields. Consider removing it or placing it last in the priority order to avoid false matches.

[jdx]

cc @roele @risu729—I think this will be useful for probably other tools that need complex options in registry.toml

[github-actions]

Hyperfine Performance

mise x -- echo

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
mise-2025.11.7 x -- echo	19.4 ± 0.4	18.8	23.1	1.00
mise x -- echo	20.7 ± 0.2	20.1	21.6	1.07 ± 0.02

mise env

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
mise-2025.11.7 env	19.5 ± 0.6	18.8	25.8	1.00
mise env	20.0 ± 0.7	18.6	30.1	1.03 ± 0.05

mise hook-env

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
mise-2025.11.7 hook-env	18.6 ± 0.4	17.8	21.6	1.00
mise hook-env	19.4 ± 0.5	18.0	20.7	1.04 ± 0.04

mise ls

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
mise-2025.11.7 ls	16.0 ± 0.4	15.3	18.6	1.00
mise ls	17.7 ± 0.4	16.2	18.8	1.10 ± 0.04

xtasks/test/perf

Command	mise-2025.11.7	mise	Variance
install (cached)	108ms	108ms	+0%
ls (cached)	64ms	65ms	-1%
bin-paths (cached)	71ms	72ms	-1%
task-ls (cached)	430ms	439ms	-2%

[cursor]

Bug: Fallback option parsing uses wrong string source

The fallback code in the opts() method attempts to parse bracket notation from self.full(), but self.full() doesn't contain bracket notation—it returns the clean backend specification. Brackets are extracted during BackendArg construction from the tool name, not the full string. While this fallback may not execute in normal usage since self.opts is set during construction, the logic is incorrect if it ever does execute. The regex check at line 294 will never match a full backend string like http:claude since bracket notation is handled separately.