AutoCraft Enterprise
LLM-powered, AST-safe code generation for FastAPI projects.
Describe an endpoint in plain English. AutoCraft generates the handler, Pydantic schemas, and pytest suite — validated, linted, and committed to a dedicated Git branch. Ready to review.
Why AutoCraft?
| Without AutoCraft | With AutoCraft |
|---|---|
| Write async handler with type hints | Generated automatically, matching your project conventions |
| Define Pydantic v2 request/response schemas | Inferred from your description and existing models |
| Register routes and middlewares | Declared in autocraft.yaml, applied automatically |
| Write tests (happy path + edge cases) | Generated as a full pytest-asyncio suite |
| Open API docs and docstrings | Inserted automatically with Args/Returns/Raises |
AutoCraft is not a chat assistant. It is a deterministic generation pipeline: the LLM's output is always AST-validated, ruff-fixed, and Git-branched for human review before touching your codebase.
Installation
pip install autocraft
Requires Python 3.11+.
Quick Start
# 1 — Set your API key
export MISTRAL_API_KEY=sk-... # or add to .env
# 2 — Initialise AutoCraft in your project
cd my-fastapi-project
autocraft init # creates autocraft.yaml
# 3 — Generate an endpoint
autocraft generate "POST /orders that receives customer_id, product_ids and quantities,
validates stock, saves to DB, returns the order with total price"
AutoCraft will:
- Parse your description (Mistral extracts method, path, inputs, rules, side-effects).
- Scan your project via AST (detects existing models, schemas, conventions).
- Generate handler + schemas + tests using a senior-grade prompt.
- Validate via
ast.parse→mypy→ruff --fix. - Commit to a new branch (
autocraft/order-post-<ts>) — ready forgit diff.
Generated Output
For POST /orders:
app/handlers/order.py ← async FastAPI route with Depends, HTTPException, docstrings
app/schemas/order.py ← OrderCreate, OrderResponse (Pydantic v2)
tests/test_order.py ← pytest-asyncio suite with happy path + edge cases
Sample generated handler:
@router.post("/orders", status_code=status.HTTP_201_CREATED, response_model=OrderResponse)
async def create_order(
order_data: OrderCreate,
db: Annotated[AsyncSession, Depends(get_db)],
current_user: Annotated[User, Depends(get_current_user)],
) -> OrderResponse:
"""
Create a new order with the given products and quantities.
Validates stock availability, calculates total price,
and persists the order and its line items atomically.
Args:
order_data: Customer ID, product IDs, and quantities.
db: Injected async database session.
current_user: JWT-authenticated user.
Returns:
OrderResponse with id, total_price, and created_at.
Raises:
HTTPException 400: mismatched list lengths.
HTTPException 404: unknown customer or product.
HTTPException 409: insufficient stock.
"""
Configuration (autocraft.yaml)
version: '1.0'
llm:
provider: mistral # mistral | openai | anthropic | azure
model: mistral/mistral-large-latest
temperature: 0.2 # low = consistent code
max_tokens: 4096
context:
scan_paths: # dirs scanned by the AST analyzer
- app/handlers
- app/schemas
- app/models
- app/services
max_examples: 3 # few-shot examples sent to the LLM
generation:
output:
handlers: app/handlers/
schemas: app/schemas/
tests: tests/
auto_approve: false # always show diff before merging
create_branch: true
branch_prefix: autocraft/
validation:
run_mypy: true
run_ruff: true
run_tests: true
min_coverage: 80
max_retries: 3
CLI Reference
| Command | Description |
|---|---|
autocraft init |
Scaffold autocraft.yaml in the current directory |
autocraft generate "<description>" |
Run the full generation pipeline |
autocraft review |
Inspect or approve the last generated diff |
How It Works
Natural Language Description
│
▼
┌───────────────────┐
│ Intent Parser │ Mistral extracts: method, path, handler_name,
│ (LLM Phase 1) │ inputs+types, business rules, side-effects, auth
└────────┬──────────┘
│
▼
┌───────────────────┐
│ Context Analyzer │ AST scans project → detects Pydantic models,
│ (AST) │ ORM entities, function signatures, decorators
└────────┬──────────┘
│
▼
┌───────────────────┐
│ Code Generator │ Senior-grade mega-prompt → Mistral produces
│ (LLM Phase 2) │ handler + schemas + tests as a JSON bundle
└────────┬──────────┘
│
▼
┌───────────────────┐
│ Validation │ ast.parse (hard gate) → mypy → ruff advisory
│ Pipeline │
└────────┬──────────┘
│
▼
┌───────────────────┐
│ Review Gateway │ ruff --fix auto-repair → write to disk
│ (Git-Native) │ → git branch + stage → diff summary
└───────────────────┘
Alternative LLM Providers
Edit autocraft.yaml and set the corresponding environment variable:
# OpenAI GPT-4o
llm:
provider: openai
model: gpt-4o
# OPENAI_API_KEY=...
# Anthropic Claude
llm:
provider: anthropic
model: claude-sonnet-4-6
# ANTHROPIC_API_KEY=...
AutoCraft uses litellm under the hood, so any provider supported by litellm works out of the box.
Security
- The LLM never receives credentials,
.envfiles, or production data. - Generated code is validated in an isolated
tempfile.TemporaryDirectorybefore being written to disk. auto_approve: false(default) — every generation requires a human diff review.- The
.envfile is in.gitignoreand never committed.
Contributing
Pull requests are welcome. For major changes, open an issue first.
git clone https://github.com/autocraft-ai/autocraft
cd autocraft
pip install -e ".[dev]"
pytest
License
MIT © 2026 AutoCraft Contributors
Metadata
Release files for autocraft 0.1.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 | Provenance | Actions |
|---|---|---|---|---|
| autocraft-0.1.0.tar.gz | 16.7 kB | Without provenance | Details for autocraft-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| autocraft-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for autocraft-0.1.0-py3-none-any.whl |
Total release size: 37.5 kB
Release files / autocraft-0.1.0.tar.gz
| Download URL | autocraft-0.1.0.tar.gz |
|---|---|
| Size | 16.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4e39cb0831c92ed1b95ad92cb4b2f4c8b673dd6b14c2453865879a92c97cc6a7
|
|
BLAKE2b-256 checksum How to use checksums |
2c483797ce8a49fc67f5e7f681222a0734b52c3b09c826db37bfe6372c9a809e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Release files / autocraft-0.1.0-py3-none-any.whl
| Download URL | autocraft-0.1.0-py3-none-any.whl |
|---|---|
| Size | 20.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e299b7e4686ee976bbf9dca2374c7005c7492e8ce019d0dad7c3c83c94ee8119
|
|
BLAKE2b-256 checksum How to use checksums |
f182c63ad591585aebd08835394f55cc232b85df4ac4f03f86f6bf341216087b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Security for autocraft 0.1.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.