agentleFS
Sign inStart free
Seeed-ProjectsSeeed-Projects/Seeed-Jetson-DevelopTool/skills/codex/allxon-setup/AGENTS.md

Seeed-Jetson-DevelopTool / allxon-setup

AGENTS.md57 starsChanged 4 months agoMITView on GitHub

Install and configure Allxon DMS agent on NVIDIA Jetson devices for remote monitoring and management via the Allxon cloud portal. Supports JetPack 4.6+.

The file

We split this AGENTS.md into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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
  1. Distinctive:

    Run one phase at a time. After each phase:

    line 18
  2. Very specific:

    If output contains [STOP] → stop immediately, consult the failure decision tree

    line 19
  3. Very specific:

    If output ends with [OK] → tell the user "Phase N complete" and proceed

    line 20
  4. Distinctive:

    Ask the user: "Do you already have an Allxon DMS account?"

    line 42
  5. Distinctive:

    Verify account via activation email

    line 46
  6. Distinctive:

    Verify agent is running:

    line 62

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Allxon DMS Setup on Jetson

Allxon is an edge device management solution for remote monitoring and management of Jetson devices via a cloud portal. Installation is a single command.

Hardware: Any NVIDIA Jetson device, OOB Enabler (optional for out-of-band management) Software: JetPack 4.6+, internet connection

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

Confirm JetPack 4.6 or later. Check internet:

ping -c 2 get.allxon.net

[OK] when JetPack version confirmed and internet works. [STOP] if JetPack < 4.6 or no internet.

Phase 2 — create Allxon account (human action)

Ask the user: "Do you already have an Allxon DMS account?"

If no:

  1. Sign up at: https://dms.allxon.com/next/signup
  2. Verify account via activation email
  3. Create a password

[OK] when user confirms they have an account.

Phase 3 — install Allxon DMS agent (~2 min)

sudo wget -qO - "https://get.allxon.net/linux/standard" | sudo bash -s

During installation, it will ask whether to install Trend Micro IoT Security (3-month free trial). User can choose Y or N.

Verify agent is running:

systemctl status allxon-dms-agent

[OK] when agent is active/running.

Phase 4 — get pairing code (~30 s)

CLI method:

dms-get-pairing-code

Or GUI method: press Ctrl + Shift + B on the Jetson desktop to open the agent window, then click "Get device pairing code".

[OK] when pairing code is obtained.

Phase 5 — pair device with portal (~1 min)

  1. Login to https://dms.allxon.com/next/signin
  2. Click Devices → + Add Device
  3. Enter the pairing code from Phase 4
  4. Click Next to complete pairing

[OK] when device appears in the Allxon DMS Portal.

Failure decision tree

SymptomAction
wget install script failsCheck internet. Verify get.allxon.net is reachable. Try with sudo.
Agent not running after installRun sudo systemctl start allxon-dms-agent. Check logs with journalctl -u allxon-dms-agent.
GUI agent doesn't appearPress Ctrl + Shift + B to start it. Or use CLI dms-get-pairing-code.
Pairing code rejectedEnsure device has internet. Regenerate code and try again.
Device not showing in portalWait 1–2 minutes. Refresh the portal page. Check agent status.

Uninstall

sudo systemctl disable dms-install.service
sudo wget -qO - "https://get.allxon.net/linux/uninstall" | sudo bash -s

Reference files

  • references/source.body.md — Original Seeed wiki with screenshots and wiring diagrams

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free