coreason-optimizer
Automated Prompt Engineering / LLM Compilation / DSPy Integration for CoReason-AI
coreason-optimizer is the "Compiler" for the CoReason Agentic Platform. It automates prompt engineering by treating prompts as trainable weights, optimizing them against ground-truth datasets to maximize performance metrics.
Installation
pip install coreason-optimizer
Features
- Automated Optimization: Rewrites instructions and selects examples to maximize a score, not human intuition.
- Optimization-as-a-Service: Run as a microservice API to compile prompts on-demand.
- Model-Specific Compilation: Generates optimized prompts specifically tuned for target models (e.g., GPT-4, Claude 3.5).
- Continuous Learning: Re-runs optimization on recent logs to patch prompts against data drift.
- Mutate-Evaluate Loop: Systematic cycle of drafting, evaluating, diagnosing, mutating, and selecting prompts.
- Strategies: Includes BootstrapFewShot (mining successful traces) and MIPRO (Multi-prompt Instruction PRoposal Optimizer).
- Integration: Works seamlessly with
coreason-construct,coreason-archive, andcoreason-assay.
For full product requirements, see docs/product_requirements.md.
Usage
You can use coreason-optimizer as a Python library, a CLI tool, or a Microservice.
1. Python Library
from coreason_optimizer import OptimizerConfig, PromptOptimizer
from coreason_optimizer.core.interfaces import Construct
from coreason_optimizer.data import Dataset
# Define Agent
class MockAgent(Construct):
inputs = ["question"]
outputs = ["answer"]
system_prompt = "You are a helpful assistant."
agent = MockAgent()
# Compile
dataset = Dataset.from_csv("data/gold_set.csv")
train_set, val_set = dataset.split(train_ratio=0.8)
optimizer = PromptOptimizer(config=OptimizerConfig(target_model="gpt-4o"))
manifest = optimizer.compile(agent, train_set, val_set)
print(f"Optimized Score: {manifest.performance_metric}")
2. Server Mode (Microservice)
Run the optimizer as a standalone service using Docker:
docker run -p 8000:8000 -e OPENAI_API_KEY=$OPENAI_API_KEY coreason-optimizer:latest
Then call the API:
curl -X POST http://localhost:8000/optimize -d @request.json
For detailed instructions, see docs/usage.md.
Metadata
Release files for coreason-optimizer 0.3.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 | |
|---|---|---|---|
| coreason_optimizer-0.3.0.tar.gz | 27.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| coreason_optimizer-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 68.7 kB
Release files / coreason_optimizer-0.3.0.tar.gz
| Download URL | coreason_optimizer-0.3.0.tar.gz |
|---|---|
| Size | 27.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aa664a7335c0fb5e00e7df70901bd06cc72f155f65d0d3319daaa231db83aa64
|
|
BLAKE2b-256 checksum How to use checksums |
020ea05685293cd3eb86062cc41917f9329467e8b4db214993d823a59476050e
|
| 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 Jan 31, 2026.
Transparency logRelease files / coreason_optimizer-0.3.0-py3-none-any.whl
| Download URL | coreason_optimizer-0.3.0-py3-none-any.whl |
|---|---|
| Size | 41.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bc506f24b69b7cf17e938c9ad71c0819a6a223ebf14d1249a14288521dcecf11
|
|
BLAKE2b-256 checksum How to use checksums |
3bdcae3f39ef28871ea1dcfe5a79c7c8bbdedbd1fb04252c54a949a567a14d26
|
| 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 Jan 31, 2026.
Transparency log