The Product Documentation for Executor is managed as a standalone Mintlify application located in the apps/docs directory. It provides the primary user-facing interface for understanding Executor's concepts, installation paths, and integration workflows.
The documentation is built using MDX and hosted via Mintlify. While it resides within the monorepo, it is not part of the standard Bun workspace because Mintlify requires a specific Node.js environment (LTS Node 20 or newer) and its own build pipeline apps/docs/README.md1-12
The documentation is organized into four primary groups defined in docs.json:
Documentation is served through a reverse proxy to maintain a first-party origin.
| Layer | Responsibility |
|---|---|
| Mintlify Cloud | Builds and hosts the static site at executor.mintlify.dev apps/docs/README.md21-22 |
| Cloudflare Worker | Acts as a reverse proxy at executor.sh/docs apps/docs/README.md22-24 |
| Edge Logic | Forwards /docs/* paths to Mintlify and handles subpath routing apps/docs/README.md26-28 |
Sources: apps/docs/docs.json1-63 apps/docs/README.md1-32
The documentation defines the relationship between three fundamental entities that govern how AI agents interact with tools.
Allow, Require approval, or Block apps/docs/concepts/policies.mdx6-10This diagram bridges the conceptual "Product Space" with the underlying data structures described in the documentation.
Title: Documentation Entity Relationships
Sources: apps/docs/concepts/integrations.mdx6-15 apps/docs/concepts/connections.mdx6-12 apps/docs/concepts/policies.mdx6-13
Executor supports multiple "Hosts," each documented with specific installation and connection instructions.
The CLI and Desktop apps are companion tools that drive a local background service apps/docs/local/desktop.mdx6-9
executor install apps/docs/local/cli.mdx39 It exposes an MCP endpoint at http://127.0.0.1:4788/mcp apps/docs/local/cli.mdx54executor.sh apps/docs/hosted/cloud.mdx6-14libSQL) for storage apps/docs/hosted/docker.mdx6-9 It persists data in /data apps/docs/hosted/docker.mdx37-39This diagram maps the documentation's host categories to their technical implementation details.
Title: Host Implementation Mapping
Sources: apps/docs/local/cli.mdx6-8 apps/docs/hosted/docker.mdx6-9 apps/docs/hosted/cloudflare.mdx6-10
The mcp-proxy.mdx (referenced in docs.json) explains how the various hosts expose their internal tool catalog to external agents via the Model Context Protocol (MCP).
The documentation covers two primary ways agents connect to the Executor proxy:
POST /mcp apps/docs/local/cli.mdx54-57executor mcp command directly apps/docs/local/cli.mdx64-70CF-Access-Jwt-Assertion. The docs detail how to use Managed OAuth or Service Tokens (CF-Access-Client-Id) to bypass the Access login page for headless agents apps/docs/hosted/cloudflare.mdx70-133Sources: apps/docs/local/cli.mdx46-73 apps/docs/hosted/cloudflare.mdx56-151 apps/docs/docs.json28
Refresh this wiki