autoresearch vs io.github.James-Chahwan/repo-graph
autoresearch is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑27.
autoresearch is a plugin bundle for AI coding tools published by James S Tayler. No marketplace we read lists it any more. io.github.James-Chahwan/repo-graph is an MCP server published by James-Chahwan. Marketplaces we read that list it: 3 (Official MCP Registry, PyPI (MCP servers), Community GitHub marketplaces). As of our marketplace pass on 2026-10-27. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.James-Chahwan/repo-graph | |
|---|---|---|
| Community marketplace james-s-tayler/lazy-developer | Removed on 2026-10-27 Version: 1.1.0 Forks (GitHub): 0 Stars (GitHub): 12 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.5.2 Downloads/month (PyPI): 1 097 Downloads/week (PyPI): 234 Forks (GitHub): 1 Stars (GitHub): 87 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 0.5.2 Downloads/month (PyPI): 1 097 Downloads/week (PyPI): 234 Forks (GitHub): 1 Stars (GitHub): 87 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | autoresearchno longer listed · | io.github.James-Chahwan/repo-graph |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 3 |
| Stars (GitHub) (differs) | 12 | 87 |
| Forks (GitHub) (differs) | 0 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (mcp-repo-graph) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Parts of the bundle (differs) | 3 | 1 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/james-s-tayler/lazy-developer | github.com/james-chahwan/repo-graph |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-22 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of autoresearch
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Autonomous experiment loops on any codebase — one file, one metric, one loop. An agent edits a constrained file, runs an eval, keeps improvements, reverts failures, and repeats…
-
Autonomous experiment loop for Claude Code. Run an endless optimize-measure-keep/discard cycle on any optimization target: LLM training loss, test speed, bundle size, build time…
-
Self-correcting loop engineering and automated codebase research.
-
Drop-in agentic loop skills (autoresearch, literature & writing, data, optimization, red-team, power analysis). Skills install namespaced as agent-loops:<name>.
-
Autonomous experiment loop — optimize any file by a measurable metric. 5 slash commands (/ar:setup, /ar:ar-run, /ar:loop, /ar:ar-status, /ar:ar-resume), 8 built-in evaluators…
-
Structured experiment-driven code optimization using tree search and parallel subagents
What each says it does
autoresearch
Set up autonomous goal-driven optimization — creates a GOAL.md fitness function and runs an improvement loop
io.github.James-Chahwan/repo-graph
Structural graph map of any codebase so LLMs navigate by structure, not guesswork.
How to run each
autoresearch
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.James-Chahwan/repo-graph As a local MCP server: PyPI package
claude mcp add --transport stdio repo-graph -- uvx mcp-repo-graphCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of autoresearch publish no settings it asks for, so we do not compare settings.
What it can do: autoresearch · What it can do: io.github.James-Chahwan/repo-graph · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.