✦ ✦ ✦ ▓▓▓ ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ ▒▒▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▒▒ ▒▒▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▒▒ ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ ▓▓▓▓▓▓▓▓▓▓▓▓ ▓▓ ▓▓ ▓▓ ▓▓ ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
AI coding sessions you can verify, replay, and defend in review.
Akmon is a terminal-first AI coding agent for regulated engineering teams that need explicit policy boundaries, auditable tool activity, and portable session evidence across local development and CI.
Realistic workflow preview for regulated teams: scoped discovery, policy-gated changes, then verifiable evidence checks. The sequence below cycles through a representative run.
Step 1 — You steer; Akmon proposes tools.
Akmon is designed for teams that need defensible software change history: explicit permissions, portable session evidence, deterministic checks, and provider control.
Every run can produce structured audit and evidence artifacts that survive beyond chat history and support review workflows.
Filesystem, shell, network, and tool actions are policy-evaluated, so sensitive operations are governed instead of implied.
Terminal-first operation in local shells, SSH, and CI without dependency on editor plugin runtime stacks.
Use local or hosted models with your own credentials and routing choices, instead of binding engineering workflows to one vendor.
Token usage, cache effects, and run cost estimates stay visible so teams can reason about budget and drift over time.
Review write hunks before approval, compare sessions with akmon diff, and validate deterministic behavior with replay workflows.
Use akmon slo verify and akmon slo trend to enforce reliability thresholds in CI instead of relying on ad hoc confidence.
Move from dev to staging to prod using deterministic profile + policy-pack layering and effective-policy inspection.
v2.0.0 organizes Akmon around a reviewable session lifecycle: run, inspect, replay, diff, verify, and evidence export. Sessions are content-addressed, cryptographically linked, replayable, and portable as AGEF bundles.
Wondering how Akmon differs from other coding agents? Other tools vs Akmon — short notes in the docs, not a billboard here.
GitHub Releases attach a real binary per platform. Writing to /usr/local/bin usually requires sudo on macOS — installing to ~/bin avoids that. If a download is HTML instead of a binary, the matching release asset is missing (cut a v* tag after the release workflow runs).
One tool, any model. Set an environment variable and it works. No config files required to get started.
Akmon logs every action to a JSONL audit file. Every session ends with a full summary—so you can see what ran, what it cost, and what changed.
See exactly what changes before approving. Green for additions, red for removals.
Every tool call, permission verdict, and token usage logged with timestamps.
Sessions end with tool calls, files touched, cache savings, and USD cost.
Cache hit tokens shown in green. Session cost always visible.
Akmon is Apache 2.0—friendly to shipping CLI wrappers, internal forks, and agent experiments. Issues, docs fixes, and focused PRs are welcome.
Read the development setup, run tests with cargo test --workspace, and open a PR with a clear description.
The book covers tutorials, capabilities, and automation patterns—help us keep examples sharp.
Apache 2.0 only. See license notes for why that fits agent tooling.
The AI agent that respects your security, your budget, and your workflow. Single binary. No subscription. Every action audited.