LLM Workflow Engine
LLM Workflow Engine (LWE) is a Power CLI and Workflow manager for LLMs.
Read the documentation
WATCH INTRO VIDEO
Welcome!
What would you like to do?
- Learn about the project
- Install LWE
- Learn how to use it
- Read the documentation
- Learn more about configuration/features
- Troubleshoot common issues
- Upgrade LWE
- Using GPT4
- Report a bug
- Get support
What happend to the original ChatGPT Wrapper project?
ChatGPT Wrapper was an amazing tool for its time, thank you to its original creator mmabrouk for all your hard work, it lives on in a new form :)
Highlights
🤖 LWE lets you use the powerful ChatGPT/GPT4 bot from the command line.
💬 Runs in Shell. You can call and interact with ChatGPT/GPT4 in the terminal.
💻 Supports official ChatGPT API. Make API calls directly to the OpenAI ChatGPT endpoint (all supported models accessible by your OpenAI account)
🔌 Simple plugin architecture. Extend LWE with custom functionality
🗣 Supports multiple LLM providers. Provider plugins allow interacting with other LLMs (GPT-3, Cohere, Huggingface, etc.)
🔄Build workflows. Easily integrate calls to an LLM into larger workflows via Ansible Playbooks
🔧 Tool use. (for supported providers)
🐳 Docker image. LWE is also available as a docker image. (experimental)
🐍Python API. LWE also has a Python library that lets you use ChatGPT/GPT4 in your Python scripts.
Projects built with the original ChatGPT Wrapper
- bookast: ChatGPT Podcast Generator For Books
- ChatGPT.el: ChatGPT in Emacs
- ChatGPT Reddit Bot
- Smarty GPT
- ChatGPTify
- selection-to-chatgpt
Contributing
We welcome contributions to LWE! If you have an idea for a new feature or have found a bug, please open an issue on the GitHub repository.
License
This project is licensed under the MIT License - see the LICENSE file for details.
Acknowledgments
- The original ChatGPT Wrapper project (which LWE grew from) was created and maintained by mmabrouk
- The original ChatGPT Wrapper project is a modification from Taranjeet code which is a modification of Daniel Gross code.
Star History
1 maintainer
Metadata
1 maintainer
Release files for llm-workflow-engine 0.23.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 | |
|---|---|---|---|
| llm_workflow_engine-0.23.0.tar.gz | 151.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| llm_workflow_engine-0.23.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 350.5 kB
Release files / llm_workflow_engine-0.23.0.tar.gz
| Download URL | llm_workflow_engine-0.23.0.tar.gz |
|---|---|
| Size | 151.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6420654aa5c53ceacf92fe9413cdec4f0381d24ce23d2287d892894c7ba00895
|
|
BLAKE2b-256 checksum How to use checksums |
f59fc1e9df2f4227887d22eaa73ef1d050f7dd0cf31e06eb952f11eac85977ec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 13, 2026.
Transparency logRelease files / llm_workflow_engine-0.23.0-py3-none-any.whl
| Download URL | llm_workflow_engine-0.23.0-py3-none-any.whl |
|---|---|
| Size | 198.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ddd0c8ec618cebd39292f04d2f2ccae52c482f992bd56fb731f36abdd7f10634
|
|
BLAKE2b-256 checksum How to use checksums |
487a0823e349398d8a9f5d37ffe99b338e145f91554902a0a381f217f36e3dd0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 13, 2026.
Transparency log
