Interactive visualization and search for 3,073 execution-grounded auto-research records.
SeevoMap is the frontend for BotResearchNet — a community knowledge graph where every node is a real experiment: idea → code → execution → result.
Live: https://huggingface.co/spaces/akiwatanabe/seevomap
The app prefers a bundled public/map.json fallback and can also fetch the
latest graph from HuggingFace at runtime:
- Graph data:
akiwatanabe/seevomap-graph(map.json, currently 3,073 nodes) - Search API:
akiwatanabe/seevomap(Gradio Space)
Bundling public/map.json keeps the graph usable even when HF fetches fail
because of proxies, CORS, or offline development.
npm install
npm run dev:local
npm run buildLocal preview convention:
- Use
npm run dev:localfor frontend work. - The dev server is expected to run on port
3456so changes can be checked immediately before any GitHub push. - For a production-like local check, run
npm run buildfirst and then serve the built site locally withnpm run preview -- --host 0.0.0.0 --port 3456. - The local site can point at a different backend by setting
VITE_SEEVOMAP_SPACE_URLbefore starting the dev server or preview server. - Website sign-in now defaults to the public SeevoMap CIMD client id at
https://internscience.github.io/SeevoMap-Home/.well-known/oauth-cimd. VITE_SEEVOMAP_HF_CLIENT_IDis now only an optional override if you want to point this deployment at a different Hugging Face OAuth app.
Local sign-in setup:
cp .env.local.example .env.local- Local dev can reuse the default SeevoMap public client id.
- If you keep the default, use one of the already-registered callbacks:
http://127.0.0.1:3456/oauth/callback/huggingface/http://localhost:3456/oauth/callback/huggingface/http://127.0.0.1:3457/oauth/callback/huggingface/http://localhost:3457/oauth/callback/huggingface/http://127.0.0.1:3458/oauth/callback/huggingface/http://localhost:3458/oauth/callback/huggingface/http://127.0.0.1:3459/oauth/callback/huggingface/http://localhost:3459/oauth/callback/huggingface/
- If you want to point the site at a different OAuth app, set
VITE_SEEVOMAP_HF_CLIENT_IDin.env.local.
# Docker
docker build -t seevomap .
docker run -p 3000:80 seevomap
# Or static: npm run build → serve dist/This repo is configured for GitHub Pages deployment:
- Make and test changes locally first
- Run
npm run buildbefore claiming the site is ready - Push
docs-autoresearch-previewif you want a preview deployment - Push or merge to
mainwhen you want the production site updated - In GitHub repo settings, set
Pagessource toGitHub Actions
Notes:
- Routing uses
HashRouter, so deep links work on static GitHub hosting. - The bundled
public/map.jsonfallback is loaded via a relative path, so it still works when the site is served fromhttps://<user>.github.io/<repo>/. - During frontend work, rerun the local preview first and check port
3456before treating the change as ready. - Production deploys are triggered by
.github/workflows/deploy-pages.ymlon pushes tomain. - Preview deploys are triggered by
.github/workflows/preview-pages.ymlon pushes todocs-autoresearch-preview. - The intended workflow is local preview first, GitHub preview second, production deploy last.
pip install seevomap
seevomap search "optimize transformer pretraining" --top-k 10
seevomap leaderboard --limit 10from seevomap import SeevoMap
svm = SeevoMap()
results = svm.search("my task", top_k=5)The static website now includes a public /leaderboard route backed by the
Space API, plus a Search-page flow that creates inject sessions and allows
optional session-bound helpful / not helpful feedback.
React 19 + TypeScript + Vite + Tailwind CSS v4 + Plotly.js
- PyPI · HF Space · HF Dataset