Dejo
A browser your AI agent remembers. This is the engine.
Your agent walks a website once: signing in, clicking, reading. Dejo writes down the route. Every run after that follows the route instead: one call, no page reading, zero model calls. When the site changes, Dejo repairs the one step that moved and keeps the rest.
pip install dejo
playwright install chromium # the browser, a separate download
dejo run "count open issues" --site github.com
dejo show github.com # the route, step by step
dejo forget --site github.com # make it forget
Most people want Dejo wired into their agent instead. That is
dejo-mcp: Dejo as MCP tools for Claude Code, Codex,
Cursor and any MCP client.
No API key and no account. Dejo never calls a model, and the memory is a local file.
Documentation: https://github.com/dejohq/dejo-mcp · Website: https://dejo.run · MIT licensed.
1 maintainer
Metadata
1 maintainer
Release files for dejo 0.1.2
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 | |
|---|---|---|---|---|
| dejo-0.1.2.tar.gz | 217.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dejo-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 344.4 kB
Release files / dejo-0.1.2.tar.gz
| Download URL | dejo-0.1.2.tar.gz |
|---|---|
| Size | 217.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9abece049f1bda7bdfeb0499808443e219a8ef5b774ee249cd3760dba4011a7a
|
|
BLAKE2b-256 checksum How to use checksums |
546007fefc6c9e145f4256eb3f15a863c1413d56a81fc72ed51445d00375a046
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.7
|
Release files / dejo-0.1.2-py3-none-any.whl
| Download URL | dejo-0.1.2-py3-none-any.whl |
|---|---|
| Size | 127.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3f110ef5c2998ce0d7604f5549aa872b0c6ee3ec505eefb385c8393f5f29f229
|
|
BLAKE2b-256 checksum How to use checksums |
b03a46e3cb4cccfab7aa75ee1ff947c5cd97575a373188644548181c28cdce8e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.7
|
Security for dejo 0.1.2
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.
