Gurusup Brain · Developers

Changelog

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

  1. App

    When your first build stops, Home tells you what to do

    Building your company memory for the first time can take a while. If it failed, Home used to show a technical message and a Retry bootstrap button, which left you wondering whether your content was lost and whose problem it was.

    Now Home says it plainly: Building your company memory stopped on our side. Your content is safe and new content keeps arriving. Retry, and if it stops again, contact support. The button reads Retry.

    You know nothing you connected or uploaded is lost, that sources keep sending content while the build is stopped, and what to do next. If a retry does not fix it, it is ours to fix: contact support. Either way, the sources you connected stay connected and you do not need to set anything up again.

  2. Sources

    Meetings from HappyScribe come into Gurusup Brain on their own

    Decisions are made in meetings, and recordings tend to stay in the tool that made them. If your team records with HappyScribe, what was agreed in those meetings never reached your company memory unless someone copied it over.

    Now an admin can connect HappyScribe from its panel in Sources. Copy the API key of an account that owns or administers your HappyScribe workspace (Settings > Personal > API), paste it in the Connect tab and click Connect. Each meeting HappyScribe finishes after that comes in as one document, with its summary, action items and transcript.

    • Only meetings that finish after you connect come in.
    • HappyScribe does not label private meetings yet, so every meeting comes in for your whole organization. The panel shows this before you connect.
    • If HappyScribe stops accepting the key, the status shows Needs reconnect and Connections tells you to paste a new one. Your access and settings stay as they were.

    Your agent can now answer what was decided in a call and connect it with the rest of your work, for example whether the action items from Tuesday's meeting already have an owner in your project tracker.

  3. App

    Admins get a Your Brain is ready dialog with next steps

    The first build of your memory runs in the background. Admins used to find out it was done only by going back to Home, and then had to work out on their own what to do next.

    Now, the first time your organization's memory is ready, admins see a Your Brain is ready dialog over Home. What you get sums up what Gurusup Brain can do for you, and Connect your AI tool lists Claude Desktop, Claude Code, Codex, ChatGPT and Other MCP client, with More tools for the rest.

    • If the app is open when the build finishes, you hear a short tone. If you are in another tab or window, the tab title tells you it is ready.
    • Closing the dialog hides it in that browser. Members do not see it.

    You can start the build, get on with your day and come back when it tells you, then go straight from a ready memory to asking it your first question from the AI tool you already use.

  4. Agents

    Your agent asks Gurusup Brain with a subject and gets full evidence

    The ask_company_memory tool took more than ten parameters for every question. Its answers also came with a confidence label and a list of gaps that trimmed the evidence, so the agent ended up second-guessing Brain instead of reading what it found.

    Now the tool takes a subject (the customer, project or person the question is about), a question and an optional activity_id. It returns the evidence in full, passages and claims included, and leaves the judgement to your agent, which knows what it is trying to answer.

    • Answers no longer include a confidence label or gaps, and new queries in Queries no longer show them.
    • Answers can be longer, because nothing is cut.
    • Calls without subject are rejected. Refresh the tool schema in your client and pass subject, or null when the question is not about anything specific.

    With the subject named up front, a question like "what is the status of the renewal?" is tied to the right customer, and your agent gets all the evidence to give a complete answer.

    MCP reference →
  5. App

    Set up your organization in three steps

    Getting started used to mix loose questions with a source setup that only happened later, on Home. New admins could not tell when they were done.

    Now every admin goes through one full-screen setup, once: Name your organization, Connect your sources and Connect your agent. The organization name is suggested from your email. In Connect your sources you choose between connecting live tools and migrating your current wiki, and you can also drop files or add a custom webhook. Notion and HubSpot import everything you give access to as soon as you authorize them.

    • Continue turns on as soon as a source is connected or a file is saved, so you do not wait for Gurusup Brain to finish reading.
    • Until the memory is built, Home shows your sources, a Build my memory button and how many minutes are left.

    You go from signing up to a memory that is building and an agent that is connected to it, which is what it takes to ask your first real question.

  6. Agents

    Connect your agent with one card per tool

    Gurusup Brain is meant to be used from the AI tool you already work in. Connecting it used to be one generic step with a server address, and each tool wants that address in a different place.

    Now Connect your agent has a card for each client, with the exact steps for that tool: Claude Desktop, Claude Code, Codex, ChatGPT, Cursor, VS Code and Other MCP client.

    • Cursor and VS Code install in one click.
    • Claude Code and Codex give you one command to paste in your terminal.
    • ChatGPT adds it as a custom connector in Settings, and Claude Desktop as an MCP server in the desktop app.
    • Other MCP client gives you the server URL to paste into any client that supports remote MCP.

    Whoever sets it up only needs the card for their tool, and once it is connected they can ask about your company's knowledge without leaving the conversation they are already having.

    MCP reference →
  7. Memory

    Your first memory starts from the most useful content

    The first build used to wait until everything you imported had been read. With a large Slack history or a big Notion workspace, that meant waiting a long time before you could ask anything.

    Now Gurusup Brain starts with a first batch and brings in the rest on later passes. It reads uploaded files first, then Notion, HubSpot, webhooks and Slack, in that order.

    You can start asking much sooner, and the memory keeps filling in behind you. With very large imports, the first answers may not cover everything yet, and Ingest shows what is still being learned. As later passes finish, the same question gets a more complete answer without you doing anything.

  8. Sources

    Choose which Notion pages and HubSpot deals go into Gurusup Brain

    Not everything in a Notion workspace or a CRM belongs in your company memory. HubSpot used to offer only a Backfill button that brought in everything it could reach, with no say in what came in.

    Now Choose content lets you pick. Search, filter deals by pipeline, stage and date, tick what you want and press Import selected. In Notion, Choose content replaces Backfill.

    You can start with the pipeline or the pages that matter, for example this quarter's open deals and the sales playbook, and add more later. A focused memory gives more precise answers, and you stay in control of what goes into it. If you change your mind, open Choose content again and import more.

  9. Sources

    Webhooks tell you when content has arrived

    A webhook lets any tool send content to Gurusup Brain, even one we do not connect to yet. But after creating one there was no way to know whether anything had arrived, so you could not tell a working setup from a broken one.

    Now each webhook shows Waiting for content until the first delivery and Content received after it.

    • Generate new URL replaces a URL you can no longer see.
    • Admins can paste up to 1 MB of JSON with Send JSON, to try the webhook or send content without setting anything up outside.

    You can wire up an internal tool or an automation, send one test event and see straight away that it reached your memory, before you rely on it. If the status stays on Waiting for content, the problem is on the sending side.

  10. App

    Your organization, named the same way everywhere

    Gurusup Brain called the same thing a workspace in some screens and an organization in others, which made it unclear whether sign-up, plans and settings were talking about the same account.

    Now it is organization everywhere: sign-up, plans, settings and access notices. Team and Settings live in the sidebar under Organization, and any admin can rename the organization from Settings. Contradictions is now called Conflicts, and old links still work.

    One name for one thing means fewer questions when you invite your team or change your plan, and the word in the app matches the word in the docs. If you were used to Contradictions, everything that was there is now under Conflicts.