`/steal` moves recent context between Cursor and Kilo Code
`/steal` is a small tool that moves recent between Cursor and Kilo Code. Cursor does not include GLM 5.2 or Fireworks models, so some makers use Cursor with Opus 4.8 and use Kilo Code with Fireworks for GLM. Switching tools during the same task can force the same background explanation to be repeated.
After setup, typing `/steal` in Cursor brings in the latest Kilo Code session for the current project, and typing `/steal` in Kilo Code brings in the latest Cursor session. The direction is automatic, so there are no extra options to remember. It takes about 50 milliseconds because it reads Cursor’s JSONL session files and Kilo Code’s directly instead of searching a full history.
Setup uses `npm i -g steal-context`, then `steal-context init` inside the project folder, then `/steal` inside either tool. It , reads only, sends 40 recent messages by default, allows that number to be changed, and is released under the .
Key points
- `/steal` copies recent project between Cursor and Kilo Code.
- In Cursor it pulls the latest Kilo Code session; in Kilo Code it pulls the latest Cursor session.
- It reads Cursor JSONL files and the Kilo Code directly, so each call is about 50 milliseconds.
- Setup uses a global npm install, then project-level initialization.
- It is local, read-only, , and defaults to handing over 40 recent messages.