Every settings page works the same way.
Register items with the Add button; each item can be edited or deleted .
Each page comes with recommended presets that you can apply instantly with a single click.
For each item you set a Required / Recommended enforcement level. For details, see the Policy operations guide .
AI Models Register and approve the AI models your organization is allowed to use.
Supported integration types include official APIs, open-model APIs, cloud providers (Vertex AI · Azure OpenAI · AWS Bedrock), and self-hosted servers (OpenAI-compatible endpoints).
Model whitelist — Only the models approved by your organization appear in the model picker in the IDE. This lets you run a model strategy driven by company cost and security standards rather than individual preference.
MCP Servers Restrict integrations to only the external tools your organization has approved, such as GitHub and Jira.
Register a server name and URL, and it is automatically deployed to every IDE in the organization.
Authentication supports API keys or OAuth.
Use Test connection and Fetch tool list to verify that everything works correctly.
Preserve extensibility while preventing data leaks caused by connecting unvetted external tools.
RAG (Internal Knowledge) Upload your internal wiki, API documentation, and policy documents, and the AI references them when answering.
Supported formats: .txt .md .pdf .docx .json .csv
By referencing shared team documents, the AI provides answers that “understand your company’s context.”
Skills (Development Rules) Register the team rules the AI must follow when writing code, in Markdown.
Categories are divided into version control, coding style, project architecture, dependency policy, DB, and custom.
Developers don’t have to memorize every rule; the AI adheres to team standards at the generation stage.
Build/Test Settings Register the validation and formatter commands to run automatically after code generation. You can specify different commands per language.
If validation fails, the AI analyzes the error and attempts to fix it on its own.
Hot Load Register keywords, and when a team member types a sentence containing one of them in chat, a predefined command runs automatically.
Turn your team’s repetitive-task know-how into automation rules as reusable assets .
Hooks Attach shell commands to specific points in the workflow. Use them for audit logging or integrating with internal systems.
You can set matching conditions so a hook responds only to specific tools, and configure synchronous/asynchronous execution and timeouts.
Agents Register subagents to deploy across the entire company. Team members invoke them with @agentname
By deploying agents with dedicated roles—such as “security reviewer” or “test writer”—everyone on the team receives reviews held to the same standard .
Security Rules Block the execution of dangerous commands and access to sensitive files.
Exclude Patterns Register the paths to exclude from project indexing, file search, and context collection as glob patterns. .gitignore is applied automatically.
Put safeguards in place at the system level without friction between the security and development teams.
