The Spider ecosystem is a based around the Spiderweb agent 'hosted' OS,
- Spiderweb - A agent first distributed OS that any agent can use with just basic filesystem tools
- SpiderApp - front end gui, to interact and observe the Spiderweb
- SpiderNode - small nodes that provide new filesystems and venoms to the Spiderweb
- SpiderVenoms - first-party capability venoms and managed local bundle releases
- SpiderVenomRegistry - signed static registry metadata for published venom bundles
- SpiderMonkey - custom research AI agent that is designed specifically for Spiderweb
git clone --recurse-submodules <this-repo-url>If you already cloned the repo without submodules:
git submodule update --init --recursivegit submodule update --remote --mergeProduct-local packaging stays inside each product repo:
Spiderweb/platform/macos/scripts/package-spiderweb-macos-release.shSpiderApp/scripts/package-macos-app.sh
The parent repo now owns suite-level macOS packaging:
./scripts/package-spider-suite-macos.shThat script orchestrates the existing Spiderweb and SpiderApp packagers, re-signs the staged SpiderApp bundle for distribution, builds a top-level SpiderSuite-...pkg, stages everything together under dist/, writes a suite manifest, renders RELEASE_NOTES.md, and zips the combined bundle.
The parent repo now also owns the canonical Linux suite archive:
./scripts/package-spider-suite-linux.shThat Linux archive bundles:
spideras the operator CLI/TUIspiderwebandspiderweb-configspiderweb-fs-node- shared runtime assets under
share/
The supported Linux path is Ubuntu/Debian with systemd, using spider as the primary operator surface.
Install from a published archive with:
sudo ./install-linux.shThen run:
spiderThe guided Linux home offers exactly three jobs:
Host Spiderweb HereConnect This Linux MachineStatus / Repair
Further docs:
For Linux node pairing on a macOS-hosted Spiderweb, use the same spider CLI on the Mac host for:
spider node invite-createspider node pendingspider node approve <request-id>spider node deny <request-id>
