Ygg v0.3.0-alpha

Ygg v0.3.0-alpha

Ygg v0.3.0-alpha is a focused terminal-quality and trust-boundary release. It makes
the default interface quieter and easier to copy, turns opaque failed runs into
actionable diagnostics, and carries recent security hardening into a focused
pre-1.0 alpha.

Ygg is not an operating-system sandbox. An enabled bash tool runs with the
authority of the user who launched Ygg; use OS isolation for untrusted workspaces,
models, or extensions.

Install

Ygg supports macOS and Linux. Install Rust 1.86 or newer and rg (ripgrep), then
run the pinned installer:

curl --proto '=https' --tlsv1.2 -LsSf \
  https://raw.githubusercontent.com/skaft-software/ygg/v0.3.0-alpha/scripts/install.sh | sh

Or install without changing a shell profile:

cargo install --locked \
  --git https://github.com/skaft-software/ygg \
  --tag v0.3.0-alpha \
  --bin ygg \
  ygg-coding-agent

Verify the installation with ygg --version and ygg --help.

Highlights

• Copy-safe code, quiet composer. Fenced Markdown code uses borderless,
  terminal-adaptive light/dark shading. The default prompt composer stays
  unfilled and restrained at rest, adding a model-colored perimeter shimmer only
  while work is active. Explicit themes retain their authored chrome.
• Actionable failed runs. The familiar failed · <duration> lifecycle row is
  preserved and now followed by a bounded, terminal-safe reason that is included
  in semantic copy. Provider diagnostics redact the credentials used for that
  request before reaching the frontend.
• Hardened trust boundaries. Request diagnostics, OAuth and update responses,
  command output, session exports, credential refresh, atomic file publication,
  and extension JSON-RPC framing received focused adversarial coverage and tighter
  failure behavior.
• Small by design. The release remains a four-crate Rust workspace with direct
  provider traffic, local inspectable sessions, and no hosted Ygg control plane.

Failure-observability note

Earlier interactive releases retained the underlying AgentError in memory but
rendered only a generic failure row. That made historical provider failures
impossible to diagnose from the transcript. v0.3.0-alpha exposes the already
credential-redacted reason safely. It does not guess at, or silently extend, the
existing 120-second stream-idle and 30-minute per-request deadlines.

Compatibility and limitations

• Existing Ygg sessions and historical exec tool records remain supported.
• The compiled default theme changes fenced-code chrome while retaining the
  bordered composer; named and custom themes preserve their explicit settings.
• Configuration, session, extension, and public crate APIs remain pre-1.0 and may
  evolve in later releases.
• Command execution is Unix-only and inherits the launching user's filesystem,
  environment, process, and network authority.

See the changelog
and security policy
for the complete changes and security boundary.