Gurusup Brain · Developers

Changelog

What we've shipped in Gurusup Brain, newest first.

  1. Sources

    Linear, Holded and docs sites connect with fewer dead ends

    A source that half works is worse than one that fails clearly. Linear could mark a whole connection as broken because of one missing permission, Holded rejected a token without saying why, and docs sites asked for an address in an exact format.

    Now each of these tells you what is going on and keeps working where it can.

    • Linear: if Linear denies access to one type of content, such as customers or initiatives, the connection stays Connected in Sources. Brain imports everything else, and what it cannot read shows as No access in Ingest.
    • Holded: a token without the right permissions now says it is missing Developers → API usage or Developers → Webhooks, so you know what to change in Holded before pasting it again.
    • Mintlify and Documentation.AI: typing docs.yourcompany.com is enough, and an http address is read as https.

    You spend less time guessing why a source is not bringing anything in, and you can keep asking Brain about your Linear projects while someone sorts out the one permission that is missing.

  2. Sources

    Gurusup Brain walks you through inviting it to Slack channels

    Gurusup Brain only reads the Slack channels it has been invited to. After connecting Slack you saw Slack connected., even if Brain was not in any channel yet, and the explanation was tucked away in the integration panel. So Slack looked connected while Brain had nothing to read.

    Now, when you come back from connecting or reconnecting Slack, a Finish setting up Slack dialog opens with three steps: open a channel, invite Brain with /invite @GuruSup Brain, which you copy with one click, and Brain joins. Slack connected. shows when you click Done.

    Nobody connects Slack and then wonders why Brain knows nothing about it. Invite Brain to the channels where your team decides things, and within minutes you can ask it what was agreed there, next to what your docs and your CRM say.

  3. Sources

    Connect one Slack or Notion account to several organizations

    Groups, agencies and companies with several teams often work from one Slack workspace or one Notion account but keep separate organizations in Gurusup Brain. Connecting an account that another organization already used was cancelled with already connected to another organization, so only one of them could learn from it.

    Now each organization connects and authorizes the same Slack, Notion, HubSpot, Linear or HappyScribe account on its own from Sources. Credentials, sources, selected content and permissions stay separate, and disconnecting in one organization does not touch the other.

    • If the connection changes while you are signing in, you see The Notion connection changed while you were signing in (or Slack). Refresh the page and connect again.

    Each team gets a Brain that learns from the workspace it shares with the others, and each one only sees what it chose to connect.

  4. Sources

    Everyone on your team sees what feeds Gurusup Brain

    Screenshot of Gurusup Brain: the Company sources table in Sources, with one row per app, its status and its contribution to the Brain.

    Only admins could open Sources. Members had a separate page, so they could not see where Brain's answers came from or which tools the company could connect, and they had to ask an admin.

    Now everyone opens Sources, with two tabs: Sources and Catalog. Members see the Contribution to the Brain chart and the company's sources read only, and opening one shows its About tab. Catalog shows every app Brain can read and who can connect it. Admins keep the buttons to connect, upload files and manage each source.

    • Company sources shows one row per app, so two Notion or two HubSpot accounts appear once, with their numbers added up and the status that needs attention first. Slack stays one row per workspace.
    • Old links to the members' page take you to Sources.

    A new teammate can see in one screen that Brain reads your Notion, Slack and HubSpot, and ask with confidence about anything that lives there.

  5. Agents

    Install Gurusup Brain in Claude, ChatGPT and Codex as a plugin

    Connecting Gurusup Brain to your AI tool meant copying the server URL and pasting it into a settings screen. It worked, but it was the step where people got stuck, and the tool did not learn how to use Brain well.

    Now, in Connect Brain to your tools and in Brain MCP, the main tools install Brain as a plugin. The plugin brings the server and Brain's skill together, so your tool knows how to ask Brain from the start.

    • Claude Desktop: Add plugin from Claude opens the plugin. Click Add, then connect gurusup-brain in its Connectors tab and sign in. On the Free plan, use Manual instead.
    • ChatGPT: Add plugin from OpenAI.
    • Claude Code and Codex: one command in the terminal.
    • Cursor and VS Code keep the same setup as before.

    In a couple of minutes your team can ask Claude or ChatGPT what was decided about a customer and get an answer that pulls from Slack, Notion and your CRM at once, with sources.

  6. Sources

    Each source's panel has tabs and connects without leaving it

    Before you connect a tool, you want to know what Gurusup Brain will read from it and what you will be able to ask afterwards. That used to be scattered, and connecting meant a dialog on top of the source's panel.

    Now each source's panel is organized in tabs, and you connect or reconnect inside it. About explains what Brain reads, gives example questions and says how the source stays current. Connect, which becomes Connections once the source is connected, holds the form and the steps to create a token. Actions appears when the source has something to do. A tab only shows when there is something to put in it.

    • Under Connections, Current connection shows which account is connected and what Brain reads from it.
    • A connected source has a single Disconnect button. Its dialog says Brain stops reading from the source and that what it already learned stays.
    • The status sits next to the name: Connected, Needs reconnect or Error.

    The result is that an admin can decide whether a source is worth connecting, connect it and check that it works, all from one place.

  7. App

    Ingest updates itself, so you no longer refresh it

    Ingest is where you watch content come into Gurusup Brain. It used to show the list as it was when you opened it, so after connecting a source you kept pressing Refresh to see whether anything had arrived.

    Now the list updates on its own and the Refresh button is gone. Each item's status changes in place as it moves from Queued to Learning to Learned, and the list checks more often while something is still being learned.

    • New rows slide in at the top. If you have scrolled down or have a row open, they wait behind a button that reads N new, so nothing moves while you read. Click it to bring them in.
    • An item without a title reads Untitled item.

    You can connect a source, leave Ingest open and see your content being learned as it happens, which is the quickest way to know Brain is ready to answer about it.

  8. Sources

    Connect ClickUp, Asana, Linear, monday.com and five more tools

    A lot of what a team knows lives in its project tracker, its CRM, its invoicing tool, its meeting notes and its public docs. When Gurusup Brain could not read those tools, that knowledge stayed out of every answer, and someone had to go and look it up by hand.

    Sources now offers nine more tools, and an admin connects each one by pasting a token or an address. Brain starts reading as soon as you connect, so the first content shows up in Ingest sooner instead of waiting for the next pass.

    • Projects and tasks: ClickUp (tasks in shared spaces, with subtasks, checklists, fields and comments), Asana (shared projects, status updates and tasks with comments), Linear (public issues, projects, documents, cycles, releases, customers and initiatives) and monday.com (public boards, with items, subitems and comments).
    • Customers and finance: Attio (companies and deals, with their notes, tasks, comments and call transcripts) and Holded (invoices, estimates, orders and purchases, each with its lines and contact). When you paste the Holded token, the panel lists the permissions Brain needs and marks the ones it lacks.
    • Meetings: Granola, with the notes, summary and transcript of each meeting your team shares.
    • Public docs: Mintlify and Documentation.AI. Paste the address of your published docs, no key needed, and Brain keeps them current on its own.

    With these connected, your agent can answer questions that cross tools, such as "which open deals in Attio are waiting on an issue that is still open in Linear?"

  9. Sources

    Bring your current wiki into Gurusup Brain in one upload

    Many teams already have years of knowledge in a wiki or a notes tool. Moving it meant knowing which export to make, and many export formats could not be read, so whole wikis stayed behind.

    Now setup starts by asking Where does your team's knowledge live?, with two paths: Connect live sources and Migrate your current wiki. In Sources, Import from another wiki sits next to Upload files. Pick your tool and the dialog gives you the export steps with that tool's own menu names, then you drop the file. Each page or note comes in as its own document, so you can upload a whole wiki at once.

    • Guided tools: Confluence, Obsidian, Logseq, Evernote, Notion, BookStack, MediaWiki, Roam Research, TiddlyWiki, GitBook, Outline, Joplin and a Markdown folder. Other gives general steps for anything else.
    • Upload files also reads HTML pages, .org, AsciiDoc, Obsidian Canvas, TiddlyWiki and TextPack files, plus exports from BookStack, MediaWiki, Evernote, Roam and TiddlyWiki.
    • Tool folders such as .obsidian or .trash are skipped, and links between notes keep working, also in ZIP files made on macOS with accented names.

    Once it is in, your old wiki answers next to your live tools: your agent can tell you what the onboarding guide in Confluence says and whether last week's Slack thread changed it.

  10. Sources

    Sources groups your Slack channels by workspace

    If you connected many Slack channels, Sources showed each one as its own card and its own slice of the Contribution to the Brain chart. With dozens of channels the page was long, and it was hard to see what Slack as a whole was bringing in.

    Now you get one card and one slice per Slack workspace, named Slack · followed by the workspace name, with its channels, documents and status added up. Click Manage on the card to see every channel, each with its documents, memories, contribution and status.

    • You manage the workspace connection, not each channel, so channel rows no longer have their own Manage button.
    • In the chart, channels that are no longer connected share one Slack slice instead of one slice each.

    At a glance you can compare how much Slack contributes against Notion, HubSpot or your uploaded files, and spot a quiet channel without scrolling through a list of cards.