What it does
LAN-Orangutan is a self-hosted network discovery tool. Find every device on your LAN, label and group them, snapshot your network and compare it later, and get flagged when something unexpected shows up. Single binary, no setup, Tailscale built in. Built by 291 Group.
- Connects Instruction files the AI reads, with steps that call an outside service
- Account or key Some steps need a key for ORANGUTAN_TOKEN (per the README)
- Category Other
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/291-group-lan-orangutan)Similar Skills
Same kind of work, ordered like the Skills list
| This one LAN-Orangutan | llmfit | claude-video | VideoCaptioner | claude-cookbooks | |
|---|---|---|---|---|---|
| Maker | 291-Group | AlexsJones | bradautomates | WEIFENG2333 | anthropics |
| Skills | 1 | 1 | 1 | 1 | 4 |
| GitHub stars | 1,159 | 39,096 | 21,249 | 16,577 | 54,867 |
| Last code change | Nov 19, 2026 | Nov 18, 2026 | Sep 25, 2026 | Sep 12, 2026 | Nov 17, 2026 |
| License | MIT | MIT | MIT | GPL-3.0 | MIT |
1 skills (instruction sets) by 291-Group that an AI reads and follows · not an MCP server
How a Skill differs from MCP
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Works with
Not stated by the maker · SKILL.md skills work in apps that support Agent Skills, such as Claude Code, Codex and Cursor
Install
Is it safe?
- Who made it
GitHub account 291-Group (organization), 1 years old
- Use and upkeep
★ 1,159 stars · code last changed Nov 19, 2026
- Any scripts?
No, plain text files the AI reads and follows
- Uses the internet?
No scripts, so it does not go online by itself
- Changes machine-wide settings?
No hooks or writes to machine settings found
Checked automatically from the repo files at commit ee6952f (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
First: which AI do you use?
Pick your app and this page shows only how to install it there
Option 1Upload to claude.ai (web and app)
Uploading to claude.ai would fail: the description is over 200 characters (368). Use "Let the AI install it" instead
Option 1Let Claude Code install it
Copy this sentence and paste it into a Claude Code chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Restart Claude Code, then type /lan-orangutan or ask for a matching task and Claude picks it up
Checked against official docs Nov 12, 2026 · Source: code.claude.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.claude/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
Restart Claude Code, then type /lan-orangutan or ask for a matching task and Claude picks it up
ChatGPT desktop app
The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills
Option 1Let ChatGPT install it
Open Codex in the ChatGPT desktop app and paste this sentence into the chat
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Option 2Put the folder there yourself
Put the lan-orangutan folder at ~/.agents/skills/lan-orangutan
~ is your home folder ($HOME)
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
After installing
- ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
- To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
- Codex picks up newly installed skills by itself; if one does not show up, restart Codex
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
ChatGPT on the web and mobile
Skills you install yourself do not work here; only skills that come with a plugin from the directory
To use this skill with ChatGPT, use the ChatGPT desktop app as above
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Option 1Let Codex install it
Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
Restart Codex, then ask for a matching task; Codex lists the skill
Option 1Let Cursor install it
Copy this sentence and paste it into a Cursor chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
In Cursor’s Agent chat, type / and pick lan-orangutan
Checked against official docs Nov 12, 2026 · Source: cursor.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.cursor/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
In Cursor’s Agent chat, type / and pick lan-orangutan
Option 1Let the AI install it
For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.
Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026
View the original SKILL.md
The text below comes from the maker’s repo, not from PopNx MCP
Showing the first 8,000 characters · Open the full file on GitHub
---
name: lan-orangutan
description: Install, run and operate LAN Orangutan, a self-hosted network scanner that discovers and tracks the devices on a local network. Use when the user wants to find what is on their network, install or set up LAN Orangutan, scan, list, rename, label, group or locate devices, compare snapshots, set up change notifications (webhooks), or script against its CLI or REST API.
---
# LAN Orangutan
LAN Orangutan discovers the devices on a local network with nmap and the machine's own ARP and neighbour tables, and keeps an inventory of them: addresses, MAC, manufacturer, type, and whatever names, groups, locations and notes the user adds. It is one binary with a web dashboard (port 291 by default), a CLI that can do everything the dashboard can, and a REST API.
Project and full documentation: https://github.com/291-Group/LAN-Orangutan
## Ground rules
- Scanning a network is only appropriate on networks the user owns or administers. If it is unclear whose network it is, ask.
- Ask before anything that removes or replaces data: `device delete`, `groups delete`, `groups reset`, `locations delete`, `locations prune`, `snapshot delete`, `webhook delete`, `restore`, and `token create` (which replaces the existing token).
- Never put LAN Orangutan on a public interface or forward port 291 from the internet. Never suggest `allow_insecure` unless a reverse proxy or firewall in front of it already handles authentication.
- Treat the API token and webhook URLs as secrets. Do not echo them back into the conversation, write them into shared files, or put them in command history when an environment variable will do.
- The user sets the dashboard password themselves in the browser. Do not choose one for them unless they ask for an unattended install, and then use `ORANGUTAN_PASSWORD_FILE` rather than a plain variable.
## Installing
nmap is required on every platform except Docker, where it is bundled.
| Platform | Install |
|---|---|
| macOS | `brew install nmap` then `brew install 291-group/tap/lan-orangutan` |
| Windows | Install nmap from nmap.org, then `scoop bucket add 291group https://github.com/291-Group/scoop-bucket` and `scoop install lan-orangutan` |
| Debian, Ubuntu, Raspberry Pi OS | `sudo apt install nmap`, then the `.deb` for the architecture from the Releases page. Runs as a root service |
| Fedora, RHEL | `.rpm` from the Releases page |
| Alpine | `.apk` from the Releases page |
| Docker | Linux only, with host networking: `curl -O https://raw.githubusercontent.com/291-Group/LAN-Orangutan/main/docker-compose.yml` then `docker compose up -d` |
| Anything else | The binary for the platform from https://github.com/291-Group/LAN-Orangutan/releases |
Do not install the Docker image on Docker Desktop for macOS or Windows. The container runs inside a virtual machine there, so it cannot see the real network and a scan reports devices that do not exist. Use the native binary on those systems. On Linux, the container needs `network_mode: host` plus the `NET_RAW` and `NET_ADMIN` capabilities, which the compose file already sets; on bridge networking it finds nothing.
### Running it
```bash
sudo orangutan serve # Linux and macOS; Windows: run orangutan.exe serve as Administrator
```
Then open `http://localhost:291`, or `http://<that-machine>:291` from another computer. The first visit asks for a password, and nothing is reachable until one is set. That is the whole setup.
Root or Administrator is what lets nmap read MAC addresses and manufacturers. Without it, discovery still works but those two columns stay empty.
Useful variations:
- `orangutan serve --bind 127.0.0.1` keeps it to this machine, and then no password is needed.
- `orangutan serve --port 8080` uses another port.
- `ORANGUTAN_NETWORKS=192.168.10.0/24,10.0.5.0/24` adds networks reached through a router or VLAN, which are never detected on their own. Those results have no MAC or manufacturer, because ARP does not cross a router.
## Using the CLI
The CLI reads and writes the same data folder as the server. A running server sees device, group, location, snapshot and webhook changes straight away, and settings changes by its next scan. That only holds when both use the same folder, which means the same user and the same data directory:
- Run the CLI as the same user as the server. A server started with `sudo` or installed as a package service runs as root, so use `sudo orangutan ...` for the CLI too.
- In Docker, run the CLI inside the container: `docker exec lan-orangutan orangutan list`.
- `orangutan config` prints the `data_dir` in use. `ORANGUTAN_DATA_DIR` overrides it.
- `orangutan config` and `orangutan status` show the port and bind address from the config file. A server started with `--port` or `--bind` differs; `GET /api/status` reports what the running server actually uses.
- A "permission denied" on the device list means the data belongs to another user, usually root.
For anything a program will read, ask for JSON. Most commands take `--format json`, and `list` also takes `--format csv`.
### Seeing the network
```bash
sudo orangutan scan all # Scan every detected network
sudo orangutan scan 192.168.1.0/24 # Scan one network
orangutan list --format json # Every device
orangutan list --online # Only what is up now
orangutan list --type Printer # Also --group, --location, --offline
orangutan device show 192.168.1.20 # Everything stored for one device
orangutan networks # Networks that would be scanned
orangutan status --format json # Tools found, storage, networks, config
```
`scan` exits with 0 when every network was scanned, 1 when nothing could be scanned, and 2 when nmap failed everywhere but the ARP table still gave a partial list.
In the CLI's JSON, `hostname` is what to show: the user's own name when one is set (`custom_hostname`), otherwise the scanned one (`scanned_hostname`). The API differs, see below. `online` is a boolean; a device counts as offline after an hour unseen.
### Organising devices
```bash
orangutan device set 192.168.1.20 --hostname "Living Room TV" --group Family --location "Living Room"
orangutan device set 192.168.1.20 --hostname "" # Back to the scanned name
orangutan device set 192.168.1.30 --type Printer # Or --type auto to detect again
orangutan device set 192.168.1.30 --label NAS --notes "Rack, shelf 2" --expected
orangutan device expect-all # Mark everything present now as expected
orangutan groups add Office
orangutan groups rename Office Work
orangutan locations add Garage
orangutan locations rename "Living Room" Lounge
orangutan groups # List groups with device counts
orangutan locations # List locations with device counts
orangutan device set 192.168.1.20 --group "" --location "" --expected=false # Clear them
```
Only the flags passed are changed, and `""` clears a text field. Setting a location that does not exist yet adds it to the list, and it stays there after its last device leaves; `locations prune` removes empty ones (ask first). Types are Phone, Computer, Printer, TV, Media Player, Router, Server, IoT, Game Console, or auto. Labels are up to 64 characters and notes up to 1000. A custom hostname or type survives every later scan.
Marking devices as expected is what makes "unexpected device" and "missing device" notifications meaningful, so after a first scan on a quiet network, offer `device expect-all`.
### Tracking change
```bash
orangutan snapshot save "Before new router"
orangutan snapshot list # Newest is 1
orangutan snapshot compare 1 # Snapshot 1 against the network now
orangutan snapshot compare 2 1 # Between two snapshots
orangutan report # Self-contained HTML report of the whole network
orangutan backup Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
From GitHub
- GitHub stars
- 1,159
- Maker
- 291-Group
- License
- MIT
- Last code change
- Nov 19, 2026
- SKILL.md files in the repo (including translated copies and templates)
- 1
- Topics
- cli, device-discovery, golang, homelab, internet-of-things, lan, network-discovery, network-monitoring, network-monitoring-tool, network-scanner, networking, nmap