Third-party adapters for OCTO — bridge AI agents, IM platforms, and external services into the OCTO workplace via Ope...
Copy the install, test the workflow, then decide if it earns a permanent slot.
Still active enough to matter. Good candidate for a fast stack test instead of a long evaluation loop.
Copy the install, test the workflow, then decide if it earns a permanent slot.
Reasonable to try, but it will take more than a quick skim to get real signal.
GitHub health 87/100. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
OpenClaw
Model
Multiple
Fastest way to find out if octo-adapters belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
git clone https://github.com/Mininglamp-OSS/octo-adapters ~/.claude/agents/octo-adaptersRun this first. You will know quickly if the workflow earns a permanent slot.
rm -rf ~/.claude/agents/octo-adaptersNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ ├─ agents/ │ └─ octo-adapters/ ← installs here └─ settings.json
Third-party adapters for OCTO — bridge AI agents, IM platforms, and external services into the OCTO workplace via OpenClaw channels and WebSocket.
Source: GitHub repository
Source check: July 18, 2026
Upstream commit: July 13, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.