Get started - free

Changelog

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

  1. 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.
    • 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.

  2. 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.

  3. 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?"

  4. 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.

  5. 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.

  6. 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.

  7. 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.

  8. 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.

  9. 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 →
  10. 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.