ContextHop
Hit your limit on Claude? Continue the same work on ChatGPT, Gemini, or any other model - without explaining everything from the beginning.
ContextHop turns a finished (or interrupted) AI conversation into one portable HANDOFF.md file: a starter prompt for the new model + a clean, structured copy of your context. Paste it, and the new model picks up where the old one stopped.
No API key. No account. No server. 100% local and free.
The problem
You spend an hour building something with one AI. Then: "You've reached your limit." You open another model and waste 20 minutes re-explaining the goal, the decisions, the code, and what already failed.
Your context should travel with you, not stay locked inside one app.
Two ways to use it
Way 1 - The Magic Prompt (zero install, works on mobile)
Before your limit runs out, paste the prompt in prompts/magic_handoff_prompt.md as your last message on the old model. It writes its own handoff summary. Paste that summary into the new model. Done.
Way 2 - The Python tool
git clone https://github.com/aryancodes-dev/contexthop.git
cd contexthop
python context_hop.py your_chat.txt
# creates HANDOFF.md - fill the 3 [EDIT ME] lines, then paste/upload it in the new model
Works with transcripts exported or copied from ChatGPT, Claude, Gemini, DeepSeek and Perplexity (lines starting with User: / Claude: / etc.).
Try the example:
python context_hop.py examples/sample_chat.txt
Why not just copy-paste the whole chat?
| Full copy-paste | ContextHop handoff | |
|---|---|---|
| Tokens on new model | 20,000+ | ~500-1,500 (Magic Prompt) |
| New model understands state | Has to dig through chat | Goal / decisions / next step up top |
| Works when limit already hit | Yes, but messy | Yes - transcript mode |
Roadmap
- v0.1 - Python CLI + Magic Prompt
- v0.2 - Auto-detect ChatGPT / Claude JSON exports
- v0.3 - Simple web page version (paste chat -> download HANDOFF.md)
- v0.4 - Browser extension (one-click export)
Contributing
Issues and PRs welcome. Especially: export parsers for new platforms, and translations of the Magic Prompt.
License
MIT - see LICENSE.
Metadata
Release files for contexthop 0.1.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 | |
|---|---|---|---|---|
| contexthop-0.1.0.tar.gz | 5.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| contexthop-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.5 kB
Release files / contexthop-0.1.0.tar.gz
| Download URL | contexthop-0.1.0.tar.gz |
|---|---|
| Size | 5.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
368ee5ccbdf0489f64a169b303a97a0697ef7c1a45f2099a22ebcc21a6894431
|
|
BLAKE2b-256 checksum How to use checksums |
e5c039c889fd943f37c3f350fd2ae1e30099af425c9b5fbcc03d929474f7f6ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / contexthop-0.1.0-py3-none-any.whl
| Download URL | contexthop-0.1.0-py3-none-any.whl |
|---|---|
| Size | 5.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b3b38d0576110657b033e0e95eb8d1fd11fe7713d0ba15d105e2d9b20a93cb29
|
|
BLAKE2b-256 checksum How to use checksums |
00d683fbc832fccbe8edf519a7bbc0589901a79e53d2c3bb7622094ab925f932
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for contexthop 0.1.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.
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.