Skip to main content

Welcome

Sentilai is the control plane for the AI coding assistants your team already uses. Every request from Claude Code, Cursor, GitHub Copilot, Gemini CLI or Codex CLI routes through the Sentilai Gateway, where your policy is enforced in real time and everything is audited. Your developers keep their tools and their workflow.

This is the documentation for the people who run it.

Start here

  • New to Sentilai? Read What Sentilai does for the shape of the product in three minutes, then Your first hour for the shortest path from an empty organization to a governed request you can watch arrive.
  • Rolling it out? Install the Endpoint Suite, then Govern all detected tools, then Rolling out to the team when the pilot works.
  • Setting policy? Choosing your first policy is the sequence that avoids the mistake everyone makes — blocking too much on day one and teaching your team to route around you.
  • Something is wrong? Start at Nothing appears in Activity; four times out of five the answer is that the tool was not restarted.

How this is organized

Eighteen sections, one per area of the product. Browse them from the Books page — each carries the settings, the workflows and the failure modes for one part of the system.

If you would rather ask than browse, the search box at the top searches every article.

What we promise about this documentation

It describes what is built, not what is planned. Where a feature has limits — Cursor's autocomplete is not routed, Copilot's inline completions are not routed, per-tool MCP rules apply where the Gateway can see a tool name — those limits are written down in the article about that feature, not omitted. What Sentilai does not do collects them in one place, and is five minutes better spent than any feature list.

Where something is not yet certified, we say so rather than implying otherwise.

Getting help

Admins can open a ticket from Support inside the console — we already know who you are and which organization you belong to, so there is nothing to prove. See Open a support ticket for what to attach.

Back to top