Try Pro free for 14 days (card required)HeyBrain is now generally available.Start Free

INDUSTRIES · GAMING

AI for game development studios, with your design bible answerable

Use AI for game development with design documents, lore and past decisions. Keep the studio’s context available across its AI tools.

  • Lore.
  • Ask from Claude, Cursor or Codex.
  • Keep private knowledge private.

Built for Game designers, Narrative teams, Producers, IGaming operators

What's the canon on the northern clans?

The lore bible records the northern clans' origin and alliances. The narrative decision log explains the latest change. 1

LoreExample

Keep the canon. Keep the decisions. Ship the game.

Your game designers and narrative teams share answers with sources.

  • Game designersExample

    Lore

    • What's the canon on the northern clans?

      On request

    • Which narrative decision changed the northern clans’ alliances?

      Before deciding

    Source answer: The lore bible records the northern clans' origin and alliances. The narrative decision log explains the latest change.

    Sources: Lore (Google Drive); Elm Collective · Supporting notes (Notion).

    Reads from
    • Google Drive
    • Notion
  • Narrative teamsExample

    Design decisions

    • Why did we cut the crafting system?

      Weekly

    • Which alternatives were considered before cutting the progression feature?

      Before deciding

    Source answer: The design decision links the cut to progression complexity and production scope. The review notes preserve the alternatives.

    Recorded reason for the cut
    The design decision links the cut to progression complexity and production scope.
    Alternatives in the review notes
    The review notes preserve the alternatives.

    Sources: Design decisions (Notion); Elm Collective · Supporting notes (Google Drive).

    Reads from
    • Notion
    • Google Drive
  • ProducersExample

    Unannounced projects withheld from contractors

    • What project guidance can our contractors access?

      On request

    • Which released design guidance can contractors read without unannounced project files?

      Before deciding

    Source answer: Released design guidance is available to contractors. Unannounced project documents remain restricted to the core team.

    Sources: Unannounced projects withheld from contractors (Google Drive); Elm Collective · Supporting notes (Notion).

    Reads from
    • Google Drive
    • Notion
  • IGaming operatorsExample

    Responsible gambling rules

    • What are our UK safer gambling rules?

      Weekly

    • Who owns the current safer-gambling policy reference?

      Before deciding

    Source answer: The saved safer-gambling policy identifies the operator's procedures and owners. The answer links the current reference.

    • Open the current source before the next step

    Sources: Responsible gambling rules (Notion); Elm Collective · Supporting notes (Google Drive).

    Reads from
    • Notion
    • Google Drive
  • Game designersExample

    New developer onboarding

    • Where should a new developer start to understand our game?

      On request

    • Which architecture, lore and design sources should a new developer read first?

      Before deciding

    Source answer: The onboarding index links architecture, lore and design principles. A new developer can ask why a system works as it does.

    • Open the current source before the next step

    Sources: New developer onboarding (Google Drive); Elm Collective · Supporting notes (Notion).

    Reads from
    • Google Drive
    • Notion
  • Narrative teamsExample

    Patch notes from what shipped

    • Can my AI tool draft patch notes from the changes we shipped?

      Weekly

    • Which completed changes should the AI tool use for the patch-note draft?

      Before deciding

    Source answer: The shipped checklist records the completed changes. Your AI tool can use those sources to draft patch notes.

    Completed changes
    The shipped checklist records the completed changes.
    Drafting in your AI tool
    Your AI tool can use those sources to draft patch notes.

    Sources: Patch notes from what shipped (Notion); Elm Collective · Supporting notes (Google Drive).

    Reads from
    • Notion
    • Google Drive

Less searching. More shared context.

Without HeyBrain

With HeyBrain

Read the lore bible and narrative decision log separately to reconstruct the northern clans’ canon and latest change.

Find the clans’ origin and alliances in the lore bible, with the narrative decision log explaining the latest change.

Search the design decision and review notes to reconstruct why crafting was cut and which alternatives were considered.

Find the progression-complexity and production-scope reasons for the cut, with the alternatives preserved in the review notes.

