This release adds 3 notable features for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
+14 more
Summary
AI summaryRegular ait init now prepares wrappers, .envrc, memory import, and the repo memory‑policy guardrail; ait status reports CLI readiness.
Full changelog
0.35.0
This release reduces first-run activation friction: regular ait init now prepares wrappers, .envrc, memory import, and the repo memory policy guardrail, while ait status says whether the current shell is ready for direct agent CLI use.
- Regular
ait initcreates the default.ait/memory-policy.jsonguardrail. ait initoutput reports memory policy creation state.ait status --format jsonincludesagent_cli_readyandagent_cli_message.- Text
ait statusshows direct agent CLI readiness. - Docs now present
ait initas the primary activation path;ait init --shellremains the eval-safe alternative.
Validation:
.venv/bin/pytest -q-> 246 passed, 4 subtests passed.venv/bin/python -m compileall -q src tests.venv/bin/python -m build.venv/bin/python -m twine check dist/*- Clean wheel smoke for
ait init, memory policy creation,.envrc, wrapper install, andagent_cli_readystatus
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
About Ait
All releases →Related context
Related tools
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]