CodeLogician
CodeLogician is the neurosymbolic agentic governance framework for AI-powered coding.
It helps your coding agent think logically about the code it's producing and test cases it's generating. The fundamental flaw that all LLM-powered assistants have is the reasoning they're capable of is based on statistics, while you need rigorous logic-based automated reasoning.
- Generated code is based on explainable logic, not pure statistics
- Generated test cases are generated come with quantitative coverage metrics
- Generated code is consistent with the best security practices leveraging formal verification
To run CodeLogician, please obtain an Imandra Universe API key available (there's a free starting plan)
at Imandra Universe and make sure it's available in your environment as IMANDRA_UNI_KEY.
Three typical workflows:
- DIY mode - this is where your agent (e.g. Grok) uses the CLI to:
- Learn how to use IML/ImandraX via
doccommand (e.g.codelogician doc --help) - Synthesizes IML code and uses the
evalcommand to evaluate it - If there're errors, use
codelogician doc view errorscommand to study how to correct the errors and re-evalute the code
- Agent/multi-agent mode - CodeLogician IML Agent is a Langgraph-based agent for automatically formalizing source code into Imandra Modeling Language (IML).
- With
agentcommand you can formalize a single source code file (e.g.codelogician agent PATH_TO_FILE) - With
multiagentcommand you can formalize a whole directory (e.g.codelogician agent PATH_TO_DIR)
- Server
- This is a "live" and interactive version of the
multiagentcommand - It monitors the filesystem and fire's off formalization tasks on source code updates as necessary
- You can start the server and connect to it with the TUI (we recommend separate terminal screens)
Learn more at CodeLogician!
To get started,
codelogician --help
1 maintainer
Metadata
1 maintainer
Release files for codelogician 2.22.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 | |
|---|---|---|---|---|
| codelogician-2.22.0.tar.gz | 147.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| codelogician-2.22.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 342.6 kB
Release files / codelogician-2.22.0.tar.gz
| Download URL | codelogician-2.22.0.tar.gz |
|---|---|
| Size | 147.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0239e5a9644d43b306c4d17ae3a145c7ab84551f813a1af1b72cf228b2fc8a84
|
|
BLAKE2b-256 checksum How to use checksums |
aca516c6ee88330002c3ab8c2d0671cc40c67a504ac47fa2c5e24ad0bbf73018
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.22
|
Release files / codelogician-2.22.0-py3-none-any.whl
| Download URL | codelogician-2.22.0-py3-none-any.whl |
|---|---|
| Size | 195.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d5aae062fb2c00c1f736772b3d11af9c0942e23d2099bcb6ddd4e785b26b4f7b
|
|
BLAKE2b-256 checksum How to use checksums |
531cd63217cd6882f664d354f188fa2edfae45c3117483e9d530234369777329
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.22
|
Security for codelogician 2.22.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.
