nnInteractive
AGENTS.md522 starsChanged 4 months agoApache-2.0View on GitHub
Top-level docs include readme.md, SERVERCLIENT.md, and APICHANGES_v2.md. Documentation images live in imgs/. For supervoxel work, install both layers: cd nnInteractive/supervoxel/src/sam2 && pip install -e ., then cd ../.. && pip install -e .. Also run formatting, linting, and spelling checks for touched areas. Pull requests should state what changed, why it changed, exact validation commands, related issues or integrations, and any GPU, PyTorch, checkpoint, server/client, or API-compatibility assumptions. Do not commit local model checkpoints, API keys, or generated large outputs.
- Installs packages
We split this AGENTS.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
Use Python 3.10+ for the main package and Python 3.9+ in nnInteractive/supervoxel/.
≈ “Common” is an estimate: at least 1 in 5 of the 36,368 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Repository Guidelines
Project Structure & Module Organization
nnInteractive/ is the main Python package for promptable 3D medical-image segmentation.
nnInteractive/inference/: local sessions, remote client support, server code, and the CVPR 2025 baseline wrappernnInteractive/interaction/: interaction primitives such as point promptsnnInteractive/utils/: bbox, crop, morphology, checkpoint, OS, and inference helpersnnInteractive/trainer/: lightweight checkpoint reconstruction stubnnInteractive/supervoxel/: optional SAM/SAM2 supervoxel subproject with separate packaging and CLIs
Top-level docs include readme.md, SERVER_CLIENT.md, and API_CHANGES_v2.md. Documentation images live in imgs/.
Build, Test, and Development Commands
The repo builds two distributions sharing the nnInteractive namespace: nninteractive-client (torch-free remote client, source under client/) and nnInteractive (full stack, root; depends on the client). See "Two-distribution layout" in CLAUDE.md.
pip install -e ./client && pip install -e .: editable dev install (client first, then the full stack which depends on it).pip install -e ".[dev]": add Black, Ruff, and pre-commit tooling.pip install nninteractive-client: install only the lightweight torch-free remote client (no torch / nnU-Net).pip install nnInteractiveinstalls the full stack and pulls the client in automatically.nninteractive-server --model-dir /path/to/checkpoint --fold all --host 0.0.0.0 --port 1527 --device cuda:0: run the inference server.black nnInteractive/: format Python code; the pre-commit hook uses line length 120.ruff check nnInteractive/ --fix: lint and apply safe fixes.codespell --skip='.git,*.pdf,*.svg': check spelling in source and docs.pre-commit run --all-files: run configured hooks before submitting changes.
For supervoxel work, install both layers: cd nnInteractive/supervoxel/src/sam2 && pip install -e ., then cd ../.. && pip install -e ..
Coding Style & Naming Conventions
Use Python 3.10+ for the main package and Python 3.9+ in nnInteractive/supervoxel/. Follow Black formatting with 4-space indentation and 120-character lines. Prefer typed, explicit public inference/session APIs. Use snake_case for modules, functions, and variables; PascalCase for classes; and UPPER_SNAKE_CASE for constants.
Testing Guidelines
There is no dedicated automated test suite. Validate changes with the narrowest reproducible smoke path:
- local inference through
nnInteractiveInferenceSessionusing thereadme.mdflow - remote inference by starting
nninteractive-server, checking/healthz, and exercisingnnInteractiveRemoteInferenceSession - supervoxel CLI execution on a small sample volume when touching
nnInteractive/supervoxel/
Also run formatting, linting, and spelling checks for touched areas.
Commit & Pull Request Guidelines
Recent history uses short, imperative subjects such as disable compile on cpu, reduce threshold for blosc2, and bump version. Keep commits focused and include body context for behavior changes, compatibility breaks, or dependency assumptions.
Pull requests should state what changed, why it changed, exact validation commands, related issues or integrations, and any GPU, PyTorch, checkpoint, server/client, or API-compatibility assumptions. Do not commit local model checkpoints, API keys, or generated large outputs.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 28,693 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repositoryOne other file it gives its agents.
- CLAUDE.mdCLAUDE.md
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

