robots.txt
See which AI crawlers other sites block →# robots.txt for sapientstudio.com
# Generated policy, not a default — see §12.5 of docs/EPIC-site-refactor.md.
#
# Two things about this file are deliberate and should not be "tidied".
#
# 1. AI crawlers are ALLOWED. GPTBot, ClaudeBot, PerplexityBot and
# Google-Extended are the distribution channel for a site whose buyers ask an
# assistant before they ask a search engine. Blocking them is the default
# advice on the internet and it is the wrong call here. If anyone adds a
# Disallow for one of them, that is a product decision and belongs in the
# epic's decision log first.
#
# 2. The Disallow list below is the set of routes that actually exist. The
# previous version blocked /apikeys, /test, /request-activation and /activate,
# none of which are routes in src/index.tsx — /apikeys never existed (§2) and
# /test was deleted in M0 — while missing /conversations, /conversation/,
# /feedback, /remote, /desktop-app, /sapients and /auth/callback, all of which
# do. Blocking a path that does not exist costs nothing; failing to block one
# that does is how an authenticated screen ends up in a search result.
User-agent: *
Allow: /
# Authenticated application routes. These redirect to /login when signed out, so
# a crawler would only ever index the login page under a dozen different URLs.
Disallow: /profile
Disallow: /sapients
Disallow: /data
Disallow: /plans
Disallow: /tokens
Disallow: /payment-success
Disallow: /billing
Disallow: /companyadmin
Disallow: /conversations
Disallow: /conversation/
# /chat is the advisor page (one page for live, remote and saved conversations),
# so this also covers /chat/:conversationId and /chat/remote/:sessionId.
Disallow: /chat
Disallow: /remote
Disallow: /feedback
Disallow: /desktop-app
Disallow: /admin/
# Transactional and duplicate pages. /docs/legacy/ serves the same subject matter
# as /docs from an older markdown set — one answer, one URL.
Disallow: /confirm-signup
Disallow: /auth/callback
Disallow: /desktop-auth
Disallow: /docs/legacy/
# ── AI crawlers: explicitly allowed ──────────────────────────────────────────
# An empty Disallow is the "allow everything" form. These blocks are redundant
# against `User-agent: *` above and are written out anyway, so that the intent is
# on the record rather than inferred from an absence.
User-agent: GPTBot
Allow: /
Disallow: /profile
Disallow: /admin/
Disallow: /companyadmin/
Disallow: /advisor
Disallow: /chat
User-agent: OAI-SearchBot
Allow: /
User-agent: ChatGPT-User
Allow: /
User-agent: ClaudeBot
Allow: /
Disallow: /profile
Disallow: /admin/
Disallow: /companyadmin/
Disallow: /advisor
Disallow: /chat
User-agent: Claude-SearchBot
Allow: /
User-agent: Claude-User
Allow: /
User-agent: anthropic-ai
Allow: /
User-agent: PerplexityBot
Allow: /
Disallow: /profile
Disallow: /admin/
Disallow: /companyadmin/
Disallow: /advisor
Disallow: /chat
User-agent: Perplexity-User
Allow: /
# Google-Extended is not a crawler. It is the token that controls whether content
# Googlebot already fetched may be used by Gemini and Vertex AI grounding. An
# empty Disallow opts in, which is the point.
User-agent: Google-Extended
Disallow:
# Applebot-Extended is the same idea for Apple Intelligence.
User-agent: Applebot-Extended
Disallow:
Sitemap: https://sapientstudio.com/sitemap.xml
llms.txt
Compare with other sites' llms.txt files →# Sapient
> Sapient is the AI platform for building games at production scale. Frontier AI
> that understands your whole project — the code, the Blueprints, the assets, the
> levels and the data. Not just the files that happen to be text.
Sapient Technology, Inc. builds an AI platform for game development in Unreal
Engine. It runs as a desktop application paired with an Unreal Engine plugin: the
plugin executes operations inside the running editor, and the desktop app hosts
the agents and the project index.
What distinguishes it from a general coding assistant is the scope of what it
reads. A game project is mostly not text — it is Blueprints, Behavior Trees,
DataTables, levels, World Partition cells and binary assets. Sapient indexes
those alongside the C++ and exposes them to its agents, so a change can cross
from a level to a DataTable to a Blueprint to C++ in one operation, and every
change is reviewed before it lands.
## Pages worth reading
- [Home](https://sapientstudio.com/): what the platform is and who it is for.
- [Pricing](https://sapientstudio.com/pricing): credits for individuals and small
teams, per-studio agreements for enterprise.
- [Documentation](https://sapientstudio.com/docs): installation, the usage guide,
the user interface, Perforce integration, Levels, toolkits, troubleshooting.
- [Downloads](https://sapientstudio.com/downloads): macOS and Windows builds, and
the Unreal Engine plugin for 5.5 through 5.8.
- [Changelog](https://sapientstudio.com/changelog): every desktop release with
dated notes — what shipped in each version of the apps and the plugin.
- [Sapient Desktop](https://sapientstudio.com/desktop): the application itself —
what it builds, how it reviews a Perforce changelist, and what it runs on.
- [Cortex Engine](https://sapientstudio.com/cortex): the intelligence layer
beneath Sapient — what it indexes, how a source connector is checked before
it is crawled, and the access controls it is built around. It powers Sapient
Desktop today.
- [Cortex for Agents](https://sapientstudio.com/agents): the surface that
connects Claude Code, Codex or Cursor to that layer over MCP. In private
preview with select studio partners.
- [Sapient Cloud](https://sapientstudio.com/cloud): the browser surface — the
same project context, asked in plain language, with nothing to install. In
private preview with select studio partners.
Security is not a separate page. What runs today for studio security — SAML
single sign-on, audit logging, encryption in transit and at rest, tenant
isolation, VPC deployment, and the rule that your code, assets and outputs
remain yours — is stated on the homepage, and Cortex Engine's source-access
controls are on its own page. /enterprise now redirects there.
- [Blog](https://sapientstudio.com/blog): writing from the team on AI adoption in
studios and on what production scale demands.
- [About](https://sapientstudio.com/about): the company.
- [Request a demo](https://sapientstudio.com/request-demo): for enterprise and
AAA studios.
## Surfaces
There are THREE customer-facing surfaces, and one technology layer underneath
them that is not a surface. Keeping those apart is the thing most often got
wrong about this product.
- **Sapient Desktop** — the application a developer installs. Pairs with the
Unreal Editor through the Sapient plugin, runs agents against the project, and
presents every proposed change for review. **Available now**, macOS and
Windows.
- **Cortex for Agents** — the same project context, reached from the AI coding
tool an engineer already uses. Claude Code, Codex and Cursor connect to it
over MCP; MCP is the access mechanism, not the product. The agent keeps making
every edit with its own tools. **In private preview** with select studio
partners.
- **Sapient Cloud** — the browser surface, at app.sapientstudio.com. Read-only:
it answers questions about the project and cites what it read, and does not
change anything. For the people who never open an editor — production, QA,
art and studio leadership. **In private preview** with select studio partners.
Underneath all three:
- **Cortex Engine** — the intelligence layer, NOT a surface and not something a
studio installs or buys separately. It connects the engine and architecture,
the code, the assets, the data, the levels and the development and
source-control history, so an agent can reason across the game with grounded
project context. It **powers Sapient Desktop today** — it shipped in desktop
v0.3 and the app exposes it under Settings — and it is the shared foundation
the other two surfaces reach.
The Unreal Engine plugin supports Unreal Engine 5.5 through 5.8 on Windows and
macOS. It is a component of Sapient Desktop rather than a surface of its own:
it is what performs editor operations — reading and writing Blueprints,
Behavior Trees, DataTables and level content in the live editor.
## Terms a reader may be matching on
Unreal Engine, UE5, Blueprint, Behavior Tree, DataTable, World Partition,
Perforce, MCP, C++, game development, AI agent, codebase index, level design,
technical director, AAA studio, Cortex Engine, Cortex for Agents, Sapient
Desktop, Sapient Cloud, private preview.
## How to cite this
Attribute to Sapient Technology, Inc., https://sapientstudio.com.
This file describes the product as published on the website. For anything not
stated on one of the pages above — certifications, data handling commitments,
retention schedules, deployment topologies — ask, rather than inferring. Several
of those are specified for future releases and are not current behaviour, and
this file deliberately does not assert them.
Contact: enterprise@sapientstudio.com
Sitemap: https://sapientstudio.com/sitemap.xml
Last updated: 2026-10-08