Skip to content

Ait

v0.39.0 Feature

This release adds 2 notable features for engineering teams evaluating rollout.

✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

agent-harness agent-isolation agentic ai-agents ai-coding ai-tools
+14 more
aider claude-code code-provenance codex coding-assistant cursor developer-tools gemini-cli git git-worktree llm-agents python vcs worktree

Summary

AI summary

Docs and release validation now focus on the primary workflow using claude … via PATH.

Full changelog

0.39.0

This release tightens docs and release validation around the daily command users actually type: claude ....

  • README and getting-started docs now keep the primary workflow focused on install, ait init, direnv allow only if prompted, then normal claude, codex, or aider use.
  • Lower-level shell, doctor, and bootstrap commands were moved out of the primary flow and into troubleshooting/scripted setup context.
  • Release smoke coverage now runs claude ... through PATH rather than invoking .ait/bin/claude directly.

Validation:

  • .venv/bin/pytest -q -> 248 passed, 4 subtests passed
  • .venv/bin/python -m compileall -q src tests
  • git diff --check
  • .venv/bin/python -m build
  • .venv/bin/python -m twine check dist/*
  • Clean wheel smoke that invoked claude ... through PATH and verified wrapper hit, memory policy recreation, CLAUDE.md import, attempt memory, workspace output, and attempt commit creation

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track Ait

Get notified when new releases ship.

Sign up free

Related context

Earlier breaking changes

  • v0.55.52 Keep the built-in claude-code reviewer pinned to the local claude -p CLI even when repository policy defines a conflicting command override.

Beta — feedback welcome: [email protected]