ThinkingRoot

Mission

The right context. At the right place. At the right time. Linked with past memories.

How it gets in.

Tools and chats both land in one brain. Filed where they belong.

Tools

Docs and apps sync in

Notion, Drive, and the rest land in the right branch for each client or project.

Chats

Conversations stay too

In Claude or Cursor, a trigger word saves it. In Slack or the compose box, one tap keeps it.

Context everywhere.

The same memory shows up wherever you work. AI tools and the browser.

AI tools

In every AI tool

Paste one URL. Claude, Cursor, and Codex already recall what the company knows.

Browser

Tab

In every tab

A pill at the edge of Gmail, Slack, or any page. Tab to put the line into what you are typing.

What you get.

Time back. Longer sessions. Cleaner answers. Less spend on tokens that never earned their place.

Time

The answer is already there. No hunt through threads, docs, or last week's chat.

Long sessions

The thread can run for hours. The brain still knows who you meant and what you promised.

Output quality

Replies draw from what the company already decided, not a fresh guess every turn.

Productivity

Less paste, less re-brief, less starting over. Work moves from the question.

Near zero hallucination

If the brain does not know it, it stays quiet. No inventing to fill the gap.

Token reduction

Only the facts that earn a place ride into the model. Shorter context, lower cost.

Inspired by the Human brain.

Type a line. The fact that matters rises. The rest stays quiet.

What rises at your cursor

seeded demo brain

You quoted $40 a seat on Thursday's call.

ConflictYou typed $45. Brain has $40.

Thu 3 Sep

Postgres over Mongo: one writer, no lock class.

12 Aug

I'll send the terms Friday.

due Fri

Acme starts October 1.

28 Aug

Priya is out until the 18th.

9 Sep

Dana, VP Ops, is Acme's champion.

20 Aug

What you typed disagrees with what was said. The brain rose the record.

Why ThinkingRoot.

Same question to a file, a repo, and the brain. See who answers, and what you paid to read.

A markdown file

notes.md · 28 Aug

# Acme: working notes
 
Owner: Sam. Champion on their side: Dana (VP Ops). Procurement contact: Luis.
Priya covers engineering questions until the 18th, then Marco.
 
## Where we are
 
Acme want 120 seats for the ops team, growing to 300 by Q2. They asked for
annual billing and a 30-day pilot. We agreed a pilot on the ops team only,
with a written success criterion: 80% weekly active in the pilot group.
 
Dana pushed back hard on the list price on the first call. We walked
through the volume ladder and landed on 40 per seat for the first year,
with a review at renewal. The renewal is in March. No further discount
unless they commit to 300 seats up front, which they will not do this year.
 
Legal wants our DPA signed before the pilot starts. Luis will route it.
The commercial terms are still due to them; Sam said Friday.
 
## Timeline
 
Kick-off is set for October 1. Dana wants the ops team live in the first
week; Priya says a two-week import window is realistic for their Confluence
export. Start moved once already (from September 15) when procurement
slipped, so do not promise a date without checking the sprint board first.
 
## Technical
 
Acme run their own Postgres already and asked whether we could share it.
No: one writer per brain is the whole point; a shared writer is the lock
class we removed. We chose Postgres over Mongo on 12 August for the control
plane for that reason: one writer, no lock class, and the migrations are
plain SQL the auditors can read.
 
SSO through Okta, groups mapped to branches. They asked about audit export;
we said the account endpoint gives them rows, not estimates.
 
## People
 
Dana (VP Ops): the champion. Direct, hates surprises, reads everything.
Luis (procurement): slow, fair, needs the DPA before anything else.
Marco (their eng lead): sceptical about import quality; wants to see the
Confluence run on real pages before he signs off.
 
## Open questions
 
- Does the 40 per seat hold if they come in under 120 seats?
- Who owns the Okta group mapping on their side?
- Can we show Marco a real import before the pilot instead of a slide?
 
## Call log
 
- 12 Aug: internal: database decision (see Technical).
- 20 Aug: Dana intro call; she is the champion.
- 28 Aug: pricing call with Dana and Luis; landed the number above.
 

≈ 569 tokens

Whole file rides in, every ask.

A GitHub repo

grep -ri 'quote|acme'

  • acme/notes.md:1 # Acme: working notes
  • acme/notes.md:8 Acme want 120 seats for the ops team, growing to 300 by Q2. They asked for
  • acme/notes.md:29 Acme run their own Postgres already and asked whether we could share it.
  • pricing.md:5 Volume: 50+ seats 20% off; 100+ seats 30% off; 250+ seats by quote.
  • pricing.md:8 Quote of the day: "Price is what you pay, value is what you get."
  • README.md:4 Quote numbers only after the pricing call, never before.
  • calls/2026-08-28-acme.md:1 # 28 Aug: Acme pricing call

7 word hits

Still strings. You read them to know.

The brain

recall · ≈ 38 tokens

$40 a seat for year one, from Thursday's call. Review at the March renewal.

  • You quoted $40 a seat on Thursday's call.

    metric · critical · Thu 3 Sep

  • Dana, VP Ops, is Acme's champion.

    fact · routine · 20 Aug

≈ 38 tokens

Only what answers. Nothing else.

Building the world #1 artificial brain.

World #1 on LongMemEval-S. Zero memory-poison hits on RotBench. NVIDIA Inception member. Built like a human brain, scored on the production path.

LongMemEval-S

99.0%

Recall@15 · World #1

Official 500-question suite. 481 tokens in. 16 ms warm.

Method

RotBench

0

Memory-poison hits

Tool-output poisoning, 26 runs. Day-90 recall leads published peers.

Method

NVIDIA Inception

Inception Program Member

Accepted July 2026. Building the artificial brain on NVIDIA's AI ecosystem.

Program

Questions, answered honestly.

Every claim on this site is measured or labeled as pending. Same rule here.

Why ThinkingRoot?

Context for humans and AI tools, at the cursor where they already work. Sync what lives in your systems. Keep what lives in heads and chats. Hand it back on every seat: Cursor, Claude, Chrome, and every teammate you add.

Why a brain?

Docs, mail, calls, and AI chats do not share. Each tool starts over. What lives in one head dies when the tab closes. Agents and people need the same past. A chat cannot hold that. A folder cannot serve it at the cursor.

Why not a markdown file or GitHub?

A file is storage. It does not show up in the composer you are already typing in. GitHub holds code and docs. It does not catch mail, meetings, or what someone just decided in chat. Searching a repo is not the same as asking what you agreed, on the branch you chose.

How does it show up where I already work?

Paste MCP into Cursor or Claude and ask in plain language. In Chrome, shadow text can finish the line in the box you are already in. On Meet or in person, the pillar Record button files the call on the branch you selected. Same brain. Every tool.

What's your benchmark score?

World #1 on LongMemEval-S at 99.0% Recall@15 on the official 500-question suite, measured on the production path. Zero memory-poison hits on RotBench. Method write-ups are on the blog. We do not invent ranks we have not run.

Can one person's data leak into another's answers?

No. Isolation is architectural, not a filter. Each user's memory is a separate database. Requests are scoped at the gateway. Embed tokens pin a single user. There is no shared table for data to cross.

Does it lock me into a model or a cloud?

No. Reach it over MCP, SDK, or REST with the models and tools you already use. Free tier to start. Pro, Scale, and Business as you grow. Your memory is not trapped inside one vendor's chat product.

From the blog

All posts

Bring everything you have. We'll do the thinking and the rooting.

Sync what lives in your tools. Keep what lives in chats. One company memory, back at the cursor in every AI tool and every seat.