F
fangchenghao/latex-look
One tool that lets an AI agent see a LaTeX document: compile, render the page, locate the source line, and…
no SECURITY.md
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Client config (built from the install command this repo gives)
{
"mcpServers": {
"fangchenghao-latex-look": {
"command": "npx",
"args": ["latex-look"]
}
}
}Parsed from the README we fetched on 2026-10-26; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"fangchenghao-latex-look": {
"command": "npx",
"args": ["latex-look"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio fangchenghao-latex-look -- npx latex-look
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 0 ★ · fangchenghao/latex-look · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-10-23 · last seen 2026-11-14 · seen 26× · listed by 1 sources
- Score
- score 103 · 1 sources · repo
- Install
npx latex-look
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx latex-look. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
fangchenghao/latex-look；first catalogued 2026-10-23；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# latex-look — teach an agent to see your LaTeX
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
English · 简体中文
Left: compiles with zero errors. Right: after five sentences a reader could say out
loud — "remove the rules around the title", "this table is a grid, make it a
booktabs table", "that link runs off the page", "the figure is too wide". Try it
yourself in examples/broken-layout.
A DeepSeek Harness plugin that adds exactly one tool: latexlook.
An agent that only reads .tex source is blind: a document can compile with zero errors and still look wrong. latexlook compiles the document, renders the page as an image, maps any spot on that page back to the exact source line, and diffs what your last edit changed — in a single call.
┌─────────────┐ latexlook ┌──────────────┐
│ agent │ ─────────────► │ pdf → png │
│ (edits .tex)│ │ synctex │
└─────────────┘ ◄───────────── │ pixel diff │
▲ image + line └──────────────┘
└─────────────── verification ───────────┘
Read the case study: a 215-page LaTeX book, read the way a reader reads it — 163 figures, 129 equations, six classes of defect that compile cleanly.
## Why one tool, not three
Rendering, locating, and diffing are the implementation. The agent needs one coherent verb — "look at this page" — the same way a person does. latexlook compiles, renders, resolves, and diffs in a single call, so the loop is:
look → diagnose → edit .tex → look again → confirm the change → report
## Install
Requires Node ≥ 18, a TeX engine (xelatex/lualatex/pdflatex/latexmk or tectonic), synctex, and ghostscript.
This repository is the bundle: package.json declares dsh.bundle.patch, and cordis.patch.yml inserts one row.
bash
git clone https://github.com/fangchenghao/latex-look
Then install it into the current profile (in the Harness, via the plugin manager):
pluginmanager action: installbundle target: /absolute/path/to/latex-look
That adds the row latex-look and registers the latexlook tool. Replacing the sources of an already-installed package needs a Harness restart to load a fresh module generation.
Published on npm as @fffangchenghao/dsh-latex-look, so the same row also installs straight from the registry:
pluginmanager action: installbundle target: @fffangchenghao/dsh-latex-look
### Updating
The plugin checks the registry once a day, in the background, and appends a single line to a tool reply when a newer release exists — no repeated nagging, and an offline machine sees nothing at all. To upgrade, install the same bundle again:
pluginmanager action: installbundle target: @fffangchenghao/dsh-latex-look
On a live profile the upgrade applies immediately; the harness reloads the module generation on the next start, because core.mjs (unlike index.js) is not hot-reloaded.
From a checkout, the check is available directly:
bash
npx latex-look --version
npx latex-look --check-update
### Releasing
Tagging v runs the test suite on Ubuntu with TeX and Ghostscript installed, verifies the tag matches package.json, and publishes to npm. The token comes from the NPMTOKEN repository secret.
### Optional: the knowledge skill
The tool gives the agent eyes. SKILL.md gives it the LaTeX knowledge to act on what it sees — a symptom → cause → fix playbook (a rule you want gone is usually \pagestyle/fancyhdr, not a stray \hline). Copy or symlink it into the skills root:
Left: compiles with zero errors. Right: after five sentences a reader could say out
loud — "remove the rules around the title", "this table is a grid, make it a
booktabs table", "that link runs off the page", "the figure is too wide". Try it
yourself in examples/broken-layout.
A DeepSeek Harness plugin that adds exactly one tool: latexlook.
An agent that only reads .tex source is blind: a document can compile with zero errors and still look wrong. latexlook compiles the document, renders the page as an image, maps any spot on that page back to the exact source line, and diffs what your last edit changed — in a single call.
┌─────────────┐ latexlook ┌──────────────┐
│ agent │ ─────────────► │ pdf → png │
│ (edits .tex)│ │ synctex │
└─────────────┘ ◄───────────── │ pixel diff │
▲ image + line └──────────────┘
└─────────────── verification ───────────┘
Read the case study: a 215-page LaTeX book, read the way a reader reads it — 163 figures, 129 equations, six classes of defect that compile cleanly.
## Why one tool, not three
Rendering, locating, and diffing are the implementation. The agent needs one coherent verb — "look at this page" — the same way a person does. latexlook compiles, renders, resolves, and diffs in a single call, so the loop is:
look → diagnose → edit .tex → look again → confirm the change → report
## Install
Requires Node ≥ 18, a TeX engine (xelatex/lualatex/pdflatex/latexmk or tectonic), synctex, and ghostscript.
This repository is the bundle: package.json declares dsh.bundle.patch, and cordis.patch.yml inserts one row.
bash
git clone https://github.com/fangchenghao/latex-look
Then install it into the current profile (in the Harness, via the plugin manager):
pluginmanager action: installbundle target: /absolute/path/to/latex-look
That adds the row latex-look and registers the latexlook tool. Replacing the sources of an already-installed package needs a Harness restart to load a fresh module generation.
Published on npm as @fffangchenghao/dsh-latex-look, so the same row also installs straight from the registry:
pluginmanager action: installbundle target: @fffangchenghao/dsh-latex-look
### Updating
The plugin checks the registry once a day, in the background, and appends a single line to a tool reply when a newer release exists — no repeated nagging, and an offline machine sees nothing at all. To upgrade, install the same bundle again:
pluginmanager action: installbundle target: @fffangchenghao/dsh-latex-look
On a live profile the upgrade applies immediately; the harness reloads the module generation on the next start, because core.mjs (unlike index.js) is not hot-reloaded.
From a checkout, the check is available directly:
bash
npx latex-look --version
npx latex-look --check-update
### Releasing
Tagging v runs the test suite on Ubuntu with TeX and Ghostscript installed, verifies the tag matches package.json, and publishes to npm. The token comes from the NPMTOKEN repository secret.
### Optional: the knowledge skill
The tool gives the agent eyes. SKILL.md gives it the LaTeX knowledge to act on what it sees — a symptom → cause → fix playbook (a rule you want gone is usually \pagestyle/fancyhdr, not a stray \hline). Copy or symlink it into the skills root:
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/fangchenghao-latex-look/)
- Source
- github · https://github.com/fangchenghao/latex-look
- Browse by field
- Open source
- added
- today
- Security policy
- no
SECURITY.mdat the repository root (which does not mean it is unsafe)
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.