GrokexGrokex
BlogDocsChangelogDownloadSponsor12.8k

Integrations

Grokex Hub

An optional service that sits above your daemons and gives them extra capabilities.

Private beta. Self-hosted first.

Triggers, running on your machines

Mention the bot in GitHub, Slack, or Discord and an agent starts on your daemon.

GitHubIssues, PRs, and reviews.
SlackChannels and threads.
DiscordChannels and threads.
#engineering
M
moboudra09:41

@grokex-bot show me the latest P0 issues

grokex-botBot09:41

Three P0 issues are open:

  • #2811Terminal output drops under load
  • #2804Relay reconnect loop on Android after sleep
  • #2799Worktree cleanup leaves stale branches
M
moboudra09:43

@grokex-bot create a pull request for the first one

grokex-botBot09:48

Ran on macbook-pro. Opened grokex/grokex#1234 with a fix for the terminal writes.

3 files changedtests passed
The agent ran on your daemon, with your keys.

Runs the agents you already have

The Hub ships no agent of its own, so your team works with the providers, subscriptions, and skills already configured on your daemons.

Claude Code
Codex
OpenCode
Cursor
Pi
+34 more

Works with your existing infrastructure

The Hub connects to the daemons you already run, and your apps keep connecting to those same daemons.

Triggers and teammates

GitHub
Slack
Discord
Your team
Future integrations

webhooks and mentions

Hub

Self-hosted, one per team

the same RPCs the app and CLI use

Your daemons

MacBook Pro
Hetzner VM

direct connection or relay

Grokex apps

Desktop
Web
Mobile
CLI

Getting access

Join the Grokex Discord and DM me. I'm looking for design partners who are comfortable self-hosting.

Join the Discord

FAQ

+What is the Hub?
A separate service that sits above your Grokex daemons. You connect one or more daemons to it and it gives them GitHub, Slack, and Discord triggers, with collaboration features planned. Grokex works fully without it.
+Why is it a separate service instead of part of the daemon?

The daemon stays one lean executable on one machine. The Hub talks to daemons over the same RPCs the app and the CLI use, so anyone can build their own hub on top of Grokex.

It also has a different job. The Hub is meant to be exposed to the internet, shared with a team, and run multi-tenant. None of that belongs in a single machine daemon.

+Why self-hosted first?
The Hub can trigger executions on the daemons connected to it, so it has to be trusted. I am not comfortable having people connect their daemons to my infrastructure until the daemon has stronger authorization primitives and sandboxing. That work is on the roadmap, and it applies to every Grokex user.
+What do I need to run it?
A single Node.js application and a Postgres database. You also bring your own GitHub App, Slack app, and Discord bot credentials, which is the tedious part.
+Will there be a hosted version?
Planned, once the daemon has stronger authorization primitives and sandboxing. I already run a Hub for my own repos, and I can walk you through a trial on it if you want to skip the self-hosted setup. No SLA.
+What else is planned?

Not built yet, listed so you know where this is going.

  • Provisioning daemons for your team
  • Sharing settings and skills across a team
  • More integrations
+Do I have to move my team to a new tool?
No. The Hub works in the Slack or Discord your team already uses, and on the daemons you already run. When the work gets serious you switch to the Grokex app on those same daemons.
+Which agents does it run?
Whichever ones your daemons have configured, with your own subscriptions and skills. The Hub ships no agent of its own.
+Can the Hub run code on my machines?
Yes, on the daemons you connect to it and nowhere else. That is the whole point of triggers, and it's why access to the beta stays small and trusted.
+How do I get access?
Join the Grokex Discord and DM @moboudra for an invite to the private Hub channel.