Skip to content

Akmon, a Rust AI coding agent for regulated engineering

AI Coding Tools
Rust Latest v2.1.0 · 7d ago Security brief →

Features

  • Records every AI interaction as a tamper‑evident, content‑addressed event journal
  • Provides deterministic replay and byte‑level validation of sessions
  • Exports portable AGEF evidence bundles for audit and CI use

Recent releases

View all 20 releases →
No immediate action
v2.1.0 Mixed

Resume, crash fix, validation

v2.0.0 New feature
⚠ Upgrade required
  • v2.0.0 can read sessions written by v1.8.x, but sessions created by v2.0.0 use the AGEF v0.1.1 schema and must not be downgraded to v1.8.x without verification.
  • No CLI flag breaks; existing scripts using `akmon run`, `audit`, `evidence`, `slo`, and `doctor` continue unchanged.
Notable features
  • `akmon diff` – structural and field‑level comparison between recorded sessions with optional byte‑level `--resolve` diff
  • `akmon replay` – deterministic re‑execution of sessions against playback providers in strict or default modes
  • `akmon bundle` – portable AGEF v0.1.1 session archives for evidence sharing
Full changelog

Release notes: v2.0.0

Why this release

Akmon v2.0.0 is the production-ready release positioning Akmon as the review-aware AI coding agent for regulated engineering. Every session is now a tamper-evident, content-addressed, replayable artifact suitable for audit, compliance evidence, and post-incident review.

Top user-facing wins

  • akmon diff: structural and field-level comparison between two recorded sessions, with optional --resolve for byte-level content diffs.
  • akmon replay: deterministic re-execution of recorded sessions against playback providers and tools, with strict and default comparison modes.
  • akmon bundle: portable AGEF v0.1.1 session archives for evidence sharing across environments.
  • akmon redact: compliance-driven content removal producing derivative bundles with sentinel objects.
  • AGEF v0.1.1: Akmon is the reference implementation. Bundle format and session evidence structure are now spec-stable for downstream tooling.

Upgrade notes

v2.0.0 reads sessions written by v1.8.x. Sessions written by v2.0.0 may use the AGEF v0.1.1 schema and should not be downgraded to v1.8.x without verification.

No CLI flag breaks; existing scripts targeting akmon run, akmon audit, akmon evidence, akmon slo, and akmon doctor continue to work unchanged.

Verification checklist

# Confirm install
akmon --version  # should report 2.0.0

# Verify a clean session round-trip
akmon --yes --task "echo hello" --output json | tee run.json
akmon audit verify .akmon/audit/<session-id>.jsonl
akmon evidence verify .akmon/evidence/<session-id>.json

# Try the new diff command
akmon diff <session-a> <session-b>

Docs links

Full Changelog: https://github.com/radotsvetkov/akmon/compare/v1.8.2...v2.0.0

v1.8.2 New feature
⚠ Upgrade required
  • No routing or CLI semantics changes; this release adds diagnostics only.
  • Pair `config explain-provider` (why a branch won) with `doctor providers` (keys, endpoints, reachability).
Notable features
  • Deterministic `ProviderResolutionTrace` structured output (`selected_provider`, `selected_reason`, `model_id`, ordered `candidates[]` with eligibility, reasons, missing prerequisites, priority order).
  • `akmon config explain-provider` command to print the trace in terminal or JSON.
  • `akmon doctor providers` now includes the same `provider_resolution` block in text and JSON.
Full changelog

Release notes: v1.8.2

Why this release

v1.8.2 is an operability and trust release: provider routing is fully explainable and diagnosable without changing resolver behavior. Introspection mirrors LlmConnectConfig::resolve() deterministically; no routing algorithm changes.

Top user-facing wins

  1. Deterministic ProviderResolutionTrace — structured trace (selected_provider, selected_reason, model_id, ordered candidates[] with eligible, reason, missing_prerequisites, priority_order) matching the real resolver priority. Secrets are never echoed; only named prerequisites.
  2. akmon config explain-provider — print the trace in the terminal or as JSON (--json on config, or global --output json).
  3. akmon doctor providers — includes the same provider_resolution block in text and JSON alongside existing health checks.
  4. Headless --output json — run summary JSON includes additive provider_resolution for automation (same schema as above).

Upgrade notes

  • No routing or CLI semantics changes for provider selection; this release adds diagnostics only.
  • Pair config explain-provider (why this branch won) with doctor providers (keys, endpoints, reachability).

Verification checklist

akmon config explain-provider
akmon config explain-provider --json
akmon doctor providers
akmon --output json doctor providers
# After a headless run with --output json, inspect provider_resolution on stdout

