Skip to content
yottacode v0.4.0 is out! 🎉 See the release notes ↗
Blog
yottacode v0.4.0: The Public Launch Cut

yottacode v0.4.0: The Public Launch Cut

August 13, 2026

yottacode v0.4.0 is now the public launch cut.

This release is not a single headline feature. It is the point where the day-to-day agent loop is strong enough to describe plainly: open a real repository, ask for a real engineering task, inspect the plan, approve the changes, run verification, and carry the work through GitHub without leaving the terminal.

The release also keeps the framing conservative. v0.4.0 ships the capabilities that are real today; broader launch polish such as Homebrew packaging, full paid-provider spend estimates, and broader PDF/Office ingestion are intentionally left for a later cycle.

What changed in v0.4.0

The short version: yottacode is a stronger daily-driver terminal coding agent.

Highlights include:

  • Broader provider support — Google Vertex AI joins OpenAI, Anthropic, Gemini, xAI, Ollama, ChatGPT OAuth, Copilot, and OpenAI-compatible endpoints.
  • Advisor/implementer routing — /advisor and routed Plan/Auto flows help split planning, review, and implementation work across model roles.
  • Memory and recall hardening — semantic session recall, sensitive-project quarantine, memory capture reminders, audit/health reports, and approval-gated curation make continuity more dependable.
  • Subagents and dispatch improvements — background subagents, local code review, worktree-based dispatch, token-budget enforcement, safer worker shutdown, and orphaned worktree cleanup improve parallel workflows.
  • GA LSP code intelligence — diagnostics, document symbols, signature help, type definitions, implementations, selection ranges, document highlights, rename/format previews, and safer WorkspaceEdit application are now part of the local code-intelligence surface.
  • Offline structural ranges — syntax_range provides parser-backed edit ranges for Go, TypeScript/JavaScript, Python, and Rust even when no language server is running.
  • GitHub PR workflow helpers — yottacode can inspect PR checks, fetch failed logs, watch CI, and rerun failed jobs through typed tools instead of brittle shell transcripts.
  • Local document and media foundations — experimental document ingestion/generation and ffmpeg/ffprobe marketing-video tools are available for local-first workflows.
  • TUI polish — the fullscreen transcript, grouped tool cards, startup redesign, mode indicators, approval modal scrolling, mouse handling, and theme work make long sessions easier to follow.

Read the full release notes on GitHub: yottacode v0.4.0.

Why this release matters

yottacode is designed around a few principles:

  1. Use the model you choose. The agent should not force a single provider or hosted workflow.
  2. Keep the developer in control. Plans, diffs, approvals, path validation, and checkpoints matter because agentic coding still needs reviewable boundaries.
  3. Make memory useful without making it mysterious. Durable user and project context should compound across sessions while staying inspectable and curatable.
  4. Treat GitHub workflows as first-class engineering work. Issues, commits, PRs, reviews, checks, and CI logs are part of shipping software, not side quests outside the terminal.
  5. Prefer local-first foundations. Sessions, memory, checkpoints, and project rules live on your machine; code only goes to the model provider you configure.

Those principles show up across the v0.4.0 docs:

Try it

Install on Linux or macOS:

curl -fsSL https://raw.githubusercontent.com/yottadynamics/yottacode/main/install.sh | bash

Then run setup once:

yottacode setup

Open a repository and start with a real task:

yottacode

Good first prompts:

Review this repo and suggest the safest first bug to fix.
Find why the tests are failing, explain the issue, then propose a fix.
Update this GitOps YAML for the new image tag and show me the diff before any commit.

If you want to start without API keys, use a local Ollama model and follow the installation guide.

What comes next

v0.4.0 is the launch cut, not the end state.

The next cycle focuses on the polish that should not have blocked this release: packaging expansion, fuller launch assets, cost-visibility improvements, broader document workflows, and continued hardening from real-world use.

For now, the most useful thing you can do is try yottacode on a real repository and tell us where the loop feels sharp — or where it still gets in your way.

— The YottaDynamics Team

Introducing yottacode-skills: Reusable Agent Workflows for Real Engineering Work