Comodor
The coding agent that stops making the same mistake.
Fix something it wrote, and it never writes it that way again — in this project or the next one. Not a setting you turn on. Not a file you maintain.
curl -fsSL get.comodor.ai | sh # macOS · Linux
irm get.comodor.ai | iex # Windows
████████ ██████ ██ ██ ██████ ████████ ██████ ████████
██ ██ ██ ████ ████ ██ ██ ██ ██ ██ ██ ██ ██
██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ████████
██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██
████████ ██████ ██ ██ ██████ ████████ ██████ ██ ██
it learns the way you correct it
Why this one
Every agent forgets. You correct the same thing on Monday and again on Friday, because the correction went into a conversation that ended.
Comodor watches what you do to its output. Change a name it chose, rewrite a function it wrote, tell it no, use the existing helper — it works out the rule behind the correction, tells you the rule it wrote, and follows it from then on.
◈ learned: naming.functions Name functions in snake_case. 6 of 6 definitions
◈ learned: line.length Keep lines within about 79 characters. 95% of lines are under 79
◈ learned: quotes.style Use double quotes for string literals. 176 of 176 literals
Those are real, read out of a working install.
/progress shows whether that is actually working — corrections per turn,
falling or not. A number, not a claim.
Everything else it does
| Asks instead of guessing | When a request reads two ways it settles what it can by reading your code, then puts the rest as one short form — before writing anything. → |
| Never surprises you | Reading is silent. Writing shows a diff. Commands ask. Every change is checkpointed and /undo puts it back. → |
| Drives a real browser | One that runs JavaScript, keeps cookies and can log in — not a page fetcher. → |
| Uses your screen | Mouse and keyboard in any application, with a halo showing where it is about to click before it clicks. → |
| Runs on your phone | A Telegram bot with the whole interface as buttons. Read-only until you say otherwise. → |
| Runs a model locally | Pick one, watch it download, use it with the network unplugged. No key, no account. → |
| Lives in your editor | Speaks ACP, so VS Code, JetBrains and Zed drive it from their own panels. → |
| Follows your procedures | Write a skill once; it loads when the work matches. 147 ready to install. → |
| Works with any model | Nineteen providers, or anything with an OpenAI-compatible URL. → |
| Costs less | 86% of input tokens served from cache, measured — not estimated. → |
One dependency. The HTTP client, the SSE reader, the WebSocket that drives
Chrome, the PNG encoder for screenshots, the Telegram client — all written here.
Installing Comodor pulls in rich and nothing else.
Install
Recommended installation
Linux / MacOS
curl -fsSL get.comodor.ai | sh
Windows (Powershell)
irm get.comodor.ai | iex
The one-liner above finds a Python, builds an isolated environment, puts
comodor on your PATH, and fetches a Python if there is none. Verified on a
bare debian:bookworm-slim with nothing installed.
Already have a package manager you like?
Install With uv
uv tool install comodor
Install With pip
pip install comodor
Install With pipx
pipx install comodor
Then comodor. Python 3.11 or newer. Six questions the first time, never
again.
No API key? comodor --demo runs the whole interface offline. Or pick a
local model in the setup and pay nothing, ever.
Coming from OpenClaw or Hermes? The first screen offers to bring your keys and skills across. How that works.
Using it
comodor # the interface
comodor run "fix the failing test" --yes # one task, no interface
comodor web # from a browser
comodor telegram start # from your phone
comodor acp # from your editor
comodor doctor # is everything alright?
/help every command /undo restore the last change
/mode act · plan · chat /progress proof it is improving
/cost tokens and spend /computer let it use your screen
Esc stop it F3 cycle mode
Documentation
docs/README.md — organised by what you are trying to do.
| Getting started | Install, choose a model, first task |
| The interface | Panels, keys, and all 29 commands |
| How it learns | Corrections, rules, and the evidence |
| What it can do | The 13 tools, and when it uses each |
| Safety and permissions | What it asks, and what it never does |
| From your phone | The Telegram bot, and who it answers |
| Models on your machine | Downloading one, running it offline |
| Configuration | Every setting, and what wins |
| Cost | Caching, budgets, paying less |
| Troubleshooting | When something is wrong |
Development
git clone https://github.com/ifekri/Comodor.git
cd Comodor
uv venv && uv pip install -e ".[dev]"
uv run pytest -q
uv run ruff check .
Both pass on Linux and Windows before anything is pushed. CONTRIBUTING.md
Licence
MIT — LICENSE. Security: SECURITY.md, please not a public issue.
Metadata
Release files for comodor 0.17.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 | Actions |
|---|---|---|---|---|
| comodor-0.17.0.tar.gz | 750.9 kB | With provenance | Details for comodor-0.17.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| comodor-0.17.0-py3-none-any.whl | Python 3 | none | any | Details for comodor-0.17.0-py3-none-any.whl |
Total release size: 1.4 MB
Release files / comodor-0.17.0.tar.gz
| Download URL | comodor-0.17.0.tar.gz |
|---|---|
| Size | 750.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cb3ff5a7a7cb56dbeaa923d10dec6b8b52a8e122f7c4c90e67459920bd244780
|
|
BLAKE2b-256 checksum How to use checksums |
f39adc1612cdf3faf14cec7e753bb8b5dfca001224d834d67e275124c60cc29a
|
| 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 Aug 28, 2026.
Transparency logRelease files / comodor-0.17.0-py3-none-any.whl
| Download URL | comodor-0.17.0-py3-none-any.whl |
|---|---|
| Size | 650.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e08981c578000a63d5e541e5b35b553c8ecc346de86708d578dfbf71d9839ef6
|
|
BLAKE2b-256 checksum How to use checksums |
3032f8f1289a88e2d3a1fe488dda23ed5b70370616da6e083a805e7ff3334351
|
| 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 Aug 28, 2026.
Transparency logSecurity for comodor 0.17.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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for comodor-0.17.0.tar.gz
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 Aug 28, 2026.
Transparency logA 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.