lot-map
by alexeyw
A live map beside the chat that shows what Claude Code is doing: tool calls, model steps, hooks, skills and subagents light up as they happen. Local only, in five languages.
118stars
13forks
TypeScript
Added 11/11/2026
Available after the catalog security scan passes.
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
AI Agentsagent-observabilityai-agentsclaudeclaude-codeclaude-code-plugindeveloper-toolssvg-animationtypescriptvisualization
Maintainer of this skill?
Installation
# Add to your Claude Code skills
git clone https://github.com/alexeyw/lot-mapGetting Started
Guides for using ai agents skills like lot-map.
- Caveman: Cut Claude Token Use by 65%How agent-side prompt compression works, when to use it, and when not to.
- How to Test an AI Skill: A Practical Guide to EvalsEvaluate skills with realistic fixtures, a baseline, and repeatable checks.
- Getting Started with AI SkillsFirst-time install walkthrough for Claude Code, Codex CLI, and ChatGPT.
Compare with similar skills
See how lot-map compares with popular alternatives.
lot-map
A mod for Claude Code: a live map of the work, in a pane beside the chat. Every tool call, model step, hook and skill sends a pulse from the centre to its station, so you see memory, files, shell, web and agents at work instead of reading a list of commands.
A made-up session replayed through the mod's own drawing code. Video (MP4).
Install
At the prompt of a terminal session:
/plugin install lot-map --marketplace alexeyw/lot-map
Answer y to add the marketplace, then choose a scope. From a shell:
claude plugin install lot-map --marketplace alexeyw/lot-map
In the desktop app: click + next to the prompt box, then Plugins, Add marketplace with alexeyw/lot-map, then Add plugin.
The pane opens by itself when a session starts. In a terminal it needs at least 144 columns and draws text only; otherwise type /lot-map. Built and tested on Claude Code 2.1.321 on macOS; users report it working on Windows as well.
What lights up
| Station | When |
|---|---|
| You | your messages, questions and files sent to you |
| Model | each model request, context compaction |
| Memory | Claude Code's memory folder, plus whatever you name in the options |
| Files | Read, Write, Edit, Grep, Glob, and shell commands that work on files and nothing else: they read, search, move, delete or edit in place (cat, grep, mv, sed -i, tee, find … -delete) |
| Shell | every other shell command |
| Network | web fetch and search, MCP servers, and shell commands known to reach the network: curl, gh, ssh, rsync, git push, npm install, docker pull and the like, also inside $(…) |
| Browser | browser tools |
| Agents | subagents and workflows; their own calls start from this station |
| Skills | skills and tool search |
| Hooks | settings hooks that refuse a call, ask for permission, add context or take a moment |
The shell stations go by the command's name, not by what it does: a script that opens a connection itself, such as python -c "…", shows as Shell.
A pulse flies out when something starts and returns when it ends. Refusals and errors turn red.
Reading the map
- The route. A thin line joins the last few stations the main loop went through, in order, and its newest leg draws itself. Model steps are left out, or every leg would pass through Model.
- Worn spokes. A spoke grows thicker and brighter the more its station is used, so at the end of a session the map shows where the work went.
- How long. Two clock hands grow around a station while a call runs: the inner one goes round in a minute, the outer one in ten.
- Several at once. Calls that start together fly side by side, and the station carries their number, such as
×3. - What went wrong. A red dot with a count stays on a station from an error or a refusal until your next message.
- Memory. It has a colour of its own. A solid pulse is a memory Claude asked for; a hollow one on a dashed line is what a hook brought unasked. Under the station, the plain number counts the first and
↓the second. - The context window. The ring around the centre fills as the session goes, with the percentage above the name. It turns amber at 70% and red at 90%.
- A change of model. The centre and the Model station ring for a few seconds, and the feed gets a row such as
opus 5.5 → fable 5.2. This also happens when a session starts on a different model from the last session in the same folder. - Subagents. Each one still at work circles the Agents station as a small dot, and its calls start from there.
- The answer. One wide ring leaves the centre when the answer is ready.
Below the map are the current action with the context percentage, and the last 16 rows: ● running, · done, ✕ failed or blocked, ◆ a change of model. Finished calls that follow one another at one station fold into one row, marked +2 for the two it stands for besides the one named.
| At work | Subagents | A hook refuses |
|---|---|---|
 |
 |
 |
