Seeed-Jetson-DevelopTool / cvedia-setup
AGENTS.md57 starsChanged 4 months agoMITView on GitHub
Install and run CVEDIA-RT AI inference engine on NVIDIA Jetson for pre-built computer vision applications (crowd estimation, drone detection, vehicle counting, etc.). Requires JetPack 5.1 and a CVEDIA account.
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 31,843 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 repository297 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ai-nvrAGENTS.md
- allxon-ota-updateAGENTS.md
- allxon-setupAGENTS.md
- alwaysai-setupAGENTS.md
- backup-restoreAGENTS.md
- bsp-source-buildAGENTS.md
- clawdbot-developmentAGENTS.md
- cochl-sense-setupAGENTS.md
- dashcamnet-xavier-nx-multicameraAGENTS.md
- deciai-setupAGENTS.md
- deepseek-quick-deployAGENTS.md
- deploy-deepseek-mlcAGENTS.md
- deploy-depth-anything-v3AGENTS.md
- deploy-diaAGENTS.md
- deploy-efficient-vision-engineAGENTS.md
- deploy-frigateAGENTS.md
- deploy-live-vlm-webuiAGENTS.md
- deploy-nvbloxAGENTS.md
- deploy-ollama-anythingllmAGENTS.md
- deploy-riva-llama2AGENTS.md
- developtool-deviceAGENTS.md
- disk-encryptionAGENTS.md
- diy-bsp-buildAGENTS.md
- ethercat-communicationAGENTS.md
- ethercat-setupAGENTS.md
- finetune-llm-llama-factoryAGENTS.md
- fix-browser-snap-jetsonAGENTS.md
- gapi-setupAGENTS.md
- generative-ai-introAGENTS.md
- gpt-oss-liveAGENTS.md
- gr00t-n1-5-deploy-thorAGENTS.md
- gr00t-n1-6-deploy-agxAGENTS.md
- hardhat-setupAGENTS.md
- hybrid-bsp-dk-to-recomputerAGENTS.md
- imx477-a603-setupAGENTS.md
- j501-viola-fruit-sortingAGENTS.md
- jetpack5-ssd-boot-fixAGENTS.md
- jetpack-flash-wsl2AGENTS.md
- jetpack-jetson-overviewAGENTS.md
- jetpack-ota-updateAGENTS.md
- jetson-ai-toolsAGENTS.md
- jetson-docker-setupAGENTS.md
- jetson-faqAGENTS.md
- jetson-pc-wired-shareAGENTS.md
- jetson-project-galleryAGENTS.md
- jetson-resource-indexAGENTS.md
- jetson-tutorial-exercisesAGENTS.md
- ko-module-buildAGENTS.md
- l4t-differencesAGENTS.md
- langchain-output-formattingAGENTS.md
- lerobot-env-setupAGENTS.md
- llama-cpp-rpc-distributedAGENTS.md
- llm-interface-controlAGENTS.md
- local-chatbot-multimodalAGENTS.md
- local-chatbot-physicalAGENTS.md
- local-llm-text-to-imageAGENTS.md
- local-rag-llamaindexAGENTS.md
- lumeo-setupAGENTS.md
- maskcam-nanoAGENTS.md
- The first 60 shown.
The file
We split this AGENTS.md into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Run one phase at a time. After each phase:
- Very specific: line 21
If output contains [STOP] → stop immediately, consult the failure decision tree
- Very specific: line 22
If output ends with [OK] → tell the user "Phase N complete" and proceed
- Distinctive: line 90
Wait for model and video files to download
- Distinctive: line 92
Stop and restart the application for changes to take effect
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 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
CVEDIA-RT on NVIDIA Jetson
CVEDIA-RT is a modular, cross-platform AI inference engine with pre-loaded applications: crowd estimation, drone detection, fall detection, lane occupancy, vehicle type counter, package detection, and more.
Hardware: NVIDIA Jetson device (tested with reComputer J4012) Software: JetPack 5.1 with all SDK components, internet connection Account: CVEDIA (free sign-up at rt.cvedia.com)
Execution model
Run one phase at a time. After each phase:
- If output contains
[STOP]→ stop immediately, consult the failure decision tree - If output ends with
[OK]→ tell the user "Phase N complete" and proceed
Phase 1 — prerequisites check (~30 s)
cat /etc/nv_tegra_release
# Expected: R35 (release) for JetPack 5.xdpkg -l | grep nvidia-jetpack[OK] when JetPack 5.1+ with SDK components confirmed.
[STOP] if JetPack version is incompatible.
Phase 2 — download CVEDIA-RT (human action + ~5 min)
- Visit https://rt.cvedia.com/ and sign in (or create account)
- Click Download under "NVIDIA Jetson"
- Select "Docker (Recommended)" to download the tar.gz installer
Transfer the file to the Jetson device.
[OK] when tar.gz file is on the Jetson.
Phase 3 — install CVEDIA-RT (~3 min)
mkdir -p ~/cvedia && cd ~/cvedia
tar -xzvf <filename.tar.gz>
sudo ./install.shRespond to installer prompts as needed.
[OK] when installation completes without errors.
Phase 4 — run CVEDIA-RT (~1 min)
With internet (first run, downloads models):
./run.shWithout internet (after first online run):
./run.sh -UExpected: CVEDIA-RT application opens with pre-loaded solutions.
[OK] when the application UI is visible.
Phase 5 — explore applications (~5 min)
- Click on a solution category (e.g. intelligent-transportation-systems)
- Click the run button next to a solution (e.g. lane-occupancy)
- Wait for model and video files to download
- Configure video source: gear icon → Edit Source → select camera/file → Save Instance
- Stop and restart the application for changes to take effect
[OK] when inference results are visible on the video feed.
Failure decision tree
| Symptom | Action |
install.sh fails | Verify Docker is installed with nvidia runtime. Check JetPack version. |
run.sh hangs or crashes | Check Docker logs. Ensure sufficient disk space and memory. |
| Application won't start offline | Must run each solution at least once with internet first. |
| Video source not working | Stop application, reconfigure source, restart. Check camera connectivity. |
| Low FPS / poor performance | Ensure JetPack SDK components are installed. Check GPU utilization with tegrastats. |
Reference files
references/source.body.md— Original Seeed wiki with screenshots and application examples
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.

