roder v0.1.1
0.1.1 (2026-06-15)
Features
First-party image generation providers (OpenAI GPT Image and Google Gemini Nano Banana)
Provider-neutral image generation through the core media API: an image-capable
MediaGenerationRequest/multi-output MediaGenerationResponse contract, a new
ProvidedService::MediaGenerator extension service, a runtime media generation
service backing the canonical media_generate_image tool with a deterministic
offline fallback, new roder-ext-openai-images (gpt-image-2 plus legacy ids)
and roder-ext-google-images (Nano Banana 2/Pro/base) provider crates,
[media.image_generation] config, media/image/providers/list and
media/image/generate app-server methods, roder media CLI commands, palette
entries, and regenerated schemas/SDK stubs. Live provider smokes stay opt-in
behind RODER_OPENAI_IMAGE_LIVE / RODER_GEMINI_IMAGE_LIVE.
One-command Roder package install (roder install npm:/git:/path)
Roder packages bundle process extensions, skills, slash commands, and themes
behind a root roder.toml manifest. Install from npm, git (shorthand, SSH,
raw URLs, pinned refs), or local paths; manage with roder packages list|resources|enable|disable|approve|filter|sync|init, roder remove,
roder update, and ephemeral -e loading. Resources surface through the
existing skills/commands/theme registries; the process-extension protocol
gains manifest-declared tool providers served over tools/call. New
app-server packages/* methods, a /packages builtin, and a Packages
palette section round out the surfaces. npm lifecycle scripts stay disabled
unless --allow-scripts is passed, and package process extensions never
launch before explicit approval.
Fixes
- Add a stdio Agent Client Protocol v1 adapter backed by the Roder app-server runtime.
Package-specific registry READMEs
Add package-specific README files for every Cargo crate, ensure npm and PyPI package READMEs link to roder.sh, and tighten the registry README verifier to require package-local documentation.