Axion
Analyze → Plan → Execute → Validate
A deterministic, local-first AI orchestrator for software engineers.
Axion is not a chat interface. It is not autocomplete. It is not “AI magic”.
It is an engineering tool.
What Axion is (and what it is not)
Axion treats Large Language Models as non-deterministic execution engines that must operate inside a strict, auditable pipeline.
Instead of asking an AI “please fix my code”, you force it to:
- Analyze the real project structure
- Plan concrete technical steps
- Execute changes as reviewable diffs
- Validate results with real tooling
No hidden prompts.
No blind edits.
No guessing.
Why this project exists
Most AI coding tools optimize for speed of output.
Software engineering optimizes for:
- correctness
- predictability
- debuggability
- long-term maintainability
That mismatch causes real problems:
- Code is generated without understanding the project
- Developers approve changes they don’t fully understand
- Bugs are pushed faster, not fewer
Axion exists to slow AI down and force it to behave like a junior engineer working under strict supervision.
The core difference
| Aspect | Typical AI Tools | Axion |
|---|---|---|
| Interaction | Chat / Autocomplete | Structured pipeline |
| Control | Implicit | Explicit and reviewable |
| Output | Raw code | Unified diffs |
| Context | Prompt-limited | Project-aware |
| Validation | Manual | Automated |
| Philosophy | “Trust the model” | “Trust the process” |
Design principles
Local-first
Your code stays on your machine. Axion runs locally and only sends what is strictly necessary to the model.
No magic
Every decision is logged. Every step is inspectable. Every change is explicit.
Tool-driven
The AI uses tools (AST parsing, tests, linters). It does not replace them.
Human-in-the-loop
Nothing is applied without your approval.
What Axion can do today
-
🔍 Structural code reviews
Detect bugs, architectural risks, performance issues, and security problems. -
🧭 Technical planning
Generate step-by-step implementation plans in Markdown. -
🧩 Diff-based solutions
Propose changes as standard unified diffs — no direct file mutation. -
🧪 Local validation
Run tests and tooling before applying changes. -
🔌 Extensible architecture
Plugin system for custom tools and workflows. -
🤖 Model agnostic
Works with OpenAI, Anthropic, Ollama, and any LiteLLM-compatible provider.
Installation
pip install axionflow
Python 3.10+ required.
Basic usage
Initialize / Review a project
axion review .
Generate a technical plan
axion plan "Refactor authentication to use JWT with refresh tokens"
Solve a concrete problem
axion solve "Fix silent failures in the reasoning engine error handling"
All commands follow the same pipeline:
Analyze → Plan → Execute → Validate
Extending Axion
Axion is designed to be extended by engineers.
- Custom tools
- Custom validators
- Custom reasoning steps
See the Plugin Development Guide.
Contributing
Axion is not looking for volume. It is looking for engineering-quality contributions.
If you care about:
- clean abstractions
- predictable systems
- readable diffs
- testable behavior
You’ll fit right in.
See CONTRIBUTING.md.
“Understanding the internals is the first step to excellence.”
Metadata
Release files for axionflow 1.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| axionflow-1.4.0.tar.gz | 37.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| axionflow-1.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 76.9 kB
Release files / axionflow-1.4.0.tar.gz
| Download URL | axionflow-1.4.0.tar.gz |
|---|---|
| Size | 37.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3abbd275c3c0144035d0a58bcaf6f0587887d476522442a2885294870d0da323
|
|
BLAKE2b-256 checksum How to use checksums |
e00ae56a13e7bc1d6d59cc2f1413bb8c41f4f79e287bfe66c14e2a1ad9e77931
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 13, 2026.
Transparency logRelease files / axionflow-1.4.0-py3-none-any.whl
| Download URL | axionflow-1.4.0-py3-none-any.whl |
|---|---|
| Size | 39.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f8291e3a680d34584cdf51d3ca0244f17ad6694f6845ee4af8622037f50c0c9e
|
|
BLAKE2b-256 checksum How to use checksums |
342c1d3f97fc70eb724b69a80966160d8007551898e4e9cec1a6ad81a7e81349
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 13, 2026.
Transparency log