Skip to content

Rusta 1.0.1

Choose a tag to compare

@github-actions github-actions released this 12 Nov 03:37
· 13 commits to main since this release
Immutable release. Only release title and notes can be modified.

Rusta no longer hands its API keys to the processes it starts, and models now reach for Devscriptor from their first prompt.

Keys stay with Rusta

Commands, background tasks, hooks, MCP servers and git no longer see the variables Rusta reads its keys from: RUSTA_API_KEY, RUSTA_ZAI_API_KEY, each provider's key variable, the one api_key_env names, and RUSTA_CUSTOM_HEADERS. Before, a command that printed its environment sent the key to the model and into the session records. An MCP server that needs one of these variables can still be given it in its own env. See Keys stay with Rusta.

Devscriptor from the first prompt

  • Devscriptor's twelve most-used tools, for search, navigation and the Context Graph, are in the model's hands from its first request; the rest still load on demand.
  • The first prompt of every conversation that has Devscriptor's tools, a sub-agent's included, comes with a short reminder to find code with Devscriptor first. It comes again after a compaction.
  • With prompts that do not mention Devscriptor, three models used it in 19 of 24 runs on eight coding tasks, against 5 of 24 with Rusta 1.0.0. See the benchmarks page.
  • Any deferred MCP server can keep tools loaded with the new preload setting, and preload = [] loads every tool on demand. rusta doctor reports a preload name the server does not list. See MCP servers.

Security

  • MCP OAuth sign-in: endpoints discovered from a server's metadata can no longer send requests to addresses only your machine or network reaches. Another origin must resolve to public addresses, or to internal ones of the kind the server's own host resolves to. Redirects are checked the same way, and responses are read up to 1 MiB. Endpoints you configure yourself are not restricted.
  • rmcp 3.9 fixes RUSTSEC-2026-0457, RUSTSEC-2026-0461 and RUSTSEC-2026-0462: MCP responses over HTTP are now read up to 16 MiB, and error bodies up to 64 KiB. rustix 1.1.6 fixes RUSTSEC-2026-0486.
  • Profiles and skill frontmatter are now read with serde-saphyr, a YAML parser in safe Rust, in place of the deprecated serde_yaml and its unmaintained unsafe-libyaml (RUSTSEC-2024-0449).

Other changes

  • The YAML rules stay the same: only true and false are booleans, and a key left without a value takes its default. An error is now one line that names the file's line and quotes it.
  • fetch now reads URLs that hold an IPv6 address.
  • Building from source needs Rust 1.89 or newer.