FrankCode
Advanced multi-agent orchestrator for OpenCode.
FrankCode acts as a wrapper and orchestration layer around OpenCode, managing specialized agent setups, safety plugins, verification passes, and environment configurations to accomplish complex development tasks safely and robustly.
Requirements
Before installing FrankCode, ensure you have the following prerequisites installed on your system:
- Python:
>= 3.10 - Node.js & npm: Required to install OpenCode plugins and manage the environment dynamically. FrankCode will attempt to automatically resolve Node via
nvmif available. - OpenCode: Make sure the
opencodeCLI is installed and available in yourPATH.
Installation
You can install FrankCode directly via pip:
pip install frankcode
Alternatively, to run from source:
git clone https://github.com/joeyism/frankcode.git
cd frankcode
pip install -e .
Usage
FrankCode provides a simple CLI. To execute a task using the default multi-agent orchestrator:
frankcode exec "Create a new React component that fetches data from an API and displays it in a table"
Options
--model: Specify the LLM model to use (default:google/gemini-3.1-pro-preview).--verbose,-v: Show debug logs.--no-verify: Disable the autonomous verification and fix passes.--clean: Wipe the.frankcodeexecution environment before starting.
Example:
frankcode exec "Refactor the auth logic to use JWT" --model openai/gpt-5.4 --verbose
How It Works
- Environment Setup: FrankCode creates an isolated
.frankcodedirectory to store logs, quarantine artifacts, and install specific OpenCode plugins dynamically. - Execution: Your prompt is passed into an enhanced OpenCode session. FrankCode actively monitors the process for infinite error loops or idle timeouts.
- Verification Loop (Optional but enabled by default): After the main task completes, an adversarial validation agent reads the outputs and devises independent tests. If the tests fail, FrankCode triggers a "fix pass" and repeats the verification.
- Cleanup: Temporary artifacts generated during agent reasoning are quarantined.
License
MIT License. See LICENSE for details.
Metadata
Release files for frankcode 0.1.10
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| frankcode-0.1.10.tar.gz | 328.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| frankcode-0.1.10-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 692.6 kB
Release files / frankcode-0.1.10.tar.gz
| Download URL | frankcode-0.1.10.tar.gz |
|---|---|
| Size | 328.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9f729e9e365b5d1dedf842b4907b2a8b8009e211a4c54b85cbc5b3bd7caa361e
|
|
BLAKE2b-256 checksum How to use checksums |
90a988728270a4f1d3c844102860713d5a918a3eb06493db8ff9fcb92c65183e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 15, 2026.
Transparency logRelease files / frankcode-0.1.10-py3-none-any.whl
| Download URL | frankcode-0.1.10-py3-none-any.whl |
|---|---|
| Size | 364.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cd26216467b1cd268bb7f5d091c5b942c716ca7fa9dbe71fe7ef8c81cc257467
|
|
BLAKE2b-256 checksum How to use checksums |
ebff19c44b22ca0f0f82363cf24dfca01d8b7174f4d8f6f09d53318fc68f9fa5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 15, 2026.
Transparency log