GhostMode
The Air-Gapped, Self-Healing Code Repair Agent for Low-Resource Hardware.
GhostMode runs a trusted test command, identifies a likely application frame, asks a local Ollama model for a function replacement, applies it with a backup, and retains it only after the tests pass. It never contacts a network target other than loopback Ollama.
Supported languages
GhostMode currently supports Python, JavaScript/React (.js, .jsx, .ts, .tsx), and PHP/Laravel. Python receives AST syntax validation; JavaScript/React and PHP use conservative structural validation before their own local test tools provide final verification.
Install and run
pip install ghostmode-cli
ollama pull qwen2.5-coder:1.5b
ghostmode doctor
To upgrade an existing installation:
pip install --upgrade ghostmode-cli
Run GhostMode from the project you want to repair:
ghostmode run "pytest -q"
For npm projects:
ghostmode run "npm test"
Inspect a project locally for high-signal risks without changing files:
ghostmode inspect
Each finding includes severity, repair priority, and potential impact so developers can review the most harmful risks first.
Ask the local model to propose one high-priority inspection fix and verify that existing tests still pass:
ghostmode inspect --propose --test-cmd "pytest -q"
GhostMode asks before applying the proposal. Passing existing tests does not prove the finding is fixed; add a regression test for that behavior.
Use --dry-run to review a diff without changing files. GhostMode never edits tests unless --allow-test-edits is explicitly passed.
For Vitest projects, ghostmode run "npm test" automatically uses single-run mode instead of watch mode.
Memory budget
| Component | Budget |
|---|---|
| GhostMode Python process | under 100 MB RSS |
| Ollama + 0.5B model | about 1 GB |
| Ollama + 1.5B model | about 2 GB |
Limitations
Small local models are best at simple, single-function faults. Multi-file, API-wide, and logic-heavy repairs often need human review. Only run trusted test commands: the command is intentionally executed through a shell to support normal test invocations.
Metadata
Release files for ghostmode-cli 0.1.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| ghostmode_cli-0.1.5.tar.gz | 19.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ghostmode_cli-0.1.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 38.2 kB
Release files / ghostmode_cli-0.1.5.tar.gz
| Download URL | ghostmode_cli-0.1.5.tar.gz |
|---|---|
| Size | 19.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8e10e8ce246a1dbbf3f422388621318408349bcd5cd7f4079cf43c0fc5d77add
|
|
BLAKE2b-256 checksum How to use checksums |
38fb79da90280c9cc31be95c1739231c93954803487226d2f4ed99dfe4d4d580
|
| 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 9, 2026.
Transparency logRelease files / ghostmode_cli-0.1.5-py3-none-any.whl
| Download URL | ghostmode_cli-0.1.5-py3-none-any.whl |
|---|---|
| Size | 18.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bc94ff5d874924769eba556fa28ecddc04f9e09ccffefbc030f3c087353fd004
|
|
BLAKE2b-256 checksum How to use checksums |
3e3ab74118e717a9e8af6e616509045876f0cf8fbbfa11727c0fc8a8de2d95e4
|
| 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 9, 2026.
Transparency log