Docs links

Full Changelog: https://github.com/radotsvetkov/akmon/compare/v1.8.1...v1.8.2

v1.8.1 Breaking risk
⚠ Upgrade required
  • For configured policy + MCP environments, define explicit `[mcp.servers]` and `[mcp.tools]` allow rules.
  • For local-model-heavy workflows, warm models (`ollama run `) before long tasks and use `/clear` when context becomes noisy.
Notable features
  • Provider preflight command `akmon doctor providers` with actionable remediation and CI-friendly exit codes
  • MCP governance hardening with explicit `[mcp.servers]` and `[mcp.tools]` allow rules and enriched audit context
  • Deterministic docs quality checks in CI (mdBook, links, CLI snippets, JSON snippets, fixtures)
Full changelog

Release notes: v1.8.1

Why this release

v1.8.1 is a stability and operability hardening release focused on trustworthy day-2 operation: deterministic provider diagnostics, fail-closed MCP governance, docs reliability gates, internal TUI maintainability, and stronger local-model reliability behavior.

Top user-facing wins

  1. Provider preflight command: akmon doctor providers with actionable remediation and CI-friendly exit codes.
  2. MCP governance hardening with explicit server/tool policy dimensions and enriched audit context.
  3. Deterministic docs quality checks in CI (mdBook, links, CLI snippets, JSON snippets, fixtures).
  4. Local-model reliability improvements for Ollama (adaptive timeouts, unified status hints, clearer remediation).
  5. TUI internal state decomposition that improves maintainability without UX/command changes.

Upgrade notes

  • No CLI breaking changes in this release.
  • For configured policy + MCP environments, define explicit [mcp.servers] and [mcp.tools] allow rules.
  • For local-model-heavy workflows, warm models (ollama run <model>) before long tasks and use /clear when context becomes noisy.

Verification checklist

akmon doctor providers
akmon --output json doctor providers
akmon audit verify .akmon/audit/<session-id>.jsonl
akmon evidence verify .akmon/evidence/<session-id>.json
akmon slo verify .akmon/evidence/<session-id>.json --strict

Docs links

Full Changelog: https://github.com/radotsvetkov/akmon/compare/v1.8.0...v1.8.1

v1.8.0 Breaking risk
⚠ Upgrade required
  • Validate evidence using the updated `evidence_schema_version`.
  • Adopt the new policy precedence model defined in profile JSONL files.
Breaking changes
  • Update audit parsers to `AuditChainRecord` with `schema_version: "audit_chain.v1"`.
  • Run report parsers must accept additive fields `replay_metadata` and `reliability_metrics`.
Notable features
  • Deterministic policy controls via reusable profiles (`dev`, `staging`, `prod`).
  • Verifiable execution trail with `akmon audit verify` and `akmon evidence verify`.
  • Replay metadata for forensic reproducibility in structured output.
Full changelog

Release notes: v1.8.0

Why this release

v1.8.0 makes Akmon a practical trust runtime for AI-assisted engineering by combining policy governance, tamper-evident auditing, replay/evidence artifacts, and enforceable reliability gates into one operator workflow.

Top user-facing wins

  1. Deterministic policy controls with reusable profiles/packs (dev, staging, prod).
  2. Verifiable execution trail (akmon audit verify, akmon evidence verify).
  3. Replay metadata for forensic reproducibility in structured output.
  4. Reliability metrics exposed in run reports and evidence artifacts.
  5. CI-ready guardrails (akmon slo verify and akmon slo trend).

Migration checklist

  • Update audit parsers to AuditChainRecord (schema_version: "audit_chain.v1").
  • Update run report parsers to accept additive replay_metadata and reliability_metrics.
  • Validate evidence using evidence_schema_version.
  • Adopt policy precedence model: profile < packs < local < CLI override.

Verification checklist

akmon --yes --output json --task "run tests and summarize failures" | tee run.json
akmon audit verify .akmon/audit/<session-id>.jsonl
akmon evidence verify .akmon/evidence/<session-id>.json
akmon slo verify .akmon/evidence/<session-id>.json --strict
akmon slo trend .akmon/evidence/<session-id>.json --baseline-dir .akmon/evidence/history --window 20 --strict

Tutorials

Full Changelog: https://github.com/radotsvetkov/akmon/compare/v1.7.7...v1.8.0

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.

About

Stars
20
Forks
5
Languages
Rust HTML C++

Install & Platforms

Install via
shell-script
Platforms
linux

Beta — feedback welcome: [email protected]