Agent Cursor
A VS Code extension that shows where your coding agents are working, live: a marker on the line each one is on, edits that glow as they land, and a sidebar where every agent has its own look.
Why I built it
I kept losing track of where my coding agents were. With two or three sessions running in the same repo, all reading and editing files, I couldn't tell which one was where until they were done. So I built them a cursor, like the ones you see when someone else is in a shared doc.
What it shows
- A marker on the exact line each agent is on, with what it is doing ("Claude · editing"), pulsing while it works
- Lines it changes glow in its colour, then fade out over a few seconds
- Badges in the file explorer for where each agent is now, and which files it read or changed
- An Agent panel in the sidebar: your files, with each agent sliding from file to file as it moves, and a feed of everything it did
- Follow mode, which opens whatever file the agent moves to (it waits while you are typing)
Every agent gets its own look
Each agent has its own shape and colour, and a different shade for each session, so you can tell them apart at a glance. It hooks into Claude Code, Codex, Gemini CLI, Qwen Code, Cursor, Copilot CLI, OpenCode, Kimi Code and Windsurf. I have tested it live with Claude Code; the others are built from each agent's hook docs and tested against the payloads those docs describe.
How it works
Most coding agents can run a script every time they use a tool. Agent Cursor adds a small one that turns each agent's payload into one common shape and writes a line to a log on your machine. The extension follows that log and draws the agents. Nothing leaves your computer, and the hooks run in the background so they never slow an agent down.
What I learnt building it
- Check the real payload. The docs didn't confirm every field name, so I ran a real session and read the log before trusting any of them.
- VS Code's webviews block inline styles. The first version stacked every file in the sidebar on top of each other because of it, and my test page didn't have the same rule, so it only showed up on a real install.
- Codex edits files with a patch that has no line numbers. Agent Cursor finds the changed text in the file to place the glow on the right lines.
- Some agents expect their hooks to answer allow or deny. For those, Agent Cursor only listens after each action, so it can never approve or block anything for you.
Try it
Download the .vsix from the GitHub releases page, then in VS Code go to Extensions, open the ... menu and choose Install from VSIX. Open the Agent panel, click Connect, and tick the agents you use. Want to see it first? The Try the demo button runs three made-up agents over your own files.