Check contractor access to released design guidance separately from unannounced project documents.

Use released design guidance while unannounced project documents remain restricted to the core team.

Search the saved safer-gambling policy for the operator’s procedures, owners and current reference.

Find the operator’s procedures and owners in the saved policy, with the answer linking the current reference.

ONE CONNECTED BRAIN

One question, across your tools

Bring Google Drive, Notion and your uploads into one cited answer.

Question
What's the canon on the northern clans?
Answer
The lore bible records the northern clans' origin and alliances. The narrative decision log explains the latest change. (Source 1)
  • Source 1: Lore (Google Drive)
  • Additional source: Design decisions (Notion)
  • Additional source: Unannounced projects withheld from contractors (Google Drive)

Illustrative example, fictional data

FOLLOW THE SOURCE

Review the evidence behind an answer

Open the citation. Read the original wording and surrounding detail.

Answer
The design decision links the cut to progression complexity and production scope. The review notes preserve the alternatives. (Source 1)
Cited excerpt from Design decisions (Notion)
The design decision links the cut to progression complexity and production scope. The review notes preserve the alternatives.
  • Source 1: Design decisions (Notion)
  • Source 2: Lore (Google Drive)

Illustrative example, fictional data

PERMISSIONS IN EVERY ANSWER

Share the context. Keep the boundaries.

Same question, different permissions. Review the request in the activity record.

Question
What changed in the next game milestone?
Answer for Elise Okafor (Executive producer)
Production schedule and design notes available. Publisher milestone payment: September.
Answer for Leila Chen (Game designer)
Production schedule and design notes available. The restricted source is not in your access.
Not in Leila Chen’s access
PUBLISHER TERMS · PRODUCERS ONLY
Access record
14:02 · Leila Chen · Asked the brain · RECORDED

Illustrative example, fictional data

Company knowledge, under your control

Source sharing, where we can prove it

Google Drive, GitHub and Slack (beta) sharing carries into HeyBrain. Notion uses the connecting account’s access.

Every AI tool gets its own key

It acts with your access. Revoke it any time.

An activity record

Review questions asked, uploads, syncs and blocked or masked data.

Review provider data terms

Check provider data use and retention.

Bring your own model key

Connect your model to governed knowledge.

SEND PASSAGES, NOT WHOLE FILES

Send less context per task

HeyBrain sends relevant passages instead of whole documents.

Repeated contextWhole documents
With HeyBrainRelevant passages

FAQ

Questions gaming ask

  • What's the canon on the northern clans?

    The lore bible records the northern clans' origin and alliances. The narrative decision log explains the latest change. Ask follow-ups in the same conversation and open each citation to check the surrounding detail, then share the source with colleagues who can access the same collection.

  • Why did we cut the crafting system?

    The design decision links the cut to progression complexity and production scope. The review notes preserve the alternatives. Connect the relevant Drive folder or Notion pages, or upload documents, then follow citations to their original passages from the AI tools your colleagues already use.

  • Which sources and AI tools can we use?

    Connect Google Drive, Notion and document uploads; Claude, Cursor and Codex ask your company knowledge through HeyBrain MCP. Keep decisions and references available where your team works. HeyBrain supplies knowledge; agents use their own tools for actions requested by the user.

  • How does HeyBrain keep private knowledge private?

    People and agents receive answers from sources they can open. Workspace rules restrict the audience; each AI tool has its own revocable key that acts with its member’s access. Administrators review who asked and when in the activity record, alongside workspace membership and access rules.

  • How do we get the team started?

    Connect your team’s current brief, decision notes and working guide, invite the people who need them and ask a familiar question. Open its source citations before expanding the collection. Align workspace membership and each governed agent’s policy with each team’s responsibilities.

  • How does HeyBrain reduce AI token cost?

    HeyBrain sends relevant passages instead of whole documents to your AI tool. Compare costs with the context calculator on the Reduce AI token costs page. Your team shares the same connected knowledge across tools, so every new conversation can start with the relevant passages and their sources.

/ Get started today

Put your company knowledge
to work with HeyBrain