nexu: a desktop bridge that puts an OpenClaw agent inside WeChat, Feishu, Slack, and Discord
The simplest desktop client for OpenClaw 🦞 — bridge your Agent to WeChat, Feishu, Slack & Discord in one click. Works with Claude Code, Codex & any LLM. BYOK, Oauth, local-first, chat from your phone 24/7.
At a glance
- What is it?
- nexu is an MIT-licensed desktop client that connects an OpenClaw agent to mainstream IM channels with a GUI and no CLI. It targets solo operators and small teams, but its platform support and security model deserve scrutiny before adoption.
- Who is it for?
- Adopt nexu if you are a solo operator or small team already using OpenClaw and want a graphical, local-first bridge to WeChat, Feishu, Slack, or Discord without writing integration code. Do not adopt it if you need a headless server deployment, if your team requires formal security audits beyond the MIT source, or if you rely on model providers not listed in the README.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 142 days ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 15, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
What nexu actually solves
OpenClaw, the agent framework, normally runs in a CLI and requires manual configuration to reach external models and chat platforms. nexu is a desktop application that wraps OpenClaw and provides a graphical way to connect that agent to WeChat, Feishu, Slack, and Discord. The README frames it as 'the smoothest way to connect OpenClaw to WeChat: Scan, connect, and go.' The intended user is the one-person company or small team. The use cases all describe a single operator delegating tasks to an agent through a familiar chat interface: writing product listings in Feishu, drafting social posts from Slack, debugging code in Discord, or reviewing contracts forwarded on Feishu. If you already live in a team chat and want your agent there without building a custom integration, nexu is aimed directly at you. It does not try to be a general agent framework; it is a transport layer between OpenClaw and messaging apps.
How the connection works
The README does not expose an architecture diagram or a detailed data flow, but the visible mechanism is straightforward. The desktop client runs locally and hosts the OpenClaw agent. You connect an IM channel by scanning a QR code, which is the WeChat path described as 'click connect, scan with WeChat, and start chatting.' For Feishu, Slack, and Discord, the implication is that the client handles the channel registration and session management on your behalf. The agent then becomes reachable through that chat interface, and because the client stays running on your desktop, the agent is available 24/7. The data path is local: the README claims 'all data stays on your machine' and contrasts nexu with hosted stacks that route data through vendor servers. That means your conversations, prompts, and agent state are processed on your desktop, not on nexu's infrastructure. The one exception is when you use a model provider; those API calls go to the provider you choose, under your own key or OAuth token.
Getting it running: GUI, not CLI
The installation story is deliberately light on commands. The README says 'download, double-click, and start using,' with no environment variables or dependency setup. Supported platforms are macOS on Apple Silicon, macOS on Intel, and Windows. Downloads are pointed to at nexu.io. The first-run experience is described as 'as capable as it gets, ready out of the box.' For model access, you have two paths. You can bring your own API key and use the client without logging in, which the README labels 'BYOK.' Or you can use OAuth for MiniMax, OpenAI Codex, and GLM (Z.AI Coding Plan), authorizing with one click and skipping key management. The README also mentions that you can 'use Gemini and more directly via your nexu account,' which suggests there is an optional nexu account for default model access, but it does not explain what that account stores or whether it changes the local-first claim. That ambiguity is worth checking before you rely on the account path.
Built-in skills and the WeChat caveat
nexu ships with native OpenClaw Skills and full Feishu Skills, according to the README. That means the agent can act on Feishu-specific workflows like document handling or approval actions without extra integration. The phrase 'full Feishu Skills' is a strong claim; the README gives no list of which skills are included or how they map to Feishu's API permissions. On WeChat, the README is more specific: it says 'works with WeChat 8.0.7 OpenClaw plugin.' That is a narrow compatibility statement. WeChat versions change frequently, and the plugin dependency means your WeChat client must match that version and have the plugin installed. If you are on a newer WeChat build or a restricted corporate version, the scan-and-connect flow may fail. This is a real limitation that the marketing tone does not address. The client is also a desktop app, so the '24/7' availability depends on your machine staying on and connected. A laptop that sleeps at night or a corporate VPN that drops will take your agent offline.
Local-first privacy versus hosted convenience
The core privacy argument is that nexu does not host your business data. That is a meaningful difference from hosted Feishu-plus-agent stacks, which route conversations through vendor servers. With nexu, your chat messages and agent context stay on your desktop. However, local-first is not the same as private-by-default. Any model provider you call receives the prompts you send. If you use the built-in 'nexu account' for Gemini access, the README does not clarify what nexu itself sees. The BYOK path avoids a nexu account entirely, which is the strongest privacy posture. The OAuth options for MiniMax, Codex, and GLM also avoid storing a raw API key, but OAuth tokens still grant access to your provider account. For a solo operator handling customer messages, local-first means you control the logs, but you still need to trust the model provider's data handling. The MIT license lets you audit the client code, which is more than closed-source alternatives offer, but an audit is only meaningful if you actually read the source or have someone do it for you.
Alternatives: OpenClaw CLI and hosted stacks
The README itself compares nexu to two alternatives. The official OpenClaw client is open source and free, but it is CLI-based and requires manual model configuration and DIY channel integration. If you are comfortable in a terminal and only need one channel, the official client avoids installing a third-party desktop wrapper. The other alternative is a typical hosted Feishu-plus-agent stack, which the README criticizes for platform lock-in and vendor data routing. Those hosted services often provide a web dashboard, team management, and uptime guarantees that nexu cannot match because it depends on your desktop. The real difference is where the agent runs and who controls the connection. nexu keeps the agent on your machine and gives you a GUI; hosted stacks run the agent remotely and handle scaling and reliability for you. If you need multiple team members to access the same agent without each running a desktop client, a hosted stack is more practical. If you want full control over data and are willing to manage your own uptime, nexu's local-first model is the closer fit.
Licence, maturity, and maintenance cost
nexu is MIT licensed, which means you can fork, modify, and redistribute it without paying royalties. That is permissive and aligns with the audit-friendly claim. The repository shows recent releases at v0.1.12, v0.1.11, and v0.1.10, all from April 2026. The version numbers are below 1.0, which signals that the API and feature set can change without notice. The last push was in late April 2026, so the project is actively maintained at the time of writing. Maintenance cost for you as an adopter is low if you use the prebuilt binaries: you download updates when they are released. If you fork the code, you take on the cost of tracking upstream changes and rebuilding for your platform. The README does not document an upgrade path or a changelog, so you cannot easily predict what a new version will break. For a desktop tool that connects to live chat platforms, a breaking change in a channel adapter could take your agent offline until you update. Plan to check the releases page before each upgrade and test your primary channel after.
Editorial conclusion
Adopt nexu if you are a solo operator or small team already using OpenClaw and want a graphical, local-first bridge to WeChat, Feishu, Slack, or Discord without writing integration code. Do not adopt it if you need a headless server deployment, if your team requires formal security audits beyond the MIT source, or if you rely on model providers not listed in the README. Before committing, verify that your exact WeChat version (the README mentions 8.0.7 plugin support) and your chosen IM channel work on your OS, and confirm that the OAuth flows for MiniMax, Codex, or GLM cover the models you need. The project is young, with releases at v0.1.12, so test the desktop client against your real chat workloads before trusting it with customer conversations.
Community notes