The Hub gathers the parts of your day that live in a dozen tabs: every calendar, every conversation waiting on a reply, and every task you own across your workspaces. Sign in to the apps in a LumaBrowser tab and the Hub reads them from there. No API keys to create, and everything stays on your machine.
The Hub adds three widgets to the Dashboard, LumaBrowser's drag-and-drop grid. Put them next to your own live widgets from chat, resize them, or leave one out.
One board for tasks from every ClickUp workspace you use, plus local tasks of your own. Drag a card between lanes and the status follows it back to ClickUp. Quick-add a task in any lane, filter by source, and hide what you are not working on. A sync that failed is marked on the card instead of disappearing.
Today or the whole week, across every calendar you picked, with a color per calendar, all-day events first, and a line for now. Past events dim so the next thing stands out.
Open threads from Slack, Teams, Gmail, Outlook, Messages, ClickUp, Proton and Discord, built from the notifications those tabs already send. Each shows a priority, a count and a summary. Review it, snooze it, mark it done, jump to the app, or turn it into a task.
Most dashboards ask you to create developer credentials for every service. The Hub uses the sessions you already have: keep Google Calendar, Teams, Outlook or Gmail signed in as a persistent tab and the Hub reads through it.
Sign in to Google Calendar, Teams, Outlook, Slack, Gmail or ClickUp in LumaBrowser tabs, as you would in any browser.
The Connections list shows each signed-in app and account. Tick the calendars you want on the Agenda.
Paste a ClickUp API token, load your lists, and choose a scope for each one. Map ClickUp statuses to board columns.
Open the Dashboard, switch to Edit, and drag the Task board, Agenda and Conversation queue where you want them.
The Hub keeps watching those tabs. If one gets signed out (Gmail, Google Calendar, Messages, Slack, Teams, Outlook, ClickUp, Proton, Discord, WhatsApp or Telegram), you get a desktop notification instead of a silently empty widget. One click opens the tab to sign back in.
| Area | Sources |
|---|---|
| Calendars | Google Calendar and Microsoft 365 through a signed-in tab, several accounts each. Your own OAuth app for either, if you prefer. Any ICS feed, including a Proton Calendar share link, a published Outlook calendar, or a Google secret iCal address. |
| Tasks | ClickUp through an API token, across several workspaces. Per list: assigned to me, mine plus unassigned, or all tasks. Local tasks need no tracker at all. |
| Conversations | Notifications caught from any tab (Slack, Teams, Gmail, Outlook, Messages, ClickUp, Proton, Discord and others) are grouped into threads. |
| Automation | n8n or any other tool can push items into the queue and enrich threads with summaries and priorities through the /api/hub endpoints, guarded by a token you copy or rotate in Settings. Example payloads are in the same panel. |
The Hub is data your AI can use, not just a screen to look at.
Type @dashboard (or /dashboard) and every widget on your Dashboard, Hub included, comes into the conversation as text. Ask "what needs a reply before my 2 o'clock?" or "which of my tasks are overdue?" and the model answers from your real calendar, queue and board. More on slash commands and @ mentions.
The chat, sub-agents, scheduled runs and outside agents over MCP get a set of hub tools. Reading is free; anything that changes a task or thread asks for your approval first.
hub_overview · hub_list_events · hub_list_threads · hub_list_tasks · hub_create_task · hub_move_task · hub_set_thread_state · hub_link_thread_task · hub_sync_now
Events, threads and tasks live in LumaBrowser's own database on your disk. There is no Hub account and no LumaByte server in the middle.
Reads and writes go straight from your computer to Google, Microsoft and ClickUp, using your own sessions and tokens.
The Hub ships in the same AGPL-licensed code as the rest of the app. You can read exactly what it does on GitHub.
No. Sign in to Google Calendar, Teams or Outlook in a LumaBrowser tab and the Hub reads through that tab. Power users can register their own OAuth app instead, and any calendar with an ICS link can be added by hand.
No. The Hub talks to the services directly from your machine and stores what it reads locally. Nothing passes through lumabyte.com.
Yes. Local tasks work on their own, and threads in the queue can become tasks. ClickUp is the tracker the Hub syncs with today.
Proton Calendar is end-to-end encrypted, so the only way in is its share link. In Proton, choose Share, then link, and paste the ICS address into the Hub.
No. It is built into LumaBrowser 2.0. Open Settings and choose the Hub tab to set it up.
Download LumaBrowser, sign in to the apps you already use, and put the Hub on your Dashboard. Free, open source, and on your own machine.