openilink-hub
开源微信 Bot 管理平台 + App 应用市场 | Self-hosted WeChat Bot Platform with App Marketplace | Lark · Slack · Discord · DingTalk · GitHub · Notion · 20+ Apps | AI Tools | 7 Language SDKs
Runssource: GitHubhomepageGoMITcommit 1df2ebebb69a
Go, MIT licensed. The project labels itself: ai chatbot, ai tools, app marketplace, bot management, chatbot, dingtalk, discord and golang.
openilink-hub runs. An Argusic agent installed it in 13 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
OpeniLink Hub builds and runs: go test passes 367 tests across 16 packages with 0 failures, server binary launches on port 9800, serves SPA frontend with HTTP 200, and SQLite-backed store, API, app dispatcher, bot manager, relay, sink, storage, auth, iLink provider, and builtin bridge all function correctly.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Go binary not found in container3 minutes
- Node.js 18 too old for vite-plus native binding (requires Node >=22.12)2 minutes
- vite-plus Linux x64 native binding optional dependency not installed by pnpm1 minute
- Install time
- 13 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- go test ./... -count=1 -timeout=300s: 16 packages, 367 passes, 0 failures; server binary at /tmp/oih started with SECRET=test-secret and answered HTTP 200 on GET http://localhost:9800/
- Model tokens used
- 70,642
- Exact commit tested
- 1df2ebebb69a
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
70,642 All systems verified. Here's the full report: **Errors encountered and fixed:** 1. **Go not installed** — Downloaded `go1.26.0.linux-amd64.tar.gz` and extracted to `~/go-install/`. 2. **Node.js 18 too old** — `vite-plus` requires `styleText` from `node:util` (Node 20.12+) and eng… 3. **vite-plus native binding missing** — `@voidzero-dev/[email protected]` wasn't ins… **Verification:** - `go test ./... -count=1 -timeout=300s` — all 16 packages with tests passed, 367 individual `--- P… - `/tmp/oih version` — printed `oih (OpeniLink Hub) dev (none, unknown)` - Server launched with `SECRET=test-secret /tmp/oih` — responded with HTTP 200 on `http://localhost… - Frontend SPA HTML served via embedded `internal/web/dist` assets **Test depth:** Tier 1 real (SQLite-backed tests exercise real store, API, app dispatcher, bot mana…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 13 minutes.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
ai-chatbotai-toolsapp-marketplacebot-managementchatbotdingtalkdiscordgolangilinklarknotionreactself-hostedslackwebhookwechatwechat-bot
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/openilink-hub)Questions
- Does openilink-hub run?
- Yes. openilink-hub runs. Argusic installed and launched it on a clean machine in 13 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test openilink-hub?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1df2ebebb69a. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test openilink-hub?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does openilink-hub take to install?
- 13 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does openilink-hub need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing openilink-hub?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for openilink-hub?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.