I built `/steal` — a Cursor slash command that pulls in your latest Kilo Code / GLM 5.2 chat and vice versa
Cursor doesn't ship GLM 5.2 (or any Fireworks models), so a lot of us use Cursor
for Opus 4.8 and something like Kilo Code + Fireworks for GLM. Great — until you
want to move between them mid-task and end up re-explaining the whole context.
I wrote a tiny MIT tool that installs a `/steal` slash command in both editors.
In Cursor, `/steal` pulls in your most recent Kilo session for the current
project; in Kilo, `/steal` pulls in your most recent Cursor session. Direction is
baked in — no arguments to remember. About 50 ms per call because it reads each
tool's session store directly (Cursor's JSONL under
`~/.cursor/projects/<slug>/agent-transcripts/`, Kilo's SQLite under
`~/.local/share/kilo/kilo.db`) instead of scanning your whole history.
Install:
npm i -g steal-context
cd your-project
steal-context init
Then `/steal` in either tool.
Everything is local, read-only, MIT-licensed. Default handoff is 40 messages
sized for Opus/GLM's context windows, adjustable.
Repo: https://github.com/alonsorobots/steal-context
Curious if others hit the same workflow gap and if there are other Cursor pairings
worth supporting fast (Cline, Claude Code, Codex, etc.).