> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.livingbrain.com/docs/use-cases/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.livingbrain.com/_mcp/server.

# Use cases

Use this page to find where a brain fits in your work. Connect one to the AI tools you already use, or
build it into your own product.

## Worked examples

Start with the one closest to what you're building.

#### [One brain in every AI tool](/docs/use-cases/one-brain-every-tool)

Save something from one tool and ask for it from another. Claude can also open the brain's graph inside the chat.

![The Living Brain graph open inside a Claude chat](/_fern-files/_img/2d3fb53de3fdd6f6144663c82d853a5906126f889f590c8e5f07028a55f7c97d.webp)

#### [Automated X Support Bot](/docs/use-cases/x-support-bot)

Replies to @mentions on X using only what a curated brain supports, and sends the rest to the team in Slack.

#### [Coding agent memory](/docs/use-cases/coding-agent-memory)

Claude Code, Codex and Cursor share a project's decisions, so a new session can find out why the last one chose what it did.

![A Cursor CLI session answering from Living Brain](/_fern-files/_img/95f19831810a6e899ad727e1697ee388d87f29c7804c0d26b52bf53861a41ccd.webp)

#### [Shared rules in code review](/docs/use-cases/shared-rules-code-review)

Claude Code saves the team's coding rules, and Codex uses them to catch a pull request that breaks them.

![Codex quoting a team rule from Living Brain in a pull request review](/_fern-files/_img/64a0eb9caabe7ca238cd9e1d1a4f1a6ed87ca4fb55ac6fa083f9dddd965fb500.webp)

#### [Customer feedback](/docs/use-cases/customer-feedback)

Tickets, interviews and sales notes compile into one page per customer problem, with a link to each source.

#### [New-hire onboarding](/docs/use-cases/new-hire-onboarding)

An assistant answers "why do we do it this way?" from the team's decisions and their history, and asks the owner when no page covers the question.

#### [Game characters](/docs/use-cases/game-characters)

A character remembers what each player did in a saved game and brings it up in a later play session.

#### [Case files](/docs/use-cases/case-files)

Filings and witness transcripts compile into pages for each case, and conflicting statements stay on the page with their sources.

#### [Team knowledge in Slack](/docs/slack)

Post briefs and page changes to the channels where your team already works.

## Examples by team

These are starting points for your own brain.

#### Engineering

* Capture architecture decisions and ask why a service works the way it does.
* Capture merged pull requests from CI, so review decisions reach the next coding session.
* Import postmortems and search them before changing the system involved.
* Keep runbooks in a brain and flag the pages nobody has touched in months.

#### Product

* Group tickets and interviews by customer problem, however each customer words it.
* Bring back earlier research when a roadmap item is reopened.
* Keep the reason a feature was cut next to the decision to cut it.
* Get a weekly list of every page that changed since the last review.

#### Customer support

* Draft replies from approved pages and cite each one.
* Send questions with no supporting page to a person, with the reason attached.
* Turn a person's answer into a page, so the next similar question has a source.
* Review contested pages when a release note and a ticket disagree.

#### Sales and accounts

* Keep calls, emails and implementation notes on one account's pages.
* Ask what changed on an account since the last meeting.
* Plan with every constraint in view, including the data-residency rule from an old call.
* Hand an account to a new owner along with its history and sources.

#### Research

* Capture papers and links, and let the brain group them into topic pages.
* See which findings connect across papers that use different words.
* Use daily briefs to bring back threads you haven't opened in a while.
* Compare what two sources say about the same claim.

#### People and operations

* Answer a new hire's questions from team decisions, with sources.
* Show how a process changed by reading a page's earlier versions.
* Send stale pages to their owners on a schedule.
* Keep meeting notes searchable by what was decided.

#### Founders and leadership

* Keep plans, updates and open risks in one brain and ask for next steps from any AI tool.
* Prepare for a meeting from the notes behind each decision.
* See where the written record disagrees with itself.

#### Your own product

* Send each chat turn through the classifier. The brain keeps preferences and decisions and drops
  small talk.
* Load the prompt index at the start of a session, then search when a question needs more.
* Give each end user their own brain by using one subject per user.

## What each job needs

Most use cases combine a few of these jobs.

| Job                        | Use                                                                 | Reach for it when                            |
| -------------------------- | ------------------------------------------------------------------- | -------------------------------------------- |
| Find an answer             | [`searchPages`](/docs/search), then `getPage`                       | A question needs something specific          |
| Load general context       | [`index`](/docs/search#prompt-index)                                | An agent starts a session                    |
| Remember something         | [`capture`](/docs/capturing)                                        | A decision, note or document should last     |
| Import history             | [`captureBatch`](/docs/capturing#batches)                           | You have existing documents to bring in      |
| Explain a change           | `pageVersions`                                                      | The question is about why or when            |
| Surface disagreement       | [`contested` status and `resolve`](/docs/pages#contested-pages)     | New material contradicts a page              |
| Keep other systems in step | [Webhooks and the change feed](/docs/changes)                       | A tracker or an app mirrors page state       |
| Tell people what changed   | [Daily briefs](/docs/changes#daily-briefs) and [Slack](/docs/slack) | A team reviews on a schedule                 |
| Work inside AI tools       | [MCP](/mcp) and the [CLI](/cli)                                     | People or agents already work in those tools |

## When to use something else

Use your database for exact records such as balances and order status. Use your analytics tool for
counts and rates. Link to the original document when the wording has legal or financial weight, because
a page summarises what its sources say.

[How to build with Living Brain](/docs/build) covers the write and read paths these examples share.

> Where a brain fits, with worked examples you can copy.

## Docs

- [One brain in every AI tool](https://docs.livingbrain.com/docs/use-cases/one-brain-every-tool.md): Save something in one AI tool and ask for it from another.
- [Automated X Support Bot](https://docs.livingbrain.com/docs/use-cases/x-support-bot.md): Answering public @mentions from one brain and handing the rest to a person.
- [Coding agent memory](https://docs.livingbrain.com/docs/use-cases/coding-agent-memory.md): Keeping a project's decisions across sessions and coding tools.
- [Shared rules in code review](https://docs.livingbrain.com/docs/use-cases/shared-rules-code-review.md): One coding agent saves the team's rules, and another applies them in review.
- [Customer feedback](https://docs.livingbrain.com/docs/use-cases/customer-feedback.md): Collecting tickets, interviews and sales notes into one page per customer problem.
- [New-hire onboarding](https://docs.livingbrain.com/docs/use-cases/new-hire-onboarding.md): Answering a new hire's questions from the team's own decisions, with sources.
- [Game characters](https://docs.livingbrain.com/docs/use-cases/game-characters.md): Giving a character a memory of what each player did, across play sessions.
- [Case files](https://docs.livingbrain.com/docs/use-cases/case-files.md): Compiling a case's filings and transcripts into pages, with each conflict and its sources in view.