| A change of model | After the answer | Light colours |
|---|---|---|
 |
 |
 |
Options
The install offers them on a screen. Later, use /config in a terminal or claude plugin configure, then restart the session.
| Option | Default | Meaning |
|---|---|---|
language |
en |
en, ru, es, fr or de |
coreName |
CLAUDE |
what the circle in the middle says, up to ten characters |
memoryServers |
memory |
MCP servers whose tools light Memory |
memoryCommands |
none | shell commands or scripts that light Memory; a name counts when it is the command itself or begins with it and -, _ or ., so recall also names recall-sync.py |
memorySubcommands |
none | words after a memory command that the map may show, such as add or search; without them the command goes by its own name |
memoryPaths |
none | parts of a path that make a file a memory |
memoryLabels |
none | short names for memory tools, each as tool=name |
hookRecords |
false |
turn on if a hook of yours adds memory records numbered like [#123]; they appear on Memory by number only. Such a number in the text of any hook counts, not only a memory hook's |
hookReasons |
false |
show the first line of a hook's refusal, up to 72 characters; off, the map says only which tool was stopped |
theme |
auto |
the map's colours: dark, light, or auto, which is dark on a dark surface and light on a light one |
layout |
you-top |
where you are on the map: you-top, or you-bottom, which turns the ring half a turn so that you are at the bottom and the network and the browser at the top |
For example, Russian labels and your own memory server:
echo '{"language":"ru","memoryServers":"my-memory"}' | claude plugin configure lot-map@lot-map --values-stdin
Lists are written with commas.
| Russian labels | layout set to you-bottom |
|---|---|
What it shows and what it keeps
The mod makes no network requests, reads no files, runs no processes, calls no model and adds nothing to the conversation. Its rows live only for the session.
Like any mod that follows tool calls, it is handed every call's whole input, including command lines and the text written to files. It takes names from that and nothing else; the code that does so is classify in hooks/map.ts. A marketplace added from this repository follows its main branch, so an update brings whatever is there: read the diff before updating if that matters to you.
It asks Claude Code for one thing: how full the context window is, after each model step. Between sessions it keeps one thing, the name of the model last used in each folder, so that it can show a change. Each is stored under the folder's full path, in Claude Code's own store for the plugin.
A label holds a name, never content:
- a file: the last two parts of its path;
- a web address: the host alone, without a login, password, path or query; an address that can be read two ways shows only its scheme;
- a shell command: the short description Claude wrote for it, or the command's name, never the command line;
- a memory call: the tool's name and a record number or short identifier, never the text or the query;
- a memory command: its name, and the word after it only if you listed that word in
memorySubcommands; - a subagent: the short description it was started with;
- a hook's refusal: the name of the tool it stopped. Its first line shows only with
hookReasonson, because a refusal may quote what the hook found.
Control characters are taken out of every label before it is drawn.
A fault on the map never reaches a tool call or a model turn.
Developing
claude plugin test .
claude plugin validate .
Words live in hooks/text.ts; a new language is one more table there and one more value of language in .claude-plugin/plugin.json.
License
Frequently Asked Questions
What is lot-map?
lot-map is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by alexeyw. A live map beside the chat that shows what Claude Code is doing: tool calls, model steps, hooks, skills and subagents light up as they happen. Local only, in five languages. It has 118 GitHub stars.
Is lot-map safe to use?
lot-map's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
How do I install lot-map?
Clone the repository with "git clone https://github.com/alexeyw/lot-map" and add it to your Claude Code skills directory (see the Installation section above).
What programming language is lot-map written in?
lot-map is primarily written in TypeScript. It is open-source under alexeyw on GitHub, so you can review or fork the full source.
Are there alternatives to lot-map?
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh lot-map against similar tools.
Comments (0)
to leave a comment.
No comments yet. Be the first to share your thoughts!
Related Skills
Reverse engineer anything with agents, from app behavior down to native binaries.
448,394
110,517
TypeScript
AI Agentsagent-skillsai
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
300,442
44,354
JavaScript
AI Agentsai-agentsanthropic
Skills for Real Engineers. Straight from my .agents directory.
250,518
21,171
Shell
AI Agents
An agentic skills framework & software development methodology that works.
234,966
20,863
Shell
AI Agentsaibrainstorming