arrow-left

Only this pageAll pages
gitbookPowered by GitBook
triangle-exclamation
Couldn't generate the PDF for 137 pages, generation stopped at 100.
Extend with 50 more pages.
1 of 100

BITO

Loading...

Loading...

Loading...

AI Architect

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

AI Code Reviews in Git

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

AI Code Reviews in IDE

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

AI Code Reviews in CLI

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Other Bito AI tools

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Installation guide

Welcome to Bito

Bitoarrow-up-right provides codebase intelligence for AI coding agents. Using Bito, your AI agents like Cursor, Claude, ChatGPT, GitHub Copilot, and Windsurf can understand your entire codebase architecture and generate accurate, production-ready code.

Bito's AI Architect builds a knowledge graph of your codebase — from repos to modules to APIs —delivering system-aware context to the AI coding agents you already use. This helps AI agents reason about your system instead of working with isolated code snippets.

Beyond code generation, AI Architect also powers Bito's AI Code Review Agent, which provides intelligent, context-aware code reviews in GitHub, GitLab, and Bitbucket. This catches cross-repository impacts and architectural issues that traditional tools miss, helping you merge PRs 89% faster with 34% fewer regressions.

Start free trialGetting started guide

hashtag
Key capabilities of the AI Architect

  • Grounded 1-shot production-ready code — The AI Architect learns all your services, endpoints, code usage examples, and architectural patterns. The agent automatically feeds those to your coding agent (Claude Code, Cursor, Codex, any MCP client) to provide it the necessary information to quickly and efficiently create production ready code.

  • Consistent design adherence — Code generated aligns with your architecture patterns and coding conventions.

hashtag
Getting started

Choose what you'd like to set up:

  • AI Architect

    • (Fully managed by Bito — no infrastructure setup required)

    • (Run AI Architect on your own infrastructure for maximum control)

hashtag
Helpful resources

hashtag
AI Architect

hashtag
AI Code Review Agent

hashtag
Video library

hashtag
Need help?

If you have any questions, feel free to email us at

Quickstart

This guide will help you set up and start using Bito's AI-powered tools. Whether you're looking to enhance feedback of your coding agents with AI Architect or automate code reviews with our AI Code Review Agent, you'll find everything you need below.

hashtag
AI Architect

1

hashtag
Install AI Architect

hashtag
Bito-hosted

  1. and connect your Git provider.

  2. Provide your repository list to Bito

  3. Bito indexes your repositories and builds a knowledge graph

hashtag
Self-hosted

  1. Download and install AI Architect with a single command.

  2. Configure AI Architect with your Git and LLM credentials.

  3. Configure your repositories

2

hashtag
Connect to your AI coding agent

Using the Bito MCP URL and Bito MCP Access Token, you can connect AI Architect to your AI coding tools either through an automated installer or via manual configuration, depending on your agent and environment.

hashtag
AI Code Reviews in Git

1

hashtag
Sign up for Bito

Create your account at to get started.

2

Privacy and security

Bito doesn't read or store your code. Nor do we use your code for AI model training.

This document explains some of Bito's privacy and security practices. Our outlines our various accreditations (SOC 2 Type II) and our various security policies. You can read our full Privacy Policy at .

hashtag
Bito AI

Security is top of mind at Bito, especially when it comes to your code. A fundamental approach we have taken is we do not store any code, code snippets, indexes or embedding vectors on Bito’s servers unless you expressly allow it. You decide where you want to store your code, either locally on your machine, in your cloud, or on Bito’s cloud. Importantly, our AI partners do not store any of this information.

Install/run as a self-hosted service

Deploy the AI Code Review Agent on your machine.

The self-hosted AI Code Review Agent offers a more private and customizable option for teams looking to enhance their code review processes within their own infrastructure, while maintaining complete control over their data. This approach is ideal for organizations with specific compliance, security, or customization requirements.

hashtag
Understanding CLI vs webhooks service

When setting up the AI Code Review Agent, you have the flexibility to choose between two primary modes of operation: CLI and webhooks service.

Install/run using Bito Cloud

Deploy the AI Code Review Agent in Bito Cloud.

offers a single-click solution for using the , eliminating the need for any downloads on your machine. You can create multiple instances of the Agent, allowing each to be used with a different repository on a Git provider such as GitHub, GitLab, or Bitbucket.

We also support GitHub (Self-Managed), GitLab (Self-Managed), and Bitbucket (Self-Managed).

circle-info

The Free Plan offers AI-generated pull request summaries to provide a quick overview of changes. For advanced features like line-level code suggestions, consider upgrading to the

Integrating AI Architect with AI Code Review Agent

Leverage AI Architect's knowledge graph to power more intelligent code reviews

Enhance your code reviews with deeper codebase intelligence by connecting Bito's to . This integration enables significantly more accurate and context-aware reviews by leveraging the comprehensive knowledge graph that AI Architect builds from your codebase.

hashtag
What this integration provides

When AI Code Review Agent accesses AI Architect's knowledge graph, it gains a complete understanding of your codebase architecture — including microservices, modules, APIs, dependencies, and design patterns.

Delete unused Agent instances

Easily delete Agent instances you no longer need.

If you no longer need an instance, you can delete it to keep your workspace organized. Follow the steps below to quickly remove any unused Agents.

  1. and select a workspace to get started.

  2. From the left sidebar, select .

    If your Bito workspace is connected to your GitHub/GitLab/Bitbucket account, a list of AI Code Review Agent instances configured in your workspace will appear.

Clone an Agent instance

Easily duplicate Agent configurations for faster setup.

Save time and effort by quickly creating a new instance using the configuration settings of an existing one. It’s a fast and simple way to set up multiple Agent instances without having to reconfigure each one.

Follow the steps below to get started:

  1. and select a workspace to get started.

  2. From the left sidebar, select .

Installing on Cursor

It takes less than 2 minutes

Get up and running with Bito in just a few steps! Bito seamlessly integrates with Cursor, providing powerful AI-driven code reviews directly within your editor. Click the button below to quickly install the Bito extension and start optimizing your development workflow with context-aware , and more.

hashtag
Installation Steps

Getting started

Deploy the AI Code Review Agent in Bito Cloud or opt for self-hosted service.

The supports two deployment options:

Each option comes with its own set of benefits and considerations.

Open Bito in a new tab or window

Learn how to customize Bito’s view by switching from a side panel to a new tab or a separate window.

Chat session history

Bito automatically saves the chat session History. The session history is stored locally on your computer. You can return to any chat session and continue the AI conversation from where you left off. Bito will automatically maintain and restore the memory of the loaded chat session.

You can "Delete" any saved chat session or share a permalink to the session with your coworkers.

Here is the video overview of accessing and managing the session history.

CLI allows developers to manually initiate code reviews directly from terminal. This mode is ideal for quick, on-demand code reviews without the need for continuous monitoring or integration.

  • Webhooks service transforms the Agent into a persistent service that automatically triggers code reviews based on specific events, such as pull requests or comments on pull requests. This mode is suitable for teams looking to automate their code review processes.

  • For more details, visit the CLI vs webhooks service page.

    hashtag
    Deployment Options

    Based on your needs and the desired integration level with your development workflow, choose one of the following options to install and run the AI Code Review Agent:

    circle-info

    Before proceeding, ensure you've completed all necessary prerequisites for self-hosted AI Code Review Agent.

    1. Install/run via CLI: Ideal for developers seeking a simple, interactive way to conduct code reviews from the command line.

    2. Install/run via webhooks service: Perfect for teams looking to automate code reviews through external events, enhancing their CI/CD workflow.

    3. Install/run via GitHub Actions: A great option for GitHub users to seamlessly integrate automated code reviews into their GitHub Actions workflows.

    All requests are transmitted over HTTPS and are fully encrypted.

    None of your code or AI requests are used for AI model training. None of your code or AI requests are stored by our AI partners. Our AI model partners are OpenAI, Anthropic, and Google. Here are their policies where they state that they do not store or train on data related to API access (we access all AI models via APIs):

    1. OpenAI: https://openai.com/enterprise-privacy/arrow-up-right

    2. Anthropic: https://www.anthropic.com/uk-government-internal-ai-safety-policy-response/data-input-controls-and-auditarrow-up-right

    3. Google Cloud: https://cloud.google.com/blog/products/ai-machine-learning/google-cloud-unveils-ai-and-ml-privacy-commitmentarrow-up-right (5th paragraph)

    The AI requests including code snippets you send to Bito are sent to Bito servers for processing so that we can respond with an answer.

    Interactions with Bito AI are auto-moderated and managed for toxicity and harmful inputs and outputs.

    Any response generated by the Bito IDE AI Assistant is stored locally on your machine to show the history in Bito UI. You can clear the history anytime you want from the Bito UI.

    hashtag
    SOC 2 Type II Compliance

    Bito is SOC 2 Type II compliant. This certification reinforces our commitment to safeguarding user data by adhering to strict security, availability, and confidentiality standards. SOC 2 Type II compliance is an independent, rigorous audit that evaluates how well an organization implements and follows these security practices over time.

    Our SOC 2 Type II compliance means:

    • Enhanced Data Security: We consistently implement robust controls to protect your data from unauthorized access and ensure it remains secure.

    • Operational Excellence: Our processes are designed to maintain high availability and reliability, ensuring uninterrupted service.

    • Regular Monitoring and Testing: We conduct continuous monitoring and regular internal reviews to uphold the highest security standards.

    This certification is an assurance that Bito operates with a high level of trust and transparency, providing you with a secure environment for your code and data.

    For any further questions regarding our SOC 2 Type II compliance or to request a copy of the audit report, please reach out to [email protected]envelope

    hashtag
    Code Flow through Bito’s System

    hashtag
    AI Code Review Agent

    When you use the self-hosted/docker version that you have setup in your VPC, in the docker image Bito checks out the diff and clones the repo for static analysis and also to determine relevant code context for code review. This context and the diff is passed to Bito's system. The request is then sent to a third-party LLM (e.g., OpenAI, Google Cloud, etc.). The LLM processes the prompt and return the response to Bito. No code is retained by the LLM. Bito then receives the response, processes it (such as formatting), and returns it to your self-hosted docker instance. This then posts it to your Git provider. However, the original query is not retained, nor are the results. After each code review is completed, the diff and the checked out repo are deleted.

    If you use the Bito cloud to run the AI Code Review Agent, it runs similarly to the self-hosted version. Bito ephemerally checks out the diff and clones the repo for static analysis and to determine the relevant code context for code review. This context and the diff is passed to Bito's system. The request is then sent by Bito to a third-party LLM (e.g., OpenAI, Google Cloud, etc.). The LLM processes the prompt and return the response to Bito. No code is retained by the LLM. Bito then receives the response, processes it (such as formatting), and posts it to your Git provider. However, the original query is not retained, nor are the results. After each code review is completed, the diff and the checked out repo are deleted.

    hashtag
    AI Chat and Code Completions

    When we receive an AI request from a user, it is processed by Bito's system (such as adding relevant context and determining the Large Language Model (LLM) to use). However, the original query is not retained. The request is then sent to a third-party LLM (e.g., OpenAI, Google Cloud, etc.). The LLM processes the prompt and return the response to Bito. Bito then receives the response, processes it (such as formatting), and returns it to the user’s machine.

    For enterprises, we have the ability to connect to your own private LLM accounts, including but not limited to OpenAI, Google Cloud, Anthropic, or third-party services such as AWS Bedrock, Azure OpenAI. This way all data goes through your own accounts or Virtual Private Cloud (VPC), ensuring enhanced control and security.

    hashtag
    Data and Business Privacy Policy

    In line with Bito's commitment to transparency and adherence to data privacy standards, our comprehensive data and business privacy policy is integrated into our practices. Our complete Terms of Use, including the Privacy Policy, are available at https://bito.ai/terms-of-use/arrow-up-right, with our principal licensing information detailed at https://bito.ai/terms-of-service/arrow-up-right.

    hashtag
    Data Retention Policy

    Our data retention policy is carefully designed to comply with legal standards and to respect our customers' privacy concerns. The policy is categorized into four levels of data:

    1. Relationship and Usage Meta Data: This includes all data related to the customer's interaction with Bito, such as address, billing amounts, user account data (name and email), and usage metrics (number of queries made, time of day, length of query, etc.). This category of data is retained indefinitely for ongoing service improvement and customer support.

    2. Bito Business Data: Includes customer-created templates and settings. This data is terminated 90 days after the end of the business relationship with Bito.

    3. Confidential Customer Business Data: This includes code, code artifacts, and other organization-owned data such as Jira, Confluence, etc. This data is either stored on-prem/locally on the customer’s machines, or, if in the cloud, is terminated at the end of the business relationship with Bito.

    4. AI Requests: Data in an AI request to Bito’s AI system. AI requests are neither retained nor viewed by Bito. We ensure the confidentiality of your AI queries; Bito and our LLM partners do not store your code, and none of your data is used for model training. All requests are transmitted via HTTPS and are fully encrypted.

    hashtag
    Sub-processor

    Bito uses the following third-party services: Amazon AWS, Anthropic, Clearbit, Github, Google Analytics, Google Cloud, HelpScout, Hubspot, Microsoft Azure, Mixpanel, OpenAI, SendGrid, SiteGround, and Slack for infrastructure, support, and functional capabilities.

    hashtag
    Personal Data

    Bito follows industry standard practices for protecting your e-mail and other personal details. Our password-less login process - which requires one-time passcode sent to your e-mail for every login - ensures the complete security of your account.

    If you have any questions about our security and privacy, please email [email protected]envelope

    Trust Center arrow-up-right
    https://bito.ai/privacy-policy/arrow-up-right
    This enhanced context allows the AI Code Review Agent to:
    • Provide system-aware code reviews - Understand how changes in one service or module impact other parts of your system

    • Catch architectural inconsistencies - Identify when new code doesn't align with your established patterns and conventions

    • Detect cross-repository issues - Spot problems that span multiple repositories or services

    • Deliver more accurate suggestions - Generate fixes that are grounded in your actual codebase structure and usage patterns

    • Reduce false positives - Better understand context to avoid flagging valid code as problematic

    hashtag
    Setup instructions

    Follow these steps to connect AI Architect with AI Code Review Agent:

    1. Log in to Bito Cloudarrow-up-right

    2. Open the AI Architect Settingsarrow-up-right dashboard.

    3. In the Server URL field, enter your Bito MCP URL

    4. In the Auth token field, enter your Bito MCP Access Token

    hashtag
    Need help?

    Contact our team at [email protected]envelope to request a trial. We'll help you configure the integration and get your team up and running quickly.

    AI Code Review Agent
    AI Architect
    This guide walks you through both options to help you determine which deployment model best fits your team’s needs.

    hashtag
    Bito Cloud

    Bito Cloud provides a managed environment for running the AI Code Review Agent, offering a seamless, hassle-free experience. This option is ideal for teams looking for quick deployment and minimal operational overhead.

    Pros:

    • Simplicity: Enjoy a straightforward setup with a single-click installation process, making it easy to get started without technical hurdles.

    • Maintenance-Free: Bito Cloud takes care of all necessary updates and maintenance, ensuring your Agent always operates on the latest software version without any effort on your part.

    • Scalability: The platform is designed to easily scale, accommodating project growth effortlessly and ensuring reliable performance under varying loads.

    Cons:

    • Handling of Pull Request Diffs: For analysis purposes, diffs from pull requests are temporarily stored on our servers.

    Install/run using Bito Cloud


    hashtag
    Self-hosted service

    Self-hosted AI Code Review Agent offers a higher degree of control and customization, suited for organizations with specific requirements or those who prefer to manage their own infrastructure.

    Pros:

    • Full Control: Self-hosting provides complete control over the deployment environment, allowing for extensive customization and the ability to integrate with existing systems as needed.

    • Privacy and Security: Keeping the AI Code Review Agent within your own infrastructure can enhance data security and privacy, as all information remains under your direct control.

    Cons:

    • Setup Complexity: Establishing a self-hosted environment requires technical know-how and can be more complex than using a managed service, potentially leading to longer setup times.

    • Maintenance Responsibility: The responsibility of maintaining and updating the software falls entirely on your team, which includes ensuring the system is scaled appropriately to handle demand.

    Install/run as a self-hosted service

    AI Code Review Agent
    Bito Cloud (fully managed)
    Self-hosted service (run on your own infrastructure)

    Spec-driven development — Automatically generate highly detailed, implementation-ready technical requirement documents (TRDs) and low-level designs (LLDs) with a deep, context-aware understanding of your codebase, services, and design patterns, ensuring architectural integrity and consistency at a granular level.

    • Watch demo videoarrow-up-right

  • Triaging production issues — Easily and quickly find root causes to production issues based on errors/logs/etc.

    • Watch demo videoarrow-up-right

  • Faster onboarding — New engineers or AI agents can quickly understand how a system or component system structure.

  • Enhanced documentation and diagramming — Through its internal understanding of interconnections between modules and APIs.

  • Smarter code reviews — Reviews with system-wide awareness of dependencies and impacts.

  • AI Code Review Agent
    • Use in Git (GitHub, GitLab, Bitbucket)

    • Use in IDE (VS Code, Cursor, Windsurf, JetBrains)

    • Use in CLI (integrates seamlessly with AI coding agents like Cursor, Claude Code, Windsurf, and others.)

    Watch demo videoarrow-up-right
    Bito-hosted
    Self-hosted
    [email protected]envelope
    Cover

    AI Architect

    Cover

    AI Code Review Agent

    Cover

    Account and settings

    Cover

    Billing and plans

    Cover

    Privacy and security

    Cover

    Get support

    Cover

    Changelog

    Cover

    Bito-hosted AI Architect

    Cover

    Self-hosted AI Architect

    Cover

    MCP integration with AI coding agents

    Cover

    AI that understands your code

    Cover

    Chat with AI Code Review Agent

    Cover

    Custom code review rules and guidelines

    Cover

    Code review analytics

    Cover

    Supported programming languages and tools

    Cover

    Available commands

    Cover

    Agent settings

    Cover

    FAQs

    Bito will provide you with MCP server URL and access token
    Start indexing to build knowledge graph of your codebase
  • Get your MCP server URL and access token

  • Automated setup (recommended) The installer will automatically configure AI Architect for all compatible AI coding tools on your system.

    Quick MCP Integration Guide

  • Manual setup

    If you prefer hands-on control over your configuration or encounter issues with automated setup, we provide detailed step-by-step guides for each supported AI coding tool:

    • Guide for Claude Code

    • Guide for Claude Desktop

  • hashtag
    Connect your Git provider

    Select your preferred Git platform and follow the guided setup to install the agent:

    • GitHub

    • GitHub (Self-Managed)

    • GitLab

    Once installed, the agent will be linked to your repositories and ready to assist.

    3

    hashtag
    Review pull requests

    The AI agent will automatically review new pull requests and leave inline comments with suggestions. You can also manually trigger a review by commenting /review on any pull request.

    See full list of available commands

    4

    hashtag
    Chat with the agent

    You can reply to comments posted by the Bito AI agent in a pull request to ask follow-up questions or request clarification. The agent will respond with context-aware answers to help you understand the feedback better.

    Learn more

    5

    hashtag
    Configure agent settings

    To customize your agent, go to Repositoriesarrow-up-right and click the Settings button next to the relevant agent. From there, you can choose the review feedback mode, enable or disable automatic reviews, define custom guidelines to align with your team’s standards, and more.

    Learn more

    Log in to Bito Cloudarrow-up-right
    Complete installation guide →
    Complete installation guide →
    alpha.bito.aiarrow-up-right
    Team Plan
    . For detailed pricing information, visit our
    page.

    Get a 14-day FREE trial of Bito's AI Code Review Agent.arrow-up-right

    hashtag
    Connect Bito to your Git provider

    Select your Git provider from the options below and follow the step-by-step installation guide to seamlessly set up your AI Code Review Agent.

    Bito Cloudarrow-up-right
    AI Code Review Agent
    Pricingarrow-up-right

    1. Before deleting an Agent, ensure that any repositories currently using it are reassigned to another Agent otherwise a warning popup will appear.

    1. Locate the Agent you wish to delete and click the Delete button given in front of it.

    circle-info

    Note: The Default Agent (provided by Bito) cannot be deleted.

    AI Code Review Agent
    Log in to Bito Cloudarrow-up-right
    Code Review Agentsarrow-up-right

    1. If your Bito workspace is connected to your GitHub/GitLab/Bitbucket account, a list of AI Code Review Agent instances configured in your workspace will appear. Locate the instance you wish to duplicate and click the Clone button given in front of it.

    1. An Agent configuration form will open, pre-populated with the input field values. You can edit these values as needed.

    1. Click Select repositories to choose Git repositories for the new Agent.

    1. To enable code review for a specific repository, simply select its corresponding checkbox. You can also enable repositories later, after the Agent has been created. Once done, click Save and continue to save the new Agent configuration.

    1. When you save the configuration, your new Agent instance will be added and available on the Code Review Agentsarrow-up-right page.

    AI Code Review Agent
    Log in to Bito Cloudarrow-up-right
    Code Review Agentsarrow-up-right
    hashtag
    Step 1: Open Cursor IDE

    Launch Cursor IDE on your computer.

    circle-info

    Note: Bito’s IDE plugin supports Cursor version 2.0.77 and later. Please ensure your Cursor installation is updated to this version or newer before installing the plugin.

    hashtag
    Step 2: Access the extensions marketplace

    From the top menu, click View -> Extensions to open the Extensions marketplace.

    circle-info

    You can also use keyboard shortcut to open the Extensions view:

    • Windows/Linux: Press Ctrl+Shift+X

    • Mac: Press Cmd+Shift+X

    hashtag
    Step 3: Search for Bito and install the extension

    1. In the Extensions search bar at the top, type "Bito"

    2. Look for the official Bito extension in the search results. The extension should be published by "Bito".

    3. Click the Install button

    4. Wait for the installation to complete (this usually takes just a few seconds)

    hashtag
    Step 4: Sign in to Bito

    Once installed, you'll need to authenticate:

    1. Click "Sign up or Sign-in"

    2. Bito authentication screen will display.

    3. Log in with your Bito account credentials (or create a new account)

    hashtag
    Step 5: Verify installation

    To confirm Bito is working correctly:

    1. You should see the Bito icon in your Cursor IDE sidebar

    2. Click on it to open the Bito panel

    3. You should now have access to all Bito features

    AI Chat
    Install on Cursor

    Privacy and security in AI Architect

    Your code stays yours — understand how Bito protects your data

    Security and privacy are fundamental to how Bito's AI Architect operates. Bito doesn't store your code and we don't use your code for AI model training.

    This document explains how AI Architect handles your code and data across different deployment modes.

    hashtag
    Code storage: Bito-hosted vs. Self-hosted

    The way AI Architect handles your code depends on your deployment choice:

    hashtag
    Bito-hosted AI Architect

    Your code is not stored on Bito's servers.

    When you use Bito-hosted AI Architect, Bito stores only summaries and indexes of your code — not the code itself. These indexes help AI Architect understand your repository structure, key functionalities, service calls, design patterns, variable naming conventions, and architectural relationships across microservices.

    How it works:

    • AI Architect analyzes your code to build a knowledge graph

    • Only metadata and summaries are stored on Bito's servers (e.g., "this repo contains authentication services," "this module calls these other services")

    • The actual code is never persisted in Bito's cloud

    When code access is needed:

    • If you ask a question that requires viewing actual code, AI Architect authenticates with your Git provider using your credentials

    • It fetches the specific file on-demand

    • Extracts the necessary information

    hashtag
    Code caching

    For performance optimization, Bito temporarily caches individual code files for up to 10 minutes during analysis. You have full control over this behavior — you can configure the cache duration or disable caching entirely through your settings.

    hashtag
    Self-hosted AI Architect

    Your code remains entirely in your data center.

    When you deploy AI Architect on-premises in your own infrastructure, all code and indexes are stored locally. Bito receives no code or code-related information. We only receive anonymous metadata about usage to confirm the product is working properly — no details about what your code does or contains.

    hashtag
    Performance considerations

    Bito-hosted AI Architect adds a few seconds to requests that require actual code access because the code must be fetched on-demand from your Git provider. This slight latency is the trade-off for keeping your code off Bito's servers. In practice, this difference is not material to user experience.

    hashtag
    Code security and encryption

    • All requests to and from AI Architect are transmitted over HTTPS and fully encrypted

    • Your Git credentials are used only to authenticate and fetch code when needed

    • Code accessed during analysis is handled securely and not logged or stored beyond the temporary cache window

    hashtag
    No AI model training

    Your code is never used for AI model training. Bito doesn't train on, learn from, or retain any of your code snippets or queries for model improvement purposes.

    hashtag
    Privacy and third parties

    Bito uses leading AI providers (such as Anthropic, OpenAI, etc.) via their APIs to power AI Architect features. None of your code or AI requests are stored by these partners. All AI providers we work with maintain commitments to not use API data for model training or retain user data beyond the immediate request processing.

    hashtag
    Metadata and usage analytics

    To ensure AI Architect is working correctly and to improve the product, Bito collects:

    • Anonymous usage metrics

    • Feature usage statistics

    • Error logs (without code content)

    This information helps us understand how AI Architect is being used and identify areas for improvement.

    hashtag
    Compliance and certifications

    Bito maintains SOC 2 Type II compliance and follows industry-leading security practices. For detailed information about our security posture and certifications, visit our .

    For our full privacy practices, see our .

    hashtag
    Questions?

    If you have questions about how AI Architect handles your code or data, contact the Bito team at . We're committed to transparency about security and privacy practices.

    Installing on JetBrain IDEs

    It takes less than 2 minutes

    Get up and running with Bito in just a few steps! Bito seamlessly integrates with popular JetBrains IDEs such as IntelliJ IDEA, PyCharm, and WebStorm, providing powerful AI-driven code reviews directly within your editor. Click the button below to quickly install the Bito extension and start optimizing your development workflow with context-aware AI Chat, and more.

    hashtag
    Video guide

    Watch the video below to learn how to download the Bito extension on JetBrains IDEs.

    hashtag
    Step-by-step instructions

    1. In JetBrains IDEs such as IntelliJ, go to File -> Settings to open the Settings dialog, and click Plugins -> Marketplace tab in the settings dialog. Search for Bito.

    2. Click "Install" to install the Bito extension. We recommend you restart the IDE after the installation is complete.

    circle-info

    Starting with Bito version 1.3.4, the extension is only supported on JetBrains versions 2021.2.4 and higher. JetBrains version 2021.1.3 is no longer supported from Bito version 1.3.4 onward.

    3. Bito panel will appear on the right-hand sidebar. Click it to complete the setup process. You will either need to create a new workspace if you are the first in your company to install Bito or join an existing workspace created by a co-worker. See

    circle-info

    The menu to invoke the settings dialog may differ for different IDEs of the JetBrains family. The screenshots highlighted above are for the IntelliJ IDEA. You can access the Bito extension directly from the JetBrains marketplace at .

    How does Bito Understand My Code?

    Sneak Peek into the Inner Workings of Bito

    Bito deploys a Vector Database locally on the user’s machine, bundled as part of the Bito IDE plug-in. This database uses Embeddings (a vector with over 1,000 dimensions) to retrieve text, function names, objects, etc. from the codebase and then transform them into multi-dimensional vector space.

    Then when you give it a function name or ask it a question, that query is converted into a vector and is compared to other vectors nearby. This returns the relevant search results. So, it's a way to perform search not on keywords, but on meaning. Vector Databases are able to do this kind of search very quickly.

    circle-info

    Learn more about how Bito indexes your code so that it can understand it.

    Bito also uses an Agent Selection Framework that acts like an autonomous entity capable of perceiving its environment, making decisions, and taking actions to achieve certain goals. It figures out if it’s necessary to do an embeddings comparison on your codebase, do we need to perform an action against Jira, or do we do something else.

    Finally, Bito utilizes from Open AI, Anthropic, and others that actually provide the answer to the question by leveraging the context provided by the Agent Selection Framework and the embeddings.

    This is what makes us stand out from other AI tools like ChatGPT, GitHub Copilot, etc. that do not understand your entire codebase.

    We’re making significant innovations in our to simplify coding for everyone. To learn more about this head over to .

    Appearance settings

    The IDE customization settings are accessible through the new toolbar dropdown menu titled "Extension Settings".

    hashtag
    Light and Dark Themes

    In Visual Studio Code and JetBrains IDEs, you can choose between a light or dark theme for the Bito panel to match your coding environment preference. For VS Code users, Bito also offers an adaptive theme mode in which the Bito panel and font colors automatically adjust based on your selected VS Code theme, creating a seamless visual experience.

    You can set the desired theme through the Theme dropdown.

    hashtag
    Theme Screenshots

    hashtag
    “Always Light” Theme

    hashtag
    “Always Dark” Theme

    hashtag
    “Light” or “Dark” Theme - Matching IDE

    hashtag
    “Adaptive” Theme

    Theme adapted from “Noctis Lux”:

    Theme adapted from “Solarized Light”:

    Theme adapted from “Tomorrow Night Blue”:

    Theme adapted from “barn-cat”:


    hashtag
    Font Size Control

    Take control of your code readability! Within the Bito extension settings, you can now adjust the font size for a comfortable viewing experience.

    You can set the desired font size through the Font Size text field. However, if you check the Font Size (Match with IDE Font) checkbox, it will override the set font size with the Editor font size.

    CLI vs webhooks service

    From one-time reviews to continuous automated reviews.

    On your machine or in a Private Cloud, you can run the AI Code Review Agent via either CLI or webhooks service. This guide will teach you about the key differences between CLI and webhooks service and when to use each mode.

    hashtag
    Difference Between CLI and webhooks service

    The main difference between CLI and webhooks service lies in their operational approach and purpose. In CLI, the docker container is used for a one-time code review. This mode is ideal for isolated, single-instance analyses where a quick, direct review of the code is needed.

    On the other hand, webhooks service is designed for continuous operation. When set in webhooks service mode, the AI Code Review Agent remains online and active at a specified URL. This continuous operation allows it to respond automatically whenever a pull request is opened in a repository. In this scenario, the git provider notifies the server, triggering the AI Code Review Agent to analyze the pull request and post its review as a comment directly on it.

    hashtag
    When to Use CLI and When to Use webhooks service

    Selecting the appropriate mode for code review with the AI Code Review Agent depends largely on the nature and frequency of your code review needs.

    hashtag
    CLI: Ideal for Specific, One-Time Reviews

    CLI mode is best suited for scenarios requiring immediate, one-time code reviews. It's particularly effective for:

    • Conducting quick assessments of specific pull requests.

    • Performing periodic, scheduled code analyses.

    • Reviewing code in environments with limited or no continuous integration support.

    CLI mode stands out for its simplicity and is perfect for standalone tasks where a single, direct execution of the code review process is all that's needed.

    hashtag
    Webhooks service: For Continuous, Automated Reviews

    Webhooks service, on the other hand, is the go-to choice for continuous code review processes. It excels in:

    • Continuously monitoring all pull requests in a repository.

    • Providing instant feedback in collaborative projects.

    • Seamlessly integrating with CI/CD pipelines for automated reviews.

    Webhooks service is indispensable in active development environments where consistent monitoring and immediate feedback are critical. It automates the code review process, integrating seamlessly into the workflow and eliminating the need for manual initiation of code reviews.

    Installing on Windsurf

    It takes less than 2 minutes

    Get up and running with Bito in just a few steps! Bito seamlessly integrates with Windsurf, providing powerful AI-driven code reviews directly within your editor. Click the button below to quickly install the Bito extension and start optimizing your development workflow with context-aware AI Chat, and more.

    Install on Windsurf

    hashtag
    Installation Steps

    hashtag
    Step 1: Open Windsurf IDE

    Launch Windsurf IDE on your computer.

    circle-info

    Note: Bito’s IDE plugin supports Windsurf version 1.11.0 and later. Please ensure your Windsurf installation is updated to this version or newer before installing the plugin.

    hashtag
    Step 2: Access the extensions marketplace

    From the top menu, click View -> Extensions to open the Extensions marketplace.

    circle-info

    You can also use keyboard shortcut to open the Extensions view:

    • Windows/Linux: Press Ctrl+Shift+X

    hashtag
    Step 3: Search for Bito and install the extension

    1. In the Extensions search bar at the top, type "Bito"

    2. Look for the official Bito extension in the search results. The extension should be published by "Bito"

    3. Click the Install button and wait for the installation to complete (this usually takes just a few seconds).

    hashtag
    Step 4: Sign in to Bito

    Once installed, you'll need to authenticate:

    1. Click "Sign up or Sign-in"

    2. Bito authentication screen will display.

    3. Log in with your Bito account credentials (or create a new account)

    hashtag
    Step 6: Verify installation

    To confirm Bito is working correctly:

    1. You should see the Bito icon in your Windsurf IDE sidebar

    2. Click on it to open the Bito panel

    3. You should now have access to all Bito features

    Upgrading Bito plugin

    How to Update Bito Plugin on VS Code and JetBrains IDEs

    Keeping your Bito plugin up to date ensures you have access to the latest features and improvements. In this article, we will guide you through the steps to update the Bito plugin on both VS Code and JetBrains IDEs. Let's dive in!

    Updating Bito Plugin on VS Code

    1. Open your VS Code IDE

    2. Navigate to the Extensions view by clicking on the square icon in the left sidebar

    3. In the search bar, type "Bito" to locate the Bito plugin

    4. Once you locate the Bito plugin, click on the update button to initiate the update

    Pro Tip 💡: Enable Auto-update for Bito Plugin on VS Code (as shown in the video)

    Updating Bito Plugin on JetBrains IDEs

    1. Open your JetBrains IDE (e.g., IntelliJ IDEA, PyCharm, etc.)

    2. Go to Settings by clicking on "File" in the menu bar (Windows/Linux) or by clicking on "IntelliJ IDEA" in the menu bar (macOS).

    3. In the Settings window, navigate to the "Plugins" section

    AI that Understands Your Code

    Work on your code with AI that knows your code!

    AI Chat in Bito

    Bito AI chat is the most versatile and flexible way to use AI assistance. You can type any technical question to generate the best possible response. Check out these Use cases and examples to understand all you can do with Bito.

    To use AI Chat, type the question in the chat box, and press 'Enter' to send. You can add a new line in the question with 'SHIFT+ ENTER'.

    Bito starts streaming answers within a few seconds, depending on the size and complexity of the prompt.

    circle-info

    Note: Team Plan users receive 50 AI Chat requests per user per day in the Bito IDE extension, while Free Trial users are limited to 20 AI Chat requests per day.

    Bito makes it super easy to use the answer generated by AI, and take a number of actions.

    hashtag
    Copy Answer

    Copy the answer to the clipboard.

    hashtag
    Regenerate Answer

    AI may not give the best answer on the first attempt every time. You can ask Bito AI to regenerate the answer by clicking "Regenerate" button next to the answer.

    hashtag
    Rate Response

    Vote response "Up" or "Down". This feedback Bito improve the prompt handling.

    hashtag
    Modify Last Prompt

    Many of these commands can be executed with keyboard shortcuts documented here:

    Troubleshooting

    Solutions to common issues when using AI Code Reviews in CLI.

    hashtag
    Enable debug output

    hashtag
    Enable verbose logging

    hashtag
    Common issues

    Issue: "API key not found"

    Issue: "Wingman binary not found"

    Re-run the CLI installer to reinstall wingman:

    • macOS/Linux (Terminal):

    • Windows (PowerShell):

    Issue: Slow reviews on large codebases

    • Use --mode essential for faster feedback

    • Focus on specific files: bitoreview review src/changed-file.js

    • Use --type uncommitted to limit scope

    Issue: Too many low-priority issues

    hashtag
    Performance expectations

    Codebase size
    Approximate time

    Install AI Architect (Bito-hosted)

    Deploy AI Architect on Bito's managed infrastructure for instant setup and effortless maintenance.

    This guide walks you through setting up Bito-hosted . You'll connect your Git account (GitHub, GitLab, or Bitbucket) to index your repositories, then use the MCP server credentials to integrate AI Architect with your coding agents. This enables your agents to access codebase-aware context and provide more accurate, relevant answers.

    hashtag
    Bito-hosted vs. Self-hosted AI Architect

    Bito offers two deployment options for AI Architect:

    Example Questions

    What Types of Questions Can be Asked?

    You can try asking any question you may have in mind regarding your codebase. In most cases, Bito will give you an accurate answer. Bito uses AI to determine if you are asking about something in your codebase.

    However, if you want to ask a question about your code no matter what, then you can use our pre-defined keywords such as "my code", "my repo", "my project", "my workspace", etc., in your question.

    The complete list of these keywords is given on our page.

    hashtag

    Chat with AI Code Review Agent

    Ask questions about highlighted issues, request alternative solutions, or seek clarifications on suggested fixes.

    Ask questions directly to the AI Code Review Agent regarding its code review feedback. You can inquire about highlighted issues, request alternative solutions, or seek clarifications on suggested fixes.

    Real-time collaboration with the AI Code Review Agent accelerates your development cycle. By delivering immediate, actionable insights, it eliminates the delays typically experienced with human reviews. Developers can engage directly with the Agent to clarify recommendations on the spot, ensuring that any issues are addressed swiftly and accurately.

    Bito supports over 20 languages—including English, Hindi, Chinese, and Spanish—so you can interact with the AI in the language you’re most comfortable with.

    Integrate the AI Code Review Agent into the CI/CD pipeline

    Automate code reviews in your Continuous Integration/Continuous Deployment (CI/CD) pipeline—compatible with all CI/CD tools, including Jenkins, Argo CD, GitLab CI/CD, and more.

    lets you integrate the into your CI/CD pipeline for automated code reviews. This document provides a step-by-step guide to help you configure and run the script successfully.

    hashtag
    Installation and Configuration Steps

    Share chat session

    Let your friends see what you and Bito are creating together.

    Easily share insights from any session by creating a unique shareable link directly from the Bito extension in VS Code or JetBrains IDEs.

    Whether you need to share AI-generated code suggestions, explanations, or any other chat insights, this feature allows you to create a public link that others can access. The link will remain active for 15 days and can be viewed by anyone with access to the URL, making collaboration and knowledge sharing seamless.

    Additionally, you can quickly share your AI Chat session through a pre-written Tweet or an Email.

    circle-info

    How it Works?

    Bito indexes your code locally using AI

    When you open a project in Visual Studio Code or JetBrains IDEs, Bito lets you enable the of code files from that project’s folder. Basically, this indexing mechanism leverages our new that enables Bito to understand your entire codebase and answer any questions regarding it.

    The index is stored locally on your system to provide better performance while maintaining the security/privacy of your private code.

    circle-info

    It takes 12 minutes per each 10MB of code to understand your repo, as the index is being built locally.

    FAQs

    Answers to popular questions about the AI Code Review Agent.

    hashtag
    How do I whitelist Bito's gateway IP address for my on-premise Git platform?

    To ensure the operates smoothly with your GitHub (Self-Managed), GitLab (Self-Managed), or Bitbucket (Self-Managed), please whitelist all of Bito's gateway IP addresses in your firewall to allow incoming traffic from Bito. This will enable Bito to access your self-hosted repository.

    List of IP addresses to whitelist:

    Available Keywords

    Keywords to invoke AI that understands your code

    Here is the list of keywords in different languages to ask questions regarding your entire codebase. Use any of these keywords in your prompts inside Bito chatbox.

    hashtag
    English:

    • my code

    Configuration

    Manage Bito CLI settings

    hashtag
    bito config [flags]

    • run bito config -l or bito config --list to list all config variables and values.

    Overview

    Bito CLI (Command Line Interface)

    is an innovative tool that harnesses the power of functionality to automate software development workflows. It can automate repetitive tasks like software documentation, test case generation, pull request review, release notes generation, writing commit message or pull request description, and much more.

    For example, you can run a command like bito –p writedocprompt.txt -f mycode.js for non-interactive mode in Bito CLI (where writedocprompt.txt will contain your prompt text such as Explain the code below in brief and mycode.js will contain the actual code on which the action is to be performed).

    Bito CLI

    Command Line Interface (Powered by Bito AI Chat) to Automate Your Tasks

    curl -fsSL https://aiarchitect.bito.ai/install.sh | bash
    bitoreview review --debug
    # or
    bitoreview review -d
    bitoreview review --verbose
    # or
    bitoreview review -v
    Integrating with batch processing scripts for ad-hoc analysis.
  • Using in educational settings to demonstrate code review practices.

  • Experimenting with different code review configurations.

  • Reviewing code on local setups or for personal projects.

  • Performing a final check before pushing code to a repository.

  • Performing automated code quality checks in team environments.
  • Conducting real-time security scans on new pull requests.

  • Ensuring adherence to coding standards in every pull request.

  • Streamlining the code review process in large-scale projects.

  • Maintaining consistency in code review across multiple projects.

  • Enhancing workflows in remote or distributed development teams.

  • Offering prompt feedback in agile development settings.

  • Mac:
    Press
    Cmd+Shift+X
    Try asking Bito a simple question to test the connection

    my repo

  • my project

  • my workspace

  • hashtag
    Chinese:

    • 我的代码

    • 我的仓库

    • 我的代码库

    • 我的项目

    • 我的文件夹

    hashtag
    Chinese Traditional:

    • 我的程式碼

    • 我的倉庫

    • 我的項目

    • 我的工作區

    hashtag
    Spanish:

    • Mi código

    • Mi repo

    • Mi proyecto

    • Mi espacio de trabajo

    hashtag
    Japanese:

    • 私のコード

    • 私のリポ

    • 私のプロジェクト

    • 私のワークスペース

    hashtag
    Portuguese:

    • Meu código

    • Meu repo

    • Meu projeto

    • Meu espaço de trabalho

    hashtag
    Polish

    • Mój obszar roboczy

    • moje miejsce pracy

    • mój obszar roboczy

    • moj kod

    • mój kod

    • moim kodzie

    • moje repo

    • moje repozytorium

    • moim repo

    • moj projekt

    • mój projekt

    • moim projekcie

    Guide for GitHub

    Guide for GitHub (Self-Managed)

    Guide for GitLab

    Guide for GitLab (Self-Managed)

    Guide for Bitbucket

    Guide for Bitbucket (Self-Managed)

    Guide for Claude.ai (Web)
    Guide for Cursor
    Guide for Windsurf
    Guide for GitHub Copilot (VS Code)
    Guide for Junie (JetBrains)
    Guide for JetBrains AI Assistant
    Guide for ChatGPT (Web & Desktop)
    GitLab (Self-Managed)
    Bitbucket
    Bitbucket (Self-Managed)
    Passes it back to you through the MCP server
  • The code is not retained after the request

  • Trust Centerarrow-up-right
    Privacy Policyarrow-up-right
    [email protected]envelope
    Large Language Models (LLMs)
    AI Stack
    Bito’s AI Stack documentation

    AI that Understands Your Code

    Bito indexes your code locally using AI

    Keywords to invoke AI that understands your code

    What type of questions can be asked?

    Sneak peek into the inner workings of Bito

    AI that understands your code in VS Code

    AI that understands your code in JetBrains IDEs (e.g., PyCharm)

    Exclude unnecessary files and folders from repo to index faster!

    Answers to popular questions

    Overview
    How it Works?
    Available Keywords
    Example Questions
    How does Bito Understand My Code?
    Using in Visual Studio Code
    Using in JetBrains IDEs
    Managing Index Size
    FAQs
    Here are some popular use cases (with example questions):

    hashtag
    Code Explanation

    • What a particular code file does

      • In my code what does code in sendgrid/sendemail.sh do?

    • What a particular function in my code does

      • In my repo explain what function message_tokens do

    hashtag
    Code Translation

    • In my project rewrite the code of signup.php file in nodejs

    hashtag
    Code Refactoring

    • In my workspace suggest code refactoring for api.py and mention all other files that need to be updated accordingly

    hashtag
    Fix Bugs

    • In my code find runtime error possibilities in script.js

    • Find logical errors in scraper.py in my code

    hashtag
    Detect Code Smells

    • In my code detect code smells in /app/cart.php and give solution

    hashtag
    Generate Documentation

    • Generate documentation for search.ts in my workspace in markdown format

    hashtag
    Generate Unit tests

    • In my code write unit tests for index.php

    • In my code generate test code for code coverage of cache.c

    hashtag
    Summarize Recent Code Changes

    • summarize recent code changes in my code

    hashtag
    Code Search using natural language

    • Any function to compute tokens in my project?

    • Any code or script to send emails in my workspace?

    • In my repo list all the line numbers where $alexa array is used in index.php.

    hashtag
    Give details of making modifications

    • In my code list all the files and code changes needed to add column desc in table raw_data in dailyReport DB.

    Available Keywords

    18.188.201.104

  • 3.23.173.30

  • 18.216.64.170

  • The agent response can come from any of these IPs.

    hashtag
    How can I prevent the AI Code Review Agent from stopping due to token expiry?

    You should set a longer expiration period for your GitHub Personal Access Token (Classic), GitLab Personal Access Token, or Bitbucket Personal Access Token. We recommend setting the expiration to at least one year. This prevents the token from expiring early and avoids disruptions in the AI Code Review Agent's functionality.

    Additionally, we highly recommend updating the token before expiry to maintain seamless integration and code review processes.

    For more details on how to create tokens, follow these guides:

    • GitHub Personal Access Token (Classic): View Guidearrow-up-right

    • GitLab Personal Access Token: View Guidearrow-up-right

    • Bitbucket Personal Access Token: View Guidearrow-up-right

    hashtag
    Why does Bito need access to my Git account?

    Bito requires certain permissions to analyze pull requests and provide AI-powered code reviews. It never stores your code and only accesses the necessary data to deliver review insights.

    hashtag
    What permissions does Bito need?

    Bito requires:

    1. Read access to code and metadata: To analyze PRs and suggest improvements

    2. Read and write access to issues and pull requests: To post AI-generated review comments

    3. Read access to organization members: To provide better review context

    hashtag
    I don’t have admin permissions. Can I still use Bito?

    If you don’t have admin access, you’ll need your administrator to install Bito on your organization’s Git account. Once installed, you can use it for PR reviews on allowed repositories. GitHub also sends a notification to the organization owner to request the organization owner to install the app.

    hashtag
    Does Bito store my code?

    No, Bito does not store or train models on your code. It only analyzes pull request data in real-time and provides suggestions directly within the PR.

    hashtag
    Can I choose which repositories Bito has access to?

    Yes, after installation, you can select specific repositories instead of granting access to all. You can also manage repository access later through our web dashboard.

    hashtag
    What happens after I install the Bito App?

    Once installed, you’ll be redirected to Bito, where you can:

    1. Select repositories for AI-powered reviews

    2. Customize review settings to fit your workflow

    3. Open a pull request to start receiving AI-driven suggestions

    hashtag
    Where can I get help if I have issues installing Bito?

    Contact [email protected]envelope for any assistance.

    AI Code Review Agent
    Theme adapted from “Noctis Lux”
    Theme adapted from “Solarized Light”
    Theme adapted from “Tomorrow Night Blue”
    Theme adapted from “barn-cat”
    Keyboard shortcuts

    Small (<5 files)

    30-60 seconds

    Medium (5-20 files)

    1-3 minutes

    Large (20+ files)

    3-8 minutes

    run bito config -e or bito config --edit to open the config file in default editor.

    hashtag
    Sample Configuration

    hashtag
    What is an Access Key and How to Get it?

    Access Key is an alternate authentication mechanism to Email & OTP based authentication. You can use an Access Key in Bito CLI to access various functionalities such as Bito AI Chat. Here’s a guide on how to create an Access Key. Basically, after creating the Access Key, you have to use it in the config file mentioned above. For example, access_key: “YOUR_ACCESS_KEY_HERE”

    Access Key can be persisted in Bito CLI by adding it in the config file using bito config -e. Such persisted Access Key can be over-ridden by running bito -k <access-key> or bito --key <access-key> for the transient session (sessions that last only for a short time).

    hashtag
    Preferred AI Model Type

    By default AI Model Type is set to ADVANCED and it can be overridden by running bito -m <BASIC/ADVANCED>. Model type is used for AI query in the current session. Model type can be set to BASIC or ADVANCED, which is case insensitive.

    "ADVANCED" refers to AI models like GPT-4o, Claude Sonnet 3.5, and best in class AI models, while "BASIC" refers to AI models like GPT-4o mini and similar models.

    When using Basic AI models, your prompts and the chat's memory are limited to 40,000 characters (about 18 single-spaced pages). However, with Advanced AI models, your prompts and the chat memory can go up to 240,000 characters (about 110 single-spaced pages). This means that Advanced models can process your entire code files, leading to more accurate answers.

    If you are seeking the best results for complex tasks, then choose Advanced AI models.

    circle-info

    Access to Advanced AI models is only available in Bito's Team Planarrow-up-right. However, Basic AI models can be used by both free and paid users.

    To see how many Advanced AI requests you have left, please visit the Requests Usagearrow-up-right page. On this page, you can also set hard and soft limitsarrow-up-right to control usage of Advanced AI model requests for your workspace and avoid unexpected expenses.

    Also note that even if you have set preferred_ai_model: ADVANCED in Bito CLI config but your Advanced AI model requests quota is finished (or your self-imposed hard limitarrow-up-right is reached) then Bito CLI will start using Basic AI models instead of Advanced AI models.

    # Set your API key
    bitoreview config set-api-key YOUR_KEY
    
    # Verify it's set
    bitoreview config show-api-key
    curl -fsSL https://bitoreview.bito.ai/install.sh | bash
    irm https://bitoreview.bito.ai/install.ps1 | iex
    # Filter to high severity only
    bitoreview review --severity high
    
    # Or use essential mode
    bitoreview review --mode essential
    bito:
     access_key: ""
     email: [email protected]
     
     preferred_ai_model: ADVANCED
    settings:
     auto_update: true
     max_context_entries: 20

    Switch to the "Installed" tab to view the list of installed plugins

  • Locate the Bito plugin in the list and click on the update button to initiate the update

  • Bito-hosted (Fully managed by Bito — no infrastructure setup required)

  • Self-hosted (Run AI Architect on your own infrastructure for maximum control)

  • Bito-hosted
    Self-hosted

    Infrastructure

    Bito manages indexes and infrastructure on our secure servers

    You host AI Architect in your own environment

    Code storage

    We don't store your code after indexing — only repository metadata is retained. Code is fetched at runtime as needed.

    Full control over your data and indexes

    Maintenance

    Fully managed by Bito

    Requires infrastructure setup and maintenance

    For information on self-hosted deployment, visit the self-hosted installation guide.

    hashtag
    Installation steps

    1

    hashtag
    Connect your Git provider

    Log in to Bito Cloudarrow-up-right and select a workspace to get started.

    Use the Bito UI to connect your Git provider account (GitHub, GitLab, or Bitbucket). This enables Bito to clone your repositories and fetch code at runtime when needed.

    2

    hashtag
    Submit repositories for indexing

    Contact the Bito team at with a list of repositories you want to index. Include the repository names and paths.

    3

    hashtag
    Bito creates your indexes

    Bito will:

    • Clone your repositories

    4

    hashtag
    Receive your MCP connection details

    Once your indexes are ready, Bito will provide you with:

    hashtag
    Code retrieval at runtime

    Bito-hosted AI Architect includes smart code retrieval (getCode MCP tool) that works behind the scenes. When you ask questions about specific code — like "show me the authenticate method in the Auth class" — AI Architect automatically fetches the relevant code at runtime using your Git credentials.

    This means you get detailed, accurate code references without storing any code on Bito's servers. Code is fetched on-demand and never persisted.

    hashtag
    Need help?

    If you have questions about the setup process or need to modify your indexed repositories, reach out to the Bito team at [email protected]envelope. We're here to help you get the most out of AI Architect.

    AI Architect
    hashtag
    How to chat?

    To start a conversation, type your question directly as a reply to the Agent’s code review comment.

    The AI Code Review Agent will analyze your comment and determine if it’s a valid and relevant question.

    • If the agent decides it’s a valid question, it will respond with helpful insights.

    • If the agent determines it’s unclear, off-topic, or not related to its feedback, it will not respond.

    To help the agent recognize your question faster, you can also tag your comment with @bitoagent or @askbito. Tagging informs the Agent that your message is intended as a question. However, tagging does not guarantee a reply. The agent will still analyze your comment and decide whether it is a valid question worth responding to.

    Bito usually responds within about 10 seconds.

    • On GitHub and Bitbucket, you may need to manually refresh the page to see the response.

    • On GitLab, updates happen automatically.

    circle-info

    Note: The AI Code Review Agent will only respond to questions posted as a reply to its own comments. It will not reply to questions added on threads that it didn’t start.

    hashtag
    What you can ask about

    When chatting with the AI Code Review Agent, you can ask questions to better understand or improve the code feedback it provided. Here are examples of what you can ask:

    • Clarifications about a highlighted issue Ask the AI to explain why it flagged a certain line of code or why something might cause a problem.

    • Request for alternative solutions Request different ways to fix or improve the code beyond what was originally suggested.

    • Deeper explanations If you want to understand the technical reasoning behind a suggestion (e.g., security concerns, performance impacts, best practices), you can ask for more detailed explanations.

    • Request for examples Ask the AI to provide an example snippet showing the corrected or improved code.

    • Trade-off discussions Ask the AI about pros and cons of different approaches it may have suggested (e.g., performance vs. readability).

    • Best practices guidance Request advice on best practices related to the specific code snippet — such as naming conventions, error handling, optimization tips, or design patterns.

    • Language-specific advice If you’re working in a particular language (e.g., JavaScript, Python, Java), you can ask for language-specific guidance related to the comment.

    • Request for more context If the suggestion feels too "short" or "surface level," you can ask the AI to explain more about the broader coding or architectural concept behind its feedback.

    • Security and safety questions If a suggestion touches on security (like input validation, authentication, or encryption), you can ask for further security-related advice.

    • Testing and validation Ask the AI if it recommends writing any tests based on its code suggestions and what those tests might look like.

    circle-info

    Tip: Feel free to ask your question in your preferred language! Bito supports over 20 languages, including English, Hindi, Chinese, and Spanish.

    hashtag
    What you cannot ask about

    The AI can only answer questions related to its own code review comments.

    • You cannot ask general questions about the repository or unrelated topics.

    • You cannot start a new thread independently — your question must be a reply to a comment made by Bito’s AI Code Review Agent.

    If your comment is not linked to a Bito review comment, the AI will not respond.

    Select the appropriate Git provider guide from this link based on your Git provider, and follow the step-by-step instructions to install the AI Code Review Agent using Bito Cloud. Be sure to review the prerequisites and the installation/configuration steps provided in the documentation.
  • Download the bito-action-script folder from GitHubarrow-up-right, which includes a shell script (bito-actions.sh) and a configuration file (bito_action.properties).

  • You can integrate the AI Code Review Agent into your CI/CD pipeline in two ways, depending on your preference:

    • Option 1: Using the bito_action.properties File

      • Configure the following properties in the bito_action.properties file located in the downloaded bito-action-script folder.

    Property Name
    Description

    agent_instance_url

    The URL of the Agent instance provided after configuring the AI Code Review Agent with Bito Cloud.

    agent_instance_secret

    The secret key for the Agent instance obtained after configuring the AI Code Review Agent with Bito Cloud.

    pr_url

    URL of your pull request on GitLab, GitHub, or BitBucket.

    • Run the following command:

      • ./bito_actions.sh bito_action.properties

      • Note: When using the properties file, make sure to provide all the three parameters in .properties file

    • hashtag
      Option 2: Using Runtime Values

      • Provide all necessary values directly on the command line:

        • ./bito_actions.sh agent_instance_url=<agent_instance_url> agent_instance_secret=<secret> pr_url=<pr_url>

        • Replace <agent_instance_url>, <secret>, and <pr_url> with your specific values.

      • Note: You can also override the values given in the .properties file or provide values that are not included in the file. For example, you can configure agent_instance_url and agent_instance_secret in the bito_action.properties file, and only pass pr_url on the command line during runtime.

        • ./bito_actions.sh bito_action.properties pr_url=<pr_url>

    1. Incorporate the AI Code Review Agent into your CI/CD pipeline by adding the appropriate commands to your build or deployment scripts. This integration will automatically trigger code reviews as part of the pipeline, enhancing your development workflow by enforcing code quality checks with every change.

    Bito Cloudarrow-up-right
    AI Code Review Agent
    Note:
    • The link will expire in 15 days.

    • The session link will be publicly accessible by anyone with the link.

    • Recipients can access the chat session in any web browser by using the unique URL.

    Let's see how it is done:

    1. Open Bito in Visual Studio Code or any JetBrains IDE.

    2. Start a conversation in Bito’s AI Chat user interface.

    3. Locate the share button on the top right of the Bito extension side-panel.

    4. Click the share button to open a menu with options, including X (Twitter), Email, and Link.

    5. Share on X (Twitter):

      1. Click on X (Twitter) from the menu, and a dialogue window will appear, asking whether you want to open the external site.

      2. Simply click "Open" to proceed.

    6. Share Through Email:

      1. Click on Email from the menu, and you will be redirected to your email application.

      2. Select your email account if needed.

    7. Share the Link:

      1. Click on Link from the menu.

      2. A confirmation popup will appear. Click Share session to generate a unique URL for your chat session, which will automatically be copied to your clipboard for easy sharing.

    AI Chat
    hashtag
    How to Ask Questions?

    Once indexing is complete, you can ask any question in the Bito chatbox. Bito uses AI to determine if you are asking about something in your codebase. If Bito is confident, it grabs the relevant parts of your code from our index and feeds them to the Large Language Models (LLMs) for accurate answers. But if it's unsure, Bito will ask you to confirm before proceeding.

    In case you ask a general question (not related to your codebase), then Bito will directly send your request to our LLM without first looking for the appropriate local context.

    However, if you want to ask a question about your code no matter what, then you can use specific keywords such as "my code", "my repo", "my project", "my workspace", etc., in your question.

    The complete list of these keywords is given on our Available Keywords page.

    Once Bito sees any input containing these keywords, it will use the index to identify relevant portions of code or content in your folder and use it for processing your question, query, or task.

    hashtag
    Security of your code

    As usual, security is top of mind at Bito, especially when it comes to your code. A fundamental approach we have taken is to keep all code on your machine, and not store any code, code snippets, indexes, or embedding vectors on Bito’s servers or our API partners. All code remains on your machine, Bito does not store it. In addition, none of your code is used for AI model training.

    Learn more about Bito’s Privacy and Security Practices.

    indexing
    AI Stack
    circle-info

    Here is the complete list of available commands for Bito CLI.

    Download Bito CLI from GitHub:

    With support for 50+ programming languages (Python, JavaScript, SQL, etc.) and 50+ spoken languages (English, German, Chinese, etc.), Bito CLI is versatile and adaptable to different project needs. Furthermore, it's designed to be compatible across multiple operating systems, including Windows, Mac, and Linux, ensuring a wide range of usability.

    You can either use "ADVANCED" AI models like GPT-4o, Claude Sonnet 3.5, and best in class AI models, or "BASIC" AI models like GPT-4o mini and similar models inside Bito CLI.

    When using Basic AI models, your prompts and the chat's memory are limited to 40,000 characters (about 18 single-spaced pages). However, with Advanced AI models, your prompts and the chat memory can go up to 240,000 characters (about 110 single-spaced pages). This means that Advanced models can process your entire code files, leading to more accurate answers.

    If you are seeking the best results for complex tasks, then choose Advanced AI models.

    circle-info

    Access to Advanced AI models is only available in Bito's Team Planarrow-up-right. However, Basic AI models can be used by both free and paid users.

    Bito CLI is an invaluable asset for developers looking to increase efficiency and productivity in their workflows. It allows developers to save time and focus on more complex and creative aspects of their work. Additionally, Bito CLI plays a crucial role in supporting continuous integration and deployment (CI/CD) processes. Explore some intelligent AI automationsarrow-up-right we've created using Bito CLI, which you can implement in your projects right now. These automations showcase the powerful capabilities of Bito CLI.

    To get started, check out our guide on how to use Bito CLI, ensuring you make the most out of it.

    Bito CLI (Command Line Interface)arrow-up-right
    Bito AI chat

    Install on JetBrains

    Managing workspace members
    https://plugins.jetbrains.com/plugin/18289-bitoarrow-up-right
    Settings in IntelliJ IDE
    Bito in IntelliJ right-hand side bar
    Overview

    Bito CLI (Command Line Interface)

    Install or uninstall

    Learn how to setup Bito CLI on your device (Mac, Linux, and Windows)

    Configuration

    Manage Bito CLI settings

    How to use?

    Learn how to work with Bito CLI (including examples)

    Available commands

    Learn about all the powerful commands to use Bito CLI

    FAQs

    Answers to popular questions

    Available MCP tools

    Access deep repository intelligence and codebase insights through AI Architect's MCP server

    AI Architect's MCP server provides a comprehensive suite of tools for exploring, analyzing, and understanding your organization's codebase. These tools enable AI coding assistants to access deep repository intelligence, architectural insights, and code-level information across all your Git repositories.

    Below is the complete list of MCP tools provided by AI Architect:

    Tool name
    Description

    getCapabilities

    Discover what repository intelligence and analysis capabilities this MCP server provides.

    Returns comprehensive information about available repository data, dependency analysis features, architectural insights, and clustering patterns for your organization's Git repositories.

    Use this to understand what repository information is available through this specialized service.

    listRepositories

    Browse all Git repositories in your organization. Returns comprehensive repository catalog with names, descriptions, and resource URIs.

    Use this to discover available repositories, understand the organization's project landscape, identify microservices and components, or get an overview of all systems.

    Each entry includes a resource URI for accessing detailed repository information.

    Instant access to pre-indexed organizational repository data.

    Guide for Claude.ai (Web)

    Integrate Claude.ai with AI Architect for more accurate, codebase-aware AI assistance.

    Use Bito's AI Architect with Claude.ai (Web) to enhance your AI-powered coding experience.

    Once connected via MCP (Model Context Protocol), Claude.ai can leverage AI Architect's deep contextual understanding of your project, enabling more accurate code suggestions, explanations, and code insights.

    hashtag
    Prerequisites

    1. Follow the . Upon successful setup, you will receive a Bito MCP URL and Bito MCP Access Token that you need to enter in your coding agent.

      • Note: The Bito MCP URL must be publicly accessible. Localhost or private network URLs (for example, http://localhost or internal IP addresses) are not supported and will not work.

    2. . You will need to copy/paste the content from this file later when configuring AI Architect.

      • Note: This file contains best practices, usage instructions, and prompting guidelines for the Bito AI Architect MCP server. The setup will work without this file, but including it helps AI tools interact more effectively with the Bito AI Architect MCP server.

    3. A paid Claude.ai subscription - MCP integrations require one of the following:

      • Claude Pro

      • Claude Max

    circle-info

    Note: Free tier accounts do not have access to MCP Integrations.

    hashtag
    OAuth authentication

    Claude.ai uses OAuth 2.1 with PKCE for secure authentication, so you don't need to manually manage access tokens. Your email will be collected during the OAuth consent flow for tracking purposes.

    How OAuth authentication works:

    1. You add the MCP server URL in Claude.ai Integrations settings

    2. Claude.ai initiates an OAuth flow

    3. Your browser opens a consent page hosted by Bito

    Benefits:

    • No manual token management

    • Secure browser-based authentication

    • Automatic token refresh

    • Email collected during consent (no separate header needed)

    OAuth Callback URL: https://claude.ai/api/mcp/auth_callback

    hashtag
    Set up AI Architect

    1

    hashtag
    Open Claude.ai integrations

    1. Go to and sign in with your paid account

    hashtag
    Troubleshooting Claude.ai

    hashtag
    "Integrations" option not visible:

    • Verify you have a paid Claude subscription (Pro, Max, Team, or Enterprise)

    • Free tier accounts do not have MCP access

    • Contact Anthropic support if you have a paid plan but don't see the option

    hashtag
    OAuth authorization fails:

    • Ensure pop-ups are allowed for claude.ai

    • Check that your Workspace ID is correct

    • Verify your organization has OAuth enabled for the MCP server

    hashtag
    Connection shows "Disconnected":

    • Click the server entry and select "Reconnect"

    • OAuth tokens may have expired - re-authorize when prompted

    • Check if your Bito workspace is still active

    hashtag
    Tools not appearing in conversation:

    • Ensure the MCP server shows "Connected" status

    • Try starting a fresh conversation

    • Some tools may require specific prompts to activate

    Overview

    On-demand, context-aware AI code reviews for GitHub, GitLab, and Bitbucket.

    circle-info

    Get a 14-day FREE trial of Bito's AI Code Review Agent.arrow-up-right

    Bito’s AI Code Review Agentarrow-up-right is the first agent built with Bito’s AI Agent framework and engine. It is an automated AI assistant (powered by Anthropic’s Claude Sonnet 3.7) that will review your team’s code; it spots bugs, issues, code smells, and security vulnerabilities in Pull/Merge Requests (PR/MR) and provides high-quality suggestions to fix them.

    It seamlessly integrates with Git providers such as GitHub, GitLab, and Bitbucket, automatically posting recommendations directly as comments within the corresponding Pull Request. It includes real-time recommendations from Static Code Analysis and OSS vulnerability tools such as fbinfer, Dependency-Check, etc. and can include high severity suggestions from other 3rd party tools you use such as Snyk.

    circle-info

    We also support GitHub (Self-Managed) and GitLab (Self-Managed).

    The AI Code Review Agent acts as a set of specialized engineers each analyzing different aspects of your PR. They analyze aspects such as Performance, Code Structure, Security, Optimization, and Scalability. By combining and filtering the results, the Agent can provide you with much more detailed and insightful code reviews, bringing you a better quality code review and helping you save time.

    The AI Code Review Agent helps engineering teams merge code faster while also keeping the code clean and up to standard, making sure it runs smoothly and follows best practices.

    It ensures a secure and confidential experience without compromising on reliability. Bito neither reads nor stores your code, and none of your code is used for AI model training. Learn more about our .

    By accessing Bito's feature, the AI Code Review Agent can analyze relevant context from your entire repository, providing better context-aware analysis and suggestions. This tailored approach ensures a more personalized and contextually relevant code review experience.

    To comprehend your code and its dependencies, we use Symbol Indexing, Abstract Syntax Trees (AST), and Embeddings. Each step feeds into the next, starting from locating specific code snippets with Symbol Indexing, getting their structural context with AST parsing, and then leveraging embedding vectors for broader semantic insights. This approach ensures a detailed understanding of the code's functionality and its dependencies. For more information, see

    The AI Code Review Agent is built using Bito Dev Agents, an open framework and engine to build custom AI Agents for software developers that understands code, can connect to your organization’s data and tools, and can be discovered and shared via a global registry.

    hashtag
    Why use an AI Agent for code review?

    In many organizations, senior developers spend approximately half of their time reviewing code changes in PRs to find potential issues. The AI Code Review Agent can help save this valuable time.

    AI Code Review Agent speeds up PR merges by 89%, reduces regressions by 34%, and delivers 87% human-grade feedback.

    However, it's important to remember that the AI Code Review Agent is designed to assist, not replace, senior software engineers. It takes care of many of the more mundane issues involved in code review, so senior engineers can focus on the business logic and how new development is aligned with your organization’s business goals.

    hashtag
    Pricing details

    The Free Plan offers AI-generated pull request summaries to provide a quick overview of changes. For advanced features like line-level code suggestions, consider upgrading to the Team Plan. For detailed pricing information, visit our page.

    hashtag
    Learn more

    Request changes comments

    Block merges until code issues are fixed.

    Bito’s Request changes comments feature helps enforce code quality by blocking merges until all AI-generated review comments are resolved—fully supported in GitHub, GitLab, and Bitbucket.

    When enabled, Bito identifies actionable issues in pull requests and posts them as formal “Request changes” review comments. If your repository uses branch protection rules that require all review conversations to be resolved before merging, Bito’s flagged comments will automatically block the pull request until addressed.

    This ensures developers don’t accidentally merge incomplete or unreviewed code.

    hashtag
    How it works

    hashtag
    1. Enable comment resolution rules in your Git provider

    hashtag
    GitHub:

    • Go to your repository → Settings → Branches

    • Create or edit a branch protection rule (e.g., for main)

    • Enable:

    hashtag
    GitLab:

    • Go to your project → Settings → Merge requests

    • Under Merge checks, enable:

      • ✅ All threads must be resolved

    hashtag
    Bitbucket:

    • Go to your repository → Repository settings → Branch restrictions

    • Click Add a branch restriction button.

    • Under Select branches, define the target branches where this restriction should apply. Pull requests merging into these branches will be blocked until all "Request changes" comments are resolved. You can choose one of two options:

    circle-info

    Note: Request change comments usually have to be resolved by the person who posted them. Since here these comments are posted by Bito, the user must comment /resolve in the pull request to resolve them.

    hashtag
    2. Turn on “Request changes comments” in Bito

    • Go to Repositories in the Bito dashboard.

    • Click on Settings for your desired AI Code Review Agent instance.

    • Enable the toggle: “Request changes comments”

    When this is on, Bito will flag actionable AI feedback as formal review comments requiring resolution. Informational or minor suggestions will remain as regular comments.

    hashtag
    3. What happens in a pull request

    • Bito runs an AI code review on your pull request or merge request.

    • Actionable issues are posted as change requests.

    • Your Git provider treats these comments according to your configured merge rules.

    hashtag
    Example workflow

    1. Developer opens a pull request or merge request.

    2. Bito reviews the code and posts a “request change” comment on a problematic line.

    3. The Git provider blocks the merge due to unresolved comments or threads.

    hashtag
    Why use this feature?

    • Enforces follow-up on critical AI-detected issues.

    • Works natively with GitHub, GitLab, and Bitbucket workflows.

    • Ensures only reviewed and clean code gets merged.

    Agent settings

    Learn how to customize the AI Code Review Agent.

    Bito's AI Code Review Agent supports different configuration methods depending on the deployment environment:

    1. Bito-hosted – The agent runs on Bito's infrastructure and is configured through the Bito web UIarrow-up-right.

    2. Self-hosted – The agent runs on user-managed infrastructure and is configured by editing the bito-cra.properties file.

    The sections below provide configuration guidance for each setup.

    hashtag
    Bito-hosted agent configuration

    In Bito-hosted AI Code Review Agent, you can configure the agent through the .

    To customize an existing agent, open the page and click the Settings button next to the Agent instance to be modified.

    The agent settings page allows configuration of options such as:

    • Agent name – Define a unique name for easy identification.

    • Review options – Choose the review mode (Essential or Comprehensive), set feedback language, and enable features like auto-review, incremental review, summaries, and change walkthroughs.

    • Custom guidelines – Create and apply custom code review rules tailored to your team’s standards directly from the dashboard.

    These settings tailor the agent’s behavior to match team workflows and project needs. For detailed guidance, see .

    hashtag
    Self-hosted agent configuration

    In self-hosted deployments, configuration is managed by editing the . This file defines how the agent operates and connects to required services.

    Key configuration options include:

    • Mode

      • mode = cli: Processes a single pull request using a manual URL input.

      • mode = server: Runs as a webhook service and listens for incoming events from Git platforms.

    Each property is documented in detail on the page.

    AI Code Review Agent (with AI Architect vs without AI Architect)

    From single-repo reviews to system-wide insights

    The AI Code Review Agent becomes significantly more powerful when paired with AI Architect.

    Below is a clear explanation of how the agent behaves in each setup and why AI Architect unlocks much deeper, system-level insights.

    hashtag
    AI Code Review Agent without AI Architect

    The standard AI Code Review Agent analyzes code at the repository level.

    It creates a within-repo knowledge graph by building:

    • Abstract Syntax Trees (ASTs)

    • Symbol indexes

    • Local dependency relationships

    This allows it to perform strong, context-aware code reviews within a single repository, including:

    • Identifying issues in the diff

    • Understanding dependencies inside the repo

    • Checking for consistency and correctness within that project

    However, the agent’s visibility stops at the repository boundary. It cannot detect effects on other services or codebases.

    hashtag
    AI Code Review Agent powered by AI Architect

    When AI Architect is enabled, the AI Code Review Agent gains a complete view of your entire engineering ecosystem.

    AI Architect builds a cross-repository knowledge graph that maps:

    • All services

    • Shared libraries

    • Modules and components

    • Inter-service dependencies

    With this system-level understanding, the agent can perform much deeper analysis.

    hashtag
    Key capabilities unlocked by AI Architect

    1. Cross-repository awareness

    The agent understands how code in one repo interacts with code in others — crucial for microservices and distributed systems.

    2. Cross-repo impact analysis

    During a pull request review, the agent can identify:

    • What breaks downstream if you change an interface

    • Which services call the function you updated

    • Which teams or repos depend on your changes

    3. Architecture-level checks

    The agent evaluates your changes not just for correctness, but for their alignment with the overall system design.

    4. Early problem detection across the entire codebase

    Ripple effects, breaking changes, or dependency violations that traditionally appear only in staging or after deployment can now be flagged directly during review.


    hashtag
    Side-by-side comparison

    Capability
    Without AI Architect
    With AI Architect

    Vim/Neovim Plugin

    Vim/ Neovim Plugin for Bito Using Bito CLI

    We are excited to announce that one of our users has developed a dedicated Vim and Neovim plugin for Bito, integrating it seamlessly with your favorite code editor. This plugin enhances your coding experience by leveraging the power of Bito's AI capabilities directly within Vim and Neovim.

    Installation

    To get started with "vim-bitoai," follow these steps:

    Step 1: Install Bito CLI

    Make sure you have Bito CLI installed on your system. If you haven't installed it, you can find detailed instructions in the Bito CLI repository at https://github.com/gitbito/CLIarrow-up-right.

    Step 2: Install the Plugin

    Open your terminal and navigate to your Vim or Neovim plugin directory. Then, clone the "vim-bitoai" repository using the following command:

    Step 3: Configure the Plugin

    Open your Vim or Neovim configuration file and add the following lines:

    Save the configuration file and restart your editor or run :source ~/.vimrc (for Vim) or :source ~/.config/nvim/init.vim (for Neovim) to load the changes.

    Step 4: Verify the Installation

    Open Vim or Neovim, and you should now have the "vim-bitoai" plugin installed and ready to use.

    Usage

    You can use its powerful features once you have installed the "vim-bitoai" plugin. Here are some of the available commands:

    • BitoAiGenerate: Generates code based on a given prompt.

    • BitoAiGenerateUnit: Generates unit test code for the selected code block.

    • BitoAiGenerateComment: Generates comments for methods, explaining parameters and output.

    To execute a command, follow these steps:

    1. Open a file in Vim or Neovim that you want to work on.

    2. Select the code block you want to act on. You can use visual mode or manually specify the range using line numbers.

    3. Execute the desired command by running the corresponding command in command mode. For example, to generate code based on a prompt, use the : BitoAiGenerate command. Note: Some commands may prompt you for additional information or options.

    By leveraging the "vim-bitoai" plugin, you can directly harness the power of Bito's AI capabilities within your favorite Vim or Neovim editor. This integration lets you streamline your software development process, saving time and effort in repetitive tasks and promoting efficient coding practices.

    Customization

    The "vim-bitoai" plugin also offers customization options tailored to your specific needs. Here are a few variables you can configure in your Vim or Neovim configuration file:

    • g:bito_buffer_name_prefix: Sets the prefix for the buffer name in the Bito history. By default, it is set to 'bito_history_'.

    • g:vim_bito_path: Specifies the path to the Bito CLI executable. If the Bito CLI is not in your system's command path, you can provide the full path to the executable.

    • g:vim_bito_prompt_{command}: Allows you to customize the prompt for a specific command. Replace {command} with the desired command.

    To define a custom prompt, add the following line to your Vim or Neovim configuration file and replace your prompt with the desired prompt text:

    Remember to restart your editor or run the appropriate command to load the changes.

    We encourage you to explore the "vim-bitoai" plugin and experience the benefits of seamless integration between Bito and your Vim or Neovim editor. Feel free to contribute to the repository or provide feedback to help us further improve this plugin and enhance your coding experience.

    Installing on Visual Studio Code

    It takes less than 2 minutes

    Get up and running with Bito in just a few steps! Bito seamlessly integrates with Visual Studio Code, providing powerful AI-driven code reviews directly within your editor. Click the button below to quickly install the Bito extension and start optimizing your development workflow with context-aware AI Chat, and more.

    hashtag
    Video guide

    Watch the video below to learn how to download the Bito extension on VS Code.

    hashtag
    Step-by-step instructions

    1. In Visual Studio Code, go to the extension tab and search for Bito.

    1. Install the extension. We recommend you restart the IDE after the installation is complete.

    circle-info

    Starting with Bito version 1.3.4, the extension is only supported on VS Code versions 1.72 and higher. Bito does not support VS Code versions below 1.72, and earlier versions of Bito do not function properly on these older versions.

    1. After a successful install, the Bito logo appears in the Visual Studio Code pane.

    1. Click the Bito logo to launch the extension and complete the setup process. You will either need to create a new workspace if you are the first in your company to install Bito or join an existing workspace created by a co-worker. See

    circle-info

    Visual Studio Code Marketplace Link

    hashtag
    Setup Bito extension in VS Code running through SSH

    SSH (Secure Shell) is a network protocol that securely enables remote access, system management, and file transfer between computers over unsecured networks.

    Visual Studio Code IDE allows developers to access and collaborate on projects from any connected machine remotely. The corresponding extension [Remote -SSH] must be installed on the host machine's Visual Studio Code IDE to utilize this feature.

    The Bito VS Code extension seamlessly integrates with Remote development via SSH, allowing developers to utilize Bito features and capabilities on their remote machines.

    hashtag
    Remote SSH connection and setup

    Please follow the instructions given in the links below:

    Video Guide:

    hashtag
    Setup Bito extension in VS Code running through WSL

    Running VS Code on WSL allows developers to work in a Linux-like environment directly from Windows. This kind of setup is to take advantage of development experience on both operating systems.

    WSL provides access to Linux command-line tools, utilities, and applications, to enhance productivity and streamline the development process.

    This setup ensures a consistent development environment across different systems, making it easier to develop, test, and deploy applications that will run on Linux servers.

    hashtag
    WSL connection and setup

    Please follow the instructions given in the links below:

    Video Guide:

    Start free trial

    Unlock premium Bito features with our 14-day free trial.

    The Bito free trial gives you access to premium features for 14 days, allowing you to experience the full capabilities of Bito's AI-powered coding assistant.

    You can start your free trial directly from the Bito IDE extension using any of the three methods below.

    hashtag
    How to start your free trial

    hashtag
    Method 1: Using Bito AI chat

    The easiest way to start your trial is through natural interaction:

    1. Type a message in the Bito chat box and send it.

    2. Look for the popup that appears after sending your message.

    3. Click Try for free in the popup notification.

    hashtag
    Method 2: Click upgrade button

    For a direct approach to upgrading:

    1. Click the UPGRADE button given at the top of the chat window

    2. Complete signup in the browser window that opens.

    3. Select Start Trial to activate your free trial.

    hashtag
    Method 3: Quick trial activation

    The fastest way to start your free trial:

    1. Hover over Include my code (located above the Bito chat box).

    2. In the popup, select Click for 14 day free trial to immediately activate your trial.

    circle-info

    💡 Pro tip: Method 3 is the quickest option as it starts your trial instantly without opening any external windows.

    hashtag
    Available features in free trial

    During your free trial, you'll have access to all the features of Bito Team Plan as mentioned on our page. It includes:

    hashtag
    Need Help?

    If you encounter any issues while starting your free trial:

    • Check your internet connection.

    • Ensure your Bito extension is up to date.

    • Contact if the trial doesn't activate properly.

    hashtag
    Next steps

    Once your free trial is active, explore all the premium features available to you. Consider upgrading to a paid plan before your trial expires to continue enjoying advanced functionality.

    How to use?

    Learn how to work with Bito CLI (including examples)

    hashtag
    Prerequisites

    Terminal

    • Bash (for Mac and Linux)

    • CMD (for Windows)

    hashtag
    Using Bito CLI

    Before you can use Bito CLI, you need to and it. Once the setup is done, follow the steps below:

    • Execute Chat: Run bito command on command prompt to get started. Ask anything you want help with such as awk command to print first and last column.

    • Note: Bito CLI supports long prompts through multiline input. To complete and submit the prompt, press Ctrl+D. Enter/Return key adds a new line to the input.

    circle-info

    Here is the complete list of .

    hashtag
    Getting Started

    Check out the video below to get started with Bito CLI.

    hashtag
    Examples

    Here are two examples for you to see My Prompt in action:

    1. How to Create Git Commit Messages and Markdown Documentation with Ease using Bito CLI My Prompt:

    1. How to generate test data using Bito CLI My Prompt:

    Overview

    AI that Understands Your Code

    Bito has created the ability for our AI to understand your codebase, which produces dramatically better results that are personalized to you. This can help you write code, refactor code, explain code, debug, and generate test cases – all with the benefits of AI knowing your entire code base.

    Bito AI automatically figures out if you're asking about something in your code. If it's confident, it grabs the relevant parts of your code from our index and feeds them to the Large Language Models (LLMs) for accurate answers. But if it's unsure, Bito will ask you to confirm before proceeding.

    circle-info

    To specifically ask questions related to your codebase, add the keyword "my code" in English, Cantonese, Japanese, Mandarin, Spanish, or Portuguese (more languages coming soon) to your questions in the Bito chatbox.

    Example: in my code explain the file apiUser.js

    Additional keywords for various languages are listed on the page.

    For now, this feature is only available for our Team Plan which costs $15 per user per month. We have plans to release it for our Free Plan soon. But it will be limited to repos of 10MB indexable size.

    Recent breakthroughs in and have helped make many AI Coding Assistant tools available, including Bito, to help you develop software faster.

    The major issue with these AI assistants, though, is that they have no idea about your entire codebase. Some tools take context from currently opened files in your IDE, while others enable you to manually enter code snippets in a chat-like interface and then ask questions about them.

    But with Bito’s AI that understands your entire repository, this is a whole new capability. For example, what if you could ask questions like:

    • how can I add a button to mute and unmute the song to my code in my music player? By default, set this button to unmute. Also, use the same design as existing buttons in UI.

    • In my code list all the files and code changes needed to add column desc in table raw_data in dailyReport DB.

    • In my code suggest code refactoring for api.py and mention all other files that needs to be updated accordingly

    This will definitely improve the way you build software.

    Overview

    System intelligence for your coding agents.

    Bito’s AI Architect builds a knowledge graph of your codebase — from repos to modules to APIs — delivering deep codebase intelligence to the coding agents you already use. This fundamentally changes the game for enterprises with many microservices or large, complex codebases.

    circle-info

    Bito provides the AI Architect in a completely secure fashion, with the AI Architect available on-prem if you desire with no code ever being sent to Bito. No AI is trained on your code and your code is not stored.

    Available commands

    Invoke the AI Code Review Agent manually or within a workflow.

    The offers a suite of commands tailored to developers' needs. You can manually trigger a code review by entering any of these commands in the comment box below a pull/merge request on GitHub, GitLab, or Bitbucket and submitting the comment. Alternatively, if you are using the self-hosted version, you can configure these commands in the for automated code reviews.

    circle-info

    It may take a few minutes to get the code review posted as a comment, depending on the size of the pull/merge request.

    Templates

    Instantly improve code performance, security, and readability with AI suggestions.

    Templates help you improve your code quality instantly with AI-powered analysis. Get automated suggestions for performance optimization, security fixes, style improvements, and code cleanup without leaving your editor. Each template provides actionable feedback and ready-to-use code improvements that you can review and apply with a single click.

    hashtag
    Available templates

    Available commands

    Learn about all the powerful commands to use Bito CLI

    hashtag
    Help

    Run any one of the below commands.

    bito --help

    or

    Install or uninstall

    Learn how to setup Bito CLI on your device (Mac, Linux, and Windows)

    hashtag
    Installing Bito CLI (Recommended)

    We recommend you use the following methods to install Bito CLI.

    hashtag

  • Replace <pr_url> with your specific values.

  • listClusters

    View automatically identified clusters of related repositories in your organization.

    Clusters represent groups of repositories with strong dependencies or architectural relationships, often forming subsystems or microservice groups.

    Use this to understand system architecture, identify bounded contexts, discover service groupings, or analyze component relationships.

    Returns cluster information with member repositories and their resource URIs.

    getRepositoryInfo

    Get comprehensive repository information including metadata, structure, and dependencies.

    To access incoming dependencies (services depending on this repo): set includeIncomingDependencies=true.

    To access outgoing dependencies (services this repo depends on): set includeOutgoingDependencies=true.

    Edge data includes various dependency types - filter by edge.type field to isolate specific categories.

    Smart defaults: dependencies auto-limited by detailLevel (summary: 10, standard: 25, full: unlimited).

    Essential for understanding repository relationships, analyzing dependencies, investigating integration points, and assessing impact of changes.

    Returns pre-analyzed dependency graphs and relationship data.

    getClusterInfo

    Examine a specific cluster of related repositories to understand subsystem architecture within your organization.

    Returns all member repositories, their interdependencies, project summaries, and resource URIs.

    Use this to analyze how repositories collaborate, understand service boundaries, explore microservice architectures, or investigate system decomposition patterns.

    Valuable for architectural reviews and impact analysis.

    searchRepositories

    ONLY use when you DON'T know the repository name. If you know exact name, use getRepositoryInfo or getFieldPath directly.

    Intelligent search across your organization's Git repositories using natural language queries.

    Search by technology, functionality, frameworks, or project characteristics when repository name is unknown.

    Uses TF-IDF algorithm on pre-indexed repository metadata for relevant results.

    Examples: 'Python microservices', 'repositories using Redis', 'authentication services', 'React applications', 'payment processing systems', 'Kubernetes deployments'.

    Returns repositories with relevance scores and direct access URIs.

    searchWithinRepository

    Search for content within a single repository including metadata and dependency data.

    Searches metadata fields and optionally incoming_dependencies and outgoing_dependencies.

    By default searches ALL data for comprehensive results.

    Use includeIncomingDependencies=false and includeOutgoingDependencies=false for faster metadata-only search.

    Returns filtered results with matches from metadata and dependencies.

    Use when: You know which repo but need to find specific information without knowing exact field paths.

    Natural language queries work well.

    getRepositorySchema

    Discover repository structure without fetching data.

    Returns field names, types, array counts, and nested hierarchy.

    Essential first step for exploring unfamiliar repositories.

    getFieldPath

    Extract specific nested field using dot notation and array indexing.

    MOST EFFICIENT for surgical data extraction - returns only requested field vs full repository.

    For dependencies: use 'incoming_dependencies' or 'outgoing_dependencies' paths with arraySlice, then filter by edge.type field to isolate specific categories.

    Supports deep nesting, array slicing, and optional parent context.

    Returns only the requested field data.

    queryFieldAcrossRepositories

    Query same field path across multiple repositories in single call.

    Comparative analysis, pattern discovery, and technology audits across repos.

    searchCode

    Search code using zoekt index with powerful query syntax.

    Supports file filters, exclusions, case sensitivity.

    Returns code matches with snippets.

    searchSymbols

    Search for symbol definitions (functions, classes, methods) across indexed codebase.

    getCode

    Retrieve actual source code content from repository files.

    Use after searchCode/searchSymbols to view the full code around matches.

    Returns file contents with line numbers. Only available when reposDir is configured.

    Complete signup in the browser window that opens.
  • Select Start Trial to activate your free trial.

  • AI that understands your code
  • and more.

  • Pricingarrow-up-right
    AI Code Reviews in Git
    AI Code Reviews in IDE
    AI Chat
    Visit our Pricing page
    [email protected]envelope

    Create optimized indexes for semantic search

  • Remove the cloned code from our servers (only index data is retained)

  • Bito MCP URL
  • Bito MCP Access Token

  • Use these credentials to connect AI Architect to your AI coding agents (Cursor, Claude Code, Windsurf, GitHub Copilot, etc.).

    Once connected, AI Architect provides codebase-aware context to your coding agent, enabling more accurate answers.

    [email protected]envelope

    You will be redirected to the X (Twitter) website, with a pre-written tweet containing a link to your Chat Session ready to be published.

  • Click the "Post" button to send the tweet.

  • The email will be pre-filled with all the necessary information, including the link to your Chat Session.

  • Add the receiver(s) of this email using the "To" input field.

  • Click the "Send" button to send the email.

  • Feel free to share this link with anyone you'd like to.

    Suggesting improvements based on local patterns

    Upstream and downstream call chains

    Whether the update introduces architecture-wide risks

    Impact analysis

    Local only

    Upstream + downstream, multi-repo

    Architecture checks

    Limited

    System-level validation

    Ripple-effect detection

    ❌

    ✅

    Multi-service understanding

    ❌

    ✅

    Scope

    Single repository

    Entire system (multi-repo)

    Knowledge graph

    Repo-only

    Cross-repository, system-wide

    AST + symbol analysis

    ✅

    ✅ (plus cross-repo linking)

    Dependency visibility

    Local to repo

    Full call chains across repos

    Chat Session History
    How to install Bito extension on JetBrains IDEs
    Updating Bito plugin on VS Code
    Updating Bito Plugin on JetBrains IDEs

    BitoAiCheck: Performs a check for potential issues in the code and suggests improvements.

  • BitoAiCheckSecurity: Checks the code for security issues and provides recommendations.

  • BitoAiCheckStyle: Checks the code for style issues and suggests style improvements.

  • BitoAiCheckPerformance: Analyzes the code for performance issues and suggests optimizations.

  • BitoAiReadable: Organizes the code to enhance readability and maintainability.

  • BitoAiExplain: Generates an explanation for the selected code.

  • The plugin will communicate with the Bito CLI and execute the command, providing the output directly within your editor.

    bito config –help

    hashtag
    Check Bito CLI Version

    Run any one of the below commands to print the version number of Bito CLI installed currently.

    bito -v

    or

    bito --version

    hashtag
    Bito CLI MyPrompt (Automation using Bito CLI)

    The below commands can help you automate repetitive tasks like software documentation, test case generation, writing pull request description, pull request review, release notes generation, writing commit message, and much more.

    circle-info

    Explore some intelligent AI automationsarrow-up-right we've created using Bito CLI, which you can implement in your projects right now. These automations showcase the powerful capabilities of Bito CLI.

    hashtag
    1- Non-Interactive Mode with File Input

    Run the below command for non-interactive mode in Bito (where writedocprompt.txt will contain your prompt text such as Explain the code below in brief and mycode.js will contain the actual code on which the action is to be performed).

    hashtag
    2- Standard Input Mode

    Run the below command to read the content at standard input in Bito (where writedocprompt.txt will contain your prompt text such as Explain the code below in brief and input provided will have the actual content on which the action is to be performed).

    hashtag
    3- Direct File Input

    Run the below command to directly concatenate a file and pipe it to bito and get instant result for your query.

    hashtag
    On Mac/Linux

    hashtag
    On Windows

    hashtag
    4- Redirect Output to a File

    hashtag
    On Mac/Linux

    Run the below command to redirect your output directly to a file (where -p can be used along with cat to perform prompt related action on the given content).

    hashtag
    On Windows

    Run the below command to redirect your output directly to a file (where -p can be used along with type to perform prompt related action on the given content).

    hashtag
    5- Store Context/Conversation History

    Run the below command to store context/conversation history in non-interactive mode in file runcontext.txt to use for next set of commands in case prior context is needed. If runcontext.txt is not present it will be created. Please provide a new file or an existing context file created by bito using -c option. With -c option now context is supported in non-interactive mode

    hashtag
    On Mac/Linux

    hashtag
    On Windows

    hashtag
    6- Instant Response for Queries

    Run the below command to instantly get response for your queries using Bito CLI.

    hashtag
    Using Comments

    Anything after # symbol in your prompt file will be considered as a comment by Bito CLI and won't be part of your prompt.

    You can use \# as an escape sequence to make # as a part of your prompt and to not use it for commenting anymore.

    hashtag
    Few examples for above:

    • Give me an example of bubble sort in python # everything written here will be considered as a comment now.

    • Explain what this part of the code do: \#include<stdio.h>

      • In the example above \# can be used as an escape sequence to include # as a part of your prompt.

    • #This will be considered as a comment as it contains # at the start of the line itself.

    hashtag
    Using Macro

    Use {{%input%}} macro in the prompt file to refer to the contents of the file provided via -f option.

    Example: To check if a file contains JS code or not, you can create a prompt file checkifjscode.txt with following prompt:

    git clone https://github.com/zhenyangze/vim-bitoai.git
    
    " Vim Plug
    Plug 'zhenyangze/vim-bitoai'
    
    " NeoBundle
    NewBundle 'zhenyangze/vim-bitoai'
    
    " Vundle
    Plugin 'zhenyangze/vim-bitoai'
    if !exists("g:vim_bito_prompt_{command}")
        let g:vim_bito_prompt_{command}="your prompt"
    endif
    bito –p writedocprompt.txt -f mycode.js
    bito –p writedocprompt.txt
    cat file.txt | bito
    type file.txt | bito
    cat inventory.sql | bito -p testdataprompt.txt > testdata.sql
    type inventory.sql | bito -p testdataprompt.txt > testdata.sql
    cat inventory.sql | bito -c runcontext.txt -p testdataprompt.txt > testdata.sql
    type inventory.sql | bito -c runcontext.txt -p testdataprompt.txt > testdata.sql
    echo "give me code for bubble sort in python" | bito
    Context is provided below within contextstart and contextend
    contextstart
    {{%input%}}
    contextend
    Check if content provided in context is JS code.
    Claude Team
  • Claude Enterprise

  • You enter your email and approve the connection
  • Claude.ai receives secure tokens automatically

  • Your email is tracked for usage analytics (collected during OAuth consent)

  • Click on your profile icon (bottom-left corner)

  • Select Settings

  • Navigate to Integrations section

  • 2

    hashtag
    Add Bito AI Architect MCP server

    1. Click "+ Add Custom Integration"

    2. Enter the integration details:

      • Name: BitoAIArchitect

      • URL: <Your-Bito-MCP-URL>

    circle-info
    • Replace <Your-Bito-MCP-URL> with the Bito MCP URL you received after completing the AI Architect setup.

      • For the Bito-hosted AI Architect, use the following URL format: https://mcp.bito.ai/<Your-Bito-Workspace-ID>/mcp

    1. Click "Connect" or "Add"

    3

    hashtag
    Complete OAuth authorization

    1. A new browser window/tab will open showing the Bito Authorization page

    2. Review the requested permissions

    3. Enter your email address (required for tracking/identification)

    4. Click "Authorize" or "Allow"

    5. The window will close and you'll be returned to Claude.ai

    4

    hashtag
    Verify connection

    1. Return to Claude.ai Settings → Integrations

    2. BitoAIArchitect should show as "Connected" with a green indicator

    3. Start a new conversation and try:

    Try clearing browser cache and cookies, then retry
    AI Architect installation instructions
    Download BitoAIArchitectGuidelines.md filearrow-up-right
    claude.aiarrow-up-right

    ✅ Require a pull request before merging

  • ✅ Require conversation resolution before merging

  • Click Save changes button.

    By branch name or pattern: Enter a specific branch name (e.g., main) or use a wildcard pattern to cover multiple branches. For example, using an asterisk * applies the restriction across all branches, while release/* applies it to every release branch.

  • By branch type: Select a branch type (e.g., development, release) from the dropdown menu.

  • Switch to Merge settings tab.

  • Under Merge checks, enable:

    • ✅ No changes are requested

  • Under Merge conditions, enable:

    • ✅ Prevent a merge with unresolved merge checks

    • Note: This setting is only available if your organization uses Bitbucket Cloud Premium. It will block anyone from merging the PR if there are unresolved "request change" comments. On Standard Bitbucket Cloud, this option is unavailable; users will see a warning if they attempt to merge with unresolved "request change" comments, but the merge will still be allowed.

  • Click Save button.

  • Save changes
    If comment resolution is required, the merge is blocked until the flagged issues are resolved.
    Developer fixes the issue and marks the thread as resolved.
  • Merge becomes possible once all conditions are met.

  • Helps maintain consistent code quality at scale.

    Filters – Exclude specific files, folders, or branches from review to focus on relevant code.

  • Tools – Enable additional checks, such as secret scanning and static analysis.

  • Chat – Configure how the agent responds to follow-up questions in pull request comments and manage automatic replies.

  • Authentication

    • bito_cli.bito.access_key: Required for authenticating the agent with the Bito platform.

    • git.provider, git.access_token, etc.: Required for connecting to the appropriate Git provider (e.g., GitHub, GitLab, Bitbucket).

  • General feedback settings

    • code_feedback: Enables or disables general feedback comments in reviews.

  • Analysis tools

    • static_analysis: Enables static code analysis.

    • dependency_check: Enables open-source dependency scanning.

    • dependency_check.snyk_auth_token: Required when using Snyk for vulnerability detection.

  • Review format and scope

    • review_comments: Defines output style (e.g., single post or inline comments).

    • review_scope: Limits the review focus to specific concerns such as security, performance, or style.

  • Filters

    • include_source_branches and include_target_branches: Restrict reviews to pull requests that match specified source and target branch patterns.

    • exclude_files: Skips selected files based on glob patterns.

    • exclude_draft_pr: Skips draft pull requests when enabled (default: True).

  • Bito web UIarrow-up-right
    Code Review > Repositoriesarrow-up-right
    Create or customize an Agent instancearrow-up-right
    bito-cra.properties file
    bito-cra.properties file documentation

    Learn more

    Learn more

    Exit Bito CLI: To quit/exit from Bito CLI, type quit and press Ctrl+D .

  • Terminate: Press Ctrl+C to terminate Bito CLI.

  • install
    configure
    available commands for Bito CLI

    Please write the frontend and backend code to take a user’s credentials, and authenticate the user. Use the authentication service in my code

    Available Keywords
    Generative AI
    Large Language Models (LLMs)
    hashtag
    Key capabilities of the AI Architect include:
    • Grounded 1-shot production-ready code — The AI Architect learns all your services, endpoints, code usage examples, and architectural patterns. The agent automatically feeds those to your coding agent (Claude Code, Cursor, Codex, any MCP client) to provide it the necessary information to quickly and efficiently create production ready code.

      • Watch demo videoarrow-up-right

    • Consistent design adherence — Code generated aligns with your architecture patterns and coding conventions.

    • Spec-driven development — Automatically generate highly detailed, implementation-ready technical requirement documents (TRDs) and low-level designs (LLDs) with a deep, context-aware understanding of your codebase, services, and design patterns, ensuring architectural integrity and consistency at a granular level.

    • Triaging production issues — Easily and quickly find root causes to production issues based on errors/logs/etc.

    • Faster onboarding — New engineers or AI agents can quickly understand how a system or component system structure.

    • Enhanced documentation and diagramming — Through its internal understanding of interconnections between modules and APIs.

    • Smarter code reviews — Reviews with system-wide awareness of dependencies and impacts.

    The AI Architect builds the knowledge graph by analyzing all your repositories (whether you have 50 or 5,000 repos) to learn about your codebase architecture, microservices, modules, API endpoints, design patterns, and more.

    hashtag
    How you can use AI Architect

    AI Architect is designed to be flexible and can power multiple use cases across different AI coding tools and workflows.

    • Integrate via MCP server – Use AI Architect as an MCP (Model Context Protocol) server to connect with tools like Claude Code, Cursor, Windsurf, GitHub Copilot (VS Code), Junie (JetBrains), and JetBrains AI Assistant. It helps connected tools understand your codebase and workflows better, resulting in accurate and more reliable suggestions.

      1. Bito-hosted version: Fully managed by Bito — no infrastructure setup required

      2. On-premises deployment: Install and run AI Architect on your own infrastructure.

    • – One example of AI Architect in action is Bito’s AI Code Review Agent, which uses AI Architect to deliver smarter, context-aware code reviews directly in your pull requests and IDEs.

    hashtag
    Why use the AI Architect?

    Most AI coding tools struggle with accuracy in real-world codebases because they

    1. Don’t fully understand the breadth and depth of your codebase. They read some of the code in your existing repository, but they don’t have a complete graph of your internal APIs, endpoints, libraries, etc. On top of that, if you are accessing a monorepo or many services not available on your machine locally, they have no context or get confused trying to access them. Bito’s AI Architect has built a knowledge graph to provide this information in a cheap and efficient way to your coding agent so it can accomplish the task with grounded and complete information.

    2. They don’t fully understand how all of your services and modules interact with each other when you are trying to understand your overall system versus just one component. The AI Architect’s graph contains a mapping of all the dependencies, allowing to provide sophisticated analysis – how you would expect an Architect too.

    hashtag
    How AI Architect differs from Embeddings?

    Traditional embeddings work like a search engine — they retrieve code snippets or documents similar to a given query.

    They can find related content but can’t understand how different parts of your system work together.

    The AI Architect, on the other hand:

    • Builds a knowledge graph that captures relationships between repositories, modules, APIs, and libraries.

    • Provides precise answers and implementations, not just search results.

    • Understands context and intent — how and why something is implemented in your codebase.

    • Enables system-aware reasoning, allowing AI agents to generate or review code with full architectural understanding.

    hashtag
    Getting started

    1. Try Bito's AI Architectarrow-up-right

    2. Get a demoarrow-up-right with our team.

    3. Lastly, email [email protected]envelope if you have any additional questions.

    hashtag
    Demos of different ways to use AI Architect

    hashtag
    /review

    This command provides a broad overview of your code changes, offering suggestions for improvement across various aspects but without diving deep for secure coding or performance optimizations or scalability improvements etc. This makes it ideal for catching general code quality issues that might not necessarily be critical blockers but can enhance readability, maintainability, and overall code health.

    Think of it as a first-pass review to identify potential areas for improvement before delving into more specialized analyses.

    hashtag
    Review Scope

    Five specialized commands are available to perform detailed analyses on specific aspects of your code. Details for each command are given below.

    1. /review security

    2. /review performance

    3. /review scalability

    4. /review codeorg

    5. /review codeoptimize

    circle-info

    You can provide comma-separated values to perform multiple types of code analysis simultaneously.

    Example: /review performance,security,codeoptimize

    hashtag
    Combining general feedback with specialized review scopes

    If you'd like to receive general code quality feedback alongside specialized analyses, include the general keyword in your review command.

    For example, to receive feedback on general code quality, performance, and security, use:

    • Example: /review general,performance,security

    This ensures a holistic review encompassing both general code quality and specific areas of concern.

    hashtag
    /review security

    This command performs an in-depth analysis of your code to identify vulnerabilities that could allow attackers to steal data, gain unauthorized access, or disrupt your application. This includes checking for weaknesses in input validation, output encoding, authentication, authorization, and session management. It also looks for proper encryption of sensitive data, secure coding practices, and potential misconfigurations that could expose your system.

    Highlighting the security vulnerability detected and the proposed solution.

    hashtag
    /review performance

    This command evaluates the current performance of the code by pinpointing slow or resource-intensive areas and identifying potential bottlenecks. It helps developers understand where the code may be underperforming against expected benchmarks or standards. It is particularly useful for identifying slow processes that could benefit from further investigation and refinement.

    This includes checking how well your code accesses data and manages tasks like database interactions and memory usage.

    Highlighting the performance issue detected and the proposed solution.

    hashtag
    /review scalability

    This command analyzes your code to identify potential roadblocks to handling increased usage or data. It checks how well the codebase supports horizontal scaling and whether it is compatible with load balancing strategies. It also ensures the code can handle concurrent requests efficiently and avoids bottlenecks from single points of failure. The command further examines error handling and retry mechanisms to promote system resilience under pressure.

    Highlighting the scalability issue detected and the proposed solution.

    hashtag
    /review codeorg

    This command scans your code for readability, maintainability, and overall clarity. This includes checking for consistent formatting, clear comments, well-defined functions, and efficient use of data structures. It also looks for opportunities to reduce code duplication, improve error handling, and ensure the code is written for future growth and maintainability.

    Highlighting the code structure issue detected and the proposed solution.

    hashtag
    /review codeoptimize

    This command helps identify specific parts of the code that can be made more efficient through optimization techniques. It suggests refactoring opportunities, algorithmic improvements, and areas where resource usage can be minimized. This command is essential for enhancing the overall efficiency of the code, making it faster and less resource-heavy.

    Precise code optimization advice pinpointing exact lines in a file.

    hashtag
    Control code review workflow

    These commands allow you to manage the AI Code Review Agent's behavior directly within your pull requests across GitHub, GitLab, and Bitbucket.

    hashtag
    /pause

    Pauses automatic AI reviews on the current pull request.

    Use case: Useful when significant changes are underway, and you want to prevent the AI from reviewing incomplete code.

    Example: Add a comment with /pause to the pull request.

    hashtag
    /resume

    Resumes the automatic AI reviews that were previously paused on the pull request.

    Use case: Once your code changes are ready for review, use this command to re-enable the AI's automatic analysis.

    Example: Add a comment with /resume to the pull request.

    hashtag
    /resolve

    Marks all Bito-posted review comments as resolved.

    Use case: After addressing the issues highlighted by the AI, use this command to clean up the comment threads.

    Example: Add a comment with /resolve to the pull request.

    circle-info

    Note: The /resolve command is currently supported in GitLab and Bitbucket.

    hashtag
    /abort

    Cancels all in-progress AI code reviews on the current pull request.

    Use case: If an AI review is no longer needed or was initiated by mistake, this command stops the process.

    Example: Add a comment with /abort to the pull request.

    hashtag
    Display Code Review in a Single Post

    By default, the /review command generates inline comments, placing code suggestions directly beneath the corresponding lines in each file for clearer guidance on improvements. If you prefer a single consolidated code review instead of separate inline comments, use the #inline_comment parameter and set its value to False.

    Example: /review #inline_comment=False

    Example: /review scalability #inline_comment=False

    circle-info

    Note: The /review command defaults to #inline_comment=True, so you can omit this parameter when its value is True.

    AI Code Review Agent
    bito-cra.properties file
    Performance Check:
    Optimize code performance and efficiency
  • Security Check: Identify and fix security vulnerabilities

  • Style Check: Apply coding style and formatting standards

  • Improve Readability: Enhance code clarity and organization

  • Clean Code: Remove debugging and logging statements

  • Templates menu in Bito Panel

    hashtag
    How to use templates

    hashtag
    Prerequisites

    Select the code you want to analyze in your editor before using any template.

    hashtag
    Method 1: Click Templates button

    1. Select code in your editor

    2. Click the Templates button at the bottom of the Bito extension panel

    1. Choose the desired template from the dropdown menu

    circle-info

    Quick navigation: Use arrow keys, Tab, or Shift+Tab to navigate the template menu

    hashtag
    Method 2: Open context menu

    1. Select code in your editor

    2. Right-click in the editor window

    3. Hover over "Bito AI" in the context menu

    4. Select the desired template from the submenu

    hashtag
    Method 3: Using slash / command in Bito chat box

    1. Select code in your editor

    2. Type / at the start of the Bito chat box

    3. Choose the desired template from the dropdown menu

    1. Type some text after the slash / to filter templates by name

    hashtag
    Method 4: Command Palette (VS Code)

    1. Select code in your editor

    2. Go to View → Command Palette (or press Ctrl+Shift+P / Cmd+Shift+P)

    3. Type "bito" to see available templates

    4. Select the desired template from the list

    hashtag
    Applying code suggestions

    When templates provide code improvements, you'll see an Apply button above the suggested code snippet.

    1. Click the Apply button to open the diff view

    1. Review the changes highlighted in the diff:

      • Red lines show code to be removed

      • Green lines show code to be added

    2. Choose your action:

      • Accept - Apply the suggested changes to your code

      • Undo - Reject the changes and keep your original code

    hashtag
    Tips

    • Select meaningful code blocks for better analysis results

    • Templates work best with complete functions or logical code segments

    • Review suggested changes before applying them to your codebase

    • Verify that the changes don't break existing functionality

    • Use multiple templates on the same code for comprehensive analysis

    • Use the diff view to understand exactly what changes will be made

    Mac and Linux

    sudo curl https://alpha.bito.ai/downloads/cli/install.sh -fsSL | bash

    Note: curl will always download the latest version.

    hashtag
    Archlinux

    Arch and Arch based distro users can install it from AURarrow-up-right

    yay -S bito-cli

    or

    paru -S bito-cli

    Note for the Mac Users: You might face issues related to verification for which you will have to manually do the steps from herearrow-up-right (we are working on fixing it as soon as possible).

    hashtag
    Windows

    • In the Bito CLI GitHub repoarrow-up-right, open the folder that has the latest version number.

    • From here, download the MSI file called Bito CLI.exe and then install Bito CLI using this installer.

    • On Windows 11, you might get notification related to publisher verification. Click on "Show more" or "More info" and click on "Run anyway" (we are working on fixing this as soon as possible).

    circle-info

    Once the installation is complete, start a new command prompt and run bito command to get started.

    hashtag
    Installing with Manual Binary Download (Not Recommended)

    While it's not recommended, you can download the Bito CLI binary from our repository, and install it manually. The binary is available for Windows, Linux, and Mac OS (x86 and ARM architecture).

    hashtag
    Mac and Linux

    1. In the Bito CLI GitHub repoarrow-up-right, open the folder that has the latest version number.

    2. From here, download the Bito CLI binary specific to your OS platform.

    3. Start the terminal, go to the location where you downloaded the binary, move the downloaded file (in the command below use bito-* filename you have downloaded) to filename bito.

      mv bito-<os>-<arch> bito

    4. Make the file executable using following command chmod +x ./bito

    5. Copy the binary to /usr/local/bin using following command sudo cp ./bito /usr/local/bin

    6. Set PATH variable so that Bito CLI is always accessible. PATH=$PATH:/usr/local/bin

    7. Run Bito CLI with bito command. If PATH variable is not set, you will need to run command with the complete or relative path to the Bito executable binary.

    hashtag
    Windows

    1. In the Bito CLI GitHub repoarrow-up-right, open the folder that has the latest version number.

    2. From here, download the Bito CLI binary for Windows called bito.exe.

    3. For using Bito CLI, always move to the directory containing Bito CLI prior to running it.

    4. Set PATH variable so that Bito CLI is always accessible.

      1. Follow the instructions as per this

      2. Edit the "Path" variable and add a new path of the location where Bito CLI is installed on your machine.

    hashtag
    Uninstalling Bito CLI

    hashtag
    Mac and Linux

    sudo curl https://alpha.bito.ai/downloads/cli/uninstall.sh -fsSL | bash

    Note: This will completely uninstall Bito CLI and all of its components.

    hashtag
    Windows

    For Windows, you can uninstall Bito CLI just like you uninstall any other software from the control panel. You can follow these steps:

    1. Click on the Windows Start button and type "control panel" in the search box, and then open the Control Panel app.

    2. Under the "Programs" option, click on "Uninstall a program".

    3. Find "Bito CLI" in the list of installed programs and click on it.

    4. Click on the "Uninstall" button (given at the top) to start the uninstallation process.

    5. Follow the instructions provided by the uninstall wizard to complete the uninstallation process.

    After completing these steps, Bito CLI should be completely removed from your Windows machine.

    Install on VS Code

    Managing workspace members
    https://marketplace.visualstudio.com/items?itemName=Bito.bitoarrow-up-right
    https://code.visualstudio.com/docs/remote/ssharrow-up-right
    https://learn.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstusearrow-up-right
    https://code.visualstudio.com/docs/remote/wsl-tutorialarrow-up-right
    https://learn.microsoft.com/en-us/windows/wsl/installarrow-up-right
    Privacy & Security practices
    AI that Understands Your Codearrow-up-right
    How does Bito’s “AI that understands your code” work?arrow-up-right
    Start free trial
    Get a demo
    Pricingarrow-up-right
    Get a 14-day FREE trial of Bito's AI Code Review Agent.arrow-up-right

    Getting Started

    Key Features

    Supported Programming Languages and Tools

    Agent Configuration: bito-cra.properties File

    FAQs

    Prerequisites

    Key requirements for self-hosting the AI Code Review Agent.

    hashtag
    Minimum System Requirements

    A machine with the following minimum specifications is recommended for Docker image deployment and for obtaining optimal performance of the AI Code Review Agent.

    Requirement
    Minimum Specification

    hashtag
    Supported Operating Systems

    • Windows

    • Linux

    • macOS


    hashtag
    OS Prerequisites

    Operating System
    Installation Steps

    hashtag
    Required Access Tokens

    • Bito Access Key: Obtain your Bito Access Key.

    • GitHub Personal Access Token (Classic): For GitHub PR code reviews, ensure you have a CLASSIC personal access token with repo access. We do not support fine-grained tokens currently.

    • GitLab Personal Access Token: For GitLab PR code reviews, a token with API access is required.

    • Snyk API Token (Auth Token): For Snyk vulnerability reports, obtain a Snyk API Token.

    Confluence integration

    Make sure every code change follows the requirements and guidance recorded in your Confluence pages.

    circle-info

    Note: The Confluence integration is available only on the Enterprise Planarrow-up-right.

    Bito integrates with Confluence to enhance functional validation by enriching pull request requirements with deeper context from linked documentation.

    It fetches relevant details from Confluence pages linked in Jira issues or directly in pull request – such as edge cases, design decisions, or test scenarios – and incorporates them into structured validation results.

    This improves accuracy when validating code changes and ensures that every pull request is aligned with the requirements.

    hashtag
    How it works

    When a pull request is opened, Bito automatically:

    1. Detects Confluence references. Bito looks for Confluence page links in the pull request description or in any linked Jira issues.

    circle-info

    Note: If is enabled, Bito finds the Confluence pages associated with the linked Jira tickets.

    1. Fetches documentation. Bito retrieves the content of those Confluence pages and extracts key information (requirements, design decisions, acceptance criteria, etc.).

    2. Validates code against the docs. It compares your code changes to the enriched context and generates structured validation feedback.

    3. Reports results in the PR. Bito posts a "Functional Validation" table directly in your pull request comments, showing how each documented requirement is met, missed, or partially implemented.

    hashtag
    Integration steps

    1

    hashtag
    Connect Bito with Confluence

    1. In your Bito dashboard, go to the page.

    circle-info

    Note: The Functional validation feature must be enabled in your Bito agent settings for the integration to work.

    hashtag
    Linking Confluence pages to pull requests

    For Bito to fetch the right documentation, your pull requests must reference the relevant Confluence pages:

    • With Jira integration: Ensure your Jira issues link to the Confluence pages (for example, by using the Jira Issue macro on the Confluence page). When a Confluence page mentions a Jira issue key, Jira automatically creates a link to that page. Bito will follow those links to gather the documentation context.

    • Without Jira integration: Include a link to the Confluence page directly in the pull request description. Bito will use that URL to retrieve the page content for validation.

    circle-info

    Note: Bito supports both full Confluence page URLs (with page ID) and short Confluence URLs.

    Supported examples:

    • https://yourcompany.atlassian.net/wiki/spaces/SPACEKEY/pages/123456789/Page-Title

    hashtag
    Understanding the validation results

    When Bito completes its analysis, it adds a "Functional Validation by Bito" table to your pull request comments. This table contains four columns:

    hashtag
    Source

    Displays the Jira issue key (e.g., "QP-11", "QP-123") that references the specific Jira ticket being validated.

    hashtag
    Requirement / Code Area

    Shows a brief description of the requirement or task that needs to be completed, summarizing what needs to be done according to the Jira ticket and Confluence page.

    hashtag
    Status

    Indicates the completion status of each requirement:

    • Met: The requirement has been fully implemented in the pull request

    • Missed: The requirement has not been addressed in the pull request

    • Partial: The requirement has been partially implemented but still needs additional work

    hashtag
    Notes

    Provides detailed information about the validation status:

    • For "Met" items: Explains what has been successfully implemented

    • For "Missed" items: Describes what is missing and needs to be addressed

    • For "Partial" items: Details what has been completed and what still remains to be done

    hashtag
    Example validation output

    Here's what a typical validation table looks like:

    hashtag
    Benefits

    • Improved traceability: Syncing code validation with Confluence documentation creates a clear audit trail from requirements to implementation.

    • Single source of truth: By pulling from Confluence (the team’s central documentation hub), Bito ensures developers review code against the definitive requirements. Teams spend less time context-switching between tools.

    • Aligned development: Automatic validation against documented scenarios helps catch missing features or edge cases early, reducing manual review effort and improving quality.

    hashtag
    Troubleshooting

    • No "Functional validation" table in pull request: Check that Confluence is connected under and that the for your Agent. Also verify that your PR or its linked Jira issues actually reference the Confluence pages.

    • Missing or incorrect context: Make sure the Confluence pages contain the up-to-date requirements or test scenarios.

    • Authorization errors: If Bito can't access Confluence, try re-authorizing the integration. Ensure your Atlassian account has permission to read the relevant Confluence pages.

    FAQs

    Answers to Popular Questions

    hashtag
    How many repositories can Bito index?

    Bito can index unlimited repositories for workspaces that have subscribed to our Team Plan. This feature is also coming soon for our Free Plan. But it will be limited to 10MB maximum indexable size of repository.

    hashtag
    Why is the index creation taking a long time?

    Bito takes time to thoroughly read your entire repository and understand it. This is completely normal. If your repository is a bit large, then it can take several hours to get .

    Bito usually takes around 12 minutes per each 10MB of code to understand your repo.

    hashtag
    Why is the answer not complete?

    There is a limit on the amount of memory/context that can be used at a time to answer the question, so the answers sometimes may not cover all the code. To solve for this, restrict the questions by providing additional criteria like:

    • In my code explain message_tokens in ai/request.js

    hashtag
    Where can I see the status of my Index?

    Open your project in VS Code or JetBrains IDEs. From the Bito plugin pane, click the laptop icon located in the top-right corner.

    On this tab, you will see the status of your current project as well as the status of any other project that you indexed previously.

    circle-info

    List of Indexing Statuses:

    • Not Indexed: A new project that you have not started indexing yet.

    hashtag
    What happens if my IDE got closed while indexing is in progress?

    In case you close the Visual Studio Code or JetBrains IDE (e.g., PyCharm) while the is in progress then don’t worry. The indexing will be paused and will automatically continue from where it left off when you reopen the IDE. Currently, the indexing will resume 5-10 minutes after reopening the IDE.

    hashtag
    How to delete project index from IDE?

    1. To delete an index, navigate to the "Manage repos" tab.

    2. Next, click on the three dots button located in front of your project’s name, and then select the "Delete" option.

    hashtag
    How to fix indexing issues in Visual Studio Code and JetBrains IDEs (e.g., IntelliJ IDEA, PyCharm, etc.)?

    circle-info

    Before getting started, please ensure that you have allowed your project sufficient time to be indexed. Bito typically requires approximately 12 minutes for every 10MB of code to understand your repository.

    If for some reason you are struggling to index your project’s folder while using Visual Studio Code or JetBrains IDEs, then follow the below steps to delete the folder that contains all the indexes and try to re-index your project.

    1. Close all JetBrains IDEs and VS Code instances where Bito is installed.

    2. Go to your users directory. For example, on Windows it will be something like C:\Users\<your username>

    3. Now, find .bito folder and delete it. (Note: All configuration settings and project indexes created by Bito will be deleted. You will also be logged out from Bito IDE plugin)

    circle-info

    If Windows is installed on a drive other than “C”, you will need to locate the .bito folder on that drive instead.

    1. Once you have deleted the .bito folder, open your project in the IDE again.

    2. After restarting the IDE, you will need to enter your email ID and a 6-digit code to log in. Once you're logged in, select the workspace that has an active paid subscription.

    3. After that, when Bito asks if you wish to index the folder, you can select "Maybe later".

    circle-info

    For testing purposes, we suggest using a folder with a small size and avoid changing the folder in IDE until indexing is completed and the folder icon turns green.

    By the way, you can continue using Bito while indexing is in progress in the background.

    BitoYouTubechevron-right

    Guide for Claude Desktop

    Integrate Claude Desktop with AI Architect for more accurate, codebase-aware AI assistance.

    Use Bito's with Claude Desktop to enhance your AI-powered coding experience.

    Once connected via MCP (Model Context Protocol), Claude Desktop can leverage AI Architect's deep contextual understanding of your project, enabling more accurate code suggestions, explanations, and code insights.

    hashtag
    Prerequisites

    Try AI code reviews using Test Mode

    Experience AI-powered code analysis on any pull request — no admin access needed.

    Bito offers Test Mode to help you quickly explore our without requiring administrator permissions for your Git repositories. Whether you're evaluating Bito for your team or simply want to see it in action before a full setup, Test Mode gives you immediate access using just a personal access token.

    You can point Bito at any pull request you have access to and receive instant AI-generated feedback.

    What you get:

    • Instant access to AI-powered code reviews

    Guide for ChatGPT (Web & Desktop)

    Integrate ChatGPT with AI Architect for more accurate, codebase-aware AI assistance.

    Use Bito's with ChatGPT (Web & Desktop) to enhance your AI-powered coding experience.

    Once connected via MCP (Model Context Protocol), ChatGPT can leverage AI Architect's deep contextual understanding of your project, enabling more accurate code suggestions, explanations, and code insights.

    circle-info

    Note: This guide covers setup for both the web interface (chat.openai.com) and the ChatGPT desktop app. The configuration is identical for both platforms.

    Interaction diagram

    Visualize code changes and their impact with automated sequence diagrams.

    The Interaction Diagram is a visual feature in Bito's that automatically generates sequence diagrams to help you quickly understand the impact of code changes in your pull requests.

    This diagram visualizes how different components of your code interact with each other, making code reviews faster and more intuitive.

    hashtag

    Install/run via CLI

    CLI mode is best suited for immediate, one-time code reviews.

    1. Prerequisites: Before proceeding, ensure you've completed all necessary AI Code Review Agent.

    2. Start Docker: Ensure Docker is running on your machine.

    3. Repository Download:

    Overview

    Get instant feedback on your code changes directly within your code editor.

    Unlock the power of AI-driven code reviews in VS Code, Cursor, Windsurf, and all JetBrains IDEs (including IntelliJ IDEA, PyCharm, WebStorm, and more) with Bito's . This tool provides real-time, human-like feedback on your code changes, catching common issues before you submit a pull request.

    The AI Code Review Agent helps you improve your code as you develop, so you don't have to wait for days to get feedback. This accelerates development cycles, boosts team productivity, and ensures higher code quality.

    You can start using the Agent immediately—no setup is required!

    linkarrow-up-right
    AI that understands your code

    Replace <Your-Bito-Workspace-ID> with your actual Bito workspace ID, which you can find after logging into your Bito account at alpha.bito.aiarrow-up-right

    What repositories are available in my organization?

    Under Available integrations, find Confluence and click Connect.

  • Click Authorize with your Confluence account. You will be redirected to Atlassian's site to grant Bito access to your Confluence workspace. This uses OAuth to securely link your Confluence content.

  • Sign in to your Atlassian account if prompted, then click Accept. After successful authorization, you will be returned to Bito.

  • 2

    hashtag
    Agent-specific settings

    After completing the initial setup, you can control Confluence integration on a per-agent basis:

    1. Go to the page in your Bito dashboard.

    2. Find the Agent instance you want to connect with Confluence and open its settings.

    3. Within the Agent settings screen, click on the .

    4. Locate the Functional validation option and enable it to enhance pull request validation by incorporating relevant context from linked Confluence pages.

    https://yourcompany.atlassian.net/wiki/x/AbCdE

    Conflict: A change contradicts another requirement (e.g., two requirements cannot both be satisfied by the current code).
  • Out‑of‑scope: The change is not in the requirements (the code change does not relate to any defined requirement).

  • For "Conflict" items: Describes why there is a contradiction between requirements and what might need to be resolved.
  • For "Out‑of‑scope" items: Explains why the change is considered outside the defined requirements.

  • Jira integration
    Manage integrationsarrow-up-right
    Manage integrationsarrow-up-right
    Functional Validation setting is enabled
    Indexing in progress:
    A project that is currently being indexed.
  • Indexing is paused: A project that was previously being indexed but is now paused for some reason. Generally, if you close the IDE while the project is being indexed, its status will change from "Indexing in progress" to "Indexing is paused".

  • Indexed: A project that has already been indexed, and Bito is ready to answer any questions about it.

  • A warning popup box will appear at the bottom of Bito's plugin pane. You can choose to click the "Delete" button to remove the project's index from your system, or click the "Cancel" button to go back.

  • Then, navigate to the "Manage repos" tab in the Bito plugin pane, where you should see the folder name listed under the "Current project" along with its size, indicating that it is not indexed. Since you have deleted the .bito folder, the "Other projects" section will no longer display any entries.

  • Finally, click on "Start Indexing" and it should begin indexing the folder.

  • indexed
    indexing

    Follow the AI Architect installation instructions. Upon successful setup, you will receive a Bito MCP URL and Bito MCP Access Token that you need to enter in your coding agent.

  • Download BitoAIArchitectGuidelines.md filearrow-up-right. You will need to copy/paste the content from this file later when configuring AI Architect.

    • Note: This file contains best practices, usage instructions, and prompting guidelines for the Bito AI Architect MCP server. The setup will work without this file, but including it helps AI tools interact more effectively with the Bito AI Architect MCP server.

  • Claude Desktop installed - Download and install Claude Desktop from claude.ai/downloadarrow-up-right if you haven't already.

  • Node.js 20.18.1 or higher - Required for the mcp-remote proxy

    • macOS:

    • Windows: Download from https://nodejs.org/arrow-up-right (download 20.x LTS)

    • Linux (Ubuntu/Debian):

    • Verify installation:

  • circle-info

    Note: Claude Desktop uses OAuth 2.1 authentication via the mcp-remote proxy, so you don't need to manually manage access tokens. Your email will be collected during the OAuth consent flow.

    hashtag
    Set up AI Architect

    Claude Desktop uses claude_desktop_config.json with the mcp-remote proxy for OAuth-enabled remote servers.

    Claude Desktop supports both local MCP servers and remote HTTP servers. For Bito AI Architect (a remote OAuth server), we use the mcp-remote proxy which handles the OAuth flow automatically.

    1

    hashtag
    Open configuration file

    hashtag
    macOS:

    1. Open Claude Desktop

    2. Click Claude menu → Settings → Developer tab

    3. Click Edit Config to open claude_desktop_config.json

    Or manually open: ~/Library/Application Support/Claude/claude_desktop_config.json

    hashtag
    Windows:

    1. Open Claude Desktop

    2. Click File → Settings → Developer tab

    3. Click Edit Config to open claude_desktop_config.json

    Or manually open: %APPDATA%\Claude\claude_desktop_config.json

    2

    hashtag
    Add AI Architect configuration

    Add the following to your claude_desktop_config.json:

    circle-info
    3

    hashtag
    Restart Claude Desktop

    1. Completely quit Claude Desktop (not just close the window)

    4

    hashtag
    Complete OAuth authorization

    On first use, mcp-remote will open your browser to complete OAuth:

    5

    hashtag
    Verify connection

    1. In Claude Desktop, click the "+" button at the bottom of the chat

    hashtag
    Troubleshooting Claude Desktop

    hashtag
    Server not appearing:

    1. Verify JSON syntax in config file

    2. Ensure Node.js 20+ is installed: node --version

    3. Check that npx is available: npx --version

    4. Fully quit and restart Claude Desktop

    hashtag
    OAuth flow not starting:

    1. Ensure your browser is set as default

    2. Allow pop-ups for the OAuth flow

    3. Check firewall settings

    hashtag
    "mcp-remote not found" error:

    • Ensure Node.js is in your PATH

    • Try running npx -y mcp-remote --help in terminal to verify it works

    hashtag
    Connection shows "Disconnected":

    • OAuth tokens may have expired - restart Claude Desktop to re-authorize

    • Check your internet connection

    • Verify the Workspace ID is correct

    AI Architect

    Support for GitHub, GitLab, and Bitbucket (cloud and self-hosted)

  • 10 complimentary pull request analyses

  • hashtag
    Who can use Test Mode?

    Test Mode is designed for first-time evaluators. You can access it when:

    • Your Bito account is on a trial subscription (or eligible for a trial, meaning you haven't used any trials before)

    • Your workspace has a clean slate (no previous Git repository connections)

    circle-info

    When you analyze your first pull request in Test Mode, Bito automatically activates your 14-day trial, giving you access to code review capabilities.

    hashtag
    Getting started

    1

    hashtag
    Log in to Bito

    Log in to Bito Cloudarrow-up-right with a fresh user account and create a new workspace

    2

    hashtag
    Access Test Mode

    • Click "Do a test code review" option at the bottom of the Git setup wizard

    3

    hashtag
    Enter pull request details

    1. Pull request URL

    4

    hashtag
    Start code review

    Click Do a test code review to start the AI code review.

    hashtag
    Test Mode dashboard

    After completing your first test review, you'll have access to a dashboard showing:

    • Number of test reviews remaining (out of 10 total)

    • History of analyzed pull requests

    • Quick-start button for new reviews

    hashtag
    Starting new test review

    To analyze another pull request, click "New code review" button in the upper-right corner of your review history table.

    hashtag
    Upgrading to full Git integration

    Once you've used all 10 test reviews, you'll need to complete full Git integration to continue using Bito's AI Code Review Agent.

    hashtag
    Why upgrade?

    Full Git integration unlocks powerful features not available in Test Mode:

    Advanced configuration:

    • Default branch settings: Customize which branch is used for code reviews

    • Custom guidelines: Define your own review rules and coding standards

    • Filters: Exclude draft PRs, files, or branches from review to focus on relevant code.

    • Tools: Enable additional checks, such as secret scanning.

    • Automation: Configure auto-reviews, batching, and summary settings

    • And much more.

    Unlimited reviews:

    • No review limits — analyze every pull request

    • Automatic reviews on new PRs

    • Incremental reviews on PR updates

    • Complete team analytics and insights

    hashtag
    How to upgrade

    From your Test Mode dashboard, click "Complete Git integration" and follow the setup wizard to connect your Git repositories.

    For detailed setup instructions, see:

    • Guide for GitHub

    • Guide for GitHub (Self-Managed)

    • Guide for GitLab

    hashtag
    FAQs

    Q: Can I use Test Mode if I've previously used Bito? A: Test Mode is only available to users who haven't previously used a trial and haven't set up Git integration in their workspace.

    Q: What happens after I use all 10 test reviews? A: You'll need to complete full Git integration to continue reviewing pull requests.

    Q: Can I test on private repositories? A: Yes, as long as your personal access token has the correct permissions to access the repository.

    Q: Does Test Mode work with self-hosted Git instances? A: Yes, Test Mode supports GitHub Enterprise, GitLab Self-Managed, and Bitbucket Server. You'll need to provide your Git domain URL and configure network access (whitelist Bito IP addresses) if needed.

    Q: Will my code be stored or used for training? A: No. Bito does not store your code, and your code is never used for AI model training. Learn more about our privacy and security practices.

    Q: What's the difference between Essential and Comprehensive review modes? A: Essential mode focuses on critical issues and completes faster, while Comprehensive mode provides deeper analysis with more detailed feedback. You can try both to see which fits your needs.

    AI Code Review Agent
    hashtag
    Prerequisites
    1. Follow the AI Architect installation instructions. Upon successful setup, you will receive a Bito MCP URL and Bito MCP Access Token that you need to enter in your coding agent.

      • Note: When using Bito AI Architect MCP with ChatGPT (Web), the Bito MCP URL must be publicly accessible. Localhost or private network URLs (for example, http://localhost or internal IP addresses) are not supported and will not work.

    2. . You will need to copy/paste the content from this file later when configuring AI Architect.

      • Note: This file contains best practices, usage instructions, and prompting guidelines for the Bito AI Architect MCP server. The setup will work without this file, but including it helps AI tools interact more effectively with the Bito AI Architect MCP server.

    3. A paid ChatGPT subscription - MCP connectors require one of the following:

      • ChatGPT Plus

      • ChatGPT Pro

    circle-info

    Note: Free tier accounts do not have access to MCP connectors.

    circle-info

    Note: Full MCP support (including write/modify actions) is available for Team, Enterprise, and Edu plans. Plus and Pro users have read/fetch permissions via Developer Mode.

    hashtag
    OAuth authentication

    ChatGPT uses OAuth 2.1 with PKCE for secure MCP server authentication via the Connectors feature in Developer Mode.

    How OAuth authentication works:

    1. You enable Developer Mode and add the MCP server URL in Connectors settings

    2. ChatGPT initiates an OAuth flow

    3. Your browser opens a consent page hosted by Bito

    4. You enter your email and approve the connection

    5. ChatGPT receives secure tokens automatically

    6. Your email is tracked for usage analytics (collected during OAuth consent)

    Benefits:

    • No manual token management

    • Secure browser-based authentication

    • Automatic token refresh

    • Email collected during consent (no separate header needed)

    hashtag
    Set up AI Architect

    1

    hashtag
    Enable Developer mode

    1. Go to chatgpt.comarrow-up-right (or open the ChatGPT desktop app) and sign in

    2. Click on your profile icon (bottom-left corner)

    3. Select Settings

    4. Go to Apps and Connectors (or just Connectors)

    5. Scroll down and click "Advanced Settings"

    6. Toggle "Developer Mode" to ON

    2

    hashtag
    Create Bito AI Architect Connector

    1. In the Connectors section, click "Create" or "+ Add Connector"

    3

    hashtag
    Complete OAuth authorization

    1. Click on the newly created BitoAIArchitect connector

    4

    hashtag
    Verify connection

    1. Return to ChatGPT Settings → Connectors

    5

    hashtag
    Using Bito AI Architect in ChatGPT

    Once connected, you can use BitoAIArchitect in several ways:

    hashtag
    Troubleshooting ChatGPT

    hashtag
    "Connectors" or Developer Mode option not visible:

    • Verify you have a paid ChatGPT subscription (Plus, Pro, Team, Enterprise, or Edu)

    • Free tier accounts do not have connector access

    • The feature may be rolling out gradually - check back later if recently subscribed

    hashtag
    OAuth authorization fails:

    • Ensure pop-ups are allowed for chatgpt.com

    • Check that your Workspace ID is correct

    • Verify your organization has OAuth enabled for the MCP server

    • Try using an incognito/private browser window

    hashtag
    "Error fetching OAuth configuration":

    • Verify the MCP server URL is correct and accessible

    • Ensure the server supports OAuth 2.1 with dynamic client registration

    • Check that code_challenge_methods_supported includes S256 in the authorization server metadata

    hashtag
    Connection shows "Error" or "Disconnected":

    • Click the connection and select "Reconnect"

    • OAuth tokens may have expired - re-authorize when prompted

    • Check if your Bito workspace is still active

    hashtag
    Tools not working in conversation:

    • Ensure the MCP connection shows "Connected" status

    • Try starting a fresh conversation

    • Explicitly mention "use BitoAIArchitect" in your prompt if tools don't activate automatically

    • Check that you're using the connector in a mode that supports tools (not all chat modes do)

    AI Architect
    How to enable
    1. Navigate to the Code Review > Repositoriesarrow-up-right dashboard.

    2. Click the Settings button next to the Agent instance you wish to modify.

    3. Under Review tab, enable the Generate interaction diagrams option.

    Once enabled, Bito will automatically post interaction diagrams during code reviews.

    hashtag
    Understanding sequence diagrams

    A sequence diagram is a type of visual diagram that shows how different parts of your system interact with each other over time.

    It illustrates the flow of operations by displaying the order in which methods are called and how data flows between different components.

    This makes it easy to trace the execution path of your code and understand dependencies between modules.

    hashtag
    Diagram components

    hashtag
    Boxes

    The main components in the diagram are displayed as boxes. The level of detail shown depends on the size of your code changes:

    • Small changes: Boxes may represent individual classes or functions with detailed interactions

    • Large changes: Boxes may represent higher-level abstractions for better readability

    Bito's AI automatically determines the appropriate level of detail based on your pull request.

    hashtag
    Labels and indicators

    Within boxes, you'll see labels that provide quick insights:

    Change type:

    Indicates what kind of modification was made to each module in your codebase.

    • 🟩 Added - New code introduced to the codebase. These are components, functions, or classes that didn't exist before this pull request.

    • 🔄 Updated - Existing code that has been modified. This indicates changes to the logic, behavior, or implementation of existing components.

    • Deleted - Code that has been removed from the codebase. These components are no longer present after this pull request is merged.

    Impact level:

    Shows the scope and significance of changes to help you prioritize your code review efforts.

    • Low - Minimal impact (● ○ ○)

      • Changes are localized and unlikely to affect other parts of the system. Safe to review with standard attention.

    • Medium - Moderate impact (● ● ○)

      • Changes affect multiple components or have moderate complexity. Requires careful review of interactions and side effects.

    • High - Significant impact (● ● ●)

      • Changes are extensive or critical, affecting core functionality or multiple system areas. Demands thorough review and testing.

    These visual indicators help you identify critical changes at a glance.

    hashtag
    Arrows and flow

    Solid arrows (→): Represent forward calls flowing left to right

    • Example: If main() calls UserService, a solid arrow points from main() to UserService

    Dotted arrows (⇢): Represent return flows going right to left

    • Example: When UserService returns data to main(), a dotted arrow points back from UserService to main()

    Circular arrows (↻): Indicate internal calls within the same module

    • Example: One component of UserService calling another component within UserService

    hashtag
    Control flow blocks

    Alt block (if-else logic)

    • Displayed as a dotted box around multiple lines

    • Contains two sections separated by a dotted line representing "if" and "else" branches

    • Shows conditional execution paths in your code

    Opt block (optional parameters)

    • Used for functions with parameter overloading

    • Contains a single section for optional execution flow

    • Represents code that may or may not execute depending on optional parameters

    Code outside these blocks represents the normal execution flow.

    hashtag
    Platform-specific behavior

    hashtag
    GitHub

    • Diagrams are posted in Mermaid format

    • Interactive controls available:

      • Pan (move top, bottom, left, right)

      • Expand/collapse

      • Zoom in/out

    hashtag
    GitLab

    • Diagrams are posted in Mermaid format

    • Note: For very large diagrams, GitLab may not render automatically. You'll see a notice box with a "Display" button - click it to manually render the diagram

    hashtag
    Bitbucket

    • Diagrams are posted as image format

    circle-info

    Note: If you see a "syntax error" or "unable to render" message, try refreshing the page.

    hashtag
    Incremental reviews

    When you run incremental reviews (for example, by using the /review command in pull request comments), the existing interaction diagram will be updated rather than creating a new comment with a separate diagram.

    hashtag
    Interaction diagram vs impact analysis diagram

    Bito can generate two types of diagrams, but only one is displayed at a time:

    • Interaction diagram: Generated by the standard Code Review Agent, focusing on code changes in the current pull request

    • Impact analysis diagram: Generated using Bito AI Architect with complete cross-repository codebase understanding.

      • Note: This feature is not publicly available yet. Please contact Bito at [email protected]envelope to have it enabled for your account.

    circle-info

    Note: If both Impact Analysis and Interaction Diagram are enabled, only the Impact Analysis diagram will be shown.

    hashtag
    Best practices

    • Review the diagram before diving into code details to get a high-level understanding

    • Use impact indicators to prioritize which changes need closer examination

    • Follow the arrow flows to understand the execution path

    • Pay special attention to "High" impact modules

    hashtag
    Troubleshooting

    • Diagram not appearing: Verify that "Generate interaction diagrams" is enabled in Bito Cloudarrow-up-right settings

    • Rendering issues:

      • In GitLab, you may need to click the Display button to manually render the diagram.

      • Refresh the page - this often resolves transient rendering errors.

    • Syntax errors: In some cases, the Mermaid diagram may contain syntax errors that prevent it from rendering. Try updating the pull request so the diagram is regenerated.

    AI Code Review Agent
    Interaction diagram by Bito
    Interaction Diagram by Bito
    GitHub repository to your machine.
  • Extract and Navigate:

    • Extract the downloaded .zip file to a preferred location.

    • Navigate to the extracted folder and then to the “cra-scripts” subfolder.

    • Note the full path to the “cra-scripts” folder for later use.

    1. Open Command Line:

      • Use Bash for Linux and macOS.

      • Use PowerShell for Windows.

    2. Set Directory:

      • Change the current directory in Bash/PowerShell to the “cra-scripts” folder.

      • Example command: cd [Path to cra-scripts folder]

      • Adjust the path based on your extraction location.

    1. Configure Properties:

      • Open the bito-cra.properties file in a text editor from the “cra-scripts” folder. Detailed information for each property is provided on Agent Configuration: bito-cra.properties File page.

      • Set mandatory properties:

        • mode = cli

        • pr_url

        • bito_cli.bito.access_key

        • git.provider

        • git.access_token

    circle-info

    Note: Valid values for git.provider are GITHUB, GITLAB, or BITBUCKET.

    • Optional properties (can be skipped or set as needed):

      • git.domain

      • code_feedback

      • static_analysis

      • dependency_check

      • dependency_check.snyk_auth_token

      • review_scope

      • exclude_branches

      • exclude_files

      • exclude_draft_pr

    circle-info

    Note: Detailed information for each property is provided on Agent Configuration: bito-cra.properties File page.

    circle-info

    Check the Required Access Tokens guide to learn more about creating the access tokens needed to configure the Agent.

    1. Run the Agent:

      • On Linux/macOS in Bash: Run ./bito-cra.sh bito-cra.properties

      • On Windows in PowerShell: Run ./bito-cra.ps1 bito-cra.properties

    circle-info

    This step might take time initially as it pulls the Docker image and performs the code review.

    1. Final Steps:

      • The script may prompt values of mandatory/optional properties if they are not preconfigured.

      • Upon completion, a code review comment is automatically posted on the Pull Request specified in the pr_url property.

    circle-info

    Note: To improve efficiency, the AI Code Review Agent is disabled by default for pull requests involving the "main" branch. This prevents unnecessary processing and token usage, as changes to the "main" branch are typically already reviewed in release or feature branches. To change this default behavior and include the "main" branch, please contact supportenvelope.

    hashtag
    Screenshots

    hashtag
    Screenshot # 1

    circle-info

    AI-generated pull request (PR) summary

    hashtag
    Screenshot # 2

    circle-info

    Changelist showing key changes and impacted files in a pull request.

    Changelist in AI Code Review Agent's feedback.

    hashtag
    Screenshot # 3

    circle-info

    AI code review feedback posted as comments on the pull request.

    prerequisites for self-hosted
    Download the AI Code Review Agentarrow-up-right
    hashtag
    Prerequisites
    1. Install the latest Bito IDE extension for VS Codearrow-up-right, JetBrainsarrow-up-right, Cursorarrow-up-right, or Windsurfarrow-up-right.

    2. A workspace subscribed to the Bito Team Plan. Read documentation on how to upgrade.

    circle-info

    Get a 14-day FREE trial of Bito's AI Code Review Agent.arrow-up-right

    1. The root of your project must use a supported Version Control System such as Git, Perforce, or SVN, and be opened in the supported IDE.

    hashtag
    How to use the Agent in IDE?

    1. Open the Bito IDE extension.

    2. Login to your workspace subscribed to the Bito Team Plan.

    3. Type @codereview in the chat box to open a menu and select from the following actions:

      • localchanges: Review only the changes you’ve made in your local workspace that haven’t been staged yet. This is useful for quickly checking your current edits before moving them forward.

      • stagedchanges: Review the changes you’ve staged in Git but haven’t committed yet. This helps ensure only clean, well-reviewed updates get committed.

      • uncommittedchanges: Review all modifications that exist locally but aren’t yet committed—both staged and unstaged. Ideal for a full review of your current working directory.

      • path: Review a specific file or multiple files by providing their paths. This allows you to target critical files without running a review across your entire project.

      • commitId: Review one commit or a range of commits by referencing their commit IDs. Perfect for validating code history, checking incremental updates, or reviewing PR-related commits.

    circle-info

    Supported review options based on your Version Control System (VCS):

    • If your project uses Git, all five review options are available.

    • If your project uses a non-Git VCS (e.g., Perforce, SVN), only two review options are available:

      • uncommittedchanges

      • path

      Unsupported options will be hidden automatically.

    1. After that, choose between Essential and Comprehensive review modes:

      • In Essential mode, only critical issues are posted.

      • In Comprehensive mode, Bito also includes minor suggestion and potential nitpicks.

    2. Submit to get the code review feedback.

    hashtag
    Start code review from context menu

    You can also invoke the AI Code Review Agent directly from the context menu by right-clicking in the code editor and selecting commands under the "Bito Code Review Agent" menu.

    This provides faster, on-the-go access to code reviews right where you work.

    hashtag
    Reviewing the feedback

    Once the AI code review is complete, you'll receive a notification in the IDE. You can view the feedback in the Bito Panel, which includes a list of issues and their fixes.

    Each item will contain the following details:

    • Issue description: Description of the identified issue.

    • Fix description: Recommended approach or steps to resolve the issue.

    • File path: The file containing the issue.

    • Code suggestion: The AI-generated code fix for the issue.

    circle-info

    Each code suggestion includes an Apply button. Click it to open the diff view, where you can review the changes and choose to accept or undo them.

    hashtag
    Code review session history

    To view past code reviews, click the Session history icon in the top-right corner of the Bito Panel. This opens the Session history tab, which lists all your previous code review sessions.

    From the list, click any session to open it and view the complete code review details along with the AI suggestions.

    AI Code Review Agent
    Install on VS Code
    Install on JetBrains
    Install on Cursor
    Install on Windsurf

    CPU Cores

    4

    RAM

    8 GB

    Hard Disk Drive

    80 GB

    Linux

    You will need:

    1. Bash (minimum version 4.x)

      • For Debian and Ubuntu systems

        sudo apt-get install bash

      • For CentOS and other RPM-based systems

        sudo yum install bash

    1. Docker (minimum version 20.x)

    macOS

    You will need:

    1. Bash (minimum version 4.x)

      brew install bash

    1. Docker (minimum version 20.x)

    Windows

    You will need:

    1. PowerShell (minimum version 5.x)

      • View Guidearrow-up-right

      • Note: In PowerShell version 7.x, run Set-ExecutionPolicy Unrestricted command. It allows the execution of scripts without any constraints, which is essential for running scripts that are otherwise blocked by default security settings.

    1. Docker (minimum version 20.x)

    View Guide
    View Guidearrow-up-right
    View Guidearrow-up-right
    View Guidearrow-up-right
    GitHub Personal Access Token (Classic)
    GitLab Personal Access Token
    Watch demo videoarrow-up-right
    Watch demo videoarrow-up-right
    See the installation instructions
    See the installation instructions
    Example: Bito’s AI Code Review Agent
    View Guide

    Quick MCP integration with AI coding agents

    Connect Bito's AI Architect to your AI coding tools (Cursor, Claude Code, Windsurf, etc.) in seconds with our automated installer

    hashtag
    Prerequisites

    Before running the installer, have these ready:

    1. Your Bito Workspace ID (or full Bito MCP URL for self-hosted instances)

    2. Your Bito MCP Access Token

    circle-info

    Note: For self-hosted instances, follow the . Upon successful setup, you will receive a Bito MCP URL and Bito MCP Access Token that you need to enter.

    1. Your email ID (for tracking/identification)

    2. At least one supported tool installed:

      • Claude Code

    circle-info

    Note: For , , and you'll need to follow the manual setup process as they require OAuth authentication through your browser.

    hashtag
    Installation guide

    Our automated installer will prompt you for credentials and automatically configure all supported AI tools available on your system.

    hashtag
    macOS / Linux

    Open your terminal and run:

    hashtag
    Windows

    Open PowerShell (not Command Prompt) and run:

    circle-info

    Note: When using a self-hosted AI Architect, ensure that the MCP server is up and running before proceeding with the setup. The setup will fail if MCP is not running.

    hashtag
    What happens next

    1. The installer starts and checks for compatible tools

    2. You'll be prompted to enter your credentials.

    3. Automatic configuration - All detected tools are configured

    hashtag
    After installation

    1

    hashtag
    Restart your AI tool

    After the installer completes, completely close and reopen your IDE(s) to ensure the configuration takes effect.

    2

    hashtag
    Uninstalling

    To remove Bito AI Architect from all tools:

    hashtag
    macOS / Linux

    Open your terminal and run:

    hashtag
    Windows

    Open PowerShell (not Command Prompt) and run:

    hashtag
    Need manual setup?

    If you prefer to configure tools individually or need to set up web-based tools (Claude.ai, ChatGPT), refer to our detailed integration guides:

    hashtag
    Troubleshooting

    hashtag
    Installer issues

    "Command not found" or similar errors:

    • Verify you're using the correct shell (bash for macOS/Linux, PowerShell for Windows)

    • Check your internet connection

    • Try running the command again

    No tools detected:

    • Ensure your AI tools are installed before running the installer

    • The installer only configures tools it can detect on your system

    • You can run the installer again after installing new tools

    hashtag
    Connection issues

    • Verify Bito MCP URL and Bito MCP Access Token are correct.

    • Test endpoint with MCP protocol:

    circle-info

    Note:

    • Replace <Your-Bito-MCP-URL> with the Bito MCP URL you received after completing the AI Architect setup.

    Server not appearing after install:

    • Completely restart your AI tool (don't just reload)

    • Verify your credentials were entered correctly

    • Check that you have the minimum required versions (see below)

    hashtag
    Minimum requirements

    Some tools require specific versions:

    • Node.js 20.18.1+ for Claude Desktop, VS Code, and JetBrains

    • VS Code 1.99+ with Agent Mode enabled

    • JetBrains 2025.1+ with AI Assistant plugin 251.26094.80.5+

    Check Node.js version:

    If you need to install or update Node.js, visit

    Guide for Windsurf

    Integrate Windsurf with AI Architect for more accurate, codebase-aware AI assistance.

    Use Bito's AI Architect with Windsurf to enhance your AI-powered coding experience.

    Once connected via MCP (Model Context Protocol), Windsurf can leverage AI Architect’s deep contextual understanding of your project, enabling more accurate code suggestions, explanations, and code insights.

    hashtag
    Quick setup (recommended)

    Want to get started faster? We offer an automated installer that can configure AI Architect for all your AI coding tools in just a few seconds.

    The automated setup will:

    • Detect all compatible AI tools installed on your system

    • Configure them automatically with your credentials

    • Save you time by eliminating manual configuration steps

    👉 for automated setup.

    hashtag
    Manual setup

    If you prefer manual configuration, follow the step-by-step instructions below.

    hashtag
    Prerequisites

    1. Follow the . Upon successful setup, you will receive a Bito MCP URL and Bito MCP Access Token that you need to enter in your coding agent.

    2. . You will need to copy/paste the content from this file later when configuring AI Architect.

      • Note: This file contains best practices, usage instructions, and prompting guidelines for the Bito AI Architect MCP server. The setup will work without this file, but including it helps AI tools interact more effectively with the Bito AI Architect MCP server.

    hashtag
    Set up AI Architect

    Follow the setup instructions for your operating system:

    hashtag
    Windows

    1

    hashtag
    Create Windsurf config directory

    1. Press Win + R

    hashtag
    macOS/Linux

    1

    hashtag
    Create Windsurf config directory

    2

    hashtag
    Troubleshooting Windsurf

    hashtag
    Server not showing:

    hashtag
    Connection errors:

    • Verify Bito MCP URL and Bito MCP Access Token are correct.

    • Test endpoint with MCP protocol:

    circle-info

    Note:

    • Replace <Your-Bito-MCP-URL> with the Bito MCP URL you received after completing the AI Architect setup.

    • Check Settings → Cascade → MCP Servers for error messages.

    Guide for Junie (JetBrains)

    Integrate Junie (JetBrains) with AI Architect for more accurate, codebase-aware AI assistance.

    Use Bito's AI Architect with Junie (JetBrains) to enhance your AI-powered coding experience.

    Once connected via MCP (Model Context Protocol), Junie can leverage AI Architect’s deep contextual understanding of your project, enabling more accurate code suggestions, explanations, and code insights.

    hashtag
    Quick setup (recommended)

    Want to get started faster? We offer an automated installer that can configure AI Architect for all your AI coding tools in just a few seconds.

    The automated setup will:

    • Detect all compatible AI tools installed on your system

    • Configure them automatically with your credentials

    • Save you time by eliminating manual configuration steps

    👉 for automated setup.

    hashtag
    Manual setup

    If you prefer manual configuration, follow the step-by-step instructions below.

    hashtag
    Prerequisites

    1. Follow the . Upon successful setup, you will receive a Bito MCP URL and Bito MCP Access Token that you need to enter in your coding agent.

    2. . You will need to copy/paste the content from this file later when configuring AI Architect.

      • Note: This file contains best practices, usage instructions, and prompting guidelines for the Bito AI Architect MCP server. The setup will work without this file, but including it helps AI tools interact more effectively with the Bito AI Architect MCP server.

    hashtag
    Set up AI Architect

    Junie has the same setup process across all platforms (Windows, macOS, Linux, WSL).

    1

    hashtag
    Access Junie MCP settings

    1. Open your JetBrains IDE (IntelliJ, PyCharm, etc.)

    hashtag
    Troubleshooting

    hashtag
    Junie not showing BitoAIArchitect:

    1. Verify Node.js is installed: node --version

    2. Check mcp.json syntax (must be valid JSON)

    3. On Windows, ensure you're using cmd with /c

    hashtag
    Connection errors:

    1. Test the endpoint manually:

    circle-info

    Note:

    • Replace <Your-Bito-MCP-URL> with the Bito MCP URL you received after completing the AI Architect setup.

    1. Verify your Bito MCP URL and Bito MCP Access Token are correct

    2. Check firewall settings

    Guide for Bitbucket (Self-Managed)

    Integrate the AI Code Review Agent into your self-hosted Bitbucket workflow.

    Speed up code reviews by configuring the AI Code Review Agent with your Bitbucket (Self-Managed) server. In this guide, you'll learn how to set up the Agent to receive automated code reviews that trigger whenever you create a pull request, as well as how to manually initiate reviews using available commands.

    circle-info

    The Free Plan offers AI-generated pull request summaries to provide a quick overview of changes. For advanced features like line-level code suggestions, consider upgrading to the Team Plan. For detailed pricing information, visit our Pricingarrow-up-right page.

    hashtag
    Video tutorial

    hashtag
    Prerequisites

    Before proceeding, ensure you've completed all necessary prerequisites.

    hashtag
    1. Create a Bitbucket Personal Access Token:

    For Bitbucket pull request code reviews, a token with Project Admin permission is required. Make sure that the token is created by a Bitbucket user who has the Admin privileges.

    circle-info

    Important: Bito posts comments using the Bitbucket user account linked to the Personal Access Token used during setup. To display "Bito" instead of your name, create a separate user account (e.g., Bito Agent) and use its token for integration.

    You can use the Create Token button that appears once you provide the Hosted Bitbucket URL and your Bitbucket username.

    Or directly visit the URL of your self-hosted Bitbucket.

    To create a token for your user account:

    1. Go to Profile picture > Manage account > HTTP access tokens.

    2. Select Create token.

    3. Set the token name, permissions, and expiry.

    hashtag
    2. Authorizing a Bitbucket Personal Access Token for use with SAML single sign-on:

    If your Bitbucket organization enforces SAML Single Sign-On (SSO), you must authorize your Personal Access Token through your Identity Provider (IdP); otherwise, Bito's AI Code Review Agent won't function properly.

    For more information, please refer to .

    hashtag
    Installation and configuration steps

    Follow the step-by-step instructions below to install the AI Code Review Agent using Bito Cloud:

    hashtag
    Step 1: Log in to Bito

    and select a workspace to get started.

    hashtag
    Step 2: Open the Code Review Agents setup

    Click under the CODE REVIEW section in the sidebar.

    hashtag
    Step 3: Select your Git provider

    Bito supports integration with the following Git providers:

    • GitHub

    • GitHub (Self-Managed)

    • GitLab

    • GitLab (Self-Managed)

    Since we are setting up the Agent for Bitbucket (Self-Managed) server, select Bitbucket (Self-Managed) to proceed.

    hashtag
    Step 4: Connect Bito to Bitbucket

    To enable pull request reviews, you’ll need to connect your Bito workspace to your Bitbucket (Self-Managed) server.

    circle-info

    If your network blocks external services from interacting with the Bitbucket server, whitelist all of Bito's gateway IP addresses in your firewall to ensure Bito can access your self-hosted repositories. The Agent response can come from any of these IPs.

    • List of IP addresses to whitelist:

    You need to enter the details for the below mentioned input fields:

    • Hosted Bitbucket URL: This is the domain portion of the URL where your Bitbucket Enterprise server is hosted (e.g., https://bitbucket.mycompany.com). Please check with your Bitbucket administrator for the correct URL.

    • Bitbucket username: This is your Bitbucket username used for login. Please check it from your user profile page or ask your Admin.

    • Personal Access Token: Generate a Bitbucket Personal Access Token

    circle-info

    Important: Bito posts comments using the Bitbucket user account linked to the Personal Access Token used during setup. To display "Bito" instead of your name, create a separate user account (e.g., Bito Agent) and use its token for integration.

    Click Validate to ensure the token is functioning properly.

    If the token is successfully validated, click Connect Bito to Bitbucket to proceed.

    hashtag
    Step 5: Enable AI Code Review Agent on repositories

    After connecting Bito to your Bitbucket self-managed server, you'll see a list of repositories that Bito has access to.

    Use the toggles in the Code Review Status column to enable or disable the Agent for each repository.

    circle-info

    To customize the Agent’s behavior, you can edit existing configurations or create new Agents as needed.

    hashtag
    Step 6: Automated and manual merge request reviews

    Once a repository is enabled, you can invoke the AI Code Review Agent in the following ways:

    1. Automated code review: By default, the Agent automatically reviews all new pull requests and provides detailed feedback.

    2. Manually trigger code review: To initiate a manual review, simply type /review in the comment box on the pull request and submit it. This action will start the code review process.

    The AI-generated code review feedback will be posted as comments directly within your pull request, making it seamless to view and address suggestions right where they matter most.

    circle-info

    Note: To enhance efficiency, the automated code reviews are only triggered for pull requests merging into the repository’s default branch. This prevents unnecessary processing and Advanced AI requests usage.

    To review additional branches, you can use the . Bito will review pull requests when the source or target branch matches the list.

    The Include Source/Target Branches filter applies only to automatically triggered reviews. Users should still be able to trigger reviews manually via the /review command.

    circle-info

    The AI Code Review Agent automatically reviews code changes up to 5000 lines when a pull request is created. For larger changes, you can use the /review command.

    circle-info

    It may take a few minutes to get the code review posted as a comment, depending on the size of the pull request.

    hashtag
    Step 7: Specialized commands for code reviews

    Bito also offers specialized commands that are designed to provide detailed insights into specific areas of your source code, including security, performance, scalability, code structure, and optimization.

    • /review security: Analyzes code to identify security vulnerabilities and ensure secure coding practices.

    • /review performance: Evaluates code for performance issues, identifying slow or resource-heavy areas.

    By default, the /review command generates inline comments, meaning that code suggestions are inserted directly beneath the code diffs in each file. This approach provides a clearer view of the exact lines requiring improvement. However, if you prefer a code review in a single post rather than separate inline comments under the diffs, you can include the optional parameter: /review #inline_comment=False

    For more details, refer to .

    hashtag
    Step 8: Chat with AI Code Review Agent

    Ask questions directly to the AI Code Review Agent regarding its code review feedback. You can inquire about highlighted issues, request alternative solutions, or seek clarifications on suggested fixes.

    To start the conversation, type your question in the comment box within the inline suggestions on your pull request, and then submit it. Typically, Bito AI responses are delivered in about 10 seconds. On GitHub and Bitbucket, you need to manually refresh the page to see the responses, while GitLab updates automatically.

    Bito supports over 20 languages—including English, Hindi, Chinese, and Spanish—so you can interact with the AI in the language you’re most comfortable with.

    hashtag
    Step 9: Configure Agent settings

    let you control how reviews are performed, ensuring feedback is tailored to your team’s needs. By adjusting the options, you can:

    • Make reviews more focused and actionable.

    • Apply your own coding standards.

    • Reduce noise by excluding irrelevant files or branches.

    Using in JetBrains IDEs

    AI that understands your codebase in JetBrains IDEs (e.g., PyCharm)

    circle-info

    This feature is only available for our Team Plan. Visit the pricing pagearrow-up-right or billing documentation to learn more about our paid plans.

    1. Open your project’s folder using a JetBrains IDE. For this guide, we are using PyCharm.

    2. Bito uses AI to create an of your project’s codebase. It enables Bito to understand the code and provide relevant answers. There are three ways to start the indexing process:

      • When you open a new project, a popup box will appear through which Bito asks you whether you want to enable indexing of this project or not. Click on the “Enable” button to start the indexing process. You can also skip this step by clicking the “Maybe later” button. You can always index the project later if you want.

    • In the bottom-left of Bito plug-in pane, hover your mouse cursor over this icon. You can also enable indexing from here by clicking on the “Click to enable it” text.

    • Another option is to open the "Manage Repos" tab by clicking the laptop icon in the top-right corner of the Bito plugin pane.

    circle-info

    Bito usually takes around 12 minutes per each 10MB of code to understand your repo.

    circle-info

    Bito will still work correctly if you don’t enable indexing of your project. However, in that case, Bito will only be able to provide general answers.

    circle-info

    If you have previously indexed some projects using Bito then they will show in the “Other projects” section.

    circle-info

    Index building is aborted if the user logs out or if the user's subscription is canceled (downgraded from a paid plan to a free plan).

    1. Let’s start the indexing process by using any of the above-mentioned methods.

    2. The status will now be updated to “Indexing in progress...” instead of “Not Indexed”. You will also see the real-time indexing progress for the current folder, based on the number of files indexed.

    circle-info

    In case you close the JetBrains IDE (e.g., PyCharm) while the indexing is in progress then don’t worry. The indexing will be paused and will automatically continue from where it left off when you reopen the IDE. Currently, the indexing will resume 5-10 minutes after reopening the IDE.

    circle-info

    The progress indicator for the other folders is updated every 5 minutes.

    1. Once the indexing is complete, the status will be updated from “Indexing in progress...” to “Indexed”, and will look like this.

    2. Now you can ask any question regarding your codebase by adding the keyword "my code" to your AI requests in the Bito chatbox. Bito is ready to answer them!

    circle-info

    Example: in my code explain the file apiUser.js

    Additional keywords for various languages are listed on the page. Also, here are some .

    1. In case you ever want to delete an index then you can do that by clicking on this three dots button and then clicking the “Delete” button.

    circle-info

    Index deletion is allowed even if the index is in progress or in a paused state.

    1. A warning popup box will open in the bottom of Bito’s plugin pane. You can either click on the “Delete” button to delete the project’s index from your system or click on the “Cancel” button to go back.

    hashtag
    A Quick Example from a Real Project

    For the sake of this tutorial, we’ve created a clone of popular game “Wordle” using Python.

    Here’s how it looks:

    We have stored the list of words in files that are inside the “word_files” folder. A word is selected from these files randomly at the start of the game that the player has to guess.

    hashtag
    Question # 1

    Let’s ask Bito to understand my code and briefly write about what this game is all about and how to play it

    Bito correctly described the game by just looking at its source code.

    hashtag
    Question # 2

    Our game (PyWordle) is working fine, but there is no count down timer to make it a bit more challenging.

    So, let’s ask Bito to add this feature.

    Here’s the question I used:

    suggest code for main.py "class PyWordle" to add a count down timer for this game in my code. I'm using "self" in functions and variable names, so suggest the code accordingly. The player will lose the game if the time runs out. Set the time limit to 2 minutes (format like 02:00). The timer will start when the game starts. Also reset the timer when the game restarts, such as when player closes the "you won / you lost" popup. Display this real-time count down timer on the right-side of where the player score is displayed. Use the similar design as the player score UI. Also tell me exactly where to add your code. Make sure all of this functionality is working.

    Bito suggested the code which looks good. But, it was a bit incomplete and needs some improvements. So, I further asked a series of questions to Bito (one-by-one) to fix the remaining issues.

    After adding the code suggested by Bito, here's how the PyWordle game looks now. As you can see the countdown timer is accurately added where we want it to be added.

    Keyboard shortcuts

    Bito UI in Visual Studio Code and JetBrains IDEs is entirely keyboard accessible. You can navigate Bito UI with standard keyboard actions such as TAB, SHIFT+TAB, ENTER, and ESC keys. Additionally, you can use the following shortcuts for quick operations.

    The following video demonstrates important keyboard shortcuts.

    hashtag
    General

    Command
    Shortcuts

    hashtag
    Question & Answers

    The following keyboard shortcuts work after the Q/A block is selected.

    Command
    Keyboard Shortcut

    hashtag
    Change Default Keyboard Shortcuts

    Bito has carefully selected the keyboard shortcuts after thorough testing. However, it's possible that Bito selected key combination may conflict with IDE or other extensions shortcut. You can change the Bito default shortcut keys to avoid such conflicts.

    hashtag
    Visual Studio Code Editor

    1. To Open the Keyboards Shortcuts editor in VS Code, navigate to the menu under File > Preferences > Keyboard Shortcuts. (Code > Preferences > Keyboard Shortcuts on macOS)

    1. Search for default available commands, keybindings, or Bito extension-specific commands in VSCode keyboard shortcut editor.

    1. Finding a conflict in Key binding → Search for the key and take necessary action, e.g., Remove or Reset.

    1. Add a new key binding or map the existing Bito extension command. Provide the necessary information (Command ID) to add the new key binding.

    hashtag
    JetBrains

    JetBrains Document:

    1. File > settings > keymaps > configure keymaps

    1. Bito extension shortcuts can be overwritten by going into the File > Settings > Keymaps > configure keymaps > to the action you want to assign. It will also overwrite the Bito shortcut if there are conflicts.

    2. Bito extension keyboard shortcuts can be changed from the IntelliJ settings. File > Settings > Keymaps > configure keymaps > plugins > Bito > action you want to change by right click.

    3. Bito extension Keyboard shortcuts can be deleted from the IntelliJ settings. File > Settings > Keymaps > configure keymaps > plugins > Bito > action you want to delete by right click.

    Guide for GitHub

    Integrate the AI Code Review Agent into your GitHub workflow.

    Speed up code reviews by configuring the AI Code Review Agent with your GitHub repositories. In this guide, you'll learn how to set up the Agent to receive automated code reviews that trigger whenever you create a pull request, as well as how to manually initiate reviews using available commandsarrow-up-right.

    circle-info

    The Free Plan offers AI-generated pull request summaries to provide a quick overview of changes. For advanced features like line-level code suggestions, consider upgrading to the Team Plan. For detailed pricing information, visit our Pricingarrow-up-right page.

    hashtag
    Video tutorial

    hashtag
    Installation and configuration steps

    Follow the step-by-step instructions below to install the AI Code Review Agent using Bito Cloud:

    hashtag
    Step 1: Log in to Bito

    and select a workspace to get started.

    hashtag
    Step 2: Open the Code Review Agents setup

    Click under the CODE REVIEW section in the sidebar.

    hashtag
    Step 3: Select your Git provider

    Bito supports integration with the following Git providers:

    • GitHub

    • GitHub (Self-Managed)

    • GitLab

    • GitLab (Self-Managed)

    Since we are setting up the Agent for GitHub, select GitHub to proceed.

    This will redirect you to GitHub.

    hashtag
    Step 4: Install the Bito app for GitHub

    To enable pull request reviews, you need to install and authorize the Bito’s AI Code Review Agent app.

    On GitHub, select where you want to install the app.

    Grant Bito access to your repositories:

    • Choose All repositories to enable Bito for every repository in your account.

    • Or, select Only select repositories and pick specific repositories using the dropdown menu.

    circle-info

    Bito app uses these permissions:

    • Read access to metadata

    • Read and write access to code, issues, and pull requests

    Click Install & Authorize to proceed. Once completed, you will be redirected to Bito.

    hashtag
    Step 5: Enable AI Code Review Agent on repositories

    After connecting Bito to your GitHub account, you'll see a list of repositories that Bito has access to.

    Use the toggles in the Code Review Status column to enable or disable the Agent for each repository.

    circle-info

    To customize the Agent’s behavior, you can edit existing configurations or create new Agents as needed.

    hashtag
    Step 6: Automated and manual pull request reviews

    Once a repository is enabled, you can invoke the AI Code Review Agent in the following ways:

    1. Automated code review: By default, the Agent automatically reviews all new pull requests and provides detailed feedback.

    2. Manually trigger code review: To initiate a manual review, simply type /review in the comment box on the pull request and submit it. This action will start the code review process.

    The AI-generated code review feedback will be posted as comments directly within your pull request, making it seamless to view and address suggestions right where they matter most.

    circle-info

    Note: To enhance efficiency, the automated code reviews are only triggered for pull requests merging into the repository’s default branch. This prevents unnecessary processing and Advanced AI requests usage.

    To review additional branches, you can use the . Bito will review pull requests when the source or target branch matches the list.

    The Include Source/Target Branches filter applies only to automatically triggered reviews. Users should still be able to trigger reviews manually via the /review command.

    circle-info

    The AI Code Review Agent automatically reviews code changes up to 5000 lines when a pull request is created. For larger changes, you can use the /review command.

    circle-info

    It may take a few minutes to get the code review posted as a comment, depending on the size of the pull request.

    hashtag
    Step 7: Specialized commands for code reviews

    Bito also offers specialized commands that are designed to provide detailed insights into specific areas of your source code, including security, performance, scalability, code structure, and optimization.

    • /review security: Analyzes code to identify security vulnerabilities and ensure secure coding practices.

    • /review performance: Evaluates code for performance issues, identifying slow or resource-heavy areas.

    By default, the /review command generates inline comments, meaning that code suggestions are inserted directly beneath the code diffs in each file. This approach provides a clearer view of the exact lines requiring improvement. However, if you prefer a code review in a single post rather than separate inline comments under the diffs, you can include the optional parameter: /review #inline_comment=False

    For more details, refer to .

    hashtag
    Step 8: Chat with AI Code Review Agent

    Ask questions directly to the AI Code Review Agent regarding its code review feedback. You can inquire about highlighted issues, request alternative solutions, or seek clarifications on suggested fixes.

    To start the conversation, type your question in the comment box within the inline suggestions on your pull request, and then submit it. Typically, Bito AI responses are delivered in about 10 seconds. On GitHub and Bitbucket, you need to manually refresh the page to see the responses, while GitLab updates automatically.

    Bito supports over 20 languages—including English, Hindi, Chinese, and Spanish—so you can interact with the AI in the language you’re most comfortable with.

    hashtag
    Step 9: Configure Agent settings

    let you control how reviews are performed, ensuring feedback is tailored to your team’s needs. By adjusting the options, you can:

    • Make reviews more focused and actionable.

    • Apply your own coding standards.

    • Reduce noise by excluding irrelevant files or branches.

    hashtag
    Screenshots

    hashtag
    Screenshot # 1

    circle-info

    AI-generated pull request (PR) summary

    hashtag
    Screenshot # 2

    circle-info

    Changelist showing key changes and impacted files in a pull request.

    hashtag
    Screenshot # 3

    circle-info

    AI code review feedback posted as comments on the pull request.

    Using in Visual Studio Code

    AI that understands your codebase in VS Code

    circle-info

    This feature is only available for our Team Plan. Visit the pricing pagearrow-up-right or billing documentation to learn more about our paid plans.

    1. Open your project’s folder using Visual Studio Code.

    2. Bito uses AI to create an of your project’s codebase. It enables Bito to understand the code and provide relevant answers. There are three ways to start the indexing process:

      • When you open a new project, a popup box will appear through which Bito asks you whether you want to enable indexing of this project or not. Click on the “Enable” button to start the indexing process. You can also skip this step by clicking the “Maybe later” button. You can always index the project later if you want.

    • In the bottom-left of Bito plug-in pane, hover your mouse cursor over this icon. You can also enable indexing from here by clicking on the “Click to enable it” text.

    • Another option is to open the "Manage Repos" tab by clicking the laptop icon in the top-right corner of the Bito plugin pane.

    circle-info

    Bito usually takes around 12 minutes per each 10MB of code to understand your repo.

    circle-info

    Bito will still work correctly if you don’t enable indexing of your project. However, in that case, Bito will only be able to provide general answers.

    circle-info

    If you have previously indexed some projects using Bito then they will show in the “Other projects” section.

    circle-info

    Index building is aborted if the user logs out or if the user's subscription is canceled (downgraded from a paid plan to a free plan).

    1. Let’s start the indexing process by using any of the above-mentioned methods.

    2. The status will now be updated to “Indexing in progress...” instead of “Not Indexed”. You will also see the real-time indexing progress for the current folder, based on the number of files indexed.

    circle-info

    In case you close the VS Code while the indexing is in progress then don’t worry. The indexing will be paused and will automatically continue from where it left off when you reopen VS Code. Currently, the indexing will resume 5-10 minutes after reopening the IDE.

    circle-info

    The progress indicator for the other folders is updated every 5 minutes.

    1. Once the indexing is complete, the status will be updated from “Indexing in progress...” to “Indexed”, and will look like this.

    2. Now you can ask any question regarding your codebase by adding the keyword "my code" to your AI requests in the Bito chatbox. Bito is ready to answer them!

    circle-info

    Example: in my code explain the file apiUser.js

    Additional keywords for various languages are listed on the page. Also, here are some .

    1. In case you ever want to delete an index then you can do that by clicking on this three dots button and then clicking the “Delete” button.

    circle-info

    Index deletion is allowed even if the index is in progress or in a paused state.

    1. A warning popup box will open in the bottom of Bito’s plugin pane. You can either click on the “Delete” button to delete the project’s index from your system or click on the “Cancel” button to go back.

    hashtag
    A Quick Example from a Real Project

    For the sake of this tutorial, we’ve created a simple “Music Player using JavaScript”.

    Here’s how it looks:

    We have added a bunch of songs to this project. The song details like name, artist, image, and the music file name are stored in a file called music-list.js

    hashtag
    Question # 1

    Let’s ask Bito to list names of all song artists used in my code

    As you can see, Bito gave the correct answer by utilizing its understanding of our repository.

    Similarly, we can ask any coding-related question like find bugs, improve code, add new features, etc.

    hashtag
    Question # 2

    Our music player is working fine, but we don’t have any option to mute/unmute the song.

    Let’s ask Bito to add this feature.

    Here’s the question I used:

    In my code how can i add a button to mute and unmute the song? By default, set this button to unmute. Also, use the same design as existing buttons in UI.

    After adding the code suggested by Bito, here’s how the music player looks when it starts (unmuted).

    And when muted:

    Overview

    AI Code Reviews in CLI

    AI Code Reviews in CLI brings fast, intelligent code reviews directly to your terminal, helping you catch issues early — before they reach production.

    It analyzes your code changes using AI to provide instant feedback on:

    • Security vulnerabilities - Detects issues such as SQL injection, XSS, insecure authentication, and unsafe data handling.

    • Potential bugs - Identifies logic errors, edge cases, incorrect assumptions, and runtime-related issues.

    • Performance problems - Flags inefficient algorithms, unnecessary computations, memory-intensive patterns, and scalability risks.

    • Code quality & best practices - Improves readability, maintainability, and design by suggesting better patterns, structure, and conventions.

    Unlike traditional linters or static analyzers, the analysis is context-aware and explains why an issue matters and how to fix it.

    By reviewing changes as you work, it helps you improve code consistency and reliability across your projects.

    hashtag
    Perfect for Agentic coding workflows

    The CLI integrates seamlessly with AI coding agents like Cursor, Claude Code, Windsurf, and others. Simply tell your agent "review my changes" and it automatically runs the review, presents findings, and can even implement fixes for you.

    Stay in natural conversation while getting expert code analysis - no manual command typing or context switching required.

    hashtag
    Supported platforms

    hashtag
    Supported Operating Systems

    • Windows

    • macOS

    • Linux

    hashtag
    Source Code Management (SCM) compatibility

    Works seamlessly across a wide range of version control systems and workflows:

    • Git

    • Subversion (SVN)

    • Mercurial

    • Perforce

    This makes it suitable for both modern Git-based projects and legacy or enterprise codebases.

    hashtag
    Why use AI Code Reviews in CLI?

    hashtag
    Terminal-first by design

    Run reviews directly from your terminal — locally, over SSH, or in cloud environments — without pushing code or opening an IDE. This makes it ideal for remote servers, containers, and minimal development setups.

    hashtag
    Catch issues earlier (Shift Left)

    Review code:

    • Before committing

    • Before pushing

    • Before opening a pull request

    • As part of automated CI/CD checks

    Earlier feedback means fewer regressions, faster reviews, and lower cost of fixes.

    hashtag
    Precise control over what gets reviewed

    Review exactly what you want, when you want:

    • Uncommitted local changes

    • One or more recent commits

    • Specific files or directories

    • Differences against any branch, tag, or commit

    This flexibility makes it easy to integrate into both individual and team workflows.

    hashtag
    AI that understands context

    Instead of only matching rules, the AI analyzes intent and structure. It can:

    • Detect non-obvious bugs

    • Explain trade-offs

    • Suggest safer or cleaner alternatives

    • Adapt feedback based on surrounding code

    hashtag
    Fits seamlessly into existing workflows

    Use it as:

    • A pre-commit quality gate

    • A pre-push validation step

    • A CI/CD job that fails builds on critical issues

    hashtag
    How it fits into the broader Bito ecosystem

    AI Code Reviews in CLI complements other review surfaces by covering scenarios where IDEs or Git platforms are not ideal.

    Platform
    Best used for

    Use the CLI when you need:

    • Terminal-native workflows

    • Automation and scripting

    • Reviews in headless or remote environments

    • Fast feedback without opening an IDE or browser

    hashtag
    Key features

    hashtag
    Smart review modes & filtering

    Focus on what matters most at each stage of development:

    • Essential mode Shows only HIGH-severity issues — ideal for pre-commit or CI gates.

    • Comprehensive mode Includes all severity levels for deeper analysis.

    • Focus areas Limit reviews to specific concerns such as:

    hashtag
    Output formats for humans and automation

    Choose the format that fits your use case:

    • Interactive terminal UI Colorized, structured output optimized for developer review.

    • Plain text output Clean, deterministic output for logs and CI/CD systems.

    • Prompt-only mode Minimal output designed for AI agents or tool chaining.

    hashtag
    Interactive fix application

    Apply suggested fixes safely and efficiently:

    • Review each issue and its proposed change

    • Apply or skip fixes individually

    • Apply all remaining fixes in one step

    This enables faster iteration without losing control.

    hashtag
    Security & privacy

    • Reviews are run on-demand and scoped to selected files or changes

    • Designed to integrate safely into local, remote, and CI environments

    • No requirement to push code to a repository to get feedback

    hashtag
    Getting started

    Ready to start reviewing code from your terminal?

    👉 Visit the to get set up in minutes.

    Next steps:

    • – Run your first code review

    • – Complete reference of CLI commands

    • – Common issues and how to resolve them

    Guide for Cursor

    Integrate Cursor with AI Architect for more accurate, codebase-aware AI assistance.

    Use Bito's with Cursor to enhance your AI-powered coding experience.

    Once connected via MCP (Model Context Protocol), Cursor can leverage AI Architect’s deep contextual understanding of your project, enabling more accurate code suggestions, explanations, and code insights.

    hashtag
    Quick setup (recommended)

    Code review analytics

    Get in-depth insights into your code review process.

    The user-friendly dashboards help you track key metrics such as pull requests reviewed, issues found, lines of code reviewed, and understand individual contributions.

    This helps you identify trends and optimize your development workflow.

    Bito provides four distinct analytical views to help you understand your code review performance from multiple perspectives:

    Jira integration

    Bring Jira issue requirements into every pull request and get validation results back automatically.

    circle-info

    Note: The Jira integration is available on the .

    Bito integrates with Jira to automatically validate pull request code changes against linked Jira ticket requirements, helping ensure your implementations align with the specified requirements in those tickets.

    hashtag

    Guide for Bitbucket

    Integrate the AI Code Review Agent into your Bitbucket workflow.

    Speed up code reviews by configuring the with your Bitbucket repositories. In this guide, you'll learn how to set up the Agent to receive automated code reviews that trigger whenever you create a pull request, as well as how to manually initiate reviews using .

    circle-info

    The Free Plan offers AI-generated pull request summaries to provide a quick overview of changes. For advanced features like line-level code suggestions, consider upgrading to the Team Plan. For detailed pricing information, visit our page.

    AI code reviews in AI coding agents

    Supercharge AI coding agents with automated code reviews

    integrates seamlessly with AI coding agents like Cursor, Claude Code, Windsurf, and others, enabling natural language code reviews and automated fixes.

    hashtag
    Prerequisites

    Before you begin, make sure you have:

    Managing Index Size

    Exclude unnecessary files and folders from repo to index faster!

    hashtag
    What is Indexable Size?

    Indexable size is size of all code files, excluding following from the folder:

    • Directory/File based filtering

    How to install Bito extension on VS Code
    brew install node@20
    # Or use nvm: nvm install 20 && nvm use 20
    Repositoriesarrow-up-right
    Functional validation tab
    View Guidearrow-up-right
    View Guidearrow-up-right
    View Guidearrow-up-right

    Plain files (no SCM required)

    An interactive review tool during active development
  • Pre-commit/pre-push validation

  • Security

  • Performance

  • Bugs

  • Tests

  • Documentation

  • Severity filtering Display only high, medium, or low-priority findings as needed.

  • Automatic backups ensure changes are reversible

    AI Code Reviews in Git (GitHub, GitLab, Bitbucket)

    Pull request and merge request reviews

    AI Code Reviews in IDE (VS Code, JetBrains, Cursor, Windsurf)

    Real-time feedback while coding

    AI Code Reviews in CLI

    CI/CD automation, remote or terminal-only workflows, pre-commit checks

    Learn more
    Installation guide
    How to use?
    Available commands
    Troubleshooting

    ✅ Installed the CLI (Installation guide)

  • ✅ Configured your Bito API key (aka Bito Access Key)

  • ✅ A Git repository with code changes (committed or uncommitted)

  • hashtag
    Why use code review CLI with AI agents?

    AI coding agents are great at writing code, but they need expert guidance to catch security vulnerabilities, performance issues, and best practices violations. The AI Code Reviews in CLI provides that expertise.

    The power combination:

    • AI Code Reviews in CLI provides specialized code analysis

    • Your AI agent (Cursor, Claude Code, Windsurf, etc.) implements the fixes and iterates based on feedback

    • You stay in natural conversation, never leaving your workflow

    hashtag
    How it works

    1

    hashtag
    Configure your agent

    Add bitoreview command to your agent's rules file so it knows when and how to run code reviews. See the Setup guide section below for commands to set this up for your specific coding agent.

    2

    hashtag
    Ask for code reviews in natural language

    Simply tell your agent "review my changes" or "check for security issues"

    3

    hashtag
    Agent runs code review CLI Automatically

    Your agent executes the bitoreview command and reads the results

    4

    hashtag
    Get fixes implemented instantly

    Tell your agent which issues to fix, and it implements the changes automatically

    hashtag
    Setup guide

    The guidelines filearrow-up-right is a set of instructions that tells your AI coding agent (Claude Code, Cursor, etc.) how to correctly run bitoreview command when you ask it to do a code review. It defines the expected workflow, such as always using --prompt-only for structured JSON output, waiting for the review to complete before responding, grouping issues by severity, and validating problems in the actual code before suggesting fixes. Without these guidelines, the AI coding agent may not know how to use Bito's AI Code Reviews in CLI.

    To get started, you need to add the guidelines to your agent's rules file. Depending on your AI coding agent, this is either done automatically during installation, or manually per project using a simple command:

    hashtag
    Global configuration (auto-applied during install)

    During setup, the installer automatically adds the usage guidelines globally for the following AI coding agents if they are detected on your system:

    AI Coding Agent
    Guidelines file location

    Claude Code

    ~/.claude/CLAUDE.md

    Windsurf

    ~/.codeium/windsurf/memories/global_rules.md

    hashtag
    Project-level configuration (manual, per-project)

    For all other supported IDEs such as Cursor, VS Code (GitHub Copilot), Junie, and JetBrains AI Assistant, you need to add the guidelines manually inside each project directory where you want them to apply.

    Navigate to your project root, then run the relevant command:

    Cursor:

    • macOS / Linux:

    • Windows:

    Windsurf:

    • macOS / Linux:

    • Windows:

    VS Code (GitHub Copilot):

    • macOS / Linux:

    • Windows:

    Junie:

    • macOS / Linux:

    • Windows:

    JetBrains AI Assistant:

    • macOS / Linux:

    • Windows:

    Other agents: Check your agent's documentation for the custom rules/instructions file location, then copy and paste the sample guidelines content provided below directly into that file.

    AI Code Reviews in CLI
    cd /path/to/your/project
    curl -fsSL https://bitoreview.bito.ai/bito_cli_review_guidelines.md -o .cursorrules
    cd C:\path\to\your\project
    irm 'https://bitoreview.bito.ai/bito_cli_review_guidelines.md' | Out-File -FilePath .cursorrules
    cd /path/to/your/project
    mkdir -p .windsurf/rules
    curl -fsSL https://bitoreview.bito.ai/bito_cli_review_guidelines.md -o .windsurf/rules/bitoai-review.md
    cd C:\path\to\your\project
    New-Item -ItemType Directory -Path .windsurf\rules -Force
    irm 'https://bitoreview.bito.ai/bito_cli_review_guidelines.md' | Out-File -FilePath .windsurf\rules\bitoai-review.md
    cd /path/to/your/project
    mkdir -p .github
    curl -fsSL https://bitoreview.bito.ai/bito_cli_review_guidelines.md -o .github/copilot-instructions.md
    cd C:\path\to\your\project
    New-Item -ItemType Directory -Path .github -Force
    irm 'https://bitoreview.bito.ai/bito_cli_review_guidelines.md' | Out-File -FilePath .github\copilot-instructions.md
    cd /path/to/your/project
    mkdir -p .junie
    curl -fsSL https://bitoreview.bito.ai/bito_cli_review_guidelines.md -o .junie/guidelines.md
    cd C:\path\to\your\project
    New-Item -ItemType Directory -Path .junie -Force
    irm 'https://bitoreview.bito.ai/bito_cli_review_guidelines.md' | Out-File -FilePath .junie\guidelines.md
    cd /path/to/your/project
    mkdir -p .aiassistant/rules
    curl -fsSL https://bitoreview.bito.ai/bito_cli_review_guidelines.md -o .aiassistant/rules/bitoai-review.md
    cd C:\path\to\your\project
    New-Item -ItemType Directory -Path .aiassistant\rules -Force
    irm 'https://bitoreview.bito.ai/bito_cli_review_guidelines.md' | Out-File -FilePath .aiassistant\rules\bitoai-review.md
    # Code Review
    
    When user asks for code review, run `bitoreview` immediately with all required permissions needed to allow it to write files to its config.
    
    ## Do
    - Always use `--prompt-only` flag (JSON output for AI)
    - Generate a unique temp filename (e.g., using timestamp)
    - Use `tee` to save output to the temp file while running
    - Wait for command to complete before responding
    - Present clear summary grouped by severity
    - Validate issue against actual code before fixing
    
    ## Don't
    - Don't use hardcoded filenames (conflicts with parallel runs)
    - Don't respond before command completes
    - Don't run the review command twice
    - Don't show raw JSON output to user
    - Don't fix issues without validating first
    
    ## Two-Step Pattern
    1. Run `bitoreview review --prompt-only 2>&1 | tee <unique_temp_file>`
    2. Parse the JSON output and present summary to user
    
    Generate unique filename using timestamp or random value in the platform's temp directory.
    
    ## After Reading Output
    1. Quick sanity check (file exists, line numbers valid)
    2. Group issues by severity (high → medium → low)
    3. Present summary: file:line, issue title, suggested fix
    4. Show metrics (total issues, by severity)
    5. Offer to help fix issues
    
    ## Before Fixing Any Issue
    1. Read the actual code at the reported file:line
    2. Validate the issue exists in current code
    3. Verify suggested fix is appropriate
    4. Apply fix only if validated
    5. If invalid, explain why to user
    
    ## Modify Command By Intent
    - "quick" / "critical" → add `--mode essential`
    - "security" → add `--focus security`
    - "performance" → add `--focus performance`
    - "before PR" → add `--base main`
    - "specific file" → add file path
    - "uncommitted" → add `--type working`
    
    ## Flags Reference
    - `--prompt-only` — always use (JSON output for AI)
    - `--mode essential` — ~20% faster, critical issues only
    - `--focus` — security | performance | bugs | best-practices
    
    ## Timing
    ~2-10 min depending on changeset size. `--mode essential` is ~20% faster.
    
    ## Platform Note
    `tee` works on Linux, macOS, PowerShell, and Git Bash/WSL. Use platform-appropriate syntax if needed.
    • Replace <Your-Bito-MCP-URL> with the Bito MCP URL you received after completing the AI Architect setup.

      • For the Bito-hosted AI Architect, use the following URL format: https://mcp.bito.ai/<Your-Bito-Workspace-ID>/mcp

        Replace <Your-Bito-Workspace-ID> with your actual Bito workspace ID, which you can find after logging into your Bito account at

    If you already have other MCP servers configured, add BitoAIArchitect to the existing mcpServers object:

    circle-info
    • Replace <Your-Bito-MCP-URL> with the Bito MCP URL you received after completing the AI Architect setup.

      • For the Bito-hosted AI Architect, use the following URL format: https://mcp.bito.ai/<Your-Bito-Workspace-ID>/mcp

        Replace <Your-Bito-Workspace-ID> with your actual Bito workspace ID, which you can find after logging into your Bito account at

    Windows-specific configuration:

    On Windows, you may need to use the cmd wrapper:

    circle-info
    • Replace <Your-Bito-MCP-URL> with the Bito MCP URL you received after completing the AI Architect setup.

      • For the Bito-hosted AI Architect, use the following URL format: https://mcp.bito.ai/<Your-Bito-Workspace-ID>/mcp

        Replace <Your-Bito-Workspace-ID> with your actual Bito workspace ID, which you can find after logging into your Bito account at

    macOS: Claude menu → Quit Claude

  • Windows: Right-click system tray icon → Exit

  • Reopen Claude Desktop

  • The MCP server will start automatically

  • A browser window opens showing the Bito Authorization page
  • Review the requested permissions

  • Enter your email address (required for tracking)

  • Click "Authorize" or "Allow"

  • Return to Claude Desktop - the connection is now active

  • Select "Connectors" or look for the hammer/wrench icon

  • BitoAIArchitect should appear in the list

  • Try asking: "What repositories are available?"

  • Enter the complete URL of the pull request you want Bito to review.
    • Example: https://github.com/username/repository/pull/123

    1. Personal Access Token

      Generate a personal access token from your Git platform to authorize Bito to read the pull request:

      1. For GitHub:

        1. Create GitHub classic Token with repo access. Fine-grained tokens are not supported.

      2. For GitLab:

        1. Create GitLab token with api scope

      3. For Bitbucket:

        1. Depending on your Bitbucket setup, you may need one of the following:

          • For Bitbucket Cloud use API Token.

      4. For Self-managed GitHub, GitLab, and Bitbucket:

        If you're using self-managed Git instances (GitHub Enterprise, GitLab Self-Managed, or Bitbucket Server):

        1. Select your Git provider

        2. Enter your Git domain URL (e.g., https://bitbucket.example.com

    1. Validate your token

      Click "Validate" to verify that your personal access token is working correctly. This ensures Bito can access the pull request before proceeding.

    1. Choose your review depth

      Select the level of analysis you want:

      • Essential: Focuses on the most critical issues (faster review)

      • Comprehensive: Provides deeper analysis with more detailed feedback (more thorough review)

    circle-info

    Feel free to experiment with both approaches on different pull requests to find what works best for your needs.

    Guide for GitLab (Self-Managed)
    Guide for Bitbucket
    Guide for Bitbucket (Self-Managed)
    ChatGPT Team
  • ChatGPT Enterprise

  • ChatGPT Edu

  • Fill in the connector details:

    • Connector Name: BitoAIArchitect

    • Description: Repository intelligence and architecture analysis for your organization

    • MCP Server URL: <Your-Bito-MCP-URL>

    • Authentication: Select "OAuth"

    circle-info

    Note:

    • Replace <Your-Bito-MCP-URL> with the Bito MCP URL you received after completing the AI Architect setup.

      • For the Bito-hosted AI Architect, use the following URL format: https://mcp.bito.ai/<Your-Bito-Workspace-ID>/mcp

        Replace <Your-Bito-Workspace-ID> with your actual Bito workspace ID, which you can find after logging into your Bito account at

    1. Click "Create" or "Save"

    Click "Connect" to initiate the OAuth flow

  • A browser window opens showing the Bito Authorization page

  • Review the requested permissions

  • Enter your email address (required for tracking)

  • Click "Authorize" or "Allow"

  • Return to ChatGPT - the connection is now active

  • BitoAIArchitect should show as "Connected"

  • Start a new conversation

  • In the composer, click "Use Connectors" or look for the connector tools

  • Try asking:

  • Direct prompts: Ask questions about your repositories
  • Deep Research: BitoAIArchitect tools appear in "Deep Research" mode

  • Connectors menu: Select BitoAIArchitect from the "Use Connectors" option

  • Download BitoAIArchitectGuidelines.md filearrow-up-right
    Cursor
  • Windsurf

  • VS Code (GitHub Copilot)

  • Junie

  • JetBrains AI Assistant

  • Confirmation - You'll see which tools were successfully set up
    hashtag
    Verify AI architect connection

    Check that AI Architect appears in your tool's MCP server list:

    • Claude Code: Run claude mcp list

    • Cursor: Settings → MCP → Check server list

    • Windsurf: Settings → Cascade → MCP Servers

    • VS Code: Copilot Chat → Tools icon

    • Junie: Settings → Tools → Junie → MCP Settings

    • JetBrains AI Assistant: Settings → Tools → AI Assistant → Model Context Protocol

    3

    hashtag
    Add guidelines (optional but highly recommended)

    The BitoAIArchitectGuidelines.md filearrow-up-right contains best practices, usage instructions, and prompting guidelines for the Bito's AI Architect MCP server. Adding it to your project helps your AI coding agent interact with Bito's AI Architect more effectively and get better results out of every query.

    If you are on Claude Code or Windsurf, the installer automatically adds the guidelines file globally, covering all your projects. If you'd also like to apply guidelines at the project level for a specific project, run the relevant command below inside that project directory.

    If you are on Cursor, VS Code (GitHub Copilot), Junie, or JetBrains AI Assistant, guidelines are not configured automatically by the installer. Run the relevant command below manually inside each project directory where you want the guidelines to apply. This is a per-project step, so repeat it whenever you start working in a new project.

    To add Bito's AI Architect guidelines to your project, run the following commands based on your coding agent:

    Claude Code:

    Cursor:

    Windsurf:

    VS Code (GitHub Copilot):

    Junie:

    JetBrains AI Assistant:

    4

    hashtag
    Run a test query

    Open a chat or conversation in your AI tool and try a test query to confirm AI Architect is working:

    • "What repositories are available in my organization?"

    • "Show me all Python repositories"

    • "List the available tools"

    If you receive accurate responses about your codebase, the setup is complete!

    Cursor
  • Windsurf

  • GitHub Copilot (VS Code)

  • Junie

  • JetBrains AI Assistant

  • ChatGPT (Web & Desktop)

  • For the Bito-hosted AI Architect, use the following URL format: https://mcp.bito.ai/<Your-Bito-Workspace-ID>/mcp

    Replace <Your-Bito-Workspace-ID> with your actual Bito workspace ID, which you can find after logging into your Bito account at alpha.bito.aiarrow-up-right

  • Replace <Your-Bito-MCP-Access-Token> with the Bito MCP Access Token you received after completing the AI Architect setup.

  • AI Architect installation instructions
    Claude.ai (Web)
    Claude Desktop
    ChatGPT (Web & Desktop)
    Claude Code
    Claude Desktop
    Claude.ai (Web)
    nodejs.orgarrow-up-right

    Type: %USERPROFILE%\.codeium\windsurf

  • Press Enter

  • If the folders don't exist, create them:

    1. Open File Explorer

    2. Navigate to %USERPROFILE%

    3. Create folders: .codeium\windsurf

    2

    hashtag
    Create or edit mcp_config.json

    1. Open %USERPROFILE%\.codeium\windsurf\mcp_config.json in a text editor.

    2. If the file doesn't exist, create it with this content:

    circle-info

    Note:

    • Replace <Your-Bito-MCP-URL> with the Bito MCP URL you received after completing the AI Architect setup.

    1. If the file exists with other servers, add BitoAIArchitect to the mcpServers object:

    circle-info

    Note:

    • Replace <Your-Bito-MCP-URL> with the Bito MCP URL you received after completing the AI Architect setup.

    1. Save

    3

    hashtag
    Add guidelines (optional but highly recommended)

    The BitoAIArchitectGuidelines.md file contains best practices, usage instructions, and prompting guidelines for the Bito AI Architect MCP server.

    The setup will work without this file, but including it helps AI tools interact more effectively with the Bito AI Architect MCP server.

    hashtag
    Option A: Global guidelines (applies to all projects):

    Create directory:

    Copy the contents of your into global_rules.md file:

    hashtag
    Option B: Project-level guidelines (applies to specific project):

    In your project directory, create .windsurf\rules directory:

    Copy the contents of your into bitoai-architect.md file:

    circle-info

    Note: Windsurf Wave 8+ uses .windsurf\rules\*.md format for project-level rules. Global guidelines in ~/.codeium/windsurf/memories/global_rules.md are supported in all versions.

    4

    hashtag
    Restart Windsurf

    1. Close Windsurf completely

    2. Reopen Windsurf

    3. Open Settings → Cascade → MCP Servers

    4. Click "Refresh"

    5. Verify BitoAIArchitect appears with green status

    hashtag
    Create or edit mcp_config.json

    Add this content:

    circle-info

    Note:

    • Replace <Your-Bito-MCP-URL> with the Bito MCP URL you received after completing the AI Architect setup.

      • For the Bito-hosted AI Architect, use the following URL format: https://mcp.bito.ai/<Your-Bito-Workspace-ID>/mcp

        Replace <Your-Bito-Workspace-ID> with your actual Bito workspace ID, which you can find after logging into your Bito account at

    • Replace <Your-Bito-MCP-Access-Token> with the Bito MCP Access Token you received after completing the AI Architect setup.

    • Replace <Your-Email> with your actual email address.

    Save and exit (Ctrl+O, Enter, Ctrl+X)

    3

    hashtag
    Add guidelines (optional but highly recommended)

    The BitoAIArchitectGuidelines.md file contains best practices, usage instructions, and prompting guidelines for the Bito AI Architect MCP server.

    The setup will work without this file, but including it helps AI tools interact more effectively with the Bito AI Architect MCP server.

    hashtag
    Option A: Global guidelines (applies to all projects):

    Create directory:

    Copy the contents of your into global_rules.md file:

    hashtag
    Option B: Project-level guidelines (applies to specific project):

    In your project directory, create .windsurf/rules directory:

    Copy the contents of your into bitoai-architect.md file:

    circle-info

    Note: Windsurf Wave 8+ uses .windsurf/rules/*.md format for project-level rules. Global guidelines in ~/.codeium/windsurf/memories/global_rules.md are supported in all versions.

    4

    hashtag
    Restart Windsurf

    1. Close Windsurf completely

    2. Reopen Windsurf

    3. Open Settings → Cascade → MCP Servers

    4. Click "Refresh"

    5. Verify BitoAIArchitect appears with green status

    For the Bito-hosted AI Architect, use the following URL format: https://mcp.bito.ai/<Your-Bito-Workspace-ID>/mcp

    Replace <Your-Bito-Workspace-ID> with your actual Bito workspace ID, which you can find after logging into your Bito account at alpha.bito.aiarrow-up-right

  • Replace <Your-Bito-MCP-Access-Token> with the Bito MCP Access Token you received after completing the AI Architect setup.

  • Try our Quick MCP Integration Guide
    AI Architect installation instructions
    Download BitoAIArchitectGuidelines.md filearrow-up-right
    Windows
    macOS/Linux
  • Junie installed in a JetBrains IDE (IntelliJ IDEA, PyCharm, WebStorm, etc.)

  • Node.js 20.18.1+ installed (for mcp-remote proxy)

    1. Why Node.js 20+? The mcp-remote proxy depends on undici v7, which requires Node.js 20+ (needs the File global API added in Node 20.0.0). Node.js 18 and earlier will fail with ReferenceError: File is not defined.

    2. Verify:

    3. If Node.js is not installed or the version < 20 then

  • Go to: Settings (Ctrl/Cmd + Alt + S)

  • Navigate to: Tools → Junie → MCP Settings

  • Click the + (Add) button to open the global mcp.json configuration file in the editor, or manually edit the file as shown below

  • 2

    hashtag
    Configure BitoAIArchitect

    The global configuration file is located at:

    • macOS/Linux: ~/.junie/mcp/mcp.json

    • Windows: %USERPROFILE%\.junie\mcp\mcp.json

    macOS/Linux configuration:

    circle-info

    Note:

    • Replace <Your-Bito-MCP-URL> with the Bito MCP URL you received after completing the AI Architect setup.

    Windows configuration (IMPORTANT - uses cmd /c):

    circle-info

    Note:

    • Replace <Your-Bito-MCP-URL> with the Bito MCP URL you received after completing the AI Architect setup.

    3

    hashtag
    Save and restart

    1. Save the mcp.json file

    2. Close all JetBrains IDE windows

    3. Reopen your IDE

    4

    hashtag
    Verify connection

    1. Go to: Settings → Tools → Junie → MCP Settings

    2. Check that BitoAIArchitect appears in the server list

    3. Status should show as Connected or Running

    5

    hashtag
    Add guidelines (optional but highly recommended)

    The BitoAIArchitectGuidelines.md file contains best practices, usage instructions, and prompting guidelines for the Bito AI Architect MCP server.

    The setup will work without this file, but including it helps AI tools interact more effectively with the Bito AI Architect MCP server.

    To add Bito AI Architect usage guidelines to a specific project:

    1. Navigate to your project root

    2. Create .junie directory:

      Copy the contents of your into .junie/guidelines.md file:

    What Junie guidelines should contain:

    • BitoAIArchitect MCP usage best practices

    • When to query repository information

    • How to search for dependencies and tech stacks

    argument
  • Restart the IDE completely

  • For the Bito-hosted AI Architect, use the following URL format: https://mcp.bito.ai/<Your-Bito-Workspace-ID>/mcp

    Replace <Your-Bito-Workspace-ID> with your actual Bito workspace ID, which you can find after logging into your Bito account at alpha.bito.aiarrow-up-right

  • Replace <Your-Bito-MCP-Access-Token> with the Bito MCP Access Token you received after completing the AI Architect setup.

  • Try our Quick MCP Integration Guide
    AI Architect installation instructions
    Download BitoAIArchitectGuidelines.md filearrow-up-right

    Bitbucket

  • Bitbucket (Self-Managed)

  • 18.188.201.104
  • 3.23.173.30

  • 18.216.64.170

  • with
    Project Admin
    permission in your Bitbucket (Self-Managed) account. Ensure you have Bitbucket
    Admin
    privileges. Enter the token into the
    Personal Access Token
    input field. You can use the
    Create Token
    button that appears once you provide the
    Hosted Bitbucket URL
    and your
    Bitbucket username
    .

    For guidance, refer to the instructions in the Prerequisites section.

    /review scalability
    : Assesses the code's ability to handle increased usage and scale effectively.
  • /review codeorg: Scans for readability and maintainability, promoting clear and efficient code organization.

  • /review codeoptimize: Identifies optimization opportunities to enhance code efficiency and reduce resource usage.

  • Add extra checks to improve code quality and security.
    Get a 14-day FREE trial of Bito's AI Code Review Agent.arrow-up-right
    View Bitbucket documentation
    Bitbucket SAML SSO documentationarrow-up-right
    Log in to Bito Cloudarrow-up-right
    Repositoriesarrow-up-right
    Learn more
    Include Source/Target Branches filter
    Available Commands
    Agent settings
    Learn more
  • From here you can start the indexing process by clicking on the “Start Indexing” button given in front of your current project. Here, you will also see the total indexable size of the repository. Read more about What is Indexable Size?arrow-up-right

  • index
    Available Keywords
    Example Questions

    Regenerate the answer

    CTRL + L

    Modify the prompt for the selected Q&A. Bito copies the prompt in the chatbox that you can modify as needed.

    CTRL + U

    Open Bito Panel: Toggle Bito Panel on and off in the JetBrains IDE. In the Visual Studio Code, the shortcut opens the Bito panel if not already opened.

    SHIFT + CTRL + O

    Puts cursor in the chatbox when Bito panel is in focus.

    SPACEBAR (Or start typing your question directly)

    Execute the chat command

    ENTER

    Add a new line in the chatbox

    CTRL + ENTER or SHIFT + ENTER

    Modify the most recently executed prompt. This copies the last prompt in the chatbox for any edits.

    CTRL + M

    Expands and Collapse the "Shortcut" panel

    WINDOWS: CTRL + ⬆️ / ⬇️ MAC: CTRL + SHIFT+ ⬆️ / ⬇️

    Navigate between the Questions/Answers block.

    Note: You must select the Q/A container with TAB/SHIFT+TAB.

    ⬆️ / ⬇️

    Copy the answer to the clipboard.

    CTRL + C

    Insert the answer in the code editor

    CTRL + I

    Toggle the diff view (when Diff View is applicable)

    CTRL + D

    Expand/Collapse the code block in the question.

    WINDOWS: CTRL + ⬆️ / ⬇️ MAC: CTRL + SHIFT+ ⬆️ / ⬇️

    https://www.jetbrains.com/help/idea/configuring-keyboard-and-mouse-shortcuts.htmlarrow-up-right

    Bitbucket

  • Bitbucket (Self-Managed)

  • Read access to organization members

    /review scalability
    : Assesses the code's ability to handle increased usage and scale effectively.
  • /review codeorg: Scans for readability and maintainability, promoting clear and efficient code organization.

  • /review codeoptimize: Identifies optimization opportunities to enhance code efficiency and reduce resource usage.

  • Add extra checks to improve code quality and security.
    Get a 14-day FREE trial of Bito's AI Code Review Agent.arrow-up-right
    Log in to Bito Cloudarrow-up-right
    Repositoriesarrow-up-right
    Learn more
    Include Source/Target Branches filter
    Available Commandsarrow-up-right
    Agent settings
    Learn more
    Changelist in AI Code Review Agent's feedback.
  • From here you can start the indexing process by clicking on the “Start Indexing” button. Here, you will also see the total indexable size of the repository. Read more about What is Indexable Size?arrow-up-right

  • index
    Available Keywords
    Example Questions
    Want to get started faster? We offer an automated installer that can configure AI Architect for all your AI coding tools in just a few seconds.

    The automated setup will:

    • Detect all compatible AI tools installed on your system

    • Configure them automatically with your credentials

    • Save you time by eliminating manual configuration steps

    👉 Try our Quick MCP Integration Guide for automated setup.

    hashtag
    Manual setup

    If you prefer manual configuration, follow the step-by-step instructions below.

    hashtag
    Prerequisites

    1. Follow the AI Architect installation instructions. Upon successful setup, you will receive a Bito MCP URL and Bito MCP Access Token that you need to enter in your coding agent.

    2. Download BitoAIArchitectGuidelines.md filearrow-up-right. You will need to copy/paste the content from this file later when configuring AI Architect.

      • Note: This file contains best practices, usage instructions, and prompting guidelines for the Bito AI Architect MCP server. The setup will work without this file, but including it helps AI tools interact more effectively with the Bito AI Architect MCP server.

    hashtag
    Set up AI Architect

    Follow the setup instructions for your operating system:

    • Windows

    • macOS/Linux

    hashtag
    Windows

    1

    hashtag
    Create Cursor config directory

    1. Press Win + R

    2. Type: %USERPROFILE%\.cursor

    3. Press Enter

    If the folder doesn't exist, create it:

    1. Open File Explorer

    2. Navigate to %USERPROFILE%

    3. Create new folder: .cursor

    2

    hashtag
    Create or edit mcp.json

    1. Open %USERPROFILE%\.cursor\mcp.json in a text editor.

    3

    hashtag
    Add guidelines (optional but highly recommended)

    The contains best practices, usage instructions, and prompting guidelines for the Bito AI Architect MCP server.

    The setup will work without this file, but including it helps AI tools interact more effectively with the Bito AI Architect MCP server.

    4

    hashtag
    Restart Cursor

    1. Close Cursor completely

    hashtag
    macOS/Linux

    1

    hashtag
    Create Cursor config directory

    2

    hashtag
    Create or edit mcp.json

    Add this content:

    circle-info

    Note:

    • Replace <Your-Bito-MCP-URL> with the Bito MCP URL you received after completing the AI Architect setup.

    Save and exit (Ctrl+O, Enter, Ctrl+X)

    3

    hashtag
    Add guidelines (optional but highly recommended)

    The contains best practices, usage instructions, and prompting guidelines for the Bito AI Architect MCP server.

    The setup will work without this file, but including it helps AI tools interact more effectively with the Bito AI Architect MCP server.

    4

    hashtag
    Restart Cursor

    1. Close Cursor completely

    hashtag
    Troubleshooting Cursor

    hashtag
    Server not showing:

    hashtag
    Connection errors:

    • Verify Bito MCP URL and Bito MCP Access Token are correct.

    • Test endpoint with MCP protocol:

    circle-info

    Note:

    • Replace <Your-Bito-MCP-URL> with the Bito MCP URL you received after completing the AI Architect setup.

      • For the Bito-hosted AI Architect, use the following URL format: https://mcp.bito.ai/<Your-Bito-Workspace-ID>/mcp

        Replace <Your-Bito-Workspace-ID> with your actual Bito workspace ID, which you can find after logging into your Bito account at

    • Replace <Your-Bito-MCP-Access-Token> with the Bito MCP Access Token you received after completing the AI Architect setup.

    • Check Settings → Tools & MCP for error messages

    AI Architect
    : High-level workspace metrics and trends
  • Submitter Analytics: Individual contributor performance and patterns

  • Repository Analytics: Repository and language-specific insights

  • PR Analytics: Detailed pull request and issue tracking

  • hashtag
    "Overview" dashboard

    The Overview dashboardarrow-up-right provides a comprehensive high-level view of your workspace's code review performance, showing pull requests reviewed, issues found, and their categorization.

    hashtag
    Key metrics:

    • Code Requests Reviewed - This Month: Total number of code reviews completed by Bito, including both pull requests from git workflows and IDE-based reviews

    • Lines Reviewed - This Month: Total lines of code analyzed across all pull request diffs

    • Repositories Reviewed - This Month: Number of unique repositories that received code review coverage

    • Submitters - This Month: Count of unique developers (based on Git handles) whose pull requests were reviewed by Bito

    • Issues Found - This Month: Total number of issues identified across all reviewed code

    • Issues Categories - This Month: Visual breakdown of issues by primary categories (Security, Performance, Functionality, etc.)

      • Note: When issues span multiple categories, Bito assigns the most relevant primary category

    • Merged PRs - This Month: Number of Bito-reviewed pull requests that were subsequently merged or closed

    • Issues Evaluated for Acceptance Rate - This Month: Issues in merged pull requests evaluated for potential fixes

    • Acceptance Rate (Merged PRs) - This Month: Percentage of agent-identified issues that were potentially addressed

      • Calculated based on code changes detected in related hunks when pull requests were merged

      • Available for reviews conducted on or after August 8th, 2024

    • Pull Requests Skipped - This Month: Pull requests excluded from review due to:

      • Matching exclusion filters in agent configuration

      • Empty diffs

    • Skip Reason - This Month: Breakdown of why specific pull requests were skipped

    circle-info

    Use the Filters button (top-right) to customize your view. You can also export the data to PowerPoint or PDF using the Share menu button (top-right).

    hashtag
    "Submitter Analytics" dashboard

    The Submitter Analytics dashboardarrow-up-right helps you gain insights into individual contributor patterns and performance with user-level statistics and visualizations.

    hashtag
    Key metrics:

    • Pull Requests Reviewed - This Month: Number of pull requests reviewed for each developer. It helps you identify most active team members.

      • Shows top 30 contributors by pull request count

      • Remaining contributors aggregated under 'Other'

    • Lines of Code Reviewed - This Month: Lines of code reviewed by Bito per developer. It is useful for understanding workload distribution.

      • Displays contributors with minimum 100 lines reviewed

      • Top 30 contributors shown individually

      • Remaining contributors grouped under 'Other'

    • Issues Reported Per 1K Lines - This Month: Issue density normalized by code volume for developers with at least 1,000 lines of code, enabling fair comparison across different contribution levels. It helps identify patterns in code quality by developer

    • Issue Distribution by Category - This Month: Breakdown of issues by type for each developer, showing both total count and percentage. Categories with fewer than 5 issues are excluded, with bar height representing total issues and width showing percentage distribution. It helps identify individual strengths and areas for improvement.

    circle-info

    Use the Filters button (top-right) to customize your view. You can also export the data to PowerPoint or PDF using the Share menu button (top-right).

    hashtag
    "Repository Analytics" dashboard

    The Repository Analytics dashboardarrow-up-right helps you understand repository-level performance and language-specific trends across your codebase.

    hashtag
    Key metrics:

    • Pull Requests Reviewed - This Month: Review activity across repositories (top 30 shown, remainder grouped as 'Other'). It identifies which codebases receive most attention.

    • Lines of Code Reviewed (Repo) - This Month: Lines of code reviewed by Bito in each repository (top 30 displayed individually). It helps you understand where development effort is concentrated.

    • Lines of Code Reviewed (Language) - This Month: Breakdown of reviewed code by programming language. It is useful for resource allocation and expertise planning.

    • Issues Reported Per 1K Lines (Repo) - This Month: Issue density for repositories with at least 1,000 lines of changes. It identifies repositories that may need additional attention

    • Issues Reported Per 1K Lines (Language) - This Month: Issue rates across different programming languages (minimum 100 lines required). It helps you identify language-specific training needs.

    • Issue Distribution by Category × Language - This Month: Issues categorized by both type and programming language, with visualization showing total count (bar height) and percentage distribution (bar width). Categories with fewer than 5 issues excluded. It reveals language-specific issue patterns.

    • Issue Distribution by Category × Repo - This Month: Issues analyzed across category and repository dimensions, excluding categories with fewer than 5 issues. The visualization shows total issues (bar height) and percentage distribution (bar width). It identifies repository-specific issue trends.

    circle-info

    Use the Filters button (top-right) to customize your view. You can also export the data to PowerPoint or PDF using the Share menu button (top-right).

    hashtag
    "PR Analytics" dashboard

    The PR Analytics dashboardarrow-up-right helps you dive deep into individual pull request performance with detailed pull request and issue-level analytics.

    The dashboard organizes pull requests into three tabs:

    hashtag
    1. "Reviewed (Feedback)" tab

    • Shows pull requests where Bito provided actionable feedback

    • These pull requests contain issues that require your attention

    • Click any pull request to access comprehensive details including every feedback item with its category (Security, Performance, Linter, Functionality, etc.), affected programming language, and direct links to the specific code location within the pull request for quick reference.

    • Useful for tracking reviews that generated value

    hashtag
    2. "Reviewed (No Feedback)" tab

    • Shows pull requests that Bito reviewed but found no actionable issues

    • Indicates clean code submissions

    hashtag
    3. "Skipped" tab

    • Shows pull requests that Bito didn't review due to configuration settings or other constraints

    • Includes skip reasons for transparency

    circle-info

    Use the Filter button (top-left) to customize views by:

    • Specific submitters

    • Date ranges

    • Pull request status

    hashtag
    Benefits for technical leadership

    The detailed code review analytics reports enables tech leads and reviewers to:

    • Trace patterns: Identify recurring issues across pull requests

    • Spot trends: Recognize systematic problems in code quality

    • Connect insights: Link high-level analytics to specific code examples

    • Targeted mentoring: Provide specific guidance based on actual code issues

    • Process improvement: Adjust development practices based on concrete data

    hashtag
    Best practices for using analytics

    hashtag
    1. Regular review cadence

    • Check Overview metrics for trend monitoring

    • Review Submitter Analytics for team performance discussions

    • Analyze Repository Analytics for strategic planning

    • Use for issue tracking and mentoring

    hashtag
    2. Filtering for insights

    • Use date filters to compare time periods

    • Filter by specific teams or repositories during retrospectives

    • Focus on high-activity contributors or repositories for targeted improvements

    hashtag
    3. Export and sharing

    • Export monthly reports for stakeholder updates

    • Share repository-specific insights with relevant teams

    • Use PowerPoint exports for executive presentations

    • Archive PDF reports for compliance or historical analysis

    hashtag
    4. Action-oriented analysis

    • Identify submitters who might benefit from additional code review training

    • Focus attention on repositories with high issue density

    • Address language-specific patterns through targeted workshops

    • Use acceptance rate trends to validate review effectiveness

    Code Review Analyticsarrow-up-right
    Overview
    Code Review Analytics dashboard
    How it works

    When you create a pull request, Bito automatically:

    1. Detects Jira ticket references in your pull request description, title, or branch name

    2. Crawls the linked Jira tickets to extract requirements from issue descriptions and related Stories/Epics

    3. Analyzes your code changes against these requirements

    4. Provides structured validation results directly in your pull request comments

    hashtag
    Jira integration options in Bito

    Bito supports two ways to connect with Jira, depending on where your Jira instance is hosted:

    1. Jira Cloud: for Jira sites hosted by Atlassian (e.g., https://mycompany.atlassian.net).

    2. Jira Data Center: for Jira instances hosted on your own company domain or servers (e.g., https://jira.mycompany.com).

    hashtag
    Connect Bito with Jira Cloud (hosted by Atlassian)

    1

    hashtag
    Connect Bito to Jira

    1. Navigate to the Manage integrationsarrow-up-right page in your Bito dashboard

    2. In the Available integrations section, you will see Jira. Click Connect to proceed.

    3. Select the option Jira Cloud. You will be redirected to the official Jira website, where you need to grant Bito access to your Atlassian account.

    4. Click Accept to continue. If the integration is successful, you will be redirected back to Bito.

    2

    hashtag
    Agent-specific settings

    After completing the initial setup, you can control Jira integration on a per-agent basis:

    1. Go to the

    circle-info

    Note: The Functional validation feature must be enabled in your Bito agent settings for the integration to work.

    hashtag
    Connect Bito with Jira Data Center (hosted on your own server)

    1

    hashtag
    Connect Bito to Jira

    1. Navigate to the Manage integrationsarrow-up-right page in your Bito dashboard

    2. In the Available integrations section, you will see Jira. Click Connect to proceed.

    3. Select the option Jira Data Center (self-managed).

    4. Provide connection details:

      • Domain URL: Enter the base URL for your Jira instance (e.g. https://jira.mycompany.com).

      • Personal Access Token: Enter a valid Personal Access Token with admin permissions. Read the to learn how to create a Personal Access Token.

    5. Click Connect to Jira. You will be redirected to your self-hosted Jira website, where you need to grant Bito access to your Jira account.

    6. Click Allow to continue. If the integration is successful, you will be redirected back to Bito.

    2

    hashtag
    Agent-specific settings

    After completing the initial setup, you can control Jira integration on a per-agent basis:

    1. Go to the

    hashtag
    Linking Jira tickets to pull requests

    Bito offers multiple ways to link your Jira tickets with pull requests. You can use any of these methods:

    hashtag
    Method 1: Branch name

    Name your source branch using the Jira issue key:

    hashtag
    Method 2: Pull request description

    Include the Jira ticket reference in your PR description:

    OR

    hashtag
    Method 3: Pull request title

    Include the Jira issue key in your PR title:

    hashtag
    Understanding the validation results

    When Bito completes its analysis, it adds a "Functional Validation by Bito" table to your pull request comments. This table contains four columns:

    hashtag
    Source

    Displays the Jira issue key (e.g., "QP-11", "QP-123") that references the specific Jira ticket being validated.

    hashtag
    Requirement / Code Area

    Shows a brief description of the requirement or task that needs to be completed, summarizing what needs to be done according to the Jira ticket.

    hashtag
    Status

    Indicates the completion status of each requirement:

    • Met: The requirement has been fully implemented in the pull request

    • Missed: The requirement has not been addressed in the pull request

    • Partial: The requirement has been partially implemented but still needs additional work

    • Conflict: A change contradicts another requirement (e.g., two requirements cannot both be satisfied by the current code).

    • Out‑of‑scope: The change is not in the requirements (the code change does not relate to any defined requirement).

    hashtag
    Notes

    Provides detailed information about the validation status:

    • For "Met" items: Explains what has been successfully implemented

    • For "Missed" items: Describes what is missing and needs to be addressed

    • For "Partial" items: Details what has been completed and what still remains to be done

    • For "Conflict" items: Describes why there is a contradiction between requirements and what might need to be resolved.

    • For "Out‑of‑scope" items: Explains why the change is considered outside the defined requirements.

    hashtag
    Example validation output

    Here's what a typical validation table looks like:

    hashtag
    Benefits

    • Automated quality assurance: Ensure code changes meet specified requirements

    • Improved collaboration: Bridge the gap between project management and development

    • Reduced manual reviews: Bito AI automatically catches missing implementations during code review

    • Better traceability: Maintain clear links between requirements and code changes

    By leveraging Bito's Jira integration, your development team can maintain higher code quality while ensuring that all requirements are properly addressed in every pull request.

    hashtag
    Best practices

    hashtag
    For developers

    • Always reference Jira tickets in your pull requests using one of the supported methods

    • Review the validation table and address any "Missed" or "Partial" items before merging

    hashtag
    For teams

    • Ensure Jira tickets contain clear, detailed requirements

    • Use consistent naming conventions for branches and pull request titles

    • Enable functional validation for all relevant agents

    hashtag
    Troubleshooting

    Validation table not appearing:

    • Check that your Jira integration is properly configured in the Manage integrationsarrow-up-right page

    • Verify that Functional validation is enabled in your agent settings

    • Ensure your pull request contains valid Jira issue key references

    Incorrect validation results:

    • Review your Jira ticket descriptions for clarity and completeness

    • Verify that linked Stories/Epics contain relevant requirements

    • Check that your code changes are in the expected areas

    Professional Planarrow-up-right

    Get a 14-day FREE trial of Bito's AI Code Review Agent.arrow-up-right

    hashtag
    Video tutorial

    hashtag
    Installation and configuration steps

    Follow the step-by-step instructions below to install the AI Code Review Agent using Bito Cloud:

    hashtag
    Step 1: Log in to Bito

    Log in to Bito Cloudarrow-up-right and select a workspace to get started.

    hashtag
    Step 2: Open the Code Review Agents setup

    Click Repositoriesarrow-up-right under the CODE REVIEW section in the sidebar.

    hashtag
    Step 3: Select your Git provider

    Bito supports integration with the following Git providers:

    • GitHub

    • GitHub (Self-Managed)

    • GitLab

    • GitLab (Self-Managed)

    • Bitbucket

    • Bitbucket (Self-Managed)

    Since we are setting up the Agent for Bitbucket, select Bitbucket to proceed.

    hashtag
    Step 4: Connect Bito to Bitbucket

    To enable pull request reviews, you’ll need to connect your Bito workspace to your Bitbucket account.

    circle-info

    If your Bitbucket access control settingsarrow-up-right block external services from interacting with the Bitbucket server, whitelist all of Bito's gateway IP addresses to ensure Bito can access your repositories. The Agent response can come from any of these IPs.

    • List of IP addresses to whitelist:

      • 18.188.201.104

      • 3.23.173.30

      • 18.216.64.170

    See the for more information.

    Click Install Bito App for Bitbucket. This will redirect you to Bitbucket.

    Now, authorize the Bito App to access your Bitbucket repositories.

    Select your Bitbucket workspace from the Authorize for workspace dropdown menu and then click Grant access. Once completed, you will be redirected to Bito.

    circle-info

    Note: You'll only see Bitbucket workspaces where you have Admin access. If no workspaces appear in the dropdown, it means your account doesn’t have admin access to any workspace. To connect a workspace, make sure you have admin access for it.

    hashtag
    Step 5: Enable AI Code Review Agent on repositories

    After connecting Bito to your Bitbucket account, you'll see a list of repositories that Bito has access to.

    Use the toggles in the Code Review Status column to enable or disable the Agent for each repository.

    circle-info

    To customize the Agent’s behavior, you can edit existing configurations or create new Agents as needed.

    Learn more

    hashtag
    Step 6: Automated and manual pull request reviews

    Once a repository is enabled, you can invoke the AI Code Review Agent in the following ways:

    1. Automated code review: By default, the Agent automatically reviews all new pull requests and provides detailed feedback.

    2. Manually trigger code review: To initiate a manual review, simply type /review in the comment box on the pull request and click Add comment now to submit it. This action will start the code review process.

    circle-info

    Note: After typing /review, add a space inside the comment box to ensure that /review is not highlighted as a Bitbucket slash command so that the comment can be posted correctly.

    The AI-generated code review feedback will be posted as comments directly within your pull request, making it seamless to view and address suggestions right where they matter most.

    circle-info

    Note: To enhance efficiency, the automated code reviews are only triggered for pull requests merging into the repository’s default branch. This prevents unnecessary processing and Advanced AI requests usage.

    To review additional branches, you can use the Include Source/Target Branches filter. Bito will review pull requests when the source or target branch matches the list.

    The Include Source/Target Branches filter applies only to automatically triggered reviews. Users should still be able to trigger reviews manually via the /review command.

    circle-info

    The AI Code Review Agent automatically reviews code changes up to 5000 lines when a pull request is created. For larger changes, you can use the /review command.

    circle-info

    It may take a few minutes to get the code review posted as a comment, depending on the size of the pull request.

    hashtag
    Step 7: Specialized commands for code reviews

    Bito also offers specialized commands that are designed to provide detailed insights into specific areas of your source code, including security, performance, scalability, code structure, and optimization.

    • /review security: Analyzes code to identify security vulnerabilities and ensure secure coding practices.

    • /review performance: Evaluates code for performance issues, identifying slow or resource-heavy areas.

    • /review scalability: Assesses the code's ability to handle increased usage and scale effectively.

    • /review codeorg: Scans for readability and maintainability, promoting clear and efficient code organization.

    • /review codeoptimize: Identifies optimization opportunities to enhance code efficiency and reduce resource usage.

    By default, the /review command generates inline comments, meaning that code suggestions are inserted directly beneath the code diffs in each file. This approach provides a clearer view of the exact lines requiring improvement. However, if you prefer a code review in a single post rather than separate inline comments under the diffs, you can include the optional parameter: /review #inline_comment=False

    For more details, refer to Available Commandsarrow-up-right.

    hashtag
    Step 8: Chat with AI Code Review Agent

    Ask questions directly to the AI Code Review Agent regarding its code review feedback. You can inquire about highlighted issues, request alternative solutions, or seek clarifications on suggested fixes.

    To start the conversation, type your question in the comment box within the inline suggestions on your pull request, and then submit it. Typically, Bito AI responses are delivered in about 10 seconds. On GitHub and Bitbucket, you need to manually refresh the page to see the responses, while GitLab updates automatically.

    Bito supports over 20 languages—including English, Hindi, Chinese, and Spanish—so you can interact with the AI in the language you’re most comfortable with.

    hashtag
    Step 9: Configure Agent settings

    Agent settings let you control how reviews are performed, ensuring feedback is tailored to your team’s needs. By adjusting the options, you can:

    • Make reviews more focused and actionable.

    • Apply your own coding standards.

    • Reduce noise by excluding irrelevant files or branches.

    • Add extra checks to improve code quality and security.

    Learn more

    hashtag
    Screenshots

    hashtag
    Screenshot # 1

    circle-info

    AI-generated pull request (PR) summary

    hashtag
    Screenshot # 2

    circle-info

    Changelist showing key changes and impacted files in a pull request.

    Changelist in AI Code Review Agent's feedback.

    hashtag
    Screenshot # 3

    circle-info

    AI code review feedback posted as comments on the pull request.

    AI Code Review Agentarrow-up-right
    available commandsarrow-up-right
    Pricingarrow-up-right
  • logs, node_modules, dist, target, bin, package-lock.json, data.json, build, .gradle, .idea, gradle, extension.js, vendor.js, ngsw.json, polyfills.js, ngsw-worker.js, runtime.js, runtime-main.js, service-worker.js, bundle.js, bundle.css

  • Extension based filtering

    • bin, exe, dll, log, aac, avif, bmp, cda, gif ,mp3, mp4, mpeg, weba, webm, webp, oga, ogv, png, jpeg, jpg, bmp, wpa, tif, tiff, svg, ico, wav, mov, avi, doc, docx, ppt, pptx, xls, xlsx, ods, odp, odt, pdf, epub, rar, tar, zip, vsix, 7z, bz, bz2, gzip, jar, war, gz, tgz, woff, woff2, eot, ttf, map, apk, app, ipa, lock, tmp, logs, gmo, pt

  • Hidden files are filtered i.e., files starting with "."

  • All Empty files are filtered.

  • All Binary files are also filtered.

  • hashtag
    Is there any limit on repository size?

    For workspaces that have upgraded to Bito's Team Plan, we have set the indexable size limit to 120MB per repo. However, once we launch the "AI that Understands Your Code" feature for our Free Plan users, they will be restricted to repositories with an indexable size limit of 10MB.

    Learn more about indexable size above and see which files and folders are excluded by default.

    You can reduce your repo's indexable size by excluding certain files and folders from indexing using .bitoignore file and remain within the limit.

    hashtag
    What if a repo hits 120MB limit?

    If a repo hits 120MB limit, then the below error message will be displayed in the "Manage repos" tab and the repo's index status will be changed to "Not Indexed".

    triangle-exclamation

    Sorry, we don’t currently support repos of this size. Please use .bitoignore to reduce the size of the repo you want Bito to index.

    To fix this issue, follow our instructions regarding how to use .bitoignore file and reduce your repo's size and bring it under the max limit of 120MB.

    After that, you must delete the index and then restart the indexing by clicking on the "Start Indexing" button shown for the repo folder. You can also follow our step-by-step guides to Start Indexing in Visual Studio Code and Start Indexing in JetBrains IDEs.

    hashtag
    What is .bitoignore and how to use it?

    A .bitoignore file is a plain text file where each line contains a pattern or rules that tells Bito which files or directories to ignore and not index. In other words, it's a way to reduce your repo's indexable size. You can also see which files/folders are excluded by default.

    There are two ways to use .bitoignore file:

    1. Create a .bitoignore file inside the folder where indexes created by Bito are stored. e.g. <user-home-directory>/.bito/localcodesearch/.bitoignore

      • On Windows, this path will be something like: C:\Users\<your username>\.bito\localcodesearch\.bitoignore

      • Note: The custom ignore rules you set in this .bitoignore file will be applied to all the repositories where you have enabled indexing.

    2. Create a .bitoignore file inside your repository's root folder.

    circle-info

    If a .gitignore file is available in your repo then Bito will also use that to ignore files & folders from indexing process. Both .bitoignore and .gitignore files can work together without any issues.

    circle-info

    At present, Bito considers only those .gitignore files that are placed in the project root directory and .bitoignore files that are placed either in <user-home-directory\.bito\localcodesearch> or <project-root-directory>

    Changes to the .bitoignore file are taken into account at the beginning of the indexing process, not during or after the indexing itself.

    Therefore, to implement changes made to the .bitoignore file, you'll need to delete the index and then restart the indexing by clicking on the "Start Indexing" button shown for the repo folder. You can also follow our step-by-step guides to Start Indexing in Visual Studio Code and Start Indexing in JetBrains IDEs.

    circle-info

    Please note that any changes to the .bitoignore or .gitignore file will take a minimum of 3 to 5 minutes to trigger new indexing.

    hashtag
    Common .bitoignore Patterns

    Understanding these patterns/rules is crucial for effectively managing the files and directories that Bito indexes and excludes in your projects.

    Sample Rule
    Description

    # this is a comment.

    Any line that starts with a # symbol is considered as a comment and will not be processed.

    *

    (Wildcard character) Ignores all files

    **

    (Wildcard character) Match any number of directories.

    todo.txt

    Ignores a specific file named todo.txt

    *.txt

    Ignores all files ending with .txt

    *.*

    Ignores all files with any extension.

    hashtag
    Negation ! (exclamation mark)

    When a pattern starts with ! it negates the pattern, meaning it explicitly includes files or directories that would otherwise be ignored. For example, have a look at this sample .bitoignore file:

    Here !Engine/Build/BatchFiles/** pattern includes all files in the Engine/Build/BatchFiles directory and its subdirectories, even though Engine/** pattern would ignore them.

    circle-info

    Avoid Ambiguous Patterns: Negation patterns can become confusing when they potentially match multiple files. Target specific files or folders rather than using wildcards in negation patterns.

    For example, it is better to use patterns like !Engine/Build/BatchFiles/script.bat instead of !Engine/Build/BatchFiles/**

    hashtag
    .bitoignore Examples

    hashtag
    Exclude Files/Folders

    hashtag
    Exclude Everything Except Specific Files

    To exempt a file, ensure that the negation pattern ! appears afterward, thereby overriding any broader exclusions.

    Key features

    Explore the powerful capabilities of the AI Code Review Agent.

    Get a 14-day FREE trial of Bito's AI Code Review Agent.arrow-up-right

    hashtag
    Features overview

    A quick look at powerful features of Bito's AI Code Review Agentarrow-up-right—click to jump to details.


    hashtag
    AI that understands your code

    The understand code changes in pull requests. It analyzes relevant context from your entire repository, resulting in more accurate and helpful code reviews.

    To comprehend your code and its dependencies, it uses Symbol Indexing, Abstract Syntax Trees (AST), and Embeddings.

    hashtag
    One-click setup for GitHub, GitLab, and Bitbucket

    offers a one-click solution for using the , eliminating the need for any downloads on your machine.

    Bito supports integration with the following Git providers:

    hashtag
    Automated and manually-triggered AI code reviews

    By default, the AI Code Review Agent automatically reviews all new pull requests and provides detailed feedback.

    To initiate a manual review, simply type /review in the comment box on the pull request and submit it. This action will start the code review process.

    hashtag
    Pull request summary

    Get a concise overview of your pull request (PR) directly in the description section, making it easier to understand the code changes at a glance.

    Each pull request includes an automatically generated summary that explains the intent and scope of the changes in a clear, easy-to-read format.

    The summary highlights the main objective of the update, outlines the most important modifications, and provides a high-level view of their impact on the codebase. This allows reviewers to quickly understand what the pull request is about before diving into the detailed code changes.

    hashtag
    Changelist

    A tabular view that displays key changes in a pull request, making it easy to spot important updates at a glance without reviewing every detail. Changelist categorizes modifications and highlights impacted files, giving you a quick, comprehensive summary of what has changed.

    hashtag
    One-click to accept suggestions

    The AI-generated code review feedback is posted as comments directly within your pull request, making it seamless to view and address suggestions right where they matter most.

    You can accept the suggestions with a single click, and the changes will be added as a new commit to the pull request.

    hashtag
    Chat with AI Code Review Agent

    Ask questions directly to the AI Code Review Agent regarding its code review feedback. You can inquire about highlighted issues, request alternative solutions, or seek clarifications on suggested fixes.

    Real-time collaboration with the AI Code Review Agent accelerates your development cycle. By delivering immediate, actionable insights, it eliminates the delays typically experienced with human reviews. Developers can engage directly with the Agent to clarify recommendations on the spot, ensuring that any issues are addressed swiftly and accurately.

    Bito supports over 20 languages—including English, Hindi, Chinese, and Spanish—so you can interact with the AI in the language you’re most comfortable with.

    hashtag
    Incremental code reviews

    AI Code Review Agent automatically reviews only the recent changes each time you push new commits to a pull request. This saves time and reduces costs by avoiding unnecessary re-reviews of all files.

    You can enable or disable incremental reviews using the .

    hashtag
    Code review analytics

    Get in-depth insights into your org’s code reviews with user-friendly dashboard. Track key metrics such as pull requests reviewed, issues found, lines of code reviewed, and understand individual contributions.

    hashtag
    Custom code review rules and guidelines

    The AI Code Review Agent offers a flexible solution for teams looking to enforce custom code review rules, standards, and guidelines tailored to their unique development practices. Whether your team follows specific coding conventions or industry best practices, you can customize the Agent to suite your needs.

    We support two ways to customize AI Code Review Agent’s suggestions:

    1. , and the AI Code Review Agent automatically adapts by creating code review rules to prevent similar suggestions in the future.

    2. . Define rules through the dashboard in Bito Cloud and apply them to agent instances in your workspace.

    hashtag
    Multiple specialized engineers for targeted code analysis

    The AI Code Review Agent acts as a team of specialized engineers, each analyzing different aspects of your pull request. You'll get specific advice for improving your code, right down to the exact line in each file.

    The areas of analysis include:

    • Security

    • Performance

    • Scalability

    • Optimization

    This multifaceted analysis results in more detailed and accurate code reviews, saving you time and improving code quality.

    hashtag
    Integrated feedback from dev tools you use

    Elevate your code reviews by harnessing the power of the development tools you already trust. Bito's AI Code Review Agent seamlessly integrates feedback from essential tools including:

    • Static code analysis

    • Open source security vulnerabilities check

    • Linter integrations

    Static code analysis

    Using tools like Facebook’s open-source fbinfer (available out of the box), the Agent dives deep into your code—tailored to each language—and suggests actionable fixes. You can also configure additional tools you use for a more customized analysis experience.

    Open source security vulnerabilities check

    The AI Code Review Agent checks real-time for the latest high severity security vulnerabilities in your code, using (available out of the box). Additional tools such as , or can also be configured.

    Linter integrations

    Our integrated linter support reviews your code for consistency and adherence to best practices. By catching common errors early, it ensures your code stays clean, maintainable, and aligned with modern development standards.

    Secrets scanning

    Safeguard your sensitive data effortlessly. With built-in scanning capabilities, the Agent checks your code for exposed passwords, API keys, and other confidential information—helping to secure your codebase throughout the development lifecycle.

    hashtag
    Jira integration

    Seamlessly connect Bito with Jira to automatically validate pull request code changes against linked Jira tickets. This ensures your implementations meet specified requirements through real-time, structured validation feedback directly in your pull requests.

    Support for Jira Cloud and Jira Data Center setups enables flexible integrations, while multiple ticket-linking methods ensure accurate requirement tracking.

    Boost your team's code quality, collaboration, and traceability with automated Jira ticket validation.

    hashtag
    Supports all major programming languages

    No matter if you're coding in Python, JavaScript, Java, C++, or beyond, our AI Code Review Agent has you covered. It understands the unique syntax and best practices of every popular language, delivering tailored insights that help you write cleaner, more efficient code—every time.

    hashtag
    Enterprise-grade security

    Bito and third-party LLM providers never store or use your code, prompts, or any other data for model training or any other purpose.

    Bito is SOC 2 Type II compliant. This certification reinforces our commitment to safeguarding user data by adhering to strict security, availability, and confidentiality standards. SOC 2 Type II compliance is an independent, rigorous audit that evaluates how well an organization implements and follows these security practices over time.

    Create or customize an Agent instance

    Customize the AI Code Review Agent to match your workflow needs.

    Connecting your Bito workspace to GitHub, GitLab, or Bitbucket provides immediate access to the AI Code Review Agent. To get you started quickly, Bito offers a Default Agent instance—pre-configured and ready to deliver AI-powered code reviews for pull requests and code changes within supported IDEs such as VS Code and JetBrains.

    While the Default Agent is ready for use right away, Bito also gives you the option to create new Agent instances or customize existing ones to suit your specific requirements. This flexibility ensures that the Agent can adapt to a range of workflows and project needs.

    For example, you might configure one Agent to disable automatic code reviews for certain repositories, another to exclude specific Git branches from review, and yet another to filter out particular files or folders.

    This guide will walk you through how to create or customize an Agent instance, unlocking its full potential to streamline your code reviews.

    hashtag
    Creating or customizing AI Code Review Agents

    Once Bito is connected to your GitHub/GitLab/Bitbucket account, you can easily create a new Agent or customize an existing one to suit your workflow.

    1. To create a new Agent, navigate to the dashboard and click the New Agent button to open the Agent configuration form.

    1. If you’d like to customize an existing agent, simply go to the same dashboard and click the Settings button next to the Agent instance you wish to modify.

    Once you have selected an Agent to customize, you can modify its settings in the following areas:

    hashtag
    1. General settings

    hashtag
    Agent name

    Assign a unique alphanumeric name to your Agent. This name acts as an identifier and allows you to invoke the Agent in supported clients using the @<agent_name> command.

    hashtag
    2. Customization options

    Bito provides six tabs for in-depth Agent customization.

    These include:

    1. Review

    2. Custom Guidelines

    3. Filters

    4. Tools

    Let's have a look at each tab in detail.

    hashtag
    a. Review

    In this tab, you can configure how and when the Agent performs reviews:

    • Review language: Select the output language for code review feedback. Bito supports over 20 languages, including English, Hindi, Chinese, and Spanish. The AI code review feedback will be posted on the pull requests in the selected language.

    • Review feedback mode: Choose between Essential and Comprehensive review modes and tailor review request settings to fit your team's unique workflow requirements.

      • In Essential

    hashtag
    b. Custom Guidelines

    Create, apply, and manage custom code review guidelines to align the AI agent’s reviews with your team’s specific coding standards.

    The agent will follow your guidelines when reviewing pull requests.

    hashtag
    c. Filters

    Use filters to customize which files, folders, and Git branches are reviewed when the Agent triggers automatically on pull requests:

    • Exclude Files and Folders: A list of files/folders that the AI Code Review Agent will not review if they are present in the diff. You can specify the files/folders to exclude from the review by name or glob/regex pattern. The Agent will automatically skip any files or folders that match the exclusion list. This filter applies to both manual reviews initiated through the /review command and automated reviews.

    • Include Source/Target Branches: This filter defines which pull requests trigger automated reviews based on their source or target branch, allowing you to focus on critical code and avoid unnecessary reviews or AI usage. By default, pull requests merging into the repository’s default branch are subject to review. To review additional branches, you can use the . Bito will review pull requests when the source or target branch matches the list. This filter applies only to automatically triggered reviews. Users should still be able to trigger reviews manually via the /review

    circle-info

    For more information and examples, see .

    hashtag
    d. Tools

    Enhance the Agent’s reviews by enabling additional tools for static analysis, security checks, and secret detection:

    • Secret Scanner: Enable this tool to detect and report secrets left in code changes.

    hashtag
    e. Chat

    You can chat with the to ask follow-up questions, request alternative solutions, or get clarification on review comments. From this tab, you can manage how the agent responds to these interactions.

    • Auto reply: Enable Bito to automatically reply to user questions posted as comments on its code review suggestions—no need to tag @bitoagent or @askbito.

    hashtag
    f. Functional Validation

    Automatically validate pull requests against Jira tickets. Ticket references are detected in the PR description, title, or branch name.

    If you are editing an existing agent, click Save to apply the changes.

    hashtag
    3. Select repositories for code review

    1. If you are creating a new agent instance, click Select repositories after configuration to choose the Git repositories the agent will review.

    1. To enable code review for a specific repository, simply select its corresponding checkbox. You can also enable repositories later, after the Agent has been created. Once done, click Save and continue to save the new Agent configuration.

    1. When you save the configuration, your new Agent instance will be added and available on the page.

    Guide for Claude Code

    Integrate Claude Code with AI Architect for more accurate, codebase-aware AI assistance.

    Use Bito's AI Architect with Claude Code to enhance your AI-powered coding experience.

    Once connected via MCP (Model Context Protocol), Claude Code can leverage AI Architect’s deep contextual understanding of your project, enabling more accurate code suggestions, explanations, and code insights.

    hashtag
    Quick setup (recommended)

    Want to get started faster? We offer an automated installer that can configure AI Architect for all your AI coding tools in just a few seconds.

    The automated setup will:

    • Detect all compatible AI tools installed on your system

    • Configure them automatically with your credentials

    • Save you time by eliminating manual configuration steps

    👉 for automated setup.

    hashtag
    Manual setup

    If you prefer manual configuration, follow the step-by-step instructions below.

    hashtag
    Prerequisites

    1. Follow the . Upon successful setup, you will receive a Bito MCP URL and Bito MCP Access Token that you need to enter in your coding agent.

    2. . You will need to copy/paste the content from this file later when configuring AI Architect.

      • Note: This file contains best practices, usage instructions, and prompting guidelines for the Bito AI Architect MCP server. The setup will work without this file, but including it helps AI tools interact more effectively with the Bito AI Architect MCP server.

    hashtag
    Set up AI Architect

    Claude Code has the same setup process across all platforms (Windows, macOS, Linux, WSL) using the command line.

    Claude Code uses CLI-based configuration, NOT manual JSON editing.

    1

    hashtag
    Install Claude Code

    If you haven't already:

    Verify installation:

    2

    hashtag
    Windows-specific notes

    hashtag
    Windows (Native - Command Prompt/PowerShell):

    • MCP servers using npx require the cmd /c wrapper:

    hashtag
    Windows (WSL):

    • Configuration is stored in Linux file system

    • No need for cmd /c wrapper

    • Use standard Linux paths (~/.claude/)

    hashtag
    Configuration file locations

    Platform
    Main config
    Settings
    Global guidelines
    circle-info

    IMPORTANT:

    • ✅ These files are managed automatically by claude mcp commands

    • ❌ Do NOT manually create

    hashtag
    Common Claude Code MCP commands

    hashtag
    Troubleshooting Claude Code

    hashtag
    Server not appearing:

    circle-info

    Note:

    • Replace <Your-Bito-MCP-URL> with the Bito MCP URL you received after completing the AI Architect setup.

    hashtag
    Connection issues:

    circle-info

    Note:

    • Replace <Your-Bito-MCP-URL> with the Bito MCP URL you received after completing the AI Architect setup.

    hashtag
    Permission issues (macOS/Linux):

    Guide for GitLab

    Integrate the AI Code Review Agent into your GitLab workflow.

    Speed up code reviews by configuring the AI Code Review Agentarrow-up-right with your GitLab repositories. In this guide, you'll learn how to set up the Agent to receive automated code reviews that trigger whenever you create a pull request, as well as how to manually initiate reviews using available commandsarrow-up-right.

    circle-info

    The Free Plan offers AI-generated pull request summaries to provide a quick overview of changes. For advanced features like line-level code suggestions, consider upgrading to the Team Plan. For detailed pricing information, visit our Pricingarrow-up-right page.

    hashtag
    Video tutorial

    hashtag
    Prerequisites

    Before proceeding, ensure you've completed all necessary prerequisites.

    hashtag
    1. Create a GitLab Personal Access Token:

    For GitLab merge request code reviews, a token with api scope is required. Make sure that the token is created by a GitLab user who has the Maintainer access role.

    circle-info

    Important: Bito posts comments using the GitLab user account linked to the Personal Access Token used during setup. To display "Bito" instead of your name, create a separate user account (e.g., Bito Agent) and use its token for integration.

    circle-info

    We recommend setting the token expiration to at least one year. This prevents the token from expiring early and avoids disruptions in the AI Code Review Agent's functionality.

    Additionally, we highly recommend updating the token before expiry to maintain seamless integration and code review processes.

    hashtag
    2. Authorizing a GitLab Personal Access Token for use with SAML single sign-on:

    If your GitLab organization enforces SAML Single Sign-On (SSO), you must authorize your Personal Access Token through your Identity Provider (IdP); otherwise, Bito's AI Code Review Agent won't function properly.

    For more information, please refer to these GitLab documentation:

    hashtag
    Installation and configuration steps

    Follow the step-by-step instructions below to install the AI Code Review Agent using Bito Cloud:

    hashtag
    Step 1: Log in to Bito

    and select a workspace to get started.

    hashtag
    Step 2: Open the Code Review Agents setup

    Click under the CODE REVIEW section in the sidebar.

    hashtag
    Step 3: Select your Git provider

    Bito supports integration with the following Git providers:

    • GitHub

    • GitHub (Self-Managed)

    • GitLab

    • GitLab (Self-Managed)

    Since we are setting up the Agent for GitLab, select GitLab to proceed.

    hashtag
    Step 4: Connect Bito to GitLab

    To enable merge request reviews, you’ll need to connect your Bito workspace to your GitLab account.

    You can either connect using OAuth (recommended) for a seamless, one-click setup or manually enter your Personal Access Token.

    To connect via OAuth, simply click the Connect with OAuth (Recommended) button. This will redirect you to the GitLab website, where you'll need to log in. Once authenticated, you'll be redirected back to Bito, confirming a successful connection.

    If you prefer not to use OAuth, you can connect manually using a Personal Access Token.

    Start by with api scope in your GitLab account. For guidance, refer to the instructions in the section.

    Once generated, click the Alternatively, use Personal or Group Access Token button.

    Now, enter the token into the Personal Access Token input field in Bito.

    Click Validate to ensure the token is functioning properly.

    If you've successfully connected via OAuth or manually validated your token, you can select your GitLab Group from the dropdown menu.

    Click Connect Bito to GitLab to proceed.

    hashtag
    Step 5: Enable AI Code Review Agent on repositories

    After connecting Bito to your GitLab account, you'll see a list of repositories that Bito has access to.

    Use the toggles in the Code Review Status column to enable or disable the Agent for each repository.

    circle-info

    To customize the Agent’s behavior, you can edit existing configurations or create new Agents as needed.

    hashtag
    Step 6: Automated and manual merge request reviews

    Once a repository is enabled, you can invoke the AI Code Review Agent in the following ways:

    1. Automated code review: By default, the Agent automatically reviews all new merge requests and provides detailed feedback.

    2. Manually trigger code review: To initiate a manual review, simply type /review in the comment box on the merge request and submit it. This action will start the code review process.

    The AI-generated code review feedback will be posted as comments directly within your merge request, making it seamless to view and address suggestions right where they matter most.

    circle-info

    Note: To enhance efficiency, the automated code reviews are only triggered for merge requests merging into the repository’s default branch. This prevents unnecessary processing and Advanced AI requests usage.

    To review additional branches, you can use the . Bito will review merge requests when the source or target branch matches the list.

    The Include Source/Target Branches filter applies only to automatically triggered reviews. Users should still be able to trigger reviews manually via the /review command.

    circle-info

    The AI Code Review Agent automatically reviews code changes up to 5000 lines when a merge request is created. For larger changes, you can use the /review command.

    circle-info

    It may take a few minutes to get the code review posted as a comment, depending on the size of the merge request.

    hashtag
    Step 7: Specialized commands for code reviews

    Bito also offers specialized commands that are designed to provide detailed insights into specific areas of your source code, including security, performance, scalability, code structure, and optimization.

    • /review security: Analyzes code to identify security vulnerabilities and ensure secure coding practices.

    • /review performance: Evaluates code for performance issues, identifying slow or resource-heavy areas.

    By default, the /review command generates inline comments, meaning that code suggestions are inserted directly beneath the code diffs in each file. This approach provides a clearer view of the exact lines requiring improvement. However, if you prefer a code review in a single post rather than separate inline comments under the diffs, you can include the optional parameter: /review #inline_comment=False

    For more details, refer to .

    hashtag
    Step 8: Chat with AI Code Review Agent

    Ask questions directly to the AI Code Review Agent regarding its code review feedback. You can inquire about highlighted issues, request alternative solutions, or seek clarifications on suggested fixes.

    To start the conversation, type your question in the comment box within the inline suggestions on your merge request, and then submit it. Typically, Bito AI responses are delivered in about 10 seconds. On GitHub and Bitbucket, you need to manually refresh the page to see the responses, while GitLab updates automatically.

    Bito supports over 20 languages—including English, Hindi, Chinese, and Spanish—so you can interact with the AI in the language you’re most comfortable with.

    hashtag
    Step 9: Configure Agent settings

    let you control how reviews are performed, ensuring feedback is tailored to your team’s needs. By adjusting the options, you can:

    • Make reviews more focused and actionable.

    • Apply your own coding standards.

    • Reduce noise by excluding irrelevant files or branches.

    hashtag
    Screenshots

    hashtag
    Screenshot # 1

    circle-info

    AI-generated merge request (MR) summary

    hashtag
    Screenshot # 2

    circle-info

    Changelist showing key changes and impacted files in a merge request.

    hashtag
    Screenshot # 3

    circle-info

    AI code review feedback posted as comments on the merge request.

    Guide for JetBrains AI Assistant

    Integrate JetBrains AI Assistant with AI Architect for more accurate, codebase-aware AI assistance.

    Use Bito's AI Architect with JetBrains AI Assistant to enhance your AI-powered coding experience.

    Once connected via MCP (Model Context Protocol), JetBrains AI Assistant can leverage AI Architect’s deep contextual understanding of your project, enabling more accurate code suggestions, explanations, and code insights.

    hashtag
    Quick setup (recommended)

    Want to get started faster? We offer an automated installer that can configure AI Architect for all your AI coding tools in just a few seconds.

    The automated setup will:

    • Detect all compatible AI tools installed on your system

    • Configure them automatically with your credentials

    • Save you time by eliminating manual configuration steps

    👉 for automated setup.

    hashtag
    Manual setup

    If you prefer manual configuration, follow the step-by-step instructions below.

    hashtag
    Prerequisites

    1. Follow the . Upon successful setup, you will receive a Bito MCP URL and Bito MCP Access Token that you need to enter in your coding agent.

    2. . You will need to copy/paste the content from this file later when configuring AI Architect.

      • Note: This file contains best practices, usage instructions, and prompting guidelines for the Bito AI Architect MCP server. The setup will work without this file, but including it helps AI tools interact more effectively with the Bito AI Architect MCP server.

    hashtag
    Set up AI Architect

    JetBrains AI Assistant has the same setup process across all platforms (Windows, macOS, Linux, WSL).

    1

    hashtag
    Access MCP settings

    1. Open your JetBrains IDE (IntelliJ IDEA, PyCharm, WebStorm, etc.)

    hashtag
    Troubleshooting

    hashtag
    JetBrains AI Assistant not showing MCP settings:

    1. Verify IDE version is 2025.1 or later

    2. Verify AI Assistant plugin is version 251.26094.80.5+

    3. Update both if needed

    hashtag
    BitoAIArchitect not appearing or showing "Not started":

    1. Verify Node.js is installed: node --version

    2. Check that you've toggled "Codebase" mode ON in the chat

    3. On Windows, ensure you're using cmd command (not npx directly)

    hashtag
    Connection errors:

    1. Test the endpoint manually:

    circle-info

    Note:

    • Replace <Your-Bito-MCP-URL> with the Bito MCP URL you received after completing the AI Architect setup.

    1. Verify your Bito MCP URL and Bito MCP Access Token are correct

    2. Check firewall settings

    3. Verify the --header argument format: Authorization:${AUTH_HEADER} (colon, no space)

    hashtag
    Windows-specific issues:

    1. Verify the JSON uses "command": "cmd" (not npx)

    2. Ensure "/c" is the first element in the args array

    Available commands

    This page provides a complete reference for all commands and options available in AI Code Reviews in CLI. Use it to understand what each command does, when to use it, and how to combine options for common workflows.

    hashtag
    Command structure

    For convenience, you can also use the short alias br instead of bitoreview:

    hashtag
    Commands overview

    Command
    Description

    hashtag
    review command

    The review command is the core of the CLI. It analyzes your code changes and highlights issues related to bugs, security, performance, and overall code quality.

    hashtag
    Basic syntax

    hashtag
    Examples

    hashtag
    Review scope options

    --type, -t <type>

    Specify which changes to review.

    Supported values:

    • all (default) - Review both committed and uncommitted changes

    • uncommitted - Review only working directory changes

    • committed --base <branch-name> - Review only committed changes against the specified base branch.

    Examples:

    --base <branch>

    Compare changes against a specific branch.

    Example:

    --base-commit <commit>

    Compare changes against a specific commit hash.

    Example:

    hashtag
    Review quality options

    --mode <mode>

    Control the depth and breadth of the review.

    Supported values:

    • essential - Shows only HIGH severity issues for rapid feedback

    • comprehensive (default) - Shows all severity levels for thorough analysis

    Examples:

    --focus <area>

    Concentrate the review on specific code quality aspects.

    Supported values:

    • security - SQL injection, XSS, authentication, data validation

    • performance - Memory leaks, inefficient algorithms, bottlenecks

    • bugs - Logic errors, edge cases, runtime issues

    Examples:

    --severity <level>

    Filter issues by minimum severity level.

    Supported values:

    • high - Critical issues that must be fixed

    • medium - Important issues that should be addressed

    • low - Minor suggestions and style improvements

    Examples:

    hashtag
    Output options

    --interactive, -i

    Enable interactive mode to review and apply fixes one by one.

    Example:

    --plain

    Output plain text without colors or formatting, suitable for logs and CI/CD.

    Example:

    --prompt-only

    Minimal output optimized for AI agent integration.

    Example:

    --no-color

    Disable colored output (similar to --plain but retains structure).

    Example:

    hashtag
    SCM options

    --scm <type>

    Override automatic SCM detection.

    Supported values:

    • git - Git repository

    • svn - Subversion repository

    • hg - Mercurial repository

    Example:

    hashtag
    Configuration options

    --config, -c <path>

    Use a custom configuration file path instead of .bitoreview.yaml in the project root.

    Example:

    --api-key <key>

    Provide API key directly via command line (overrides environment and config file).

    Example:

    --cwd <path>

    Set the working directory for the review.

    Example:

    hashtag
    Debugging options

    --debug, -d

    Enable debug output for troubleshooting.

    Example:

    --verbose, -v

    Enable verbose logging for detailed information.

    Example:

    --max-retries <number>

    Set the number of retry attempts for API calls (default: 2).

    Example:

    hashtag
    config command

    Manage configuration and API keys.

    hashtag
    Set API key

    Interactive mode (prompts for key):

    Direct mode (provide key in command):

    hashtag
    Show API key

    Display your configured API key (masked for security).

    hashtag
    Global options

    hashtag
    --help, -h

    Display help for any command.

    Examples:

    hashtag
    --version

    Show the installed CLI version.

    Example:

    hashtag
    Option combinations

    AI Code Reviews in CLI allows you to combine multiple options for precise control:

    Installation guide

    AI Code Reviews in CLI lets you run fast, high-quality AI-powered code reviews directly from your terminal. It works on macOS, Linux, and Windows, and installation typically takes a few minutes.

    This guide walks you through installation steps.

    hashtag
    Prerequisites

    1

    hashtag
    Bito API Key (aka Bito Access Key)

    You'll need a Bito account and a Bito Access Key to authenticate AI Code Reviews in CLI. You can sign up for a Bito account at , and create an access key from

    hashtag
    Installation guide

    1

    hashtag
    Download and install the CLI

    hashtag
    macOS and Linux:

    Repo level settings

    Configure repository-specific Code Review Agent settings using the .bito.yaml file.

    Repo-level Agent settings let you control how the behaves for each repository.

    By placing a .bito.yaml file in the root of your repository, you can define custom review preferences that apply only to that repository.

    Bito automatically detects the presence of a .bito.yaml file in a repository and applies its configuration to override the global Agent settings defined by admins in the Bito Cloud UI.

    This gives developers fine-grained control while admins maintain global oversight and billing management.

    Guide for GitHub (Self-Managed)

    Integrate the AI Code Review Agent into your self-hosted GitHub Enterprise workflow.

    Speed up code reviews by configuring the with your self-managed GitHub Enterprise server. In this guide, you'll learn how to set up the Agent to receive automated code reviews that trigger whenever you create a pull request, as well as how to manually initiate reviews using .

    circle-info

    The Free Plan offers AI-generated pull request summaries to provide a quick overview of changes. For advanced features like line-level code suggestions, consider upgrading to the Team Plan. For detailed pricing information, visit our page.

    Install/run via GitHub Actions

    Seamlessly integrate automated code reviews into your GitHub Actions workflows.

    hashtag
    Prerequisites

    • Bito Access Key: Obtain your Bito Access Key.

    GitHub - gitbito/CLI: Bito CLI (Command Line Interface) provides a command line interface to the Bito AI chat functionality. Over time, CLI will add more functions and new command options to support complex automation and workflows. This is a very early Alpha version. We would love to get your feedback on the new features or improvements.GitHubchevron-right
    curl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash -
    sudo apt-get install -y nodejs
    node --version  # Should show v20.x.x or higher
    npx --version
    {
      "mcpServers": {
        "BitoAIArchitect": {
          "command": "npx",
          "args": [
            "-y",
            "mcp-remote",
            "<Your-Bito-MCP-URL>"
          ]
        }
      }
    }
    {
      "mcpServers": {
        "existing-server": {
          ...
        },
        "BitoAIArchitect": {
          "command": "npx",
          "args": [
            "-y",
            "mcp-remote",
            "<Your-Bito-MCP-URL>"
          ]
        }
      }
    }
    {
      "mcpServers": {
        "BitoAIArchitect": {
          "command": "cmd",
          "args": [
            "/c",
            "npx",
            "-y",
            "mcp-remote",
            "<Your-Bito-MCP-URL>"
          ]
        }
      }
    }
    18.188.201.104
    3.23.173.30
    18.216.64.170
    What repositories are available in my organization?
    curl -fsSL https://mcp-setup.bito.ai/install.sh | bash
    irm https://mcp-setup.bito.ai/install.ps1 | iex
    curl -fsSL https://mcp-setup.bito.ai/uninstall.sh | bash
    irm https://mcp-setup.bito.ai/uninstall.ps1 | iex
    curl -s -X POST \
      -H "Authorization: Bearer <Your-Bito-MCP-Access-Token>" \
      -H "Content-Type: application/json" \
      -d '{"jsonrpc":"2.0","method":"initialize","params":{},"id":1}' \
      <Your-Bito-MCP-URL>
    
    # Should return HTTP 200 with JSON response for valid credentials
    # HTTP 401: Invalid Bito MCP Access Token
    # HTTP 404: Invalid Bito MCP URL
    node --version
    mkdir -p ~/.codeium/windsurf
    # Verify file location
    ls -la ~/.codeium/windsurf/mcp_config.json
    
    # Check permissions
    chmod 755 ~/.codeium/windsurf
    chmod 644 ~/.codeium/windsurf/mcp_config.json
    
    # Verify JSON syntax
    cat ~/.codeium/windsurf/mcp_config.json | python -m json.tool
    curl -s -X POST \
      -H "Authorization: Bearer <Your-Bito-MCP-Access-Token>" \
      -H "Content-Type: application/json" \
      -d '{"jsonrpc":"2.0","method":"initialize","params":{},"id":1}' \
      <Your-Bito-MCP-URL>
    
    # Should return HTTP 200 with JSON response for valid credentials
    # HTTP 401: Invalid Bito MCP Access Token
    # HTTP 404: Invalid Bito MCP URL
    nano ~/.codeium/windsurf/mcp_config.json
    {
      "mcpServers": {
        "BitoAIArchitect": {
          "serverUrl": "<Your-Bito-MCP-URL>",
          "headers": {
            "Authorization": "Bearer <Your-Bito-MCP-Access-Token>",
            "x-email-id": "<Your-Email>"
          }
        }
      }
    }
    # Use proper MCP protocol to test authentication
    curl -s -X POST \
      -H "Authorization: Bearer <Your-Bito-MCP-Access-Token>" \
      -H "Content-Type: application/json" \
      -d '{"jsonrpc":"2.0","method":"initialize","params":{},"id":1}' \
      <Your-Bito-MCP-URL>
    mkdir -p ~/.cursor
    # Verify file location
    ls -la ~/.cursor/mcp.json
    
    # Check file permissions
    chmod 644 ~/.cursor/mcp.json
    
    # Verify JSON syntax
    cat ~/.cursor/mcp.json | python -m json.tool
    curl -s -X POST \
      -H "Authorization: Bearer <Your-Bito-MCP-Access-Token>" \
      -H "Content-Type: application/json" \
      -d '{"jsonrpc":"2.0","method":"initialize","params":{},"id":1}' \
      <Your-Bito-MCP-URL>
    
    # Should return HTTP 200 with JSON response for valid credentials
    # HTTP 401: Invalid Bito MCP Access Token
    # HTTP 404: Invalid Bito MCP URL
    feature/QP-123-implement-user-authentication
    bugfix/QP-456-fix-login-error
    This PR implements user authentication as specified in QP-123.
    
    Related tickets: QP-123, QP-124
    This PR implements shopping cart functionality as specified in:
    https://your-company.atlassian.net/browse/QP-3
    https://your-company.atlassian.net/browse/QP-7
    QP-123: Implement user authentication feature
    [QP-456] Fix login validation error
    Engine/**
    !Engine/Build/BatchFiles/**
    # Ignore specific file named "config.ini"
    config.ini
    
    # Ignore all files with a '.bak' extension
    *.bak
    
    # Ignore all files with a '.kunal' extension
    *.kunal
    
    # Exclude directories
    backup
    temp/
    dist/vendor
    # Ignore all files except C++, header and python files
    *
    !*.cpp
    !*.h
    !*.py
    bitoreview <command> [options]
    br <command> [options]

    Engine/ or Engine/**

    Ignores all files in the Engine directory and their subdirectories (contents).

    subdirectory1/example.html

    Ignore the file named example.html, specifically located in the directory named subdirectory1.

    !contacts.txt

    (Negation Rule) Explicitly tracks contacts.txt, even if all .txt files are ignored.

    !Engine/Batch/Builds

    (Negation Rule) Tracks the Builds directory inside Engine/Batch, overriding a broader exclusion.

    !Engine/Batch/Builds/**

    (Negation Rule) Tracks the Builds directory and all of its subdirectories inside Engine/Batch, overriding a broader exclusion.

    !.java

    (Negation Rule) Ensures that all .java files are included, overriding any previous ignore rules that might apply to them.

    !subdirectory1/*.txt

    (Negation Rule) Track files with the .txt extension located specifically in the subdirectory1 directory, even if other rules might otherwise ignore .txt files.

    BitoUtil?.java

    The ? (question mark) matches any single character in a filename or directory name.

    alpha.bito.aiarrow-up-right
    alpha.bito.aiarrow-up-right
    alpha.bito.aiarrow-up-right

    For Bitbucket Enterprise (Self-Hosted) use HTTP Access Token. Learn morearrow-up-right

  • Required scopes:

    • read:pullrequest:bitbucket

    • write:pullrequest:bitbucket

    • read:workspace:bitbucket

    • read:repository:bitbucket

    • read:user:bitbucket

  • Enter both your Bitbucket email address and the personal access token in Bito

  • )
  • Configure Network Access

    • If your network restricts external services from accessing your Git server, add these Bito IP addresses to your allowed IP list:

  • Learn morearrow-up-right
    Learn morearrow-up-right
    Learn morearrow-up-right
    alpha.bito.aiarrow-up-right
    GitLab (Self-Managed)
  • Bitbucket

  • Bitbucket (Self-Managed)

  • Will this change break anything? Based on the diff can we include anything?

  • Code structure and formatting (e.g., tab, spaces)

  • Basic coding standards including variable names (e.g., ijk)

  • Secrets scanning (e.g., passwords, API keys, sensitive information)
    AI that understands your code
    One-click setup for GitHub, GitLab, and Bitbucket
    Automated and manually-triggered AI code reviews
    Pull request summary
    Changelist
    One-click to accept suggestions
    Chat with AI Code Review Agent
    Incremental code reviews
    Code review analytics
    Custom code review rules and guidelines
    Multiple specialized engineers for targeted code analysis
    Integrated feedback from dev tools you use
    Jira integration
    Supports all major programming languages
    Enterprise-grade security
    Start free trial
    Get a demo
    AI Code Review Agentarrow-up-right
    Bito Cloudarrow-up-right
    AI Code Review Agent
    GitHub
    GitHub (Self-Managed)
    GitLab
    Agent settings
    Code Review Analyticsarrow-up-right
    Provide feedback on Bito-reported issues in pull requests
    Create custom code review guidelines via the dashboard
    Custom Guidelinesarrow-up-right
    OWASP Dependency-Checkarrow-up-right
    Snykarrow-up-right
    GitHub Dependabotarrow-up-right

    Learn more

    Learn more

    Summary of pull request in the description section.
    Changelist in AI Code Review Agent's feedback.
    One-click to accept AI code review suggestions
    One-click to accept AI code review suggestions

    Learn more

    Code Review Analytics dashboard

    Learn more

    Learn more

    Learn more

    Static Code Analysis feedback highlighting suggestions and fixes.
    Showing high-severity security vulnerabilities report.

    Learn more

    Learn more

    Learn more

    Learn more

    Note: This is an approximation based on code change detection
    Invalid Bito plan status
    PR Analytics
    page in your Bito dashboard.
  • Find the Agent instance you want to connect with Jira and open its settings.

  • Within the Agent settings screen, click on the Integrations tab.

  • Locate the Functional validation option and enable this setting to activate automatic pull request validation against Jira tickets.

  • page in your Bito dashboard.
  • Find the Agent instance you want to connect with Jira and open its settings.

  • Within the Agent settings screen, click on the Functional validation tab.

  • Locate the Functional validation option and enable this setting to activate automatic pull request validation against Jira tickets.

  • official Jira documentationarrow-up-right
    Repositoriesarrow-up-right
    Repositoriesarrow-up-right
    For the Bito-hosted AI Architect, use the following URL format: https://mcp.bito.ai/<Your-Bito-Workspace-ID>/mcp

    Replace <Your-Bito-Workspace-ID> with your actual Bito workspace ID, which you can find after logging into your Bito account at alpha.bito.aiarrow-up-right

  • Replace <Your-Bito-MCP-Access-Token> with the Bito MCP Access Token you received after completing the AI Architect setup.

  • Replace <Your-Email> with your actual email address.

  • For the Bito-hosted AI Architect, use the following URL format: https://mcp.bito.ai/<Your-Bito-Workspace-ID>/mcp

    Replace <Your-Bito-Workspace-ID> with your actual Bito workspace ID, which you can find after logging into your Bito account at alpha.bito.aiarrow-up-right

  • Replace <Your-Bito-MCP-Access-Token> with the Bito MCP Access Token you received after completing the AI Architect setup.

  • Replace <Your-Email> with your actual email address.

  • BitoAIArchitectGuidelines.md file
    BitoAIArchitectGuidelines.md file
    alpha.bito.aiarrow-up-right
    BitoAIArchitectGuidelines.md file
    BitoAIArchitectGuidelines.md file
    For the Bito-hosted AI Architect, use the following URL format: https://mcp.bito.ai/<Your-Bito-Workspace-ID>/mcp

    Replace <Your-Bito-Workspace-ID> with your actual Bito workspace ID, which you can find after logging into your Bito account at alpha.bito.aiarrow-up-right

  • Replace <Your-Bito-MCP-Access-Token> with the Bito MCP Access Token you received after completing the AI Architect setup.

  • Replace <Your-Email> with your actual email address.

  • For the Bito-hosted AI Architect, use the following URL format: https://mcp.bito.ai/<Your-Bito-Workspace-ID>/mcp

    Replace <Your-Bito-Workspace-ID> with your actual Bito workspace ID, which you can find after logging into your Bito account at alpha.bito.aiarrow-up-right

  • Replace <Your-Bito-MCP-Access-Token> with the Bito MCP Access Token you received after completing the AI Architect setup.

  • Replace <Your-Email> with your actual email address.

  • Junie will automatically use these guidelines for the project
    download Node.js 20.x LTSarrow-up-right
    BitoAIArchitectGuidelines.md file
    • --base option is mandatory with this type.

    best-practices - Code style, design patterns, maintainability

  • tests - Test coverage, test quality, testability

  • documentation - Comments, documentation quality, code clarity

  • p4 - Perforce repository

  • plain - No version control (analyze files directly)

  • review

    Analyze code changes and generate AI-powered feedback

    config

    Manage configuration settings and API keys

    --help

    Display help information

    --version

    Display the installed CLI version

    cd /path/to/your/project
    curl -sSL "https://mcp-setup.bito.ai/BitoAIArchitectGuidelines.md" -o CLAUDE.md
    cd /path/to/your/project
    curl -sfL "https://mcp-setup.bito.ai/BitoAIArchitectGuidelines.md" -o .cursorrules
    cd /path/to/your/project
    mkdir -p .windsurf/rules
    curl -sfL "https://mcp-setup.bito.ai/BitoAIArchitectGuidelines.md" -o .windsurf/rules/bitoai-architect.md
    cd /path/to/your/project
    mkdir -p .github
    curl -sfL "https://mcp-setup.bito.ai/BitoAIArchitectGuidelines.md" -o .github/copilot-instructions.md
    cd /path/to/your/project
    mkdir -p .junie
    curl -sfL "https://mcp-setup.bito.ai/BitoAIArchitectGuidelines.md" -o .junie/guidelines.md
    cd /path/to/your/project
    mkdir -p .aiassistant/rules
    curl -sfL "https://mcp-setup.bito.ai/BitoAIArchitectGuidelines.md" -o .aiassistant/rules/bitoai-architect.md
    {
      "mcpServers": {
        "BitoAIArchitect": {
          "serverUrl": "<Your-Bito-MCP-URL>",
          "headers": {
            "Authorization": "Bearer <Your-Bito-MCP-Access-Token>",
            "x-email-id": "<Your-Email>"
          }
        }
      }
    }
    {
      "mcpServers": {
        "existing-server": {
          ...
        },
        "BitoAIArchitect": {
          "serverUrl": "<Your-Bito-MCP-URL>",
          "headers": {
            "Authorization": "Bearer <Your-Bito-MCP-Access-Token>",
            "x-email-id": "<Your-Email>"
          }
        }
      }
    }
    mkdir %USERPROFILE%\.codeium\windsurf\memories
    copy BitoAIArchitectGuidelines.md %USERPROFILE%\.codeium\windsurf\memories\global_rules.md
    mkdir .windsurf\rules
    copy BitoAIArchitectGuidelines.md .windsurf\rules\bitoai-architect.md
    mkdir -p ~/.codeium/windsurf/memories
    cp BitoAIArchitectGuidelines.md ~/.codeium/windsurf/memories/global_rules.md
    mkdir -p .windsurf/rules
    cp BitoAIArchitectGuidelines.md .windsurf/rules/bitoai-architect.md
    node --version  # Should show v20.x.x or higher
    npx --version
    {
      "mcpServers": {
        "BitoAIArchitect": {
          "command": "npx",
          "args": [
            "-y",
            "mcp-remote",
            "<Your-Bito-MCP-URL>",
            "--header",
            "Authorization:${AUTH_HEADER}",
            "--header",
            "x-email-id: <Your-Email>"
          ],
          "env": {
            "AUTH_HEADER": "Bearer <Your-Bito-MCP-Access-Token>"
          }
        }
      }
    }
    {
      "mcpServers": {
        "BitoAIArchitect": {
          "command": "cmd",
          "args": [
            "/c",
            "npx",
            "-y",
            "mcp-remote",
            "<Your-Bito-MCP-URL>",
            "--header",
            "Authorization:${AUTH_HEADER}",
            "--header",
            "x-email-id: <Your-Email>"
          ],
          "env": {
            "AUTH_HEADER": "Bearer <Your-Bito-MCP-Access-Token>"
          }
        }
      }
    }
    mkdir -p .junie
    cp /path/to/BitoAIArchitectGuidelines.md .junie/guidelines.md
    bitoreview review [files...] [options]
    # Review all changes
    bitoreview review
    
    # Review specific files
    bitoreview review src/app.js src/utils/helper.js
    
    # Review files using glob patterns
    bitoreview review "src/**/*.js"
    
    # Review only uncommitted changes
    bitoreview review --type uncommitted
    
    # Run a fast, security-focused review
    bitoreview review --focus security --mode essential
    bitoreview review --type uncommitted
    bitoreview review --type committed --base main
    bitoreview review --base main
    bitoreview review --base develop
    bitoreview review --base-commit abc123
    # Quick review
    bitoreview review --mode essential
    
    # Thorough review
    bitoreview review --mode comprehensive
    bitoreview review --focus security
    bitoreview review --focus performance --mode essential
    # Show only high severity issues
    bitoreview review --severity high
    
    # Show medium and high severity
    bitoreview review --severity medium
    bitoreview review --interactive
    # or
    bitoreview review -i
    bitoreview review --plain
    bitoreview review --plain > review-report.txt
    bitoreview review --prompt-only
    bitoreview review --no-color
    bitoreview review --scm git
    bitoreview review --scm plain
    bitoreview review --config .bitoreview-custom.yaml
    bitoreview review -c config/bitoreview.yaml
    bitoreview review --api-key YOUR_API_KEY_HERE
    bitoreview review --cwd /path/to/project
    bitoreview review --debug
    bitoreview review -d
    bitoreview review --verbose
    bitoreview review -v
    bitoreview review --max-retries 5
    bitoreview config set-api-key [key]
    bitoreview config set-api-key
    bitoreview config set-api-key YOUR_API_KEY_HERE
    bitoreview config show-api-key
    bitoreview --help
    bitoreview review --help
    bitoreview config --help
    bitoreview --version
    # Fast pre-commit security check
    bitoreview review --type uncommitted --focus security --mode essential
    
    # Comprehensive performance review against main
    bitoreview review --base main --focus performance
    
    # High-severity bugs only in specific files
    bitoreview review src/critical/*.js --focus bugs --severity high
    
    # Plain text output for CI/CD with retries
    bitoreview review --plain --max-retries 3

    If the file doesn't exist, create it with this content:

    circle-info

    Note:

    • Replace <Your-Bito-MCP-URL> with the Bito MCP URL you received after completing the AI Architect setup.

      • For the Bito-hosted AI Architect, use the following URL format: https://mcp.bito.ai/<Your-Bito-Workspace-ID>/mcp

        Replace <Your-Bito-Workspace-ID> with your actual Bito workspace ID, which you can find after logging into your Bito account at

    • Replace <Your-Bito-MCP-Access-Token> with the Bito MCP Access Token you received after completing the AI Architect setup.

    • Replace <Your-Email> with your actual email address.

    1. If the file exists with other servers, add BitoAIArchitect to the mcpServers object:

    circle-info

    Note:

    • Replace <Your-Bito-MCP-URL> with the Bito MCP URL you received after completing the AI Architect setup.

      • For the Bito-hosted AI Architect, use the following URL format: https://mcp.bito.ai/<Your-Bito-Workspace-ID>/mcp

        Replace <Your-Bito-Workspace-ID> with your actual Bito workspace ID, which you can find after logging into your Bito account at

    • Replace <Your-Bito-MCP-Access-Token> with the Bito MCP Access Token you received after completing the AI Architect setup.

    • Replace <Your-Email> with your actual email address.

    In your project root, create .cursorrules file.

  • Open this file with a text editor.

  • Copy the contents of your BitoAIArchitectGuidelines.md file into .cursorules file.

  • Save.

  • Reopen Cursor
  • Open Settings → Tools & MCP

  • Verify BitoAIArchitect appears in the MCP servers list

  • For the Bito-hosted AI Architect, use the following URL format: https://mcp.bito.ai/<Your-Bito-Workspace-ID>/mcp

    Replace <Your-Bito-Workspace-ID> with your actual Bito workspace ID, which you can find after logging into your Bito account at alpha.bito.aiarrow-up-right

  • Replace <Your-Bito-MCP-Access-Token> with the Bito MCP Access Token you received after completing the AI Architect setup.

  • Replace <Your-Email> with your actual email address.

  • In your project root, create .cursorrules file.

  • Open this file with a text editor.

  • Copy the contents of your BitoAIArchitectGuidelines.md file into .cursorules file.

  • Save.

  • Reopen Cursor
  • Open Settings → Tools & MCP

  • Verify BitoAIArchitect appears in the MCP servers list

  • BitoAIArchitectGuidelines.md file
    BitoAIArchitectGuidelines.md file
    alpha.bito.aiarrow-up-right

    Chat

  • Functional Validation

  • mode, only critical issues are posted as inline comments, and other issues appear in the main review summary under "Additional issues".
  • In Comprehensive mode, Bito also includes minor suggestion and potential nitpicks as inline comments.

  • Automatic review: Toggle to enable or disable automatic reviews when a pull request is created and ready for review.

  • Automatic incremental review: Toggle to enable or disable reviews for new commits added to a pull request. Only changes since the last review are assessed.

    • Batch time: Specifies how long the AI Code Review Agent waits before running an incremental review after new commits are pushed. The value can range from 0m (review immediately) to 24h (review after 24 hours). Lower values result in more frequent incremental reviews.

      Examples:

      • 10s → waits 10 seconds before running the review

      • 12m → waits 12 minutes before running the review

      • 1h10m

  • Request changes comments: Enable this option to get Bito feedback as "Request changes" review comments. Depending on your organization's Git settings, you may need to resolve all comments before merging.

  • Draft pull requests: By default, the Agent excludes draft pull requests from automated reviews. Disable this toggle to include drafts.

  • Automatic summary: Toggle to enable automatic generation of AI summaries for changes, which are appended to the pull request description.

  • Change Walkthrough: Enable this option to generate a table of changes and associated files, posted as a comment on the pull request.

  • Allow config file settings: Enabling this setting will allow Agent Settings to be overridden at a repository level by placing a .bito.yaml file in the root folder of that repository. Learn more

  • Auto-apply agent rules: Automatically detect and apply best-practice guidelines from agent configuration files like CLAUDE.md, AGENTS.md, .cursor/rules, .windsurf/rules, or GEMINI.md. When enabled, Bito uses these files to guide its code review. Learn more

  • Generate interaction diagrams: When enabled, Bito will post interaction diagrams during code reviews to visualize architecture and impacted changes.

  • Adaptive learning: When enabled, Bito prioritizes future suggestions based on how developers responded to past Bito reviews.

    • Filter unaddressed suggestions: When enabled, Bito will reduce recommending suggestions that are consistently unaddressed. Critical suggestions may still be made.

  • command.
  • Exclude Labels: Specify pull request (PR) labels to exclude from review by name or glob/regex pattern. The agent will skip any PRs tagged with these labels in GitHub or GitLab.

  • Code Review > Repositoriesarrow-up-right
    Code Review > Repositoriesarrow-up-right
    Learn more
    Include Source/Target Branches filter
    Excluding Files, Folders, or Branches with Filters
    AI Code Review Agent
    Learn more
    Code Review > Repositoriesarrow-up-right

    hashtag
    Add Bito AI Architect MCP server

    Use the claude mcp add command with the correct parameter order:

    circle-info

    Note:

    • Replace <Your-Bito-MCP-URL> with the Bito MCP URL you received after completing the AI Architect setup.

      • For the Bito-hosted AI Architect, use the following URL format: https://mcp.bito.ai/<Your-Bito-Workspace-ID>/mcp

        Replace <Your-Bito-Workspace-ID> with your actual Bito workspace ID, which you can find after logging into your Bito account at

    circle-info

    Important: The server name and URL must come BEFORE the --header option.

    circle-info

    Scope options:

    • --scope user: Available in all your projects (recommended)

    • --scope project

    3

    hashtag
    Verify installation

    List your MCP servers:

    You should see "BitoAIArchitect" in the list.

    Test the server:

    4

    hashtag
    Add guidelines (optional but highly recommended)

    The BitoAIArchitectGuidelines.md file contains best practices, usage instructions, and prompting guidelines for the Bito AI Architect MCP server.

    The setup will work without this file, but including it helps AI tools interact more effectively with the Bito AI Architect MCP server.

    You can either create:

    1. Global guidelines - Apply across all your projects. Best for teams or developers who want consistent standards everywhere.

    2. Project-specific guidelines - Apply to a single project only.

    Choose one of the following based on your preference:

    hashtag
    Option A: Global guidelines

    Create .claude directory if it doesn't exist:

    Create or edit CLAUDE.md:

    Copy the contents of your into this file, then save.

    hashtag
    Option B: Project-specific guidelines

    Run this command in your project directory:

    Or run these commands:

    Copy the contents of your into this file, then save.

    5

    hashtag
    Start using Claude Code

    In your project directory, run:

    Now, in the chat you can ask questions about your indexed repositories. The AI Architect will help Claude Code provide accurate answers based on your codebase.

    Try asking something like:

    WSL

    ~/.claude/claude.json

    ~/.claude/settings.json

    ~/.claude/CLAUDE.md

    ~/.claude/mcp.json
    (this file doesn't exist)
  • ❌ Do NOT manually edit ~/.claude/claude.json (use CLI commands instead)

  • For the Bito-hosted AI Architect, use the following URL format: https://mcp.bito.ai/<Your-Bito-Workspace-ID>/mcp

    Replace <Your-Bito-Workspace-ID> with your actual Bito workspace ID, which you can find after logging into your Bito account at alpha.bito.aiarrow-up-right

  • Replace <Your-Bito-MCP-Access-Token> with the Bito MCP Access Token you received after completing the AI Architect setup.

  • Replace <Your-Email> with your actual email address.

  • For the Bito-hosted AI Architect, use the following URL format: https://mcp.bito.ai/<Your-Bito-Workspace-ID>/mcp

    Replace <Your-Bito-Workspace-ID> with your actual Bito workspace ID, which you can find after logging into your Bito account at alpha.bito.aiarrow-up-right

  • Replace <Your-Bito-MCP-Access-Token> with the Bito MCP Access Token you received after completing the AI Architect setup.

  • Windows

    %USERPROFILE%\.claude\claude.json

    %USERPROFILE%\.claude\settings.json

    %USERPROFILE%\.claude\CLAUDE.md

    macOS

    ~/.claude/claude.json

    ~/.claude/settings.json

    ~/.claude/CLAUDE.md

    Linux

    ~/.claude/claude.json

    ~/.claude/settings.json

    Try our Quick MCP Integration Guide
    AI Architect installation instructions
    Download BitoAIArchitectGuidelines.md filearrow-up-right

    ~/.claude/CLAUDE.md

    Bitbucket

  • Bitbucket (Self-Managed)

  • /review scalability
    : Assesses the code's ability to handle increased usage and scale effectively.
  • /review codeorg: Scans for readability and maintainability, promoting clear and efficient code organization.

  • /review codeoptimize: Identifies optimization opportunities to enhance code efficiency and reduce resource usage.

  • Add extra checks to improve code quality and security.
    Get a 14-day FREE trial of Bito's AI Code Review Agent.arrow-up-right
    View Guidearrow-up-right
    https://docs.gitlab.com/ee/user/group/saml_sso/arrow-up-right
    https://docs.gitlab.com/ee/integration/saml.htmlarrow-up-right
    https://docs.gitlab.com/ee/integration/saml.html#password-generation-for-users-created-through-samlarrow-up-right
    Log in to Bito Cloudarrow-up-right
    Repositoriesarrow-up-right
    generating a Personal Access Tokenarrow-up-right
    Prerequisites
    Learn more
    Include Source/Target Branches filter
    Available Commandsarrow-up-right
    Agent settings
    Learn more
    GitLab Personal Access Token
    Changelist in AI Code Review Agent's feedback.
  • JetBrains IDE: IntelliJ IDEA 2025.1+ (or PyCharm, WebStorm, PhpStorm, etc. 2025.1+)

  • AI Assistant Plugin (version 251.26094.80.5 or higher)

    1. Open your JetBrains IDE

    2. Go to: Settings (Ctrl/Cmd + Alt + S)

    3. Navigate to: Plugins

    4. Search for "AI Assistant"

    5. Verify version is 251.26094.80.5 or higher

  • Node.js: 20.18.1+ installed (for mcp-remote proxy)

    1. Why Node.js 20+? The mcp-remote proxy depends on undici v7, which requires Node.js 20+ (needs the File global API added in Node 20.0.0). Node.js 18 and earlier will fail with ReferenceError: File is not defined.

    2. Verify:

    3. If Node.js is not installed or the version < 20 then

  • Go to: Settings (Ctrl/Cmd + Alt + S)

  • Navigate to: Tools → AI Assistant → Model Context Protocol (MCP)

  • Click Add to add a new MCP server

  • 2

    hashtag
    Configure BitoAIArchitect

    The configuration dialog accepts JSON input. Paste the appropriate JSON configuration for your platform:

    hashtag
    macOS/Linux configuration:

    circle-info

    Note:

    • Replace <Your-Bito-MCP-URL> with the Bito MCP URL you received after completing the AI Architect setup.

    hashtag
    Windows configuration (IMPORTANT - uses cmd):

    circle-info

    Note:

    • Replace <Your-Bito-MCP-URL> with the Bito MCP URL you received after completing the AI Architect setup.

    3

    hashtag
    Save and restart

    1. Click OK to save the MCP server configuration

    2. Click OK to close Settings

    3. Restart your IDE completely

    4

    hashtag
    Verify connection

    1. Go to: Settings → Tools → AI Assistant → Model Context Protocol (MCP)

    2. Find BitoAIArchitect in the list

    3. Check the Status column - should show Running or Connected

    5

    hashtag
    Enable Codebase Mode

    IMPORTANT: MCP tools only work in "Codebase" mode or Edit mode.

    To use BitoAIArchitect:

    1. Open JetBrains AI Assistant chat

    2. Toggle on the "Codebase" mode switch at the top of the chat window

    3. OR use Edit mode (Ctrl/Cmd + Shift + Enter), which implicitly enables codebase context

    6

    hashtag
    Add guidelines (optional but highly recommended)

    The BitoAIArchitectGuidelines.md file contains best practices, usage instructions, and prompting guidelines for the Bito AI Architect MCP server.

    The setup will work without this file, but including it helps AI tools interact more effectively with the Bito AI Architect MCP server.

    To add Bito AI Architect usage rules to a specific project:

    1. Navigate to your project root

    2. Create .aiassistant/rules/ directory:

    3. Create a rule file (e.g., bitoai-architect.md):

    What AI Assistant rules should contain:

    • BitoAIArchitect MCP usage instructions

    • When to query organizational repositories

    • How to search for dependencies and tech stacks

    Restart the IDE completely

  • Check IDE logs for errors: Help → Show Log in Explorer/Finder

    • Look for files in the mcp folder

  • For the Bito-hosted AI Architect, use the following URL format: https://mcp.bito.ai/<Your-Bito-Workspace-ID>/mcp

    Replace <Your-Bito-Workspace-ID> with your actual Bito workspace ID, which you can find after logging into your Bito account at alpha.bito.aiarrow-up-right

  • Replace <Your-Bito-MCP-Access-Token> with the Bito MCP Access Token you received after completing the AI Architect setup.

  • Node.js must be in system PATH
    Try our Quick MCP Integration Guide
    AI Architect installation instructions
    Download BitoAIArchitectGuidelines.md filearrow-up-right

    Open a terminal and run the following command:

    hashtag
    Windows:

    Open PowerShell 7 and run the following command:

    circle-info

    Note: For Windows, AI Code Reviews in CLI currently supports PowerShell 7 only. If you don't have it installed, you can download it from the Microsoft Store:

    • Install PowerShell 7arrow-up-right

    circle-info

    Tip: If you encounter execution policy errors, run PowerShell 7 as Administrator or allow script execution temporarily.


    hashtag
    What gets installed:

    The installer will:

    1. Download the CLI binary for your platform

    2. Install it in a user-local directory:

      • macOS/Linux: ~/.bitoreview/bin/

      • Windows: %USERPROFILE%\.bitoreview\bin\

    3. Add the binary to your PATH so the bitoreview command is available globally

    4. Install bito-wingman (the AI engine) if it is not already present

    5. Create a br alias for quick access

    6. Automatically configures the usage guidelines globally for Claude Code and Windsurf (if detected). For other supported IDEs (such as Cursor, VS Code, etc.), you need to add the guidelines manually at the project level. See the commands given below in Add guidelines section.

    2

    hashtag
    Add guidelines

    The guidelines filearrow-up-right is a set of instructions that tells your AI coding agent (Claude Code, Cursor, etc.) how to correctly run bitoreview command when you ask it to do a code review. It defines the expected workflow, such as always using --prompt-only for structured JSON output, waiting for the review to complete before responding, grouping issues by severity, and validating problems in the actual code before suggesting fixes. Without these guidelines, the AI coding agent may not know how to use Bito's AI Code Reviews in CLI.

    hashtag
    Global configuration (auto-applied during install)

    During setup, the installer automatically adds the usage guidelines globally for the following AI coding agents if they are detected on your system:

    AI Coding Agent
    Guidelines file location

    hashtag
    Project-level configuration (manual, per-project)

    For all other supported IDEs such as Cursor, VS Code (GitHub Copilot), Junie, and JetBrains AI Assistant, you need to add the guidelines manually inside each project directory where you want them to apply.

    Navigate to your project root, then run the relevant command:

    Cursor:

    • macOS / Linux:

    • Windows:

    Windsurf:

    • macOS / Linux:

    • Windows:

    VS Code (GitHub Copilot):

    • macOS / Linux:

    • Windows:

    Junie:

    • macOS / Linux:

    • Windows:

    JetBrains AI Assistant:

    • macOS / Linux:

    • Windows:

    3

    hashtag
    Reload your terminal environment

    To make the CLI available immediately, restart your terminal or reload your shell configuration.

    hashtag
    macOS / Linux:

    Restart your terminal or run:

    hashtag
    Windows:

    • Restart PowerShell 7 or

    • Run refreshenv if Chocolatey is installed

    4

    hashtag
    Verify installation

    Confirm that the CLI is installed correctly:

    The installer also creates a shortcut alias:

    circle-info

    Both commands should return the same version.

    5

    hashtag
    Authentication setup

    To run code reviews, the CLI requires a valid Bito API key (aka Bito Access Key).

    hashtag
    Get Bito API key:

    You can sign up for a Bito account at , and create an access key from


    hashtag
    Configure the Bito API key:

    You can configure authentication in multiple ways.

    • Method 1: Interactive setup (recommended) - You'll be prompted to paste your securely.

    • Method 2: Direct CLI setup - Useful for automation or scripted setups.

    circle-info

    Note: replace YOUR_API_KEY_HERE with your actual .

    • Method 3: Environment variable - Useful for CI/CD pipelines, shared machines, temporary or project-specific credentials

    circle-info

    Note: replace YOUR_API_KEY_HERE with your actual .


    hashtag
    Verify your Bito API key:

    To confirm your Bito API key is configured correctly, run:


    hashtag
    Bito API key resolution priority

    If multiple API keys are configured, the CLI resolves them in the following order:

    1. Command-line flag: --api-key YOUR_KEY

    2. Environment variable: BITO_API_KEY

    3. Stored configuration file: ~/.bitowingman/env

    This makes it easy to override credentials per command, project, or environment.

    6

    hashtag
    Next steps

    You’re now ready to run AI-powered code reviews from your terminal.

    • How to use? – Run your first code review

    • – Complete reference of CLI commands

    • – Common issues and how to resolve them

    https://alpha.bito.aiarrow-up-right
    Settings -> Advanced Settingsarrow-up-right
    View Guide
    hashtag
    Why use repo-level settings

    Large organizations often have different review needs across projects.

    Centralized (agent-level) settings don’t scale well — especially when each repo has its own coding standards, branch structure, or tooling.

    Repo-level configuration helps by:

    • Enabling custom review behavior per repository.

    • Allowing custom guidelines flexibility at the repo level.

    • Keeping settings version-controlled and transparent.

    hashtag
    How it works

    1. Add a .bito.yaml file to the root of your repository. To get started, download a sample .bito.yaml filearrow-up-right.

    2. Add the supported configuration fields (key-value pairs) to specify how the Code Review Agent should behave for that repository.

    3. When the Code Review Agent runs, Bito automatically detects the file and applies those settings for that repository.

    circle-info

    Note: Repo-level overrides are applied only if your workspace admin has enabled “Allow config file settings” in Agent Settings. This option is required for repo-level overrides to take effect and is turned on by default.

    hashtag
    Enabling repo-level overrides

    Admins can manage this from the Agent Settingsarrow-up-right panel.

    • Setting name: Allow config file settings

    • Description: Enabling this allows repositories to override Agent Settings by placing a .bito.yaml file in the repo root.

    circle-info

    Note: Only workspace admins can toggle this setting from the Bito dashboard (cannot be changed via .bito.yaml file).

    hashtag
    Supported settings in .bito.yaml file

    You can override the following Code Review Agent settings:

    suggestion_mode

    Controls how detailed the review comments are. Choose between Essential and Comprehensive review modes:

    • In Essential mode, only critical issues are posted as inline comments, and other issues appear in the main review summary under "Additional issues".

    • In Comprehensive mode, Bito also includes minor suggestion and potential nitpicks as inline comments.

    Valid values: essential

    post_description

    Automatically create summary of changes and append to your existing pull request summary. Valid values: true or false

    post_changelist

    Adds a walkthrough section to pull request comments. Valid values: true or false

    include_source_branches

    Source branches defined using comma-separated GLOB or regex patterns for which Bito automatically reviews pull requests. Example: "feature/*, release/*, main"

    include_target_branches

    Target branches defined using comma-separated GLOB or regex patterns for which Bito automatically reviews pull requests. Example: "feature/*, release/*, main"

    exclude_files

    Comma-separated file path GLOB patterns to exclude from code reviews. Example: "*.md, *.yaml, config/*"

    exclude_draft_pr

    Excludes draft pull requests from automatic reviews. Valid values: true or false

    hashtag
    Sample .bito.yaml file

    hashtag
    Download .bito.yaml file

    hashtag
    From GitHub:

    You can download a sample .bito.yaml configuration file directly from Bito’s official GitHub repository.

    This file includes all supported configuration fields with example values to help you get started quickly.

    1. Go to the Bito GitHub repositoryarrow-up-right.

    2. Open the .bito.yaml file.

    3. Click the Download raw file button to download it.

    hashtag
    From Bito Cloud UI:

    You can also download the sample .bito.yaml configuration file from the Bito Cloud UI.

    • Go to Repositoriesarrow-up-right dashboard.

    • Click the Download settings file button given in the Agent panel.

    circle-info

    Note: Web browsers such as Google Chrome do not allow downloading files that begin with a dot .. As a result, when you download the sample settings file, it will be saved with a different name (for example, agent.yaml or bito.yaml). To use it correctly, rename the file to .bito.yaml before adding it to your repository.

    circle-info

    Note: By default, files that start with a dot . are hidden in most file explorers.

    To view hidden files:

    • Windows: In File Explorer, go to the top menu bar, click View, then enable Hidden items.

    • macOS: Press Command + Shift + . in Finder.

    • Linux: Run ls -a in your terminal.

    circle-info

    Note: On macOS, the Finder app may not allow naming a file starting with a dot (e.g., .bito.yaml). In that case, open Terminal and use the following command to rename the file (replace filename.yaml with your actual file name):

    mv filename.yaml .bito.yaml

    hashtag
    Rules and limits

    • The .bito.yaml file is read from the source branch of the pull request.

    • If a repo defines custom guidelines, agent-level guidelines are ignored for that repository.

    • If any property in the .bito.yaml file contains an invalid value, the entire configuration file will be rejected and default Agent Settings will be used instead.

    • If a property is missing in the .bito.yaml file, the corresponding value from the global Agent Settings will be used instead.

    AI Code Review Agent

    Get a 14-day FREE trial of Bito's AI Code Review Agent.arrow-up-right

    hashtag
    Video tutorial

    coming soon...

    hashtag
    Prerequisites

    Before proceeding, ensure you've completed all necessary prerequisites.

    hashtag
    1. Create a GitHub Personal Access Token (classic):

    For GitHub pull request code reviews, ensure you have a CLASSIC personal access token with repo scope. We do not support fine-grained tokens currently.

    View Guidearrow-up-right

    GitHub Personal Access Token (classic)

    hashtag
    2. Authorizing a GitHub Personal Access Token for use with SAML single sign-on:

    If your GitHub organization enforces SAML Single Sign-On (SSO)arrow-up-right, you must authorize your Personal Access Token (classic) through your Identity Provider (IdP); otherwise, Bito's AI Code Review Agent won't function properly.

    For detailed instructions, please refer to the GitHub documentationarrow-up-right.

    hashtag
    Installation and configuration steps

    Follow the step-by-step instructions below to install the AI Code Review Agent using Bito Cloud:

    hashtag
    Step 1: Log in to Bito

    Log in to Bito Cloudarrow-up-right and select a workspace to get started.

    hashtag
    Step 2: Open the Code Review Agents setup

    Click Repositoriesarrow-up-right under the CODE REVIEW section in the sidebar.

    hashtag
    Step 3: Select your Git provider

    Bito supports integration with the following Git providers:

    • GitHub

    • GitHub (Self-Managed)

    • GitLab

    • GitLab (Self-Managed)

    • Bitbucket

    • Bitbucket (Self-Managed)

    Since we are setting up the Agent for self-managed GitHub Enterprise server, select GitHub (Self-Managed) to proceed.

    circle-info

    Supported versions:

    • GitHub Enterprise Server: 3.0 and above

    hashtag
    Step 4: Register & install the Bito App for GitHub

    To enable pull request reviews, you need to register and install the Bito’s AI Code Review Agent app on your self-managed GitHub Enterprise server.

    circle-info

    If your network blocks external services from interacting with the GitHub server, whitelist all of Bito's gateway IP addresses in your firewall to ensure Bito can access your self-hosted repositories. The Agent response can come from any of these IPs.

    • List of IP addresses to whitelist:

      • 18.188.201.104

      • 3.23.173.30

      • 18.216.64.170

    You need to enter the details for the below mentioned input fields:

    • Hosted GitHub URL: This is the domain portion of the URL where you GitHub Enterprise Server is hosted (e.g., https://yourcompany.github.com). Please check with your GitHub administrator for the correct URL.

    • Personal Access Token: Generate a Personal Access Token (classic) with “repo” scope in your GitHub (Self-Managed) account and enter it into the Personal Access Token input field. We do not support fine-grained tokens currently. For guidance, refer to the instructions in the Prerequisites section.

    Click Validate to ensure the login credentials are working correctly. If the credentials are successfully validated, click the Install Bito App for GitHub button. This will redirect you to your GitHub (Self-Managed) server.

    Before proceeding, you’ll be asked to enter your GitHub App name — this is the name that will appear in your GitHub Apps list and during installations. Choose a clear, recognizable name (for example, “Bito Code Reviewer”).

    Now select where you want to install the app:

    • Choose All repositories to enable Bito for every repository in your account.

    • Or, select Only select repositories and pick specific repositories using the dropdown menu.

    circle-info

    Bito app uses these permissions:

    • Read access to metadata

    • Read and write access to code, issues, and pull requests

    • Read access to organization members

    Click Install & Authorize to proceed. Once completed, you will be redirected to Bito.

    hashtag
    Step 5: Enable AI Code Review Agent on repositories

    After connecting Bito to your self-managed GitHub Enterprise server, you'll see a list of repositories that Bito has access to.

    Use the toggles in the Code Review Status column to enable or disable the Agent for each repository.

    circle-info

    To customize the Agent’s behavior, you can edit existing configurations or create new Agents as needed.

    Learn more

    hashtag
    Step 6: Automated and manual pull request reviews

    Once a repository is enabled, you can invoke the AI Code Review Agent in the following ways:

    1. Automated code review: By default, the Agent automatically reviews all new pull requests and provides detailed feedback.

    2. Manually trigger code review: To initiate a manual review, simply type /review in the comment box on the pull request and submit it. This action will start the code review process.

    The AI-generated code review feedback will be posted as comments directly within your pull request, making it seamless to view and address suggestions right where they matter most.

    circle-info

    Note: To enhance efficiency, the automated code reviews are only triggered for pull requests merging into the repository’s default branch. This prevents unnecessary processing and Advanced AI requests usage.

    To review additional branches, you can use the Include Source/Target Branches filter. Bito will review pull requests when the source or target branch matches the list.

    The Include Source/Target Branches filter applies only to automatically triggered reviews. Users should still be able to trigger reviews manually via the /review command.

    circle-info

    The AI Code Review Agent automatically reviews code changes up to 5000 lines when a pull request is created. For larger changes, you can use the /review command.

    circle-info

    It may take a few minutes to get the code review posted as a comment, depending on the size of the pull request.

    hashtag
    Step 7: Specialized commands for code reviews

    Bito also offers specialized commands that are designed to provide detailed insights into specific areas of your source code, including security, performance, scalability, code structure, and optimization.

    • /review security: Analyzes code to identify security vulnerabilities and ensure secure coding practices.

    • /review performance: Evaluates code for performance issues, identifying slow or resource-heavy areas.

    • /review scalability: Assesses the code's ability to handle increased usage and scale effectively.

    • /review codeorg: Scans for readability and maintainability, promoting clear and efficient code organization.

    • /review codeoptimize: Identifies optimization opportunities to enhance code efficiency and reduce resource usage.

    By default, the /review command generates inline comments, meaning that code suggestions are inserted directly beneath the code diffs in each file. This approach provides a clearer view of the exact lines requiring improvement. However, if you prefer a code review in a single post rather than separate inline comments under the diffs, you can include the optional parameter: /review #inline_comment=False

    For more details, refer to Available Commandsarrow-up-right.

    hashtag
    Step 8: Chat with AI Code Review Agent

    Ask questions directly to the AI Code Review Agent regarding its code review feedback. You can inquire about highlighted issues, request alternative solutions, or seek clarifications on suggested fixes.

    To start the conversation, type your question in the comment box within the inline suggestions on your pull request, and then submit it. Typically, Bito AI responses are delivered in about 10 seconds. On GitHub and Bitbucket, you need to manually refresh the page to see the responses, while GitLab updates automatically.

    Bito supports over 20 languages—including English, Hindi, Chinese, and Spanish—so you can interact with the AI in the language you’re most comfortable with.

    hashtag
    Step 9: Configure Agent settings

    Agent settings let you control how reviews are performed, ensuring feedback is tailored to your team’s needs. By adjusting the options, you can:

    • Make reviews more focused and actionable.

    • Apply your own coding standards.

    • Reduce noise by excluding irrelevant files or branches.

    • Add extra checks to improve code quality and security.

    Learn more

    hashtag
    Screenshots

    hashtag
    Screenshot # 1

    circle-info

    AI-generated pull request (PR) summary

    hashtag
    Screenshot # 2

    circle-info

    Changelist showing key changes and impacted files in a pull request.

    Changelist in AI Code Review Agent's feedback.

    hashtag
    Screenshot # 3

    circle-info

    AI code review feedback posted as comments on the pull request.

    AI Code Review Agentarrow-up-right
    available commandsarrow-up-right
    Pricingarrow-up-right
    GitHub Personal Access Token (Classic): For GitHub PR code reviews, ensure you have a CLASSIC personal access token with repo access. We do not support fine-grained tokens currently. View Guidearrow-up-right
    GitHub Personal Access Token (Classic)

    hashtag
    Installation and Configuration Steps:

    1. Enable GitHub Actions:

      • Login to your GitHubarrow-up-right account.

      • Open your repository and click on the "Settings" tab.

      • Select "Actions" from the left sidebar, then click on "General".

      • Under "Actions permissions", choose "Allow all actions and reusable workflows" and click "Save".

    2. Set Up Environment Variables:

      • Still in the "Settings" tab, navigate to "Secrets and variables" > "Actions" from the left sidebar.

    circle-info

    Check the above "Prerequisites" section to learn more about creating the access tokens needed to configure the Agent.

    • Configure the following under the "Variables" tab:

      For each variable, click the New repository variable button, then enter the exact name and value of the variable in the form. Finally, click Add variable to save it.

      • Name: STATIC_ANALYSIS_TOOL

        • Value: Enter the following text string as value: fb_infer,astral_ruff,mypy

      • Name: GIT_DOMAIN

        • Value: Enter the domain name of your Enterprise or self-hosted GitHub deployment or skip this if you are not using Enterprise or self-hosted GitHub deployment.

        • Example of domain name: https://your.company.git.com

      • Name: EXCLUDE_BRANCHES

        • Value: Specify branches to exclude from the review by name or valid glob/regex patterns. The agent will skip the pull request review if the source or target branch matches the exclusion list.

        • Note: For more information, see .

      • Name: EXCLUDE_FILES

        • Value: Specify files/folders to exclude from the review by name or glob/regex pattern. The agent will skip files/folders that match the exclusion list.

        • Note: For more information, see .

      • Name: EXCLUDE_DRAFT_PR

        • Value: Enter True to disable automated review for draft pull requests, or False to enable it.

    1. Create the Workflow Directory:

      • In your repository, create a new directory path: .github/workflows.

    2. Add the Workflow File:

      • from AI Code Review Agent's GitHub repo.

      • In your repository, upload this

    hashtag
    Customizations for self-hosted GitHub

    1. Create a self-hosted Runner using Linux image and x64 architecture as described in the GitHub documentationarrow-up-right.

    2. Create a copy of Bito's repository gitbito/codereviewagentarrow-up-right main branch into your self-hosted GitHub organization e.g. "myorg" under the required name e.g. "gitbito-bitocodereview". In this example, now this repository will be accessible as "myorg/gitbito-bitocodereview".

    3. Update test_cra.ymlas below:

      • Change line from:

        • runs-on: ubuntu-latest

      • to:

        • runs-on: <label of the self-hosted GitHub Runner> e.g. self-hosted, linux etc.

    4. Update test_cra.ymlas below:

      • Replace all lines having below text:

        • uses: gitbito/codereviewagent@main

    5. Commit and push your changes in test_cra.yml .

    hashtag
    Using the AI Code Review Agent

    After configuring the GitHub Actions, you can invoke the AI Code Review Agent in the following ways:

    circle-info

    Note: To improve efficiency, the AI Code Review Agent is disabled by default for pull requests involving the "main" branch. This prevents unnecessary processing and token usage, as changes to the "main" branch are typically already reviewed in release or feature branches. To change this default behavior and include the "main" branch, please contact supportenvelope.

    1. Automated Code Review: The agent will automatically review new pull requests as soon as they are created and post the review feedback as a comment within your PR.

    2. Manually Trigger Code Review: To start the process, simply type /review in the comment box on the pull request and submit it. This command prompts the agent to review the pull request and post its feedback directly in the PR as a comment.

      Bito also offers specialized commands that are designed to provide detailed insights into specific areas of your source code, including security, performance, scalability, code structure, and optimization.

      • /review security: Analyzes code to identify security vulnerabilities and ensure secure coding practices.

      • /review performance: Evaluates code for performance issues, identifying slow or resource-heavy areas.

      By default, the /review command generates inline comments, meaning that code suggestions are inserted directly beneath the code diffs in each file. This approach provides a clearer view of the exact lines requiring improvement. However, if you prefer a code review in a single post rather than separate inline comments under the diffs, you can include the optional parameter: /review #inline_comment=False

      For more details, refer to .

    circle-info

    It may take a few minutes to get the code review posted as a comment, depending on the size of the pull request.

    hashtag
    Screenshots

    hashtag
    Screenshot # 1

    circle-info

    AI-generated pull request (PR) summary

    hashtag
    Screenshot # 2

    circle-info

    Changelist showing key changes and impacted files in a pull request.

    Changelist in AI Code Review Agent's feedback.

    hashtag
    Screenshot # 3

    circle-info

    AI code review feedback posted as comments on the pull request.

    View Guide
    Bitbucket documentationarrow-up-right

    Agent Configuration: bito-cra.properties File

    Setting up your agent: understanding the bito-cra.properties file

    circle-info

    Note: This file is only available for people who are using the self-hosted version of AI Code Review Agent.

    The bito-cra.properties file offers a comprehensive range of options for configuring the AI Code Review Agent, enhancing its flexibility and adaptability to various workflow requirements.

    hashtag
    bito-cra.properties Available Options

    Property Name
    Supported Values
    Is Mandatory?
    Description

    Excluding files, folders, or branches with filters

    Customize which files, folders, and Git branches are reviewed when the Agent triggers automatically on pull requests.

    The AI Code Review Agent offers powerful filters to exclude specific files and folders from code reviews and gives you precise control over which Git branches are included in automated reviews.

    These filters can be configured at the Agent instance level, overriding the default behavior.

    hashtag
    Exclude Files and Folders filter

    A list of files/folders that the AI Code Review Agent will not review if they are present in the diff. You can specify the files/folders to exclude from the review by name or glob/regex pattern. The Agent will automatically skip any files or folders that match the exclusion list.

    This filter applies to both manual reviews initiated through the /review command and automated reviews triggered via webhook.

    By default, these files are excluded: *.xml, *.json, *.properties, .gitignore, *.yml, *.md

    hashtag
    Examples

    circle-info

    Note:

    • Patterns are case sensitive.

    • Don’t use double quotes, single quotes or comma in the pattern.

    Exclusion Rule for Files & Folders
    Applicable Pattern
    Matched Examples
    Not Matched Examples

    hashtag
    Include Source/Target Branches filter

    This filter defines which pull requests trigger automated reviews based on their source or target branch, allowing you to focus on critical code and avoid unnecessary reviews or AI usage.

    By default, pull requests merging into the repository’s default branch are subject to review. To extend review coverage, additional branches may be specified using explicit branch names or valid glob/regex patterns. When the source or target branch of a pull request matches one of the patterns on your inclusion list, Bito’s AI Code Review Agent will trigger an automated review.

    This filter applies only to automatically triggered reviews. Users should still be able to trigger reviews manually via the /review command.

    Watch video tutorial:

    hashtag
    Examples

    circle-info

    Note:

    • Patterns are case sensitive.

    • Don’t use double quotes, single quotes or comma in the pattern.

    Inclusion Rules for Branch
    Pattern
    Matched Examples
    Not Matched Examples

    hashtag
    Draft pull requests filter

    A binary setting that enables/disables automated review of pull requests (PR) based on the draft status. Enter True to disable automated review for draft pull requests, or False to enable it.

    The default value is True which skips automated review of draft PR.

    hashtag
    How to configure the filters?

    hashtag
    Bito Cloud (Bito-hosted Agent)

    You can configure filters using the Agent configuration page. For detailed instructions, please refer to the documentation page.

    hashtag
    CLI or webhooks service (self-hosted Agent)

    You can configure filters using the . Check the options exclude_branches, exclude_files, and exclude_draft_pr for more details.

    hashtag
    GitHub Actions (self-hosted Agent)

    You can configure filters using the GitHub Actions repository variables: EXCLUDE_BRANCHES, EXCLUDE_FILES, and EXCLUDE_DRAFT_PR. For detailed instructions, please refer to the documentation page.

    Guide for GitHub Copilot (VS Code)

    Integrate GitHub Copilot in VS Code with AI Architect for more accurate, codebase-aware AI assistance.

    Use Bito's AI Architect with GitHub Copilot in VS Code to enhance your AI-powered coding experience.

    Once connected via MCP (Model Context Protocol), GitHub Copilot can leverage AI Architect’s deep contextual understanding of your project, enabling more accurate code suggestions, explanations, and code insights.

    hashtag
    Quick setup (recommended)

    Want to get started faster? We offer an automated installer that can configure AI Architect for all your AI coding tools in just a few seconds.

    The automated setup will:

    • Detect all compatible AI tools installed on your system

    • Configure them automatically with your credentials

    • Save you time by eliminating manual configuration steps

    👉 for automated setup.

    hashtag
    Manual setup

    If you prefer manual configuration, follow the step-by-step instructions below.

    hashtag
    Prerequisites

    1. Follow the . Upon successful setup, you will receive a Bito MCP URL and Bito MCP Access Token that you need to enter in your coding agent.

    2. . You will need to copy/paste the content from this file later when configuring AI Architect.

      • Note: This file contains best practices, usage instructions, and prompting guidelines for the Bito AI Architect MCP server. The setup will work without this file, but including it helps AI tools interact more effectively with the Bito AI Architect MCP server.

    hashtag
    Set up AI Architect

    VS Code has the same setup process across all platforms (Windows, macOS, Linux, WSL).

    hashtag
    Workspace configuration (recommended)

    1

    hashtag
    Create .vscode directory

    In your project root:

    2

    hashtag
    User configuration (global)

    To make BitoAIArchitect available in ALL projects, create a user-level mcp.json file:

    hashtag
    Windows

    • Create/edit: %APPDATA%\Code\User\mcp.json

    hashtag
    macOS

    • Create/edit: ~/Library/Application Support/Code/User/mcp.json

    hashtag
    Linux

    • Create/edit: ~/.config/Code/User/mcp.json

    hashtag
    Configuration

    Add this to your mcp.json:

    circle-info

    Note:

    • Replace <Your-Bito-MCP-URL> with the Bito MCP URL you received after completing the AI Architect setup.

    hashtag
    Enable MCP discovery

    Also ensure MCP discovery is enabled in your settings.json:

    Important:

    • User-level config uses mcp.json (separate from settings.json)

    • Include "type": "stdio" in the configuration

    • After saving, manually start the server via Copilot Chat (see Step 4 above)

    hashtag
    Troubleshooting VS Code (GitHub Copilot)

    hashtag
    Server not appearing in MCP Servers list:

    1. Verify mcp.json is in the correct location (see paths above)

    2. Ensure "type": "stdio" is included in the configuration

    3. Check JSON syntax is valid

    hashtag
    Server not starting:

    1. Manually start the server:

      • Open Copilot Chat → gear icon → MCP Servers

      • Click gear icon next to BitoAIArchitect → Start Server

    hashtag
    Tools not showing in Copilot Chat:

    1. Ensure server is started (see above)

    2. Open Copilot Chat

    3. Switch to Agent mode

    4. Click Tools (wrench icon)

    hashtag
    Agent Mode not available:

    1. Update VS Code to 1.99+

    2. Settings → Search: chat.agent.enabled

    3. Enable the checkbox

    hashtag
    MCP discovery issues:

    Ensure settings.json has:

    Note: This must be a boolean true, NOT an object like {"claude-desktop": true}.

    hashtag
    Node.js version too old:

    Error: ReferenceError: File is not defined or similar

    • Upgrade Node.js to 20.18.1 or later

    • If using nvm: nvm install 20 && nvm use 20 && nvm alias default 20

    hashtag
    Reset if needed:

    • Ctrl/Cmd + Shift + P

    • Run: MCP: Reset Cached Tools

    • Restart VS Code

    hashtag
    OAuth prompts appearing:

    If VS Code is prompting for OAuth instead of using your Bearer token:

    1. Ensure you're using the mcp-remote proxy configuration (not direct HTTP)

    2. Verify "type": "stdio" is in your config

    3. Cancel the OAuth prompt - the server should still work

    Guide for GitLab (Self-Managed)

    Integrate the AI Code Review Agent into your self-hosted GitLab workflow.

    Speed up code reviews by configuring the with your GitLab (Self-Managed) server. In this guide, you'll learn how to set up the Agent to receive automated code reviews that trigger whenever you create a merge request, as well as how to manually initiate reviews using .

    circle-info

    The Free Plan offers AI-generated pull request summaries to provide a quick overview of changes. For advanced features like line-level code suggestions, consider upgrading to the Team Plan. For detailed pricing information, visit our page.

    nano ~/.cursor/mcp.json
    {
      "mcpServers": {
        "BitoAIArchitect": {
          "url": "<Your-Bito-MCP-URL>",
          "headers": {
            "Authorization": "Bearer <Your-Bito-MCP-Access-Token>",
            "x-email-id": "<Your-Email>"
          }
        }
      }
    }
    {
      "mcpServers": {
        "BitoAIArchitect": {
          "url": "<Your-Bito-MCP-URL>",
          "headers": {
            "Authorization": "Bearer <Your-Bito-MCP-Access-Token>",
            "x-email-id": "<Your-Email>"
          }
        }
      }
    }
    {
      "mcpServers": {
        "existing-server": {
          ...
        },
        "BitoAIArchitect": {
          "url": "<Your-Bito-MCP-URL>",
          "headers": {
            "Authorization": "Bearer <Your-Bito-MCP-Access-Token>",
            "x-email-id": "<Your-Email>"
          }
        }
      }
    }
    claude mcp add \
      --transport http \
      --scope user \
      BitoAIArchitect \
      <Your-Bito-MCP-URL> \
      --header "Authorization: Bearer <Your-Bito-MCP-Access-Token>" \
      --header "x-email-id: <Your-Email>"
    claude mcp list
    claude mcp get BitoAIArchitect
    claude
    What repositories are available in my organization?
    npm install -g @anthropic-ai/claude-code
    claude --version
    # For stdio servers on Windows
    claude mcp add --transport stdio my-server -- cmd /c npx -y @some/package
    # Add HTTP server with Bearer token (correct parameter order)
    claude mcp add --transport http --scope user \
      <name> <url> \
      --header "Authorization: Bearer <token>" \
      --header "x-email-id: <your-email>"
    
    # Add server with environment variables
    claude mcp add <name> -e API_KEY="value" -- npx @server/package
    
    # Add server with JSON config (for complex setups)
    claude mcp add-json <name> '{"type":"http","url":"...","headers":{...}}'
    
    # List all MCP servers
    claude mcp list
    
    # Get server details
    claude mcp get <name>
    
    # Remove MCP server
    claude mcp remove <name>
    
    # View server status (inside Claude Code session)
    /mcp
    
    # Reset project-scoped server approval choices
    claude mcp reset-project-choices
    
    # Verify it was added
    claude mcp list
    
    # Check for errors
    claude --verbose
    
    # Try removing and re-adding
    claude mcp remove BitoAIArchitect
    claude mcp add --transport http --scope user \
      BitoAIArchitect <Your-Bito-MCP-URL> \
      --header "Authorization: Bearer <Your-Bito-MCP-Access-Token>" \
      --header "x-email-id: <Your-Email>"
    # Test the endpoint with proper MCP protocol
    curl -s -X POST \
      -H "Authorization: Bearer <Your-Bito-MCP-Access-Token>" \
      -H "Content-Type: application/json" \
      -d '{"jsonrpc":"2.0","method":"initialize","params":{},"id":1}' \
      <Your-Bito-MCP-URL>
    
    # Should return HTTP 200 with JSON response for valid credentials
    # HTTP 401: Invalid Bito MCP Access Token
    # HTTP 404: Invalid Bito MCP URL
    chmod 755 ~/.claude
    chmod 644 ~/.claude/claude.json
    chmod 644 ~/.claude/settings.json
    # Use proper MCP protocol to test authentication
    curl -s -X POST \
      -H "Authorization: Bearer <Your-Bito-MCP-Access-Token>" \
      -H "Content-Type: application/json" \
      -d '{"jsonrpc":"2.0","method":"initialize","params":{},"id":1}' \
      <Your-Bito-MCP-URL>
    bitoreview --version
    br --version
    curl -fsSL https://bitoreview.bito.ai/install.sh | bash
    irm https://bitoreview.bito.ai/install.ps1 | iex
    suggestion_mode: comprehensive       # 'essential' = only major issues, 'comprehensive' = everything
    post_description: true                # Include summary description in PR comment
    post_changelist: true                 # Include walkthrough of changes
    
    include_source_branches: feature/**,bugfix/**
    include_target_branches: main,develop
    exclude_files: docs/**,README.md
    
    exclude_draft_pr: true            # Don't review draft PRs
    secret_scanner_feedback: true      # Enable secret scanning feedback
    linters_feedback: true             # Enable linting / static analysis
    
    custom_guidelines:
      general:
        - name: "Global Checks"
          path: "./guidelines/global_checks.txt"
        - name: "Security Rules"
          path: "./guidelines/security.txt"
        - name: "Legacy Style Guide"
          path: "./guidelines/legacy.txt"
        - name: "Performance Checks"
          path: "./guidelines/perf.txt"
        - name: "Code Style"
          path: "./guidelines/style.txt"
      per_language:
        python:
          name: "Python Best Practices"
          path: "./guidelines/py.txt"
        javascript:
          name: "JS Style Guide"
          path: "./guidelines/js.txt"
        typescript:
          name: "TS Checks"
          path: "./guidelines/ts.txt"
        java:
          name: "Java Coding Standards"  
          Path: "./guidelines/java.txt"  
    
    → waits
    1 hour and 10 minutes
    before running the review
    alpha.bito.aiarrow-up-right
    alpha.bito.aiarrow-up-right
    Logo

    Replace <Your-Bito-MCP-Access-Token> with the Bito MCP Access Token you received after completing the AI Architect setup.

  • Replace <Your-Email> with your actual email address.

  • : Only in current project (stored in
    .mcp.json
    )
  • --scope local: Only in current directory (default)

  • alpha.bito.aiarrow-up-right
    BitoAIArchitectGuidelines.md file
    BitoAIArchitectGuidelines.md file

    Claude Code

    ~/.claude/CLAUDE.md

    Windsurf

    ~/.codeium/windsurf/memories/global_rules.md

    https://alpha.bito.aiarrow-up-right
    Settings -> Advanced Settingsarrow-up-right
    View Guide
    Bito API key
    Bito API key
    Bito API key
    Available commands
    Troubleshooting
    or
    comprehensive

    secret_scanner_feedback

    Enables or disables secret scanning feedback. Bito detects and reports secrets left in code changes. Valid values: true or false

    linters_feedback

    Run Linting tools during code reviews. Valid values: true or false

    custom_guidelines

    Adds repo-defined coding guidelines, supporting both general and language-specific configurations. Provide the name and path to review guidelines that you want bito to follow. These files must exist in your source branch at review time. We accept up to 3 general guidelines and 1 language specific guideline per language. Example:

    dependency_check.enabled

    Run Dependency Check analysis during code reviews.

    Valid values: true or false

    repo_level_guidelines_enabled

    When enabled, Bito will automatically detect and use best-practice guidelines from agent configuration files such as CLAUDE.md, AGENTS.md, GEMINI.md, .cursor/rules, or .windsurf/rules during code reviews. Valid values: true or false

    sequence_diagram_enabled

    When enabled, Bito will generate interaction diagrams during code reviews to visualize the architecture and impacted components in the submitted changes. Currently, it is supported for GitHub and GitLab. Valid values: true or false

    static_analysis.fb_infer.enabled

    Run Static Analysis tools during code reviews for providing better feedback. Valid values: true or false

    labels_excluded

    Comma-separated list of labels that, if present on a pull request or merge request, skip automatic review. This is case-sensitive by default. For example, if we mention "Bug" in the repo-level .bito.yaml file and the tagged label is "bug", we won't match it. Users can use regex to make it case-insensitive, e.g., (?i)^bug$ or (?i)bug. Example: "wip, do-not-review, chore, size/*"

    post_as_request_changes

    Enable this option to get Bito feedback as "Request changes" review comments. Depending on your Git provider settings, you may need to resolve all comments before merging. For GitHub, this will automatically enable auto-approve for resolved PRs. Valid values: true or false

    functional_validation_enabled

    Enable this option to automatically validate pull requests against Jira ticket referenced in PR description, title, or branch name. Jira Integration must be completed from Bito dashboardarrow-up-right for this to work. Valid values: true or false

    For the Bito-hosted AI Architect, use the following URL format: https://mcp.bito.ai/<Your-Bito-Workspace-ID>/mcp

    Replace <Your-Bito-Workspace-ID> with your actual Bito workspace ID, which you can find after logging into your Bito account at alpha.bito.aiarrow-up-right

  • Replace <Your-Bito-MCP-Access-Token> with the Bito MCP Access Token you received after completing the AI Architect setup.

  • Replace <Your-Email> with your actual email address.

  • For the Bito-hosted AI Architect, use the following URL format: https://mcp.bito.ai/<Your-Bito-Workspace-ID>/mcp

    Replace <Your-Bito-Workspace-ID> with your actual Bito workspace ID, which you can find after logging into your Bito account at alpha.bito.aiarrow-up-right

  • Replace <Your-Bito-MCP-Access-Token> with the Bito MCP Access Token you received after completing the AI Architect setup.

  • Replace <Your-Email> with your actual email address.

  • Copy the contents of your BitoAIArchitectGuidelines.md file into .aiassistant/rules/bitoai-architect.md file:
  • In your IDE: Settings → Tools → AI Assistant → Rules

  • The rule file should appear automatically

  • Configure how it should be applied:

    • Always: Applied to all chats automatically

    • Manually: Invoked using @rule:bitoai-architect

    • By Model Decision: AI decides when to apply

    • By File Patterns: Applied when specific files are open

  • download Node.js 20.x LTSarrow-up-right
    mkdir -p ~/.claude
    nano ~/.claude/CLAUDE.md
    nano CLAUDE.md
    mkdir -p .claude
    nano .claude/CLAUDE.md
    cd /path/to/your/project
    curl -fsSL https://bitoreview.bito.ai/bito_cli_review_guidelines.md -o .cursorrules
    cd C:\path\to\your\project
    irm 'https://bitoreview.bito.ai/bito_cli_review_guidelines.md' | Out-File -FilePath .cursorrules
    cd /path/to/your/project
    mkdir -p .windsurf/rules
    curl -fsSL https://bitoreview.bito.ai/bito_cli_review_guidelines.md -o .windsurf/rules/bitoai-review.md
    cd C:\path\to\your\project
    New-Item -ItemType Directory -Path .windsurf\rules -Force
    irm 'https://bitoreview.bito.ai/bito_cli_review_guidelines.md' | Out-File -FilePath .windsurf\rules\bitoai-review.md
    cd /path/to/your/project
    mkdir -p .github
    curl -fsSL https://bitoreview.bito.ai/bito_cli_review_guidelines.md -o .github/copilot-instructions.md
    cd C:\path\to\your\project
    New-Item -ItemType Directory -Path .github -Force
    irm 'https://bitoreview.bito.ai/bito_cli_review_guidelines.md' | Out-File -FilePath .github\copilot-instructions.md
    cd /path/to/your/project
    mkdir -p .junie
    curl -fsSL https://bitoreview.bito.ai/bito_cli_review_guidelines.md -o .junie/guidelines.md
    cd C:\path\to\your\project
    New-Item -ItemType Directory -Path .junie -Force
    irm 'https://bitoreview.bito.ai/bito_cli_review_guidelines.md' | Out-File -FilePath .junie\guidelines.md
    cd /path/to/your/project
    mkdir -p .aiassistant/rules
    curl -fsSL https://bitoreview.bito.ai/bito_cli_review_guidelines.md -o .aiassistant/rules/bitoai-review.md
    cd C:\path\to\your\project
    New-Item -ItemType Directory -Path .aiassistant\rules -Force
    irm 'https://bitoreview.bito.ai/bito_cli_review_guidelines.md' | Out-File -FilePath .aiassistant\rules\bitoai-review.md
    # Bash
    source ~/.bashrc
    
    # Zsh (macOS default)
    source ~/.zshrc
    bitoreview config set-api-key
    bitoreview config set-api-key YOUR_API_KEY_HERE
    export BITO_API_KEY=YOUR_API_KEY_HERE
    bitoreview config show-api-key
    custom_guidelines:
      general:
        - name: "Global Checks"
          path: "./guidelines/global_checks.txt"
        - name: "Security Rules"
          path: "./guidelines/security.txt"
        - name: "Legacy Style Guide"
          path: "./guidelines/legacy.txt"
        - name: "Performance Checks"
          path: "./guidelines/perf.txt"
        - name: "Code Style"
          path: "./guidelines/style.txt"
      per_language:
        python:
          name: "Python Best Practices"
          path: "./guidelines/py.txt"
        javascript:
          name: "JS Style Guide"
          path: "./guidelines/js.txt"
        typescript:
          name: "TS Checks"
          path: "./guidelines/ts.txt"
        java:
          name: "Java Coding Standards"  
          Path: "./guidelines/java.txt"
    node --version  # Should show v20.x.x or higher
    npx --version
    {
      "mcpServers": {
        "BitoAIArchitect": {
          "command": "npx",
          "args": [
            "-y",
            "mcp-remote",
            "<Your-Bito-MCP-URL>",
            "--header",
            "Authorization:${AUTH_HEADER}",
            "--header",
            "x-email-id: <Your-Email>"
          ],
          "env": {
            "AUTH_HEADER": "Bearer <Your-Bito-MCP-Access-Token>"
          }
        }
      }
    }
    {
      "mcpServers": {
        "BitoAIArchitect": {
          "command": "cmd",
          "args": [
            "/c",
            "npx",
            "-y",
            "mcp-remote",
            "<Your-Bito-MCP-URL>",
            "--header",
            "Authorization:${AUTH_HEADER}",
            "--header",
            "x-email-id: <Your-Email>"
          ],
          "env": {
            "AUTH_HEADER": "Bearer <Your-Bito-MCP-Access-Token>"
          }
        }
      }
    }
    mkdir -p .aiassistant/rules
    cp /path/to/BitoAIArchitectGuidelines.md .aiassistant/rules/bitoai-architect.md
    Configure the following under the "Secrets" tab:

    For each secret, click the New repository secret button, then enter the exact name and value of the secret in the form. Finally, click Add secret to save it.

    • Name: BITO_ACCESS_KEY

      • Secret: Enter your Bito Access Key here. Refer to the guide for obtaining your Bito Access Key.

    • Name: GIT_ACCESS_TOKEN

      • Secret: Enter your GitHub Personal Access Token (Classic) with repo access. We do not support fine-grained tokens currently. For more information, see the section.

    Note: For more information, see Draft pull requests filter.
    test_cra.yml
    file inside the
    .github/workflows
    directory either in your source branch of each PR or in a branch (e.g. main) from which all the source branches for PRs will be created.

  • Commit your changes.

  • with:

    • uses: myorg/gitbito-bitocodereview@main

    /review scalability
    :
    Assesses the code's ability to handle increased usage and scale effectively.
  • /review codeorg: Scans for readability and maintainability, promoting clear and efficient code organization.

  • /review codeoptimize: Identifies optimization opportunities to enhance code efficiency and reduce resource usage.

  • Source or Target branch filter
    Files and folders filter
    Download this test_cra.yml filearrow-up-right
    Available Commands
    • True

    • False

    No

    Setting it to True activates general code review comments to identify functional issues. If set to False, general code review will not be conducted.

    bito_cli.bito.access_key

    A valid Bito Access Key generated through Bito's web UI.

    Yes

    Bito Access Key is an alternative to standard email and OTP authentication.

    git.provider

    • GITLAB

    • GITHUB

    • BITBUCKET

    Yes, if the mode is CLI.

    The name of git repository provider.

    git.access_token

    A valid Git access token provided by GITLAB or GITHUB or BITBUCKET

    Yes

    You can use a personal access token in place of a password when authenticating to GitHub/GitLab/BitBucket in the command line or with the API.

    git.domain

    A URL where Git is hosted.

    No

    It is used to enter the custom URL of self-hosted GitHub/GitLab Enterprise.

    static_analysis

    • True

    • False

    No

    Enable or disable static code analysis, which is used to uncover functional issues in the code.

    static_analysis_tool

    • fb_infer

    • astral_ruff

    • mypy

    No

    Comma-separated list of static analysis tools to run (e.g., fb_infer,astral_ruff,mypy).

    linters_feedback

    • True

    • False

    No

    Enables feedback from linters like ESLint, golangci-lint, and Astral Ruff.

    secret_scanner_feedback

    • True

    • False

    No

    Enables detection of secrets in code. For example, passwords, API keys, sensitive information, etc.

    dependency_check

    • True

    • False

    No

    This feature is designed to identify security vulnerabilities in open-source dependency packages, specifically for JS/TS/Node.JS and GoLang. Without this input, reviews for security vulnerabilities will not be conducted.

    dependency_check.snyk_auth_token

    A valid authentication token for accessing Snyk's cloud-based security database.

    No

    If not provided, access to Snyk's cloud-based security database for checking security vulnerabilities in open-source dependency packages will not be available.

    code_context

    • True

    • False

    No

    Enables enhanced code context awareness.

    server_port

    A valid and available TCP port number.

    No

    This is applicable when the mode is set to server. If not specified, the default value is 10051.

    review_comments

    • 1

    • 2

    No

    Set the value to 1 to display the code review in a single post, or 2 to show code review as inline comments, placing suggestions directly beneath the corresponding lines in each file for clearer guidance on improvements.

    The default value is 2.

    review_scope

    • security

    • performance

    • scalability

    No

    Specialized commands to perform detailed analyses on specific aspects of your code. You can provide comma-separated values to perform multiple types of code analysis simultaneously.

    include_source_branches

    Glob/regex pattern.

    No

    Comma-separated list of branch patterns (glob/regex) to allow as pull request sources.

    include_target_branches

    Glob/regex pattern.

    No

    Comma-separated list of branch patterns (glob/regex) to allow as pull request targets.

    exclude_files

    Glob/regex pattern.

    No

    A list of files/folders that the AI Code Review Agent will not review if they are present in the diff.

    By default, these files are excluded: *.xml, *.json, *.properties, .gitignore, *.yml, *.md

    exclude_draft_pr

    • True

    • False

    No

    A binary setting that enables/disables automated review of pull requests (PR) based on the draft status. The default value is True which skips automated review of draft PR.

    cra_version

    • latest

    • Any specific version tag

    No

    Sets the agent version to run (latest or a specific version tag).

    post_as_request_changes

    • True

    • False

    No

    Posts feedback as 'Request changes' review comments. Depending on your organization's Git settings, you may need to resolve all comments before merging.

    support_email

    Email address

    No

    Contact email shown in error messages.

    suggestion_mode

    • essential

    • comprehensive

    No

    Controls AI suggestion verbosity. Available options are essential and comprehensive.

    In Essential mode, only critical issues are posted as inline comments, and other issues appear in the main review summary under "Additional issues".

    In Comprehensive mode, Bito also includes minor suggestion and potential nitpicks as inline comments.

    mode

    • cli

    • server

    Yes

    Whether to run the Docker container in CLI mode for a one-time code review or as a webhooks service to continuously monitor for code review requests.

    pr_url

    Pull request URL in GitLab, GitHub and Bitbucket

    Yes, if the mode is CLI.

    The pull request provides files with changes and the actual code modifications. When the mode is set to server, the pr_url is received either through a webhook call or via a REST API call.

    This release only supports webhook calls; other REST API calls are not yet supported.

    code_feedback

    Users can pass both types of patterns - Unix files system based glob pattern or regex.

    app/resources/file.txt, config/resources/service.properties

    Exclude all files, folders and subfolders in subfolder resource and in parent folder src

    src/*/resource/*

    src/com/resource/main.html,

    src/com/resource/script/file.css, src/com/resource/app/script.js

    src/resource/file.txt, src/com/config/file.txt, app/com/config/file.txt

    Exclude non-css files from folder src/com/resource/ and subfolders

    ^src\/com\/resource\\/(?!.*\\.css$).*$

    src/com/resource/main.html, src/com/resource/app/script.js,

    src/com/config/file.txt

    src/com/resource/script/file.css

    Exclude specific file controller/webhook_controller.go

    controller/webhook_controller.go

    controller/webhook_controller.go

    controller/controller.go, controller/webhook_service.go

    Exclude non-css files from folder starting with config and its subfolders

    ^config\\/(?!.*\\.css$).*$

    config/server.yml, config/util/conf.properties

    config/profile.css, config/styles/main.css

    Exclude all files & folders

    *

    resource/file.txt, config/file.properties, app/folder/

    -

    Exclude all files & folders starting with name bito in module folder

    module/bito*

    module/bito123, module/bitofile.js, module/bito/file.js

    module/filebito.js, module/file2.txt, module/util/file.txt

    Exclude single-character folder names

    */?/*

    src/a/file.txt, app/b/folder/file.yaml

    folder/file.txt, ab/folder/file.txt

    Exclude all folders, subfolders and files in those folders except folder starting with service folder

    ^(?!service\\/).*$

    config/file.txt, resources/file.yaml

    service/file.txt, service/config/file.yaml

    Exclude all files in all folders except .py, .go, and .java files

    ^(?!.*\\.(py|go|java)$).*$

    config/file.txt, app/main.js

    main.py, module/service.go, test/Example.java

    Exclude non-css files from folder src/com/config and its subfolders

    ^config\\/(?!.*\\.css$).*$

    config/server.yml, config/util/conf.properties

    config/profile.css, config/styles/main.css

    Users can pass both types of patterns - Unix files system based glob pattern or regex.

    BITO

    Include branches like release/v1.0 and release/v1.0.1

    release/v\\d+\\.\\d+(\\.\\d+)?

    release/v1.0, release/v1.0.1

    release/v1, release/v1.0.x

    Include any branch ending with -test

    *-test

    feature-test, release-test

    test-feature, release-testing

    Include the branch that has keyword main

    main

    main, main-feature, mainline

    master, development

    Include the branch named main

    ^main$

    main

    main-feature, mainline, master, development

    Include any branch name that does not start with feature- or release-

    ^(?!release-|feature-).*$

    hotfix-123, development

    feature-123, release-v1.0

    Include branches with names containing digits

    .*\\d+.*

    feature-123, release-v1.0

    feature-abc, main

    Include branches with names ending with test or testing

    .*(test|testing)$

    feature-test, bugfix-testing

    testing-feature, test-branch

    Include branches with names containing a specific substring test

    *test*

    feature-test, test-branch, testing

    feature, release

    Include branches with names containing exactly three characters

    ^.{3}$

    abc, 123

    abcd, ab

    Include branch names starting with release, hotfix, or development but not starting with Bito or feature

    ^(?!Bito|feature)(release|hotfix|development).*$

    release-v1.0, hotfix-123, development-xyz

    Bito-release, feature-hotfix, main-release

    Include all branches where name do not contains version like 1.0, 1.0.1, etc.

    ^(?!.\\b\\d+\\.\\d+(\\.\\d+)?\\b).*

    feature-xyz, main

    release-v1.0, hotfix-1.0.1

    Include all branches which are not alphanumeric

    ^.[^a-zA-Z0-9].$

    feature-!abc, release-@123

    feature-123, release-v1.0

    Include all branches which contains space

    .*\\s.*

    feature 123, release v1.0

    feature-123, release-v1.0

    Exclude all properties files in all folders and subfolders

    *.properties

    resource/config.properties, resource/server/server.properties

    resource/config.yaml, resource/config.json

    Exclude all files, folders and subfolders in folder starting with resources

    resources/

    resources/application.properties, resources/config/config.yaml

    app/resources/file.txt, config/resources/service.properties

    Exclude all files, folders and subfolders in folder src/com/resources

    src/com/resources/

    Include any branch that starts with name BITO-

    BITO-*

    BITO-feature, BITO-123

    feature-BITO, development

    Include any branch that does not start with BITO-

    ^(?!BITO-).*

    feature-123, release-v1.0

    BITO-feature, BITO-123

    Include any branch which is not BITO

    ^(?!BITO$).*

    Install/run Using Bito Cloud
    bito-cra.properties file
    Install/Run via GitHub Actions

    resources/application.properties, resources/config/config.yaml

    feature-BITO, development

  • Requires Visual Studio Code version 1.99 or later

    1. Check VS Code version: code --version

    2. Update VS Code if needed: Help → Check for Updates

  • Enable Agent Mode

    1. Open VS Code Settings (Ctrl/Cmd + ,)

    2. Search: chat.agent.enabled

    3. Check the box to enable Agent Mode

  • Ensure Node.js 20.18.1+ is Installed:

    VS Code's MCP implementation automatically tries to use OAuth for HTTP servers. For static Bearer token authentication (which Bito AI Architect uses), you need to use the mcp-remote proxy tool.

    The mcp-remote proxy requires Node.js 20.18.1 or higher.

    Why Node.js 20+? The mcp-remote proxy depends on undici v7, which requires Node.js 20+ (needs the File global API added in Node 20.0.0). Node.js 18 and earlier will fail with ReferenceError: File is not defined.

    Windows: Download from (download 20.x LTS)

    macOS:

    Linux (Ubuntu/Debian):

    Verify:

  • GitHub Copilot extension installed and enabled

  • GitHub account with Copilot access

  • hashtag
    Create mcp.json

    Create .vscode/mcp.json:

    circle-info

    Note:

    • Replace <Your-Bito-MCP-URL> with the Bito MCP URL you received after completing the AI Architect setup.

      • For the Bito-hosted AI Architect, use the following URL format: https://mcp.bito.ai/<Your-Bito-Workspace-ID>/mcp

        Replace <Your-Bito-Workspace-ID> with your actual Bito workspace ID, which you can find after logging into your Bito account at

    • Replace <Your-Bito-MCP-Access-Token> with the Bito MCP Access Token you received after completing the AI Architect setup.

    • Replace <Your-Email> with your actual email address.

    Important:

    • Include "type": "stdio" in the configuration

    • VS Code requires mcp-remote proxy for static Bearer token authentication

    • The "servers" object is at the root level in workspace configs

    • Direct HTTP transport with static Bearer tokens triggers OAuth flows in VS Code

    Why mcp-remote? VS Code's MCP implementation automatically initiates OAuth discovery when connecting to HTTP MCP servers. Since BitoAIArchitect uses static Bearer token authentication (not OAuth), we use the mcp-remote proxy to handle the authentication properly.

    3

    hashtag
    Add guidelines (optional but highly recommended)

    The BitoAIArchitectGuidelines.md file contains best practices, usage instructions, and prompting guidelines for the Bito AI Architect MCP server.

    The setup will work without this file, but including it helps AI tools interact more effectively with the Bito AI Architect MCP server.

    Create .github directory:

    Copy the contents of your into .github/copilot-instructions.md file:

    4

    hashtag
    Start the MCP server

    Important: VS Code requires manually starting MCP servers. Follow these steps:

    1. Open Copilot Chat (Ctrl/Cmd + I)

    2. Click the gear icon in the Copilot Chat panel

    3. Select "MCP Servers"

    4. Find BitoAIArchitect in the list

    5. Click the gear icon next to BitoAIArchitect

    6. Select "Start Server"

    Alternative method:

    1. Open .vscode/mcp.json in VS Code

    2. Look for a Start button above the configuration

    3. Click Start to initialize the server

    5

    hashtag
    Verify in Copilot Chat

    1. Open Copilot Chat (Ctrl/Cmd + I)

    2. Switch to Agent mode (toggle in chat interface)

    3. Click the Tools icon (wrench)

    4. Verify BitoAIArchitect appears in the tools list

    5. Try asking: "What repositories are available?"

    For the Bito-hosted AI Architect, use the following URL format: https://mcp.bito.ai/<Your-Bito-Workspace-ID>/mcp

    Replace <Your-Bito-Workspace-ID> with your actual Bito workspace ID, which you can find after logging into your Bito account at alpha.bito.aiarrow-up-right

  • Replace <Your-Bito-MCP-Access-Token> with the Bito MCP Access Token you received after completing the AI Architect setup.

  • Replace <Your-Email> with your actual email address.

  • Restart VS Code completely (Cmd+Q / Alt+F4)

    Check Node.js version: node --version (must be 20.18.1+)
  • View → Output → select "MCP" for error messages

  • Verify BitoAIArchitect appears

    Check that Node.js and npx are installed: npx --version

    Try our Quick MCP Integration Guide
    AI Architect installation instructions
    Download BitoAIArchitectGuidelines.md filearrow-up-right

    Get a 14-day FREE trial of Bito's AI Code Review Agent.arrow-up-right

    hashtag
    Video tutorial

    coming soon...

    hashtag
    Prerequisites

    Before proceeding, ensure you've completed all necessary prerequisites.

    hashtag
    1. Create a GitLab Personal Access Token:

    For GitLab merge request code reviews, a token with api scope is required. Make sure that the token is created by a GitLab user who has the Maintainer access role.

    View Guidearrow-up-right

    circle-info

    Important: Bito posts comments using the GitLab user account linked to the Personal Access Token used during setup. To display "Bito" instead of your name, create a separate user account (e.g., Bito Agent) and use its token for integration.

    circle-info

    We recommend setting the token expiration to at least one year. This prevents the token from expiring early and avoids disruptions in the AI Code Review Agent's functionality.

    Additionally, we highly recommend updating the token before expiry to maintain seamless integration and code review processes.

    GitLab Personal Access Token

    hashtag
    2. Authorizing a GitLab Personal Access Token for use with SAML single sign-on:

    If your GitLab organization enforces SAML Single Sign-On (SSO), you must authorize your Personal Access Token through your Identity Provider (IdP); otherwise, Bito's AI Code Review Agent won't function properly.

    For more information, please refer to the following GitLab documentation:

    • SAML SSO for GitLab.com groupsarrow-up-right

    • SAML SSO for GitLab Self-Managedarrow-up-right

    • Password generation for users created through SAMLarrow-up-right

    hashtag
    Installation and configuration steps

    Follow the step-by-step instructions below to install the AI Code Review Agent using Bito Cloud:

    hashtag
    Step 1: Log in to Bito

    Log in to Bito Cloudarrow-up-right and select a workspace to get started.

    hashtag
    Step 2: Open the Code Review Agents setup

    Click Repositoriesarrow-up-right under the CODE REVIEW section in the sidebar.

    hashtag
    Step 3: Select your Git provider

    Bito supports integration with the following Git providers:

    • GitHub

    • GitHub (Self-Managed)

    • GitLab

    • GitLab (Self-Managed)

    • Bitbucket

    • Bitbucket (Self-Managed)

    Since we are setting up the Agent for GitLab (Self-Managed) server, select GitLab (Self-Managed) to proceed.

    circle-info

    Supported versions:

    • GitLab (Self-Managed): 15.5 and above

    hashtag
    Step 4: Connect Bito to GitLab

    To enable merge request reviews, you’ll need to connect your Bito workspace to your GitLab (Self-Managed) server.

    circle-info

    If your network blocks external services from interacting with the GitLab server, whitelist all of Bito's gateway IP addresses in your firewall to ensure Bito can access your self-hosted repositories. The Agent response can come from any of these IPs.

    • List of IP addresses to whitelist:

      • 18.188.201.104

      • 3.23.173.30

      • 18.216.64.170

    You need to enter the details for the below mentioned input fields:

    • Hosted GitLab URL: This is the domain portion of the URL where you GitLab Enterprise Server is hosted (e.g., https://yourcompany.gitlab.com). Please check with your GitLab administrator for the correct URL.

    • Personal Access Token: Generate a GitLab Personal Access Token with api scope in your GitLab (Self-Managed) account and enter it into the Personal Access Token input field. For guidance, refer to the instructions in the Prerequisites section.

    Click Validate to ensure the token is functioning properly.

    If the token is successfully validated, you can select your GitLab Group from the dropdown menu.

    • Note: You can select multiple groups after the setup is complete.

    Click Connect Bito to GitLab to proceed.

    hashtag
    Step 5: Enable AI Code Review Agent on repositories

    After connecting Bito to your GitLab self-managed server, you'll see a list of repositories that Bito has access to.

    Use the toggles in the Code Review Status column to enable or disable the Agent for each repository.

    circle-info

    To customize the Agent’s behavior, you can edit existing configurations or create new Agents as needed.

    Learn more

    hashtag
    Step 6: Automated and manual merge request reviews

    Once a repository is enabled, you can invoke the AI Code Review Agent in the following ways:

    1. Automated code review: By default, the Agent automatically reviews all new merge requests and provides detailed feedback.

    2. Manually trigger code review: To initiate a manual review, simply type /review in the comment box on the merge request and submit it. This action will start the code review process.

    The AI-generated code review feedback will be posted as comments directly within your merge request, making it seamless to view and address suggestions right where they matter most.

    circle-info

    Note: To enhance efficiency, the automated code reviews are only triggered for merge requests merging into the repository’s default branch. This prevents unnecessary processing and Advanced AI requests usage.

    To review additional branches, you can use the Include Source/Target Branches filter. Bito will review merge requests when the source or target branch matches the list.

    The Include Source/Target Branches filter applies only to automatically triggered reviews. Users should still be able to trigger reviews manually via the /review command.

    circle-info

    The AI Code Review Agent automatically reviews code changes up to 5000 lines when a merge request is created. For larger changes, you can use the /review command.

    circle-info

    It may take a few minutes to get the code review posted as a comment, depending on the size of the merge request.

    hashtag
    Step 7: Specialized commands for code reviews

    Bito also offers specialized commands that are designed to provide detailed insights into specific areas of your source code, including security, performance, scalability, code structure, and optimization.

    • /review security: Analyzes code to identify security vulnerabilities and ensure secure coding practices.

    • /review performance: Evaluates code for performance issues, identifying slow or resource-heavy areas.

    • /review scalability: Assesses the code's ability to handle increased usage and scale effectively.

    • /review codeorg: Scans for readability and maintainability, promoting clear and efficient code organization.

    • /review codeoptimize: Identifies optimization opportunities to enhance code efficiency and reduce resource usage.

    By default, the /review command generates inline comments, meaning that code suggestions are inserted directly beneath the code diffs in each file. This approach provides a clearer view of the exact lines requiring improvement. However, if you prefer a code review in a single post rather than separate inline comments under the diffs, you can include the optional parameter: /review #inline_comment=False

    For more details, refer to Available Commandsarrow-up-right.

    hashtag
    Step 8: Chat with AI Code Review Agent

    Ask questions directly to the AI Code Review Agent regarding its code review feedback. You can inquire about highlighted issues, request alternative solutions, or seek clarifications on suggested fixes.

    To start the conversation, type your question in the comment box within the inline suggestions on your merge request, and then submit it. Typically, Bito AI responses are delivered in about 10 seconds. On GitHub and Bitbucket, you need to manually refresh the page to see the responses, while GitLab updates automatically.

    Bito supports over 20 languages—including English, Hindi, Chinese, and Spanish—so you can interact with the AI in the language you’re most comfortable with.

    hashtag
    Step 9: Configure Agent settings

    Agent settings let you control how reviews are performed, ensuring feedback is tailored to your team’s needs. By adjusting the options, you can:

    • Make reviews more focused and actionable.

    • Apply your own coding standards.

    • Reduce noise by excluding irrelevant files or branches.

    • Add extra checks to improve code quality and security.

    Learn more

    hashtag
    Managing multiple GitLab groups in Bito Cloud

    Bito Cloudarrow-up-right allows you to connect and manage multiple GitLab groups for GitLab (Self-Managed) integrations. Use the instructions below to add or remove GitLab groups for AI code reviews.

    hashtag
    How to add multiple GitLab groups?

    You can connect more than one GitLab group to Bito for AI code reviews.

    Follow these steps to add additional groups:

    1. Go to the Repositoriesarrow-up-right page.

    1. At the top-center of the page, click the “+” (plus) icon next to the currently selected GitLab group name, then select Add group from the dropdown menu.

    1. A popup will appear. Use the dropdown menu to select a GitLab group you want to add.

    1. Click the Add group button.

    Once added, all repositories from that group will be listed and available for AI code reviews under the default agent.

    circle-info

    Note: This multiple GitLab groups feature is currently available only for GitLab (Self-Managed) integrations.

    hashtag
    How to remove a GitLab group?

    To disconnect a GitLab group from Bito Cloud:

    1. Go to the Repositoriesarrow-up-right page.

    1. At the top-center of the page, click the three dots icon next to the currently selected GitLab group name, then select Manage groups from the dropdown menu.

    1. A popup will appear showing a list of connected groups. Click the “✕” (cross) icon next to the group you want to remove.

    1. Confirm the removal in the prompt.

    Once removed, the repositories from that group will no longer appear in Bito or be included in AI code reviews.

    hashtag
    How to select one or more GitLab Groups?

    When you have multiple GitLab groups connected in Bito Cloud, the group name at the top-center of the Repositoriesarrow-up-right page becomes a dropdown menu.

    From this dropdown, you can:

    • Select a single group

    • Select multiple groups as needed

    • Select All groups

    The list of repositories displayed below will update automatically based on your selection—showing only the repositories from the selected groups.

    hashtag
    Screenshots

    hashtag
    Screenshot # 1

    circle-info

    AI-generated merge request (MR) summary

    hashtag
    Screenshot # 2

    circle-info

    Changelist showing key changes and impacted files in a merge request.

    Changelist in AI Code Review Agent's feedback.

    hashtag
    Screenshot # 3

    circle-info

    AI code review feedback posted as comments on the merge request.

    AI Code Review Agentarrow-up-right
    available commandsarrow-up-right
    Pricingarrow-up-right

    Available commands

    CLI commands for installing, operating, and maintaining Bito's AI Architect.

    Quick reference for CLI commands used to install, configure, and manage Bito's AI Architect.

    • Setup script commands: Use these commands to install AI Architect and manage its initial service setup and lifecycle.

    • AI Architect management commands (bitoarch): Use these commands after installation to manage repositories, indexing, configuration, health checks, and MCP operations.

    hashtag
    Setup script commands

    Commands used to install AI Architect and manage its initial service setup.

    Command
    Description

    hashtag
    AI Architect management commands

    Use these bitoarch commands to manage AI Architect.

    circle-info

    Note: After , the bitoarch command is available globally.

    hashtag
    Core operations

    Command
    Description
    Example

    Examples:


    hashtag
    Repository management

    Command
    Description
    Example

    Examples:


    hashtag
    Service operations

    Command
    Description
    Example

    Examples:


    hashtag
    Configuration

    Command
    Description
    Example

    Examples:


    hashtag
    MCP operations

    Command
    Description
    Example

    Examples:


    hashtag
    Output options

    Add these flags to any command:

    Flag
    Purpose
    Example

    hashtag
    Common workflows

    hashtag
    Initial setup

    hashtag
    Daily operations

    hashtag
    Adding new repositories

    hashtag
    Troubleshooting


    hashtag
    Getting help

    Command
    Shows

    Examples:


    hashtag
    Environment

    Configuration is loaded from .env-bitoarch file. Key variables:

    • BITO_API_KEY - API key for authentication

    • GIT_PROVIDER - Git provider (github, gitlab, bitbucket)

    • GIT_ACCESS_TOKEN - Git access token


    hashtag
    Version

    Check CLI version:

    mkdir .vscode
    {
      "servers": {
        "BitoAIArchitect": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "mcp-remote",
            "<Your-Bito-MCP-URL>",
            "--header",
            "Authorization: Bearer <Your-Bito-MCP-Access-Token>",
            "--header",
            "x-email-id: <Your-Email>"
          ]
        }
      }
    }
    {
      "chat.mcp.discovery.enabled": true
    }
    "chat.mcp.discovery.enabled": true
    {
      "servers": {
        "BitoAIArchitect": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "mcp-remote",
            "<Your-Bito-MCP-URL>",
            "--header",
            "Authorization: Bearer <Your-Bito-MCP-Access-Token>",
            "--header",
            "x-email-id: <Your-Email>"
          ]
        }
      }
    }
    codeorg
  • codeoptimize

  • Learn Morearrow-up-right
    Learn more
    Learn more
    Learn more
    Prerequisites
    https://nodejs.org/arrow-up-right
    alpha.bito.aiarrow-up-right
    BitoAIArchitectGuidelines.md file

    ./setup.sh --force-restart

    Restart all services and reapply environment variables. Use after updating .env-bitoarch file.

    ./setup.sh --update

    Force pull latest images based on service-versions.json and restart services

    ./setup.sh --clean

    Remove all data and services

    bitoarch stop-indexing

    Stop indexing completely

    bitoarch stop-indexing

    bitoarch index-repo-list

    List all repositories

    bitoarch index-repo-list --status active

    bitoarch show-config

    Show current configuration

    bitoarch show-config --raw

    bitoarch repo-info <name>

    Get detailed repository info

    bitoarch repo-info myrepo --dependencies

    bitoarch mcp-info

    Show MCP configuration

    Display URL and token info

    BITO_MCP_ACCESS_TOKEN - MCP server access token

  • CIS_*_EXTERNAL_PORT - Service external ports

  • ./setup.sh

    Run interactive setup wizard

    ./setup.sh --help or -h

    Show help message with all available options

    ./setup.sh --status

    Check if services are running

    ./setup.sh --logs

    View service logs for debugging

    ./setup.sh --stop

    Stop all services (preserves containers)

    ./setup.sh --restart

    Restart all services without config changes

    bitoarch index-repos

    Trigger workspace repository indexing. Use --only-new-repos to index only newly added repositories

    bitoarch index-repos --only-new-repos

    bitoarch index-status

    Check indexing status

    View progress and state

    bitoarch pause-indexing

    Pause ongoing indexing process

    bitoarch pause-indexing

    bitoarch resume-indexing

    Resume paused indexing process

    bitoarch resume-indexing

    bitoarch add-repo <namespace>

    Add single repository

    bitoarch add-repo myorg/myrepo

    bitoarch remove-repo <namespace>

    Remove repository

    bitoarch remove-repo myorg/myrepo

    bitoarch add-repos

    Load configuration from YAML

    bitoarch add-repos

    bitoarch update-repos

    Update configuration from YAML

    bitoarch update-repos

    bitoarch status

    View all services status

    Docker ps-like output

    bitoarch health

    Check health of all services

    bitoarch health --verbose

    bitoarch info

    Get platform information

    Version, ports, resources

    bitoarch update-api-key

    Update Bito API key

    Interactive or with --api-key flag

    bitoarch update-git-creds

    Update Git provider credentials

    Interactive or with flags

    bitoarch update-llm-keys

    Update LLM API keys

    Interactive prompt

    bitoarch rotate-mcp-token

    Rotate MCP access token

    bitoarch rotate-mcp-token <new-token>

    bitoarch mcp-test

    Test MCP connection

    Verify server connectivity

    bitoarch mcp-tools

    List available MCP tools

    bitoarch mcp-tools --details

    bitoarch mcp-capabilities

    Show MCP server capabilities

    bitoarch mcp-capabilities --output caps.json

    bitoarch mcp-resources

    List MCP resources

    View available data sources

    --format json

    JSON output

    For automation/scripts

    --raw

    Show full API response

    For debugging

    --output json

    Filtered JSON output

    For index-status

    --help

    Show command help

    Get usage information

    bitoarch --help

    Main menu with all commands

    bitoarch <command> --help

    Command-specific help

    installation of AI Architect
    brew install node@20
    # Or use nvm: nvm install 20 && nvm use 20
    curl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash -
    sudo apt-get install -y nodejs
    node --version  # Should show v20.x.x or higher
    npx --version
    mkdir -p .github
    cp BitoAIArchitectGuidelines.md .github/copilot-instructions.md
    # Trigger repository indexing
    bitoarch index-repos
    
    # Check indexing status (default summary)
    bitoarch index-status
    
    # Full API response for debugging
    bitoarch index-status --raw
    
    # Machine-readable filtered JSON
    bitoarch index-status --output json
    
    # List all repositories
    bitoarch index-repo-list
    # Add a single repository
    bitoarch add-repo myorg/myrepo
    
    # Remove a repository
    bitoarch remove-repo myorg/myrepo
    
    # Load multiple repositories from config file
    bitoarch add-repos
    
    # Update configuration
    bitoarch update-repos
    
    # Get repository details
    bitoarch repo-info myrepo
    # Check service status (docker ps-like)
    bitoarch status
    
    # Health check
    bitoarch health
    
    # Detailed health information
    bitoarch health --verbose
    
    # Platform information
    bitoarch info
    # Update API key (interactive)
    bitoarch update-api-key
    
    # Update API key with flag
    bitoarch update-api-key --api-key <key> --restart
    
    # Update Git credentials (interactive)
    bitoarch update-git-creds
    
    # Update Git credentials with flags
    bitoarch update-git-creds --provider github --token <token> --restart
    
    # Update LLM API keys
    bitoarch update-llm-keys
    
    # Rotate MCP token
    bitoarch rotate-mcp-token <new-token>
    # Test MCP connection
    bitoarch mcp-test
    
    # List MCP tools
    bitoarch mcp-tools
    
    # Show detailed tool information
    bitoarch mcp-tools --details
    
    # Get server capabilities
    bitoarch mcp-capabilities
    
    # Save capabilities to file
    bitoarch mcp-capabilities --output capabilities.json
    
    # List resources
    bitoarch mcp-resources
    
    # Show MCP configuration
    bitoarch mcp-info
    # 1. Check services are running
    bitoarch status
    
    # 2. Add repositories
    bitoarch add-repos
    
    # 3. Trigger indexing
    bitoarch index-repos
    
    # 4. Monitor progress
    bitoarch index-status
    # Check health
    bitoarch health
    
    # View repositories
    bitoarch index-repo-list
    
    # Check index status
    bitoarch index-status
    # Single repository
    bitoarch add-repo myorg/newrepo
    
    # Multiple repositories from config file
    bitoarch add-repos
    
    # Trigger re-indexing
    bitoarch index-repos --only-new-repos
    # Check all services
    bitoarch status
    bitoarch health --verbose
    
    # View full configuration
    bitoarch show-config --raw
    
    # Test MCP connection
    bitoarch mcp-test
    
    # Check indexing status with details
    bitoarch index-status --raw
    # Main help
    bitoarch --help
    
    # Command help
    bitoarch index-repos --help
    bitoarch add-repo --help
    bitoarch mcp-tools --help
    bitoarch --version

    How to use?

    Get up and running in minutes. This guide walks you through running your first code review from the terminal and shows common workflows you can adopt right away.

    hashtag
    Prerequisites

    Before you begin, make sure you have:

    • ✅ Installed the CLI ()

    • ✅ Configured your

    • ✅ A Git repository with code changes (committed or uncommitted)

    hashtag
    Run your first code review

    hashtag
    Review all changes (default)

    From your project's root directory, run:

    Command format:

    Options:

    Flag
    Description

    circle-info

    For complete reference of CLI commands, refer to .

    hashtag
    Review only uncommitted changes

    Use this while actively coding, before committing:

    hashtag
    Review only committed changes

    Review commits that haven't been pushed yet:

    circle-info

    --base option is mandatory with this type. Example: bitoreview review --type committed --base main

    hashtag
    Review specific files

    Limit the review scope to specific files:

    hashtag
    Review changes against a specific branch

    Compare your current branch with another branch (for example, main):

    hashtag
    Review changes against a specific commit

    Compare your current code with a specific commit by providing its hash:

    circle-info

    Note: replace abc123 with your actual commit hash.

    hashtag
    Short alias for bitoreview command

    You can use br as a shortcut:

    hashtag
    Review modes

    1

    hashtag
    Essential mode (fast, critical issues only)

    • Only shows HIGH severity issues

    hashtag
    Focus areas

    Use --focus <area> to concentrate the review on specific aspects:

    Focus area
    Description

    Example:

    hashtag
    Severity levels

    Level
    Description

    Filter by minimum severity:

    hashtag
    Output formats

    1

    hashtag
    Interactive mode (default)

    Rich terminal UI with:

    • Colored output

    hashtag
    Interactive fix application

    Enable interactive mode to review and apply suggested fixes one by one:

    hashtag
    Interactive prompts

    For each fixable issue, you'll see:

    Option
    Action

    hashtag
    Backup files

    When fixes are applied, backup files are automatically created with the .bitoreview-backup extension.

    hashtag
    Multi-SCM support

    The CLI automatically detects your version control system:

    SCM
    Detection

    hashtag
    Override SCM detection

    hashtag
    Review types across SCMs

    Review type
    Git
    SVN
    Mercurial
    Perforce

    hashtag
    Combine review options for precision

    You can mix options to match your workflow:

    hashtag
    Configuration

    Customize settings to match your project's needs and workflow preferences.

    hashtag
    Configuration methods

    AI Code Reviews in CLI can be configured in two ways, with each method overriding the previous:

    1. Built-in defaults - Sensible defaults that work for most projects

    2. CLI flags - Per-command overrides (highest priority)

    circle-info

    For complete reference of review options, refer to .

    hashtag
    Environment variables

    Variable
    Description

    hashtag
    Getting help

    View help directly from the CLI:

    Still running into issues? 👉 Visit the to find solutions for common installation, configuration, and runtime problems, along with tips for resolving frequent errors quickly.

    Logo

    --mode <mode>

    essential (HIGH only) or comprehensive (all)

    --severity <level>

    Filter by severity: high, medium, low

    --base <branch>

    Base branch for comparison

    --base-commit <commit>

    Specific commit for comparison

    --scm <type>

    Override SCM: git, svn, hg, p4, plain

    -c, --config <path>

    Custom config file path

    --api-key <key>

    Pass API key directly

    --cwd <path>

    Set working directory

    -d, --debug

    Enable debug output

    -v, --verbose

    Enable verbose logging

    --max-retries <num>

    Retry attempts (default: 2)

    --no-color

    Disable colored output

    Ideal for CI/CD pipelines and pre-commit hooks

  • Quick, focused feedback

  • 2

    hashtag
    Comprehensive mode (full analysis)

    • Shows all severity levels (HIGH, MEDIUM, LOW)

    • Thorough analysis for pull requests and code audits

    • This is the default mode.

  • Tables for metrics and issues

  • Real-time progress spinners

  • 2

    hashtag
    Plain text mode

    No colors, suitable for logs and CI/CD:

    Save to file:

    3

    hashtag
    Prompt-only mode

    Minimal output optimized for AI agents:

    Both

    Both

    Both

    Both

    -t, --type <type>

    Review type: • all - Review both uncommitted and committed changes • uncommitted - Review only working directory changes Example: bitoreview review --type uncommitted

    -t, --type <type> --base <branch-name>

    Review type: • committed - Review only committed changes against the specified base branch. --base option is mandatory with this type. Example: bitoreview review --type committed --base main

    -i, --interactive

    Enable interactive fix application

    --plain

    Plain text output (no colors)

    --prompt-only

    Minimal output optimized for AI agents

    --focus <area>

    Focus area (see Focus Areas)

    security

    SQL injection, authentication, data validation, XSS

    performance

    Bottlenecks, memory leaks, optimization opportunities

    bugs

    Logic errors, edge cases, runtime errors

    best-practices

    Code style, design patterns, maintainability

    tests

    Test coverage, test quality, testability

    documentation

    Comments, documentation, code clarity

    high

    Must-fix: crashes, security vulnerabilities, breaking changes

    medium

    Should-fix: best practice violations, moderate issues

    low

    Nice-to-have: formatting, minor refactoring suggestions

    y (yes)

    Apply this fix

    n (no)

    Skip this fix

    s (skip)

    Same as 'no'

    a (all)

    Apply all remaining fixes without prompting

    q (quit)

    Exit interactive mode

    Git

    .git directory

    SVN

    .svn directory

    Mercurial

    .hg directory

    Perforce

    .p4config file

    Plain files

    No VCS required

    uncommitted

    Working tree

    Working copy

    Working dir

    Pending changes

    committed

    Committed

    Revisions

    Changesets

    Submitted

    BITO_API_KEY

    Bito API key (aka Bito Access key) for authentication

    Installation guide
    Bito API key (aka Bito Access Key)
    Available commands
    Available commands
    Troubleshooting guide

    all

    bitoreview review --plain
    bitoreview review --plain > review-report.txt
    bitoreview review --prompt-only
    bitoreview review
    bitoreview review [files...] [options]
    bitoreview review --type uncommitted
    bitoreview review --type committed --base <branch-name>
    bitoreview review src/api/*.js src/utils/helper.js
    bitoreview review --base main
    bitoreview review --base-commit abc123
    br review
    br review --type uncommitted
    bitoreview review --focus security --mode essential
    bitoreview review --severity high
    bitoreview review --interactive
    # or
    bitoreview review -i
    bitoreview review --scm git
    bitoreview review --scm svn
    bitoreview review --scm hg
    bitoreview review --scm p4
    bitoreview review --scm plain
    # Quick security check before commit
    bitoreview review --type uncommitted --focus security --mode essential
    
    # High-severity performance issues vs main branch
    bitoreview review --base main --focus performance --severity high
    
    # Full review of selected files
    bitoreview review src/auth/*.js --mode comprehensive
    # Show help
    bitoreview --help
    bitoreview review --help
    bitoreview config --help
    
    # Show version
    bitoreview --version
    bitoreview review --mode essential
    bitoreview review
    bitoreview review --mode comprehensive

    Install/run via webhooks service

    The webhooks service is best suited for continuous, automated reviews.

    hashtag
    Prerequisites

    hashtag
    Minimum System Requirements

    A machine with the following minimum specifications is recommended for Docker image deployment and for obtaining optimal performance of the AI Code Review Agent.

    Requirement
    Minimum Specification

    hashtag
    Supported Operating Systems

    • Windows

    • Linux

    • macOS


    hashtag
    OS Prerequisites

    Operating System
    Installation Steps

    hashtag
    Required Access Tokens

    • Bito Access Key: Obtain your Bito Access Key.

    • GitHub Personal Access Token (Classic): For GitHub PR code reviews, ensure you have a CLASSIC personal access token with repo access. We do not support fine-grained tokens currently.

    • GitLab Personal Access Token: For GitLab PR code reviews, a token with API access is required.

    • Snyk API Token (Auth Token): For Snyk vulnerability reports, obtain a Snyk API Token.


    hashtag
    Installation and Configuration Steps

    1. Prerequisites: Before proceeding, ensure you've completed all necessary AI Code Review Agent.

    2. Server Requirement: Ensure you have a server with a domain name or IP address.

    3. Start Docker: Initialize Docker on your server.

    • Note the full path to the “cra-scripts” folder for later use.

    1. Open Command Line:

      • Use Bash for Linux and macOS.

      • Use PowerShell for Windows.

    1. Configure Properties:

      • Open the bito-cra.properties file in a text editor from the “cra-scripts” folder. Detailed information for each property is provided on page.

      • Set mandatory properties:

    circle-info

    Note: Valid values for git.provider are GITHUB or GITLAB.

    circle-info

    Note: Detailed information for each property is provided on page.

    circle-info

    Check the guide to learn more about creating the access tokens needed to configure the Agent.

    1. Run the Agent:

      • On Linux/macOS in Bash:

        • Run ./bito-cra.sh service start bito-cra.properties

    circle-info

    This step might take time initially as it pulls the Docker image and performs the code review.

    1. Provide Missing Property Values: The script may prompt for values of mandatory/optional properties if they are not preconfigured.

    2. Copy Webhook Secret: During the script execution, a webhook secret is generated and displayed in the shell. Copy the secret displayed under "Use below as Gitlab and Github Webhook secret:" for use in GitHub or GitLab when setting up the webhook.

    hashtag
    Webhook Setup Guide

    :

    • Login to your account.

    • Navigate to the main page of the repository. Under your repository name, click Settings.

    • In the left sidebar, click Webhooks.

    :

    • Login to your account.

    • Select the repository where the webhook needs to be configured.

    • On the left sidebar, select Settings > Webhooks.

    :

    • Login to your account.

    • Navigate to the main page of the repository. Under your repository name, click Repository Settings.

    • In the left sidebar, click Webhooks.


    hashtag
    Using the AI Code Review Agent

    After configuring the webhook, you can invoke the AI Code Review Agent in the following ways:

    circle-info

    Note: To improve efficiency, the AI Code Review Agent is disabled by default for pull requests involving the "main" branch. This prevents unnecessary processing and token usage, as changes to the "main" branch are typically already reviewed in release or feature branches. To change this default behavior and include the "main" branch, please .

    1. Automated Code Review: If the webhook is configured to be triggered on the Pull requests event (for GitHub) or Merge request event (for GitLab), the agent will automatically review new pull requests as soon as they are created and post the review feedback as a comment within your PR.

    2. Manually Trigger Code Review: To start the process, simply type /review in the comment box on the pull request and submit it. If the webhook is configured to be triggered on the Issue comments event (for GitHub) or Comments event (for GitLab), this action will initiate the code review process. The /review command prompts the agent to review the pull request and post its feedback directly in the PR as a comment.

    circle-info

    It may take a few minutes to get the code review posted as a comment, depending on the size of the pull request.

    hashtag
    Screenshots

    hashtag
    Screenshot # 1

    circle-info

    AI-generated pull request (PR) summary

    hashtag
    Screenshot # 2

    circle-info

    Changelist showing key changes and impacted files in a pull request.

    hashtag
    Screenshot # 3

    circle-info

    AI code review feedback posted as comments on the pull request.


    hashtag
    How to update the self-hosted AI Code Review Agent

    Please follow these steps:

    1. Update the Agent's repository:

      • Pull the latest changes from the repository by running the following command in your terminal, ensuring you are inside the repository folder:

      • git pull origin main


    hashtag
    Stop Docker Container

    To stop the Docker container running as a service, use the below command.

    • On Linux/macOS in Bash: Run ./bito-cra.sh service stop

    • On Windows in PowerShell: Run ./bito-cra.ps1 service stop


    hashtag
    Check Status

    To check the status of Docker container running as a service, use the below command.

    • On Linux/macOS in Bash: Run ./bito-cra.sh service status

    • On Windows in PowerShell: Run ./bito-cra.ps1 service status

    Supported programming languages and tools

    Supports key languages & tools, including fbInfer, Dependency Check, and Snyk.

    hashtag
    Supported Programming Languages

    hashtag
    AI Code Review

    Use cases and examples

    Supercharging development with AI

    Bito AI Assistance can help with generating new content or help with your existing code.

    Click on each use case for an example instruction and response.

    Clone the repository: Clone the AI Code Review Agentarrow-up-right GitHub repository to your server using the following command:

    • git clone https://github.com/gitbito/CodeReviewAgent.git

    • Note: It is recommended to clone the repository instead of downloading the .zip file. This approach allows you to easily update the Agent later using the git pull command.

  • Open the repository folder:

    • Navigate to the repository folder and then to the “cra-scripts” subfolder.

  • Set Directory:
    • Change the current directory in Bash/PowerShell to the “cra-scripts” folder.

    • Example command: cd [Path to cra-scripts folder]

    • Note: Adjust the path based on where you cloned the repository on your system.

    mode = server

  • bito_cli.bito.access_key

  • git.access_token

  • Optional properties (can be skipped or set as needed):

    • git.provider

    • git.domain

    • code_feedback

    • static_analysis

    • dependency_check

    • dependency_check.snyk_auth_token

    • server_port

    • review_scope

    • exclude_branches

    • exclude_files

    • exclude_draft_pr

  • Note: It will provide the Git Webhook secret in encrypted format.

  • On Windows in PowerShell:

    • Install OpenSSL

      • Reference-1: https://wiki.openssl.org/index.php/Binariesarrow-up-right

      • Reference-2:

    • Run ./bito-cra.ps1 service start bito-cra.properties

    • Note: It will provide the Git Webhook secret in encrypted format.

  • Click Add webhook.

  • Under Payload URL, enter the URL of the webhook endpoint. This is the server's URL to receive webhook payloads.

    • Note: The GitHub Payload URL should follow this format: https://<domain name/ip-address>/api/v1/github_webhooks, where https://<domain name/ip-address> should be mapped to Bito's AI Code Review Agent container, which runs as a service on a configured TCP port such as 10051. Essentially, you need to append the string "/api/v1/github_webhooks" (without quotes) to the URL where the AI Code Review Agent is running.

    • For example, a typical webhook URL would be https://cra.example.com/api/v1/github_webhooks

  • Select the Content type “application/json” for JSON payloads.

  • In Secret token, enter the webhook secret token that you copied above. It is used to validate payloads.

  • Click on Let me select individual events to select the events that you want to trigger the webhook. For code review select these:

    • Issue comments - To enable Code Review on-demand by issuing a command in the PR comment.

    • Pull requests - To auto-trigger Code Review when a pull request is created.

    • Pull request review comments - So, you can share feedback on the review quality by answering the feedback question in the code review comment.

  • To make the webhook active immediately after adding the configuration, select Active.

  • Click Add webhook.

  • Select Add new webhook.

  • In URL, enter the URL of the webhook endpoint. This is the server's URL to receive webhook payloads.

    • Note: The GitLab webhook URL should follow this format: https://<domain name/ip-address>/api/v1/gitlab_webhooks, where https://<domain name/ip-address> should be mapped to Bito's AI Code Review Agent container, which runs as a service on a configured TCP port such as 10051. Essentially, you need to append the string "/api/v1/gitlab_webhooks" (without quotes) to the URL where the AI Code Review Agent is running.

    • For example, a typical webhook URL would be https://cra.example.com/api/v1/gitlab_webhooks

  • In Secret token, enter the webhook secret token that you copied above. It is used to validate payloads.

  • In the Trigger section, select the events to trigger the webhook. For code review select these:

    • Comments - for on-demand code review.

    • Merge request events - for automatic code review when a merge request is created.

    • Emoji events - So, you can share feedback on the review quality using emoji reactions.

  • Select Add webhook.

  • Click Add webhook.
  • Under URL, enter the URL of the webhook endpoint. This is the server's URL to receive webhook payloads.

    • Note: The BitBucket Payload URL should follow this format: https://<domain name/ip-address>/api/v1/bitbucket_webhooks, where https://<domain name/ip-address> should be mapped to Bito's AI Code Review Agent container, which runs as a service on a configured TCP port such as 10051. Essentially, you need to append the string "/api/v1/bitbucket_webhooks" (without quotes) to the URL where the AI Code Review Agent is running.

    • For example, a typical webhook URL would be https://cra.example.com/api/v1/bitbucket_webhooks

  • In Secret token, enter the webhook secret token that you copied above. It is used to validate payloads.

  • In the Triggers section, select the events to trigger the webhook. For code review select these:

    • Pull Request > Comment created - for on-demand code review.

    • Pull Request > Created - for automatic code review when a merge request is created.

  • Select Save.

  • Bito also offers specialized commands that are designed to provide detailed insights into specific areas of your source code, including security, performance, scalability, code structure, and optimization.

    • /review security: Analyzes code to identify security vulnerabilities and ensure secure coding practices.

    • /review performance: Evaluates code for performance issues, identifying slow or resource-heavy areas.

    • /review scalability: Assesses the code's ability to handle increased usage and scale effectively.

    • /review codeorg: Scans for readability and maintainability, promoting clear and efficient code organization.

    • /review codeoptimize: Identifies optimization opportunities to enhance code efficiency and reduce resource usage.

    By default, the /review command generates inline comments, meaning that code suggestions are inserted directly beneath the code diffs in each file. This approach provides a clearer view of the exact lines requiring improvement. However, if you prefer a code review in a single post rather than separate inline comments under the diffs, you can include the optional parameter: /review #inline_comment=False

    For more details, refer to Available Commands.

    Restart the Docker container:

    • To restart the Docker container running as a service, use the below command.

    • On Linux/macOS in Bash: Run ./bito-cra.sh service restart bito-cra.properties

    • On Windows in PowerShell: Run ./bito-cra.ps1 service restart bito-cra.properties

    CPU Cores

    4

    RAM

    8 GB

    Hard Disk Drive

    80 GB

    Linux

    You will need:

    1. Bash (minimum version 4.x)

      • For Debian and Ubuntu systems

        sudo apt-get install bash

      • For CentOS and other RPM-based systems

        sudo yum install bash

    1. Docker (minimum version 20.x)

    macOS

    You will need:

    1. Bash (minimum version 4.x)

      brew install bash

    1. Docker (minimum version 20.x)

    Windows

    You will need:

    1. PowerShell (minimum version 5.x)

      • View Guidearrow-up-right

      • Note: In PowerShell version 7.x, run Set-ExecutionPolicy Unrestricted command. It allows the execution of scripts without any constraints, which is essential for running scripts that are otherwise blocked by default security settings.

    1. Docker (minimum version 20.x)

    View Guide
    View Guidearrow-up-right
    View Guidearrow-up-right
    View Guidearrow-up-right
    prerequisites for self-hosted
    Agent Configuration: bito-cra.properties File
    Agent Configuration: bito-cra.properties File
    Required Access Tokens
    GitHub Webhook Setup Guidearrow-up-right
    GitHubarrow-up-right
    GitLab Webhook Setup Guidearrow-up-right
    GitLabarrow-up-right
    BitBucket Webhook Setup Guidearrow-up-right
    BitBucketarrow-up-right
    contact supportenvelope
    https://github.com/gitbito/CodeReviewAgentarrow-up-right
    GitHub Personal Access Token (Classic)
    GitLab Personal Access Token
    Changelist in AI Code Review Agent's feedback.
    The AI Code Review Agent understands code changes in pull requests by analyzing relevant context from your entire repository, resulting in more accurate and helpful code reviews. The agent provides either Basic Code Understanding or Advanced Code Understanding based on the programming languages used in the code diff. Learn more about all the supported languages in the table below.

    Basic Code Understanding is providing the surrounding code for the diff to help AI better understand the context of the diff.

    Advanced Code Understanding is providing detailed information holistically to the LLM about the changes the diff is making—from things such as global variables, libraries, and frameworks (e.g., Lombok in Java, React for JS/TS, or Angular for TS) being used, the specific functions/methods and classes the diff is part of, to the upstream and downstream impact of a change being made. Using advanced code traversal and understanding techniques, such as symbol indexes, embeddings, and abstract syntax trees, Bito deeply tries to understand what your changes are about and the impact and relevance to the greater codebase, like a senior engineer does when doing code review. Read more here about our approacharrow-up-right.

    circle-info

    For requests to add support for specific programming languages, please reach out to us at [email protected]envelope

    Languages
    AI Code Review
    Basic Code Understanding
    Advanced Code Understanding

    Assembly

    YES

    YES

    YES

    Bash/Shell

    YES

    YES

    YES

    C

    YES


    hashtag
    Static Code Analysis and Open Source Vulnerabilities Check

    For custom SAST tools configuration to support specific languages in the AI Code Review Agent, please reach out to us at [email protected]envelope

    Languages
    Static Code Analysis / Linters
    Open Source Vulnerabilities Check

    Assembly

    NO

    NO

    Bash/Shell

    NO

    NO

    C

    YES (using Facebook Infer)

    NO


    hashtag
    Supported Tools and Platforms

    Tool
    Type
    Supported/Integrated

    Astral Ruff

    Linter for Python

    YES

    Azure DevOps

    Code Repository

    Coming soon

    Bitbucket

    Code Repository

    YES

    detect-secrets


    hashtag
    Supported output languages for code review feedback

    Bito supports posting code review feedback in over 20 languages. You can choose your preferred language in the agent settings. Supported languages include the following:

    1. Arabic (عربي)

    2. Bulgarian (български)

    3. Chinese (Simplified) (简体中文)

    4. Chinese (Traditional) (繁體中文)

    5. Czech (čeština)

    6. Dutch (Nederlands)

    7. English (English)

    8. French (français)

    9. German (Deutsch)

    10. Hebrew (עִברִית)

    11. Hindi (हिंदी)

    12. Hungarian (magyar)

    13. Italian (italiano)

    14. Japanese (日本語)

    15. Korean (한국어)

    16. Malay (Melayu)

    17. Polish (polski)

    18. Portuguese (português)

    19. Russian (русский)

    20. Spanish (español)

    21. Turkish (Türkçe)

    22. Vietnamese (Tiếng Việt)

    Learn technical concepts

  • Generate test cases

  • Explain code

  • Comment method

  • Improve code performance

  • Check security

  • Find style issues

  • hashtag
    Generate Code

    Instruction

    circle-info

    Implement a simple rest API in Go.

    Response

    circle-check

    hashtag
    Command Syntax

    Instruction

    circle-info

    How to rebase a branch in git?

    Response

    circle-check
    1. Checkout the branch you want to rebase:

    $ git checkout

    1. Rebase your branch against the upstream branch:

    $ git rebase upstream/

    1. Resolve any conflicts that arise.

    2. Once all conflicts are resolved, do a git status to verify that all files have been updated correctly.

    3. Finally, push the rebased branch to the remote repository:

    $ git push origin --force

    hashtag
    Learn Technical Concepts

    Instruction

    circle-info

    Can you explain the B+ tree with a code example?

    Response

    circle-check

    A B+ tree is a self-balancing tree data structure used in databases to store and retrieve data efficiently. It is a variation of the B-tree and is designed to minimize the number of disk accesses required for insertion, deletion, and retrieval operations. B+ trees are characterized by the number of keys stored per node, the order of the nodes, and the number of children per node.

    For example, a B+ tree of order 5 would have 5 keys per node and 5 children per node. When a node becomes full, it will split into two nodes, each containing half of the keys and half of the children. This means that all the nodes at the same level will have the same number of keys, making retrieval operations more efficient.

    Here is an example in Python

    hashtag
    Test Case

    Instruction

    circle-info

    Generate test cases for the following method.

    Response

    circle-check

    Test Case 1: Input: newLabelArray = [ 'Apple', 'Banana', 'Mango', 'Apple' ] oldLabelArray = [ 'Banana', 'Mango', 'Orange' ] Expected Output: ['Apple:2', 'Orange:-1']

    Test Case 2: Input: newLabelArray = [ 'Apple', 'Banana', 'Apple', 'Orange' ] oldLabelArray = [ 'Banana', 'Mango', 'Orange' ] Expected Output: ['Apple:2', 'Mango:-1']

    hashtag
    Explain this Code

    Instruction

    circle-info

    What does this code do?

    Response

    circle-check

    This code takes two arrays, newLabelArray and oldLabelArray, and generates a new array that contains the difference between the two arrays. It does this by first creating three empty arrays, new_, old_, and merged_. It then iterates through the newLabelArray and adds each label to the new_ array, as well as the merged_ array. It then iterates through the oldLabelArray and does the same for the old_ array, but also subtracts it from the merged_ array. Finally, it iterates through the merged_ array and checks for any values that are not equal to 0 and adds them to the final array. It then returns this final array.

    hashtag
    Comment Method

    Instruction

    circle-info

    Generate a comment for this method, explaining the parameters and output

    Response

    circle-check

    /* This method takes two arrays, newLabelArray and oldLabelArray. It uses the elements of both arrays to generate a merged array, merged_, where it counts the occurrences of each element in both arrays. It then creates a third array, final, containing the elements of merged_ where the difference is not 0. The output is the final array. */

    hashtag
    Improve Performance

    Instruction

    circle-info

    How can I improve the performance of this code?

    Response

    circle-check
    1. Use ES6 syntax to simplify the code.

    2. Use a hashmap instead of looping through the arrays.

    3. Use a single loop to build the final array instead of two loops.

    4. Use array methods instead of for-each loops.

    5. Use optimized data structures like Set and Map.

    Instruction

    circle-info

    Rewrite this code with performance improvements?

    Response

    circle-check

    hashtag
    Check for Security

    Instruction

    circle-info

    Find potential security issues in this code

    Response

    circle-check
    1. A lack of input validation: the user-supplied search term is not being validated to ensure it is safe to use in a database query. This could leave the system open to SQL injection attacks.

    2. A lack of output encoding: the results from the database are not being encoded before they are printed. This could leave the system open to cross-site scripting attacks.

    Instruction

    circle-info

    Rewrite this code with fix to potential security issues

    Response

    circle-check

    hashtag
    Find Style Issues

    Instruction

    circle-info

    Identify potential issues that EsLint would find in this code

    Response

    circle-check

    //ESLint would find the following issues:

    • Missing semicolons (potential syntax errors)

    • Missing spacing after 'forEach' statements

    • Unused variables (e.g. 'old_')

    • Missing spacing between operators (e.g. '++new_[lbl]')

    Generate Code
    Command Syntax
    package main
    import ( 
    "encoding/json" "fmt" "net/http" )
    type user struct { Name string json:"name" Age int json:"age" }
    func main() 
    {http.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) { 
    	// Create user 
    	u := user{ Name: "John Doe", Age: 25, }
    	// Encode user
    	uj, err := json.Marshal(u)
    	if err != nil {
    		fmt.Fprintf(w, err.Error())
    	}
    	// Return user
    	w.Header().Set("Content-Type", "application/json")
    	w.WriteHeader(http.StatusOK)
    	fmt.Fprintf(w, "%s\n", uj)
    })
    http.ListenAndServe(":3000", nil)
    }
    genrateLabelDiffArray(newLabelArray,oldLabelArray=[])
      {
        let new_ =[],old_=[],merged_=[];
        newLabelArray.forEach((lbl)=>{
          if(new_[lbl] === undefined){ new_[lbl] =0;merged_[lbl]=0; }
          ++new_[lbl];
          ++merged_[lbl];
        });
        
        oldLabelArray.forEach((lbl)=>{
          if(old_[lbl] === undefined){ old_[lbl] =0; }
          if(merged_[lbl] === undefined){ merged_[lbl] =0; }
    
          ++old_[lbl];
          --merged_[lbl]
        });
        let final = [];
    
        merged_.forEach((value,key)=>{
          if(value!=0){ 
          //  final[key.toString()] = value;
          final.push(key+":"+value);
           }
        })
        
          return final;
      }
    genrateLabelDiffArray(newLabelArray,oldLabelArray=[])
      {
        let new_ =[],old_=[],merged_=[];
        newLabelArray.forEach((lbl)=>{
          if(new_[lbl] === undefined){ new_[lbl] =0;merged_[lbl]=0; }
          ++new_[lbl];
          ++merged_[lbl];
        });
        
        oldLabelArray.forEach((lbl)=>{
          if(old_[lbl] === undefined){ old_[lbl] =0; }
          if(merged_[lbl] === undefined){ merged_[lbl] =0; }
    
          ++old_[lbl];
          --merged_[lbl]
        });
        let final = [];
    
        merged_.forEach((value,key)=>{
          if(value!=0){ 
          //  final[key.toString()] = value;
          final.push(key+":"+value);
           }
        })
        
          return final;
      }
    genrateLabelDiffArray(newLabelArray,oldLabelArray=[])
      {
        let new_ =[],old_=[],merged_=[];
        newLabelArray.forEach((lbl)=>{
          if(new_[lbl] === undefined){ new_[lbl] =0;merged_[lbl]=0; }
          ++new_[lbl];
          ++merged_[lbl];
        });
        
        oldLabelArray.forEach((lbl)=>{
          if(old_[lbl] === undefined){ old_[lbl] =0; }
          if(merged_[lbl] === undefined){ merged_[lbl] =0; }
    
          ++old_[lbl];
          --merged_[lbl]
        });
        let final = [];
    
        merged_.forEach((value,key)=>{
          if(value!=0){ 
          //  final[key.toString()] = value;
          final.push(key+":"+value);
           }
        })
        
          return final;
      }
    genrateLabelDiffArray(newLabelArray,oldLabelArray=[])
      {
        let new_ =[],old_=[],merged_=[];
        newLabelArray.forEach((lbl)=>{
          if(new_[lbl] === undefined){ new_[lbl] =0;merged_[lbl]=0; }
          ++new_[lbl];
          ++merged_[lbl];
        });
        
        oldLabelArray.forEach((lbl)=>{
          if(old_[lbl] === undefined){ old_[lbl] =0; }
          if(merged_[lbl] === undefined){ merged_[lbl] =0; }
    
          ++old_[lbl];
          --merged_[lbl]
        });
        let final = [];
    
        merged_.forEach((value,key)=>{
          if(value!=0){ 
          //  final[key.toString()] = value;
          final.push(key+":"+value);
           }
        })
        
          return final;
      }
    genrateLabelDiffArray(newLabelArray,oldLabelArray=[])
      {
        let new_ =[],old_=[],merged_=[];
        newLabelArray.forEach((lbl)=>{
          if(new_[lbl] === undefined){ new_[lbl] =0;merged_[lbl]=0; }
          ++new_[lbl];
          ++merged_[lbl];
        });
        
        oldLabelArray.forEach((lbl)=>{
          if(old_[lbl] === undefined){ old_[lbl] =0; }
          if(merged_[lbl] === undefined){ merged_[lbl] =0; }
    
          ++old_[lbl];
          --merged_[lbl]
        });
        let final = [];
    
        merged_.forEach((value,key)=>{
          if(value!=0){ 
          //  final[key.toString()] = value;
          final.push(key+":"+value);
           }
        })
        
          return final;
      }
    // Rewritten Code
    function genrateLabelDiffArray(newLabelArray, oldLabelArray = []) {
      let new_ = {},
        old_ = {},
        merged_ = {},
        final = [];
    
      newLabelArray.forEach((lbl) => {
        new_[lbl] = new_[lbl] ? new_[lbl] + 1 : 1;
        merged_[lbl] = merged_[lbl] ? merged_[lbl] + 1 : 1;
      });
    
      oldLabelArray.forEach((lbl) => {
        old_[lbl] = old_[lbl] ? old_[lbl] + 1 : 1;
        merged_[lbl] = merged_[lbl] ? merged_[lbl] - 1 : -1;
      });
    
      Object.entries(merged_).forEach(([key, value]) => {
        if (value !== 0) {
          final.push(key + ":" + value);
        }
      });
      
      return final;
    }
    import database
    search_term = input("Enter a search term: ")
    query = "SELECT * FROM users WHERE name = '" + search_term + "'"
    results = database.query(query)
    print(results)
    import database
    search_term = input("Enter a search term: ")
    query = "SELECT * FROM users WHERE name = '" + search_term + "'"
    results = database.query(query)
    print(results)
    import database
    
    # Get the user-supplied search term
    search_term = input("Enter a search term: ")
    
    # Use the user-supplied search term to query the database
    query = "SELECT * FROM users WHERE name = %s"
    results = database.query(query, (search_term,))
    
    # Print the results
    print(results)
    genrateLabelDiffArray(newLabelArray,oldLabelArray=[])
      {
        let new_ =[],old_=[],merged_=[];
        newLabelArray.forEach((lbl)=>{
          if(new_[lbl] === undefined){ new_[lbl] =0;merged_[lbl]=0; }
          ++new_[lbl];
          ++merged_[lbl];
        });
        
        oldLabelArray.forEach((lbl)=>{
          if(old_[lbl] === undefined){ old_[lbl] =0; }
          if(merged_[lbl] === undefined){ merged_[lbl] =0; }
    
          ++old_[lbl];
          --merged_[lbl]
        });
        let final = [];
    
        merged_.forEach((value,key)=>{
          if(value!=0){ 
          //  final[key.toString()] = value;
          final.push(key+":"+value);
           }
        })
        
          return final;
      }

    YES

    YES

    C++

    YES

    YES

    YES

    C#

    YES

    YES

    YES

    Dart

    YES

    YES

    YES

    Delphi

    YES

    YES

    YES

    Go

    YES

    YES

    YES

    Groovy

    YES

    YES

    YES

    HTML/CSS

    YES

    YES

    YES

    Java

    YES

    YES

    YES

    JavaScript

    YES

    YES

    YES

    JavaScript Framework

    YES

    YES

    YES

    Kotlin

    YES

    YES

    YES

    Lua

    YES

    YES

    YES

    Objective-C

    YES

    YES

    YES

    PHP

    YES

    YES

    YES

    PowerShell

    YES

    YES

    YES

    Python

    YES

    YES

    YES

    R

    YES

    YES

    YES

    Ruby

    YES

    YES

    YES

    Rust

    YES

    YES

    YES

    Scala

    YES

    YES

    YES

    SCSS

    YES

    YES

    YES

    SQL

    YES

    YES

    YES

    Swift

    YES

    YES

    YES

    Terraform

    YES

    YES

    YES

    TypeScript

    YES

    YES

    YES

    TypeScript Framework

    YES

    YES

    YES

    Vue.js

    YES

    YES

    YES

    Visual Basic .NET

    YES

    YES

    YES

    Others

    YES

    YES

    YES

    C++

    YES (using Facebook Infer)

    NO

    C#

    NO

    NO

    Dart

    NO

    NO

    Delphi

    NO

    NO

    Go

    YES (using golangci-lint)

    YES

    Groovy

    NO

    NO

    HTML/CSS

    NO

    NO

    Java

    YES (using Facebook Infer)

    NO

    JavaScript

    YES (using ESLint)

    YES

    Kotlin

    NO

    NO

    Lua

    NO

    NO

    Objective-C

    YES (using Facebook Infer)

    NO

    PHP

    NO

    NO

    PowerShell

    NO

    NO

    Python

    YES (using Astral Ruff and Mypy)

    NO

    R

    NO

    NO

    Ruby

    NO

    NO

    Rust

    NO

    NO

    Scala

    NO

    NO

    SCSS

    NO

    NO

    SQL

    NO

    NO

    Swift

    NO

    NO

    Terraform

    NO

    NO

    TypeScript

    YES (using ESLint)

    YES

    Vue.js

    NO

    NO

    Visual Basic .NET

    NO

    NO

    Others

    NO

    NO

    Secrets scanner (e.g., passwords, API keys, sensitive information)

    YES

    ESLint

    Linter for JavaScript and TypeScript

    YES

    Facebook Infer

    Static Code Analysis for Java, C, C++, and Objective-C

    YES

    GitHub cloud

    Code Repository

    YES

    GitHub (Self-Managed)

    Code Repository

    YES, supports version 3.0 and above.

    GitLab cloud

    Code Repository

    YES

    GitLab (Self-Managed)

    Code Repository

    YES, supports version 15.5 and above.

    golangci-lint

    Linter for Go

    YES

    Mypy

    Static Type Checker for Python

    YES

    OWASP dependency Check

    Security

    YES

    Snyk

    Security

    YES

    Whispers

    Secrets scanner (e.g., passwords, API keys, sensitive information)

    YES

    https://slproweb.com/products/Win32OpenSSL.htmlarrow-up-right
    View Guidearrow-up-right
    View Guidearrow-up-right
    View Guidearrow-up-right
    class Node:
        def __init__(self, order):
            self.order = order
            self.keys = []
            self.children = [None] * (order + 1)
    
    class BPlusTree:
        def __init__(self, order):
            self.root = Node(order)
     
        def insert(self, key):
            if not self.root.keys:
                self.root.keys.append(key)
            else:
                pass # traverse the tree and insert the key
     
        def delete(self, key):
            pass # traverse the tree and delete the key
     
        def search(self, key):
            pass # traverse the tree and search for the key
     
    # Create a B+ tree of order 5
    bplus_tree = BPlusTree(5)
     
    # Insert a key
    bplus_tree.insert(10)
     
    # Delete a key
    bplus_tree.delete(10)
    
    # Search for a key
    bplus_tree.search(10)

    Install AI Architect (self-hosted)

    Deploy AI Architect in your own infrastructure for complete data control and enhanced security

    This guide walks you through installing Bito's AI Architect as a self-hosted service in your own infrastructure. Self-hosting gives you complete control over where your code knowledge graph resides and how AI Architect accesses your repositories.

    Why choose self-hosted deployment? Organizations with strict data governance requirements, air-gapped environments, or specific compliance needs benefit from running AI Architect within their own infrastructure. Your codebase analysis and knowledge graph stay entirely within your control, while still providing the same powerful context-aware capabilities to your AI coding tools.

    What you'll accomplish: By the end of this guide, you'll have AI Architect running on your infrastructure, connected to your Git repositories, and ready to integrate with AI coding tools like Claude Code, Cursor, Windsurf, and GitHub Copilot through the Model Context Protocol (MCP).

    hashtag
    Deployment options

    AI Architect can be deployed in three different configurations depending on your team size, infrastructure, and security requirements:

    hashtag
    a. Personal use (with your LLM keys)

    Set up AI Architect on your local machine for individual development work. You'll provide your own LLM API keys for indexing, giving you complete control over the AI models used and associated costs.

    Best for: Individual developers who want codebase understanding on their personal machine.

    hashtag
    b. Team / shared access (with your LLM keys)

    Deploy AI Architect on a shared server within your infrastructure, allowing multiple team members to connect their AI coding tools to the same MCP server. Each team member can configure AI Architect with their preferred AI coding agent while sharing the same indexed codebase knowledge graph.

    Best for: Development teams that want to share codebase intelligence across the team while managing their own LLM costs.

    hashtag
    c. Enterprise deployment (requires Bito Enterprise Plan)

    Deploy AI Architect on your infrastructure (local machine or shared server) with indexing managed by Bito. Instead of providing your own LLM keys, Bito handles the repository indexing process, simplifying setup and cost management.

    Best for: Organizations that prefer managed indexing without handling individual LLM API keys and costs.

    circle-info

    Note: All deployment options are self-hosted on your infrastructure — your code and knowledge graph remain under your control.

    hashtag
    Prerequisites

    hashtag
    a. Required accounts and tokens

    1

    hashtag
    Bito API Key (aka Bito Access Key)

    You'll need a Bito account and a Bito Access Key to authenticate AI Architect. You can sign up for a Bito account at , and create an access key from

    hashtag
    b. System requirements

    AI Architect can be installed on your local machine for individual use, or on a shared server that your entire team can connect to. When installed on a server, multiple developers can configure their AI coding tools (such as Claude Code, Cursor, Windsurf, etc.) to use the same MCP server, sharing access to the indexed codebase.

    The AI Architect supports the following operating systems:

    • macOS

    • Unix-based systems (Ubuntu, Debian, RHEL, or similar distributions)

    • Windows (via WSL2)

    hashtag
    Shared servers (for team deployments)

    • On-premise physical servers - Bare metal Linux servers in your data center

    • On-premise virtual machines - VMware, Hyper-V, Proxmox, KVM, or other virtualization platforms

    • Cloud virtual machines - AWS EC2, Google Cloud Compute Engine, Azure VMs, DigitalOcean Droplets, or similar cloud instances

    1

    hashtag
    Hardware specifications

    Recommended

    hashtag
    Installation guide

    1

    hashtag
    Install AI Architect

    Before proceeding with the installation, ensure Docker Desktop / Docker Service or Kubernetes cluster is running on your system. If it's not already running, launch it and wait for it to fully start before continuing.

    Open your terminal:

    hashtag
    Update repository list and re-index

    Edit /usr/local/etc/bitoarch/.bitoarch-config.yaml file to add/remove repositories.

    To apply the changes, run this command:

    Start the re-indexing process using this command:

    hashtag
    Accessing services (Kubernetes-based deployment)

    Port-forwards are exposed on all network interfaces (0.0.0.0) and are accessible from any machine on the network.

    hashtag
    Local access (from the Kubernetes host machine)

    hashtag
    Network access (from other machines on your network)

    Get the host machine's IP address:

    From another machine on the network:

    hashtag
    Security considerations

    Important security notes:

    • Port-forwards use HTTP (not HTTPS) - traffic is unencrypted

    • Services are accessible from any machine that can reach the host

    For production internet-facing deployments:

    hashtag
    Alternative: Kubernetes Ingress (production)

    For production deployments, configure a Kubernetes Ingress Controller with TLS/SSL instead of using port-forwards. This provides secure HTTPS access with proper certificate management.

    hashtag
    Setting up AI Architect MCP in coding agents

    Now that AI Architect is installed and your repositories are indexed, the next step is to connect it to your AI coding tools (such as Claude Code, Cursor, Windsurf, GitHub Copilot, etc.) through the Model Context Protocol (MCP).

    hashtag
    Quick setup (recommended)

    Save time with our automated installer! We provide a one-command setup that automatically configures AI Architect for all compatible AI coding tools on your system.

    The automated installer will:

    • Detect all supported AI tools installed on your system

    • Configure them automatically with your MCP credentials

    • Get you up and running in seconds instead of manually configuring each tool

    👉 for automated setup across all your tools.

    hashtag
    Manual setup

    If you prefer hands-on control over your configuration or encounter issues with automated setup, we provide detailed step-by-step guides for each supported AI coding tool:

    Each guide walks you through the complete manual configuration process for that specific tool.

    hashtag
    Configuring AI Architect for Bito AI Code Review Agent

    Now that you have AI Architect set up, you can take your code quality to the next level by integrating it with . This powerful combination delivers significantly more accurate and context-aware code reviews by leveraging the deep codebase knowledge graph that AI Architect has built.

    Why integrate AI Architect with AI Code Review Agent?

    When the AI Code Review Agent has access to AI Architect's knowledge graph, it gains a comprehensive understanding of your entire codebase architecture — including microservices, modules, APIs, dependencies, and design patterns.

    This enables the AI Code Review Agent to:

    • Provide system-aware code reviews - Understand how changes in one service or module impact other parts of your system

    • Catch architectural inconsistencies - Identify when new code doesn't align with your established patterns and conventions

    • Detect cross-repository issues - Spot problems that span multiple repositories or services

    hashtag
    Getting started with AI Architect-powered code reviews

    1. Log in to

    2. Open the dashboard.

    3. In the Server URL field, enter your Bito MCP URL

    Need help getting started? Contact our team at to request a trial. We'll help you configure the integration and get your team up and running quickly.

    hashtag
    Upgrading AI Architect

    Upgrade your AI Architect installation to the latest version while preserving your data and configuration. The upgrade process:

    • Automatically detects your current version

    • Downloads and extracts the new version

    • Migrates your configuration and data

    hashtag
    Upgrade instructions

    hashtag
    Option 1: Upgrade from within your installation (Recommended)

    If you're running version 1.1.0 or higher, navigate to your current installation directory and run:

    hashtag
    Option 2: Upgrade from external location

    If you need to run the upgrade from outside your installation directory (useful for version 1.0.0), use the --old-path parameter:

    hashtag
    Upgrade parameters

    The upgrade script supports the following parameters:

    circle-info

    Your data is safe: All repositories, indexes, API keys, and settings are automatically preserved during upgrade.

    circle-info

    Important: You can only upgrade within the same deployment type. To switch from Docker Compose to Kubernetes or vice versa, you must use the ./setup.sh --clean command, which will result in data loss.

    hashtag
    Troubleshooting guide

    hashtag
    Commands specific to Kubernetes-based deployment

    hashtag
    Available commands

    For complete reference of AI Architect CLI commands, refer to .

    View Guide

    2

    hashtag
    Git provider

    We support the following Git providers:

    • GitHub

    • GitLab

    • Bitbucket

    So, you'll need an account on one of these Git providers to index your repositories with AI Architect.

    3

    hashtag
    Git Access Token

    A personal access token from your chosen Git provider is required. You'll use this token to allow AI Architect to read and index your repositories.

    1. GitHub Personal Access Token (Classic): To use GitHub repositories with AI Architect, ensure you have a CLASSIC personal access token with repo access. We do not support fine-grained tokens currently.

    2. GitLab Personal Access Token: To use GitLab repositories with AI Architect, a token with API access is required.

    3. Bitbucket Access Token: To use Bitbucket repositories with AI Architect, you need API Token or HTTP Access Token depending on your Bitbucket setup.

      1. Bitbucket Cloud (API Token): You must provide both your token and email address.

    4

    hashtag
    LLM API keys

    Bito's AI Architect uses Large Language Models (LLMs) to build a knowledge graph of your codebase.

    We suggest you provide API keys for both Anthropic and Grok LLMs, as that provides the best coverage and the best cost of indexing.

    Bito will use Claude Haiku and Grok Code Fast together to index your codebase. It will cost you approximately USD $0.20 - $0.40 per MB of indexable code (we do not index binaries, TARs, zips, images, etc). If you provide only an Anthropic key without Grok, your indexing costs will be significantly higher, approximately USD $1.00 - $1.50 per MB of indexable code.

    RAM

    8-12 GB

    Disk

    SSD with adequate IOPS Note: Ensure sufficient disk space is available, as all configured repositories will be cloned to this disk during setup.

    AI Architect automatically detects available system resources during setup and configures optimal resource allocation for its Docker containers. For most deployments, the automatic configuration provides good performance. However, you can manually adjust these settings to fine-tune performance or accommodate specific workload requirements.

    You can customize resource limits by editing the .env-bitoarch file and run the command ./setup.sh --force-restart to update the allocation. The following environment variables can be manually configured to control resource allocation.

    2

    hashtag
    WSL2 is required for Windows users

    If you're running Windows, Windows Subsystem for Linux 2 (WSL2) must be installed before proceeding.

    To install WSL2:

    1. Open PowerShell or Command Prompt as Administrator

    2. Run the following command:

    1. Set up your Ubuntu username and password when prompted.

    3

    hashtag
    Docker Desktop / Docker Service (required)

    Docker Compose is required to run AI Architect.

    The easiest and recommended way to get Docker Compose is to install Docker Desktop.

    Docker Desktop includes Docker Compose along with Docker Engine and Docker CLI which are Docker Compose prerequisites.

    Configuration for Windows (WSL2):

    If you're using Windows with WSL2, you need to enable Docker integration with your WSL distribution:

    1. Open Docker Desktop

    2. Go to Settings > Resources > WSL Integration

    3. Enable integration for your WSL distribution (e.g., Ubuntu)

    4

    hashtag
    Kubernetes cluster (required for Kubernetes based deployment method)

    hashtag
    For production environments:

    During the setup process given below, if you choose as your deployment method, you must have an existing Kubernetes cluster set up and running.

    Ensure your Kubernetes cluster have the following required tools:

    • kubectl (Kubernetes command-line tool)

    • helm (Kubernetes package manager)

    hashtag
    For testing and development:

    For testing purposes, you can create a local Kubernetes cluster using KIND (Kubernetes in Docker). KIND allows you to run Kubernetes clusters in Docker containers.

    Install KIND:

    • macOS:

    • Linux:

    circle-info

    Note: Before creating a KIND cluster, verify Docker has sufficient resources:

    Required: Minimum 4 CPUs and 8GB RAM

    If resources are insufficient, increase Docker Desktop resources (Preferences → Resources) and restart Docker.

    hashtag
    Setting up a test cluster with KIND

    Create a KIND cluster with proper port mappings for service access:

    circle-info

    Note: Services use ClusterIP for secure, internal-only access. External access is configured via Ingress Controller on ports 80/443.

    hashtag
    Verify cluster

    Linux/macOS: Use your standard terminal application

  • Windows (WSL2): Launch the Ubuntu application from the Start menu

  • Execute the installation command:

    The installation script will:

    • Download the latest Bito AI Architect package

    • Extract it to your system

    • Initialize the setup process

    circle-info

    Installing dependencies:

    The AI Architect setup process will automatically check for required tools on your system. If any dependencies are missing (such as jq, which is needed for JSON processing), you'll be prompted to install them. Simply type y and press Enter to proceed with the installation.

    2

    hashtag
    Configuration

    Follow the on-screen prompts to configure your deployment. You'll provide the following information:

    hashtag
    Select AI Architect deployment method:

    Choose how you want to deploy Bito's AI Architect. We support two deployment methods:

    1. Docker Compose: Deploys AI Architect using Docker Compose.

    2. Kubernetes: Deploys AI Architect to an existing Kubernetes cluster. Choose this option if you have an existing Kubernetes cluster running and want to leverage Kubernetes for orchestration, scaling, and management.

      • Note: The setup script will automatically deploy AI Architect services to your Kubernetes cluster in the bito-ai-architect

    circle-info

    If you have a Kubernetes cluster:

    1. Ensure it's running

    2. Verify the current Kubernetes context: kubectl config current-context

    hashtag
    You'll need to provide the following details when prompted:

    circle-info

    Note: Refer to the for details on how to obtain these.

    • Bito API Key (required) - Enter your Bito Access key and press Enter.

    • Git provider (required):

      You'll be prompted to choose your Git provider:

      1. GitLab

    3

    hashtag
    Add repositories

    Once your Git account is connected successfully, Bito automatically detects your repositories and populates the /usr/local/etc/bitoarch/.bitoarch-config.yaml file with an initial list. Review this file to confirm which repositories you want to index — feel free to remove any that should be excluded or add others as needed. Once the list looks correct, save the file, and continue with the steps below.

    circle-info

    For versions older than 1.4.0, configuration file can be found in installation directory.

    Below is an example of how the .bitoarch-config.yaml file is structured:

    After updating the .bitoarch-config.yaml file, you have two options to proceed with adding your repositories for indexing:

    1. Auto Configure (recommended)

      • Automatically saves the repositories and starts indexing

      • If needed, edit the repo list before selecting this option

    Once you select an option, your Bito MCP URL and Bito MCP Access Token will be displayed. Make sure to store them in a safe place, you'll need them later when configuring MCP server in your AI coding agent (e.g., Claude Code, Cursor, Windsurf, GitHub Copilot (VS Code), etc.).

    To manually apply the configuration, run this command:

    4

    hashtag
    Start indexing

    Once your repositories are configured, AI Architect needs to analyze and index them to build the knowledge graph. This process scans your codebase structure, dependencies, and relationships to enable context-aware AI assistance.

    Start the indexing process by running:

    circle-info

    Note: Indexing process will take approximately 3-10 minutes per repository. Smaller repos take less time.

    Once the indexing is complete, you can configure AI Architect MCP server in any coding or chat agent that supports MCP.

    5

    hashtag
    Check indexing status

    Run this command to check the status of your indexing:

    circle-info

    Example output:

    What each section represents:

    • Configured Repositories: Shows how many repositories are added in your config file for indexing.

    • Repository Index Status: Shows the indexing progress for each individual repository.

    • Workspace Index Progress: Shows the status of indexes that combine and process information across multiple repositories.

    6

    hashtag
    Check MCP server details

    To manually check the MCP server details (e.g. Bito MCP URL and Bito MCP Access Token), use the following command:

    If you need to update your Bito MCP Access Token, use the following command:

    circle-info

    Replace <new-token> with your new secure token value.

    Important: After rotating the token, you'll need to update it in all AI coding agents (Claude Code, Cursor, Windsurf, etc.) where you've configured this MCP server.

    Use firewall rules to restrict access to trusted IPs

  • Consider using Kubernetes Ingress with TLS/SSL

  • Implement VPN for remote access

  • Use network policies to limit pod-to-pod traffic

  • Guide for GitHub Copilot (VS Code)
  • Guide for Junie (JetBrains)

  • Guide for JetBrains AI Assistant

  • Deliver more accurate suggestions - Generate fixes that are grounded in your actual codebase structure and usage patterns

  • Reduce false positives - Better understand context to avoid flagging valid code as problematic

  • In the Auth token field, enter your Bito MCP Access Token
    Seamlessly transitions to the new version
  • Preserves all indexed repositories and settings

  • CPU

    6-8 cores

    https://alpha.bito.aiarrow-up-right
    Settings -> Advanced Settingsarrow-up-right
    Try our Quick MCP Integration Guide
    Guide for Claude Code
    Guide for Cursor
    Guide for Windsurf
    Bito's AI Code Review Agentarrow-up-right
    Bito Cloudarrow-up-right
    AI Architect Settingsarrow-up-right
    [email protected]envelope
    Available commands
    bitoarch index-repos
    bitoarch index-status
    bitoarch mcp-info
    bitoarch rotate-mcp-token <new-token>
    vim /usr/local/etc/bitoarch/.bitoarch-config.yaml
    bitoarch update-repos
    bitoarch index-repos --only-new-repos
    curl http://localhost:5001/health          # Provider
    curl http://localhost:5002/health          # Manager
    curl http://localhost:5003/health          # Config
    kubectl get nodes -o wide
    # Or: hostname -I (Linux) / ifconfig (macOS)
    curl http://<host-ip>:5001/health          # Provider
    curl http://<host-ip>:5002/health          # Manager
    curl http://<host-ip>:5003/health          # Config
    curl http://<host-ip>:5005/health          # Tracker
    cd /path/to/bito-ai-architect
    ./scripts/upgrade.sh --version=latest
    # Download the standalone upgrade script
    curl -O https://github.com/gitbito/ai-architect/blob/main/upgrade.sh
    chmod +x upgrade.sh
    
    # Run upgrade with explicit path
    ./upgrade.sh --old-path=/path/to/bito-ai-architect --version=latest
    # Description
    --version=VERSION
    
    # Upgrade to specific version
    --version=latest
    
    # Upgrade from custom URL or file
    --url=file:///path/to/package.tar.gz
    
    # Specify installation path (required if running outside installation directory)
    --old-path=/opt/bito-ai-architect
    
    # Show help message
    --help
    # Check all services
    bitoarch status
    bitoarch health --verbose
    
    # View full configuration
    bitoarch show-config --raw
    
    # Test MCP connection
    bitoarch mcp-test
    
    # Check indexing status with details
    bitoarch index-status --raw
    
    # Check setup log
    tail -f setup.log
    
    # Local log files
    tail -f var/logs/cis-provider/provider.log
    tail -f var/logs/cis-manager/manager.log
    
    # Complete logs
    ./setup.sh --logs
    
    # Reset installation (removes all data and configuration)
    ./setup.sh --clean
    
    # Then run setup again
    ./setup.sh
    
    # To stop all the service
    ./setup.sh --stop
    
    # Restart service (for env based config updates)
    ./setup.sh --restart
    
    # Force pull latest images based on service-versions.json and restart services
    ./setup.sh --update
    # Check Kubernetes pod status
    # All pods should show "Running" status.
    kubectl get pods -n bito-ai-architect
    
    # Check detailed information about a specific Kubernetes pod
    kubectl describe pod <pod-name> -n bito-ai-architect
    
    # Access Kubernetes pod shell
    kubectl exec -it -n bito-ai-architect \
      $(kubectl get pod -n bito-ai-architect -l app.kubernetes.io/component=provider -o jsonpath='{.items[0].metadata.name}') \
      -- /bin/sh
    
    # Stop KIND cluster (preserves data)
    docker stop bito-ai-architect-control-plane
    
    # Start KIND cluster again
    docker start bito-ai-architect-control-plane
    
    # Delete KIND cluster completely
    kind delete cluster --name bito-ai-architect
    
    # View Provider service logs:
    kubectl logs -n bito-ai-architect -l app.kubernetes.io/component=provider --tail=100 -f
    
    # View Manager service logs:
    kubectl logs -n bito-ai-architect -l app.kubernetes.io/component=manager --tail=100 -f
    CIS_PROVIDER_MEMORY_LIMIT=1g
    CIS_MANAGER_MEMORY_LIMIT=2g
    CIS_CONFIG_MEMORY_LIMIT=512m
    MYSQL_MEMORY_LIMIT=2g
    CIS_TRACKER_MEMORY_LIMIT=512m
    
    
    CIS_PROVIDER_CPU_LIMIT=1.0
    CIS_MANAGER_CPU_LIMIT=2.0
    CIS_CONFIG_CPU_LIMIT=0.5
    MYSQL_CPU_LIMIT=1.0
    CIS_TRACKER_CPU_LIMIT=0.5
    curl -fsSL https://aiarchitect.bito.ai/install.sh | bash
    View Guidearrow-up-right
  • Bitbucket Self-Hosted (HTTP Access Token): You must provide both your token and username.

    • View Guidearrow-up-right

  • Click Apply
    namespace.
  • Check connectivity: kubectl cluster-info

  • If you don't have a Kubernetes cluster:

    1. Select Docker Compose (option 1)

    GitHub

  • Bitbucket

  • Enter the number corresponding to your Git provider and press Enter.

  • Is your Git provider self-hosted or cloud-based?

    • Type y for enterprise/self-hosted instances (like https://github.company.com) and enter your custom domain URL

    • Type n for standard cloud providers (github.com, gitlab.com, bitbucket.org)

    Press Enter to continue.

  • Git Access Token (required) - Enter personal access token for your Git provider and press Enter.

  • Configure LLM API keys (required) - Choose which AI model provider(s) to configure:

    1. Anthropic

    2. Grok

    3. OpenAI

    Enter the number corresponding to your AI model provider, then provide your API key when prompted.

    We suggest you provide API keys for both Anthropic and Grok LLMs, as that provides the best coverage and the best cost of indexing.

    After adding a provider, you'll be asked: "Do you want to configure another provider?"

    • Type y to add additional providers (recommended for better coverage and fallback options).

    • Type n when you're done adding LLM providers.

    Press Enter to continue.

  • Generate a secure MCP access token? - You'll be asked if you want Bito to create a secure token to prevent unauthorized access to your MCP server:

    • Type y to generate a secure access token (recommended)

    • Type n to skip token generation

    Press Enter to continue.

  • Manual Setup
    • You have to manually update the configuration file and then start the indexing. Below we have provided complete details of the manual process.

    Overall Status: Provides a single summary indicating whether indexing is still running, completed successfully, or failed.

    View Guidearrow-up-right
    View Guidearrow-up-right
    Install Docker Desktoparrow-up-right
    Kubernetesarrow-up-right
    Prerequisites section
    wsl --install
    brew install kind kubectl helm
    # KIND
    curl -Lo ./kind https://kind.sigs.k8s.io/dl/v0.20.0/kind-linux-amd64
    chmod +x ./kind
    sudo mv ./kind /usr/local/bin/kind
    
    # kubectl
    curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl"
    chmod +x kubectl
    sudo mv kubectl /usr/local/bin/
    
    # Helm
    curl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash
    docker info --format 'CPUs={{.NCPU}} Mem={{.MemTotal}}'
    kind create cluster --name bito-ai-architect --config - <<EOF
    kind: Cluster
    apiVersion: kind.x-k8s.io/v1alpha4
    nodes:
    - role: control-plane
      extraPortMappings:
      - containerPort: 80
        hostPort: 80
      - containerPort: 443
        hostPort: 443
    EOF
    kubectl cluster-info --context kind-bito-ai-architect
    kubectl get nodes
    repository:
      configured_repos:
        - namespace: your-org/repo-name-1
        - namespace: your-org/repo-name-2
        - namespace: your-org/repo-name-3
    bitoarch add-repos
    Configured Repositories:
      Total: 3
    
    Repository Index Status:
    State: ⏳ running
      Progress: 0 / 1 completed
      In Progress: 1
    
    Workspace Index Progress:
    State: ⏳ running
      Progress: 1 / 2 completed
      In Progress: 1
    
    Overall Status: in-progress

    Implementing custom code review rules

    Customize Bito’s AI Code Review Agent to enforce your coding practices.

    Bito’s AI Code Review Agent offers a flexible solution for teams looking to enforce custom code review rules, standards, and guidelines tailored to their unique development practices. Whether your team follows specific coding conventions or industry best practices, you can customize the Agent to suite your needs.

    We support three ways to customize AI Code Review Agent’s suggestions:

    1. Provide feedback on Bito-reported issues in pull requests, and the AI Code Review Agent automatically adapts by creating code review rules to prevent similar suggestions in the future.

    2. . Define rules through the dashboard in Bito Cloud and apply them to agent instances in your workspace, or add them directly to your repository using a .

    3. . Add guideline files (like .cursor/rules/*.mdc, .windsurf/rules/*.md, CLAUDE.md, GEMINI.md, or AGENTS.md) to your repository, and the AI Code Review Agent automatically uses them during pull request reviews to provide feedback aligned with your project's standards.

    hashtag
    1- Provide feedback on Bito-reported issues

    AI Code Review Agent refines its suggestions based on your feedback. When you provide negative feedback on Bito-reported issues in pull requests, the Agent automatically adapts by creating custom code review rules to prevent similar suggestions in the future.

    Depending on your Git platform, you can provide negative feedback in the following ways:

    • GitHub: Select the checkbox given in feedback question at the end of each Bito suggestion or leave a negative comment explaining the issue with the suggestion.

    • GitLab: React with negative emojis (e.g., thumbs down) or leave a negative comment explaining the issue with the suggestion.

    • Bitbucket: Provide manual review feedback by leaving a negative comment explaining the issue with the suggestion.

    The custom code review rules are displayed on the dashboard in Bito Cloud.

    These rules are applied at the repository level for the specific programming language.

    By default, newly generated custom code review rules are disabled. Once negative feedback for a specific rule reaches a threshold of 3, the rule is automatically enabled. You can also manually enable or disable these rules at any time using the toggle button in the Status column.

    circle-info

    Note: Providing a positive reaction emoji or comment has no effect and will not generate a new code review rule.

    After you provide negative feedback, Bito generates a new code review rule in your workspace. The next time the AI Code Review Agent reviews your pull requests, it will automatically filter out the unwanted suggestions.

    hashtag
    2- Create custom code review guidelines

    We understand that different development teams have unique needs. To accommodate these needs, we offer the ability to implement custom code review guidelines in Bito’s .

    Once you add guidelines, the agent will follow them when reviewing pull requests.

    You can manage guidelines in two ways:

    1. - Create, apply, and edit guidelines entirely in the web interface

    2. - Add custom guidelines directly to your repository for version-controlled, repository-specific configuration

    By enabling custom code review guidelines, Bito helps your team maintain consistency and improve code quality.

    circle-info

    Note: Custom review guidelines are available on the . Enabling this feature will upgrade your workspace to the Professional Plan.

    hashtag
    How to add a guideline

    hashtag
    Step 1: Open the Custom Guidelines tab

    • Sign in to .

    • Click in the sidebar.

    hashtag
    Step 2: Fill the form

    A. Manual setup

    1. Click Add guidelines button from the top right.

    2. Fill out:

      • Guideline name

    B. Use a Template

    1. Click Add guidelines button from the top right.

    2. Choose a template from the Use template dropdown menu.

    3. Review/edit fields as needed.

    hashtag
    Step 3: Apply to an Agent

    • After creating a guideline, you’ll see an Apply review guideline dropdown.

    • Select the Agent instance, then click Manage review guidelines to open its settings.

    circle-info

    To apply the guideline later: go to , find the Agent instance, click Settings, and manage guidelines there.

    hashtag
    Step 4: Save configuration

    On the Agent settings page, hit Save (top-right) to apply guideline changes.

    circle-info

    Note: Visit the tab to edit or delete any guideline.

    hashtag
    Managing review guidelines from agent settings

    Efficiently control which custom guidelines apply to your AI Code Review Agent through the Agent settings interface.

    1. Go to dashboard from the Bito Cloud sidebar.

    2. Click Settings next to the target agent instance.

    1. Navigate to the Custom Guidelines section. Here you can either create a new guideline or select from existing guidelines.

    1. Create a new guideline

      • If you click Create a new guideline button, you will see the same form as mentioned earlier where you can enter the details to create a review guideline.

    1. Or select an existing guideline

      • If you click Select from existing guidelines button, you will get a popup screen from where you can select from a list review guidelines you already created. Use checkboxes to enable or disable each guideline for the selected agent and then click Add selected.

    1. Once you’ve applied or adjusted guidelines, click the Save button in the top-right corner to confirm changes.

    hashtag
    FAQs

    hashtag
    What types of custom code review guidelines can be implemented?

    You can implement a wide range of custom code review guidelines, including:

    • Style and formatting guidelines

    • Security best practices

    • Performance optimization checks

    • Code complexity and maintainability standards

    hashtag
    Is "custom code review guidelines" feature available in Team Plan?

    No, this feature is available on the . Enabling the "custom code review guidelines" feature also upgrades your workspace to the Professional Plan.

    For more details on Professional Plan, visit our .

    hashtag
    3- Use project-specific guideline files

    The AI Code Review Agent can read guideline files directly from your repository and use them during code reviews. These are the same guideline files that AI coding assistants (like Cursor, Windsurf, and Claude Code) use to help developers write code.

    By adding these files to your repository, the agent automatically follows your project's specific coding standards, architecture patterns, and best practices when reviewing pull requests.

    hashtag
    Supported guideline files

    The AI Code Review Agent currently supports analyzing the following guideline files that are commonly used by different AI coding agents:

    CRA currently supports analyzing the following guideline files that are commonly used by different AI coding agents:

    hashtag
    How to organize your guideline files

    Multiple files in one directory

    You can split your guidelines across multiple files:

    For Windsurf, use the .md extension:

    Module-specific guidelines:

    Place guideline files in subdirectories to create rules for specific parts of your codebase:

    The agent finds all relevant guideline files based on which files changed in your pull request.

    circle-info

    Note: Rule precedence (where subdirectory rules override parent-level rules) will be added in a future release. Currently, the agent considers all applicable guideline files equally.

    hashtag
    How citations work

    Every relevant Bito comment includes a Citations section that links to the specific guideline that triggered the comment. The link takes you directly to the relevant line in your guideline file, making it easy to verify the feedback and understand why it was given.

    hashtag
    Example scenario

    Let's say you're building an application that integrates multiple LLM providers. Your guideline file specifies:

    • All providers must extend the BaseLLMProvider class

    • All providers must implement standard methods like generateResponse() and streamResponse()

    • New providers must be registered in the

    When someone submits a pull request to add a new provider, the agent can catch issues like:

    • The new provider doesn't extend the base class

    • Required methods are missing

    • The provider wasn't added to the configuration file

    Each comment links back to the specific guideline, so the developer knows exactly what needs to be fixed.

    hashtag
    Sample guideline file

    Here's an example AGENT.md file to help you get started:

    Language (select a specific programming language or select General if the guideline applies to all languages)
  • Custom Guidelines and Rules (enter your guidelines here)

  • Click Create guideline.

  • Click Create guideline.
  • etc.

  • config/providers.json
    file

    .cursor/rules/*.mdc

    Cursor IDE

    .windsurf/rules/*.md

    Windsurf IDE

    CLAUDE.md

    Claude Code

    GEMINI.md

    Gemini CLI

    AGENTS.md

    OpenAI CodeX, Cursor IDE

    Create custom code review guidelines
    Custom Guidelinesarrow-up-right
    .bito.yaml file
    Use project-specific guideline files
    Learned Rulesarrow-up-right
    AI Code Review Agent
    Through the Bito Cloud dashboardarrow-up-right
    Using a .bito.yaml file
    Professional Planarrow-up-right
    Visit pricing pagearrow-up-right
    Bito Cloudarrow-up-right
    Custom Guidelinesarrow-up-right
    Repositoriesarrow-up-right
    Custom Guidelinesarrow-up-right
    Repositoriesarrow-up-right
    Professional Planarrow-up-right
    Pricing Pagearrow-up-right
    .cursor/rules/project-overview.mdc
    .cursor/rules/architecture-principles.mdc
    .cursor/rules/security-standards.mdc
    .windsurf/rules/coding-standards.md
    .windsurf/rules/api-patterns.md
    .cursor/rules/global-standards.mdc
    providers/.cursor/rules/provider-implementation.mdc
    auth/.cursor/rules/authentication-rules.mdc
    # LLM Proxy Architecture & Design Document
    
    ## Document Overview
    
    ### Purpose
    This document serves as a coding guideline and technical reference for AI agents working with this codebase. It provides comprehensive information about the current architecture, design patterns, implementation details, and the rationale behind design decisions. AI agents should use this document to understand the existing code structure, maintain consistency when making modifications, and follow established patterns when extending functionality.
    
    ### What This Document Covers
    - **System Architecture**: High-level overview of components and their interactions
    - **Design Patterns**: Detailed explanation of the Factory Pattern implementation
    - **Component Design**: In-depth analysis of each system component
    - **Data Flow**: Request/response lifecycle through the system
    - **Design Decisions**: Rationale behind current architectural choices
    - **Implementation Details**: Code structure, conventions, and patterns in use
    
    ---
    
    ## Table of Contents
    1. [System Architecture](#system-architecture)
    2. [Design Patterns](#design-patterns)
    3. [Component Design](#component-design)
    4. [Data Flow](#data-flow)
    5. [Design Decisions](#design-decisions)
    6. [Error Handling Strategy](#error-handling-strategy)
    7. [Security Considerations](#security-considerations)
    8. [Coding Conventions](#coding-conventions)
    
    ---
    
    ## System Architecture
    
    ### High-Level Overview
    
    The LLM Proxy application follows a layered architecture with clear separation between the presentation layer (FastAPI), business logic layer (Provider implementations), and integration layer (external LLM APIs).
    
    ```
    ┌─────────────────────────────────────────────┐
    │           FastAPI Application               │
    │         (Presentation Layer)                │
    │   - Request validation (Pydantic)           │
    │   - Route handling (/chat endpoint)         │
    │   - Response formatting                     │
    └────────────────┬────────────────────────────┘
                     │
                     ▼
    ┌─────────────────────────────────────────────┐
    │          Provider Factory                   │
    │        (Abstraction Layer)                  │
    │   - Provider selection logic                │
    │   - Instance creation                       │
    └────────────────┬────────────────────────────┘
                     │
            ┌────────┴────────┐
            ▼                 ▼
    ┌──────────────┐   ┌──────────────┐
    │   OpenAI     │   │  Anthropic   │
    │   Provider   │   │   Provider   │
    │              │   │              │
    │ (Concrete    │   │ (Concrete    │
    │  Impl.)      │   │  Impl.)      │
    └──────┬───────┘   └──────┬───────┘
           │                  │
           ▼                  ▼
    ┌──────────────┐   ┌──────────────┐
    │  OpenAI API  │   │ Anthropic API│
    └──────────────┘   └──────────────┘
    ```
    
    ### Component Layers
    
    1. **Presentation Layer** (`main.py`)
       - Handles HTTP requests/responses
       - Validates input using Pydantic models
       - Manages API endpoints
    
    2. **Abstraction Layer** (`providers/factory.py`)
       - Implements Factory Pattern
       - Routes requests to appropriate providers
       - Decouples client code from concrete implementations
    
    3. **Business Logic Layer** (`providers/*.py`)
       - Abstract base class defines contract
       - Concrete providers implement LLM-specific logic
       - Handles API communication and response parsing
    
    4. **Integration Layer**
       - External API calls via httpx
       - Authentication management
       - Network error handling
    
    ---
    
    ## Design Patterns
    
    ### Factory Design Pattern
    
    The application implements the **Factory Design Pattern** to create provider instances without exposing creation logic to the client.
    
    #### Pattern Components
    
    1. **Abstract Product** (`LLMProvider`)
    ```python
    class LLMProvider(ABC):
        def __init__(self, model: str):
            self.model = model
        
        @abstractmethod
        def generate_response(self, prompt: str) -> str:
            pass
    ```
    
    **Purpose**: Defines the contract that all concrete providers must implement.
    
    2. **Concrete Products** (`OpenAIProvider`, `AnthropicProvider`)
    ```python
    class OpenAIProvider(LLMProvider):
        def generate_response(self, prompt: str) -> str:
            # OpenAI-specific implementation
            pass
    ```
    
    **Purpose**: Implement provider-specific logic while adhering to the base contract.
    
    3. **Factory** (`ProviderFactory`)
    ```python
    class ProviderFactory:
        @staticmethod
        def get_provider(provider_name: str, model: str) -> LLMProvider:
            providers = {
                "openai": OpenAIProvider,
                "anthropic": AnthropicProvider
            }
            return providers[provider_name.lower()](model)
    ```
    
    **Purpose**: Encapsulates provider instantiation logic.
    
    #### Benefits of This Pattern
    
    - **Loose Coupling**: Client code depends on abstractions, not concrete classes
    - **Open/Closed Principle**: Open for extension (new providers), closed for modification
    - **Single Responsibility**: Each provider handles only its specific implementation
    - **Testability**: Easy to mock providers for testing
    - **Scalability**: Adding new providers requires minimal changes
    
    ---
    
    ## Component Design
    
    ### 1. Base Provider (`providers/base.py`)
    
    **Responsibility**: Define the contract for all LLM providers
    
    **Key Design Decisions**:
    - Uses ABC (Abstract Base Class) to enforce implementation
    - Stores model name as instance variable for reuse
    - Single abstract method keeps interface simple
    
    **Design Rationale**:
    - Python's ABC ensures compile-time checking of implementations
    - Simple interface reduces cognitive load for implementers
    - Storing model allows for provider-specific model validation in future
    
    ### 2. OpenAI Provider (`providers/openai_provider.py`)
    
    **Responsibility**: Implement OpenAI Chat Completions API integration
    
    **Key Features**:
    - Environment-based API key management
    - Message format conversion (user prompt → OpenAI format)
    - Response parsing (extract content from choices)
    - Timeout handling (30 seconds)
    
    **API Contract**:
    ```
    POST https://api.openai.com/v1/chat/completions
    Headers: Authorization: Bearer <key>
    Body: {
      "model": "gpt-4",
      "messages": [{"role": "user", "content": "prompt"}]
    }
    ```
    
    **Error Handling**:
    - Validates API key presence on initialization
    - Catches HTTP errors and wraps with descriptive messages
    - Re-raises exceptions for upstream handling
    
    ### 3. Anthropic Provider (`providers/anthropic_provider.py`)
    
    **Responsibility**: Implement Anthropic Messages API integration
    
    **Key Features**:
    - Custom header format (x-api-key, anthropic-version)
    - Max tokens configuration (1024)
    - Content array response parsing
    
    **API Contract**:
    ```
    POST https://api.anthropic.com/v1/messages
    Headers: 
      x-api-key: <key>
      anthropic-version: 2023-06-01
    Body: {
      "model": "claude-3-sonnet",
      "max_tokens": 1024,
      "messages": [{"role": "user", "content": "prompt"}]
    }
    ```
    
    **Design Choices**:
    - Hard-coded max_tokens provides consistent behavior
    - Version header ensures API stability
    - Array access for content assumes single response
    
    ### 4. Provider Factory (`providers/factory.py`)
    
    **Responsibility**: Create provider instances based on string identifiers
    
    **Implementation Strategy**:
    - Dictionary-based mapping for O(1) lookup
    - Case-insensitive provider names
    - Descriptive error messages for invalid providers
    
    **Extensibility**:
    ```python
    # Adding new provider:
    providers = {
        "openai": OpenAIProvider,
        "anthropic": AnthropicProvider,
        "deepseek": DeepseekProvider,  # Just add here
    }
    ```
    
    ### 5. FastAPI Application (`main.py`)
    
    **Responsibility**: HTTP interface and request orchestration
    
    **Key Components**:
    
    1. **Request Model**:
    ```python
    class ChatRequest(BaseModel):
        provider: str
        model: str
        prompt: str
    ```
    - Leverages Pydantic for automatic validation
    - Clear field names match user expectations
    
    2. **Response Model**:
    ```python
    class ChatResponse(BaseModel):
        provider: str
        model: str
        response: str
    ```
    - Echoes input parameters for traceability
    - Returns plain text response
    
    3. **Endpoint Handler**:
    ```python
    @app.post("/chat", response_model=ChatResponse)
    async def chat(request: ChatRequest):
        provider = ProviderFactory.get_provider(request.provider, request.model)
        response_text = provider.generate_response(request.prompt)
        return ChatResponse(...)
    ```
    
    **Error Mapping**:
    - `ValueError` (invalid provider) → HTTP 400
    - Generic `Exception` (API errors) → HTTP 500
    
    ---
    
    ## Data Flow
    
    ### Request Lifecycle
    
    ```
    1. Client sends POST /chat
       ↓
    2. FastAPI receives request
       ↓
    3. Pydantic validates request body
       ↓
    4. ProviderFactory.get_provider() called
       ↓
    5. Factory returns concrete provider instance
       ↓
    6. provider.generate_response() called
       ↓
    7. Provider makes HTTP call to LLM API
       ↓
    8. Provider parses response
       ↓
    9. Response wrapped in ChatResponse model
       ↓
    10. JSON response sent to client
    ```
    
    ### Detailed Flow Example (OpenAI)
    
    ```python
    # Client Request
    POST /chat
    {
      "provider": "openai",
      "model": "gpt-4",
      "prompt": "Tell me a joke"
    }
    
    # Internal Processing
    1. Pydantic validates: ChatRequest object created
    2. Factory called: ProviderFactory.get_provider("openai", "gpt-4")
    3. OpenAIProvider instantiated with model="gpt-4"
    4. generate_response("Tell me a joke") called
    5. HTTP POST to OpenAI API:
       {
         "model": "gpt-4",
         "messages": [{"role": "user", "content": "Tell me a joke"}]
       }
    6. OpenAI responds with completion
    7. Extract: data["choices"][0]["message"]["content"]
    8. Return text to endpoint
    9. Wrap in ChatResponse
    
    # Client Response
    {
      "provider": "openai",
      "model": "gpt-4",
      "response": "Why did the chicken cross the road?..."
    }
    ```
    
    ---
    
    ## Design Decisions
    
    ### 1. Why Factory Pattern?
    
    **Decision**: Use Factory Pattern instead of simple if/else logic
    
    **Rationale**:
    - **Scalability**: Adding providers doesn't require modifying existing code
    - **Testability**: Easy to mock factory for unit tests
    - **Maintainability**: Provider logic isolated in separate classes
    - **Professional Standard**: Industry-recognized pattern for this use case
    
    **Alternative Considered**: Direct instantiation with if/else
    ```python
    # Rejected approach
    if provider == "openai":
        result = OpenAIProvider(model).generate_response(prompt)
    elif provider == "anthropic":
        result = AnthropicProvider(model).generate_response(prompt)
    ```
    **Why Rejected**: Violates Open/Closed Principle, harder to extend
    
    ### 2. Why httpx Over Official SDKs?
    
    **Decision**: Use httpx for HTTP calls instead of official provider SDKs
    
    **Rationale**:
    - **Minimal Dependencies**: Keeps requirements.txt small
    - **Unified Interface**: Single HTTP client for all providers
    - **Transparency**: Direct API calls are easier to debug
    - **Control**: Full control over request/response handling
    
    **Trade-offs**:
    - Less abstraction (must handle response parsing)
    - No built-in retry logic
    - Manual API version management
    
    ### 3. Synchronous vs Asynchronous
    
    **Decision**: Use synchronous HTTP calls with httpx.Client
    
    **Rationale**:
    - **Simplicity**: Easier to understand and debug
    - **Current Scale**: Single request doesn't benefit from async
    - **API Constraints**: LLM APIs are inherently blocking
    
    **Future Consideration**: Switch to async if supporting streaming responses
    
    ### 4. Error Handling Strategy
    
    **Decision**: Simple try/except with HTTP status code mapping
    
    **Rationale**:
    - **Simplicity**: Requirements specified basic error handling
    - **Client Clarity**: HTTP status codes are standard
    - **Debugging**: Error messages preserved in exceptions
    
    **Not Included** (but recommended for production):
    - Structured logging
    - Retry logic
    - Rate limiting
    - Circuit breakers
    
    ### 5. Environment Variables for API Keys
    
    **Decision**: Use environment variables instead of configuration files
    
    **Rationale**:
    - **Security**: Prevents accidental commit of credentials
    - **12-Factor App**: Follows best practices for configuration
    - **Flexibility**: Easy to change without code modification
    - **Cloud-Ready**: Works seamlessly with container orchestration
    
    
    ---
    
    ## Error Handling Strategy
    
    ### Current Implementation
    
    ```python
    try:
        provider = ProviderFactory.get_provider(request.provider, request.model)
        response_text = provider.generate_response(request.prompt)
        return ChatResponse(...)
    except ValueError as e:
        # Invalid provider name
        raise HTTPException(status_code=400, detail=str(e))
    except Exception as e:
        # API errors, network issues, etc.
        raise HTTPException(status_code=500, detail=str(e))
    ```
    
    ### Error Categories
    
    1. **Client Errors (400)**:
       - Invalid provider name
       - Unsupported model
       - Malformed request
    
    2. **Server Errors (500)**:
       - Missing API keys
       - Network timeouts
       - API errors (rate limits, service unavailable)
       - Response parsing failures
    
    
    ---
    
    ## Security Considerations
    
    ### Current Implementation
    
    1. **API Key Management**:
       - Stored in environment variables
       - Never logged or returned in responses
       - Validated on provider initialization
    
    2. **Request Validation**:
       - Pydantic models enforce type safety
       - No SQL injection risk (no database)
       - No command injection (no shell execution)
    
    ### Current Limitations
    
    1. **No Rate Limiting**: The application does not implement rate limiting
    2. **No Authentication**: Endpoints are publicly accessible
    3. **No Input Sanitization**: Prompt length and content are not validated beyond Pydantic type checking
    4. **No Retry Logic**: Failed API calls are not automatically retried
    
    ---
    
    ## Coding Conventions
    
    ### File Organization
    
    **Current Structure**:
    ```
    llm-proxy/
    ├── main.py                      # FastAPI application entry point
    ├── providers/                   # Provider package
    │   ├── __init__.py             # Package exports
    │   ├── base.py                 # Abstract base class
    │   ├── openai_provider.py      # OpenAI implementation
    │   ├── anthropic_provider.py   # Anthropic implementation
    │   └── factory.py              # Factory implementation
    ├── requirements.txt             # Python dependencies
    ├── .env.example                # Environment variable template
    └── README.md                   # User documentation
    ```
    
    ### Naming Conventions
    
    1. **Classes**: PascalCase (e.g., `LLMProvider`, `OpenAIProvider`)
    2. **Functions/Methods**: snake_case (e.g., `generate_response`, `get_provider`)
    3. **Constants**: UPPER_SNAKE_CASE (e.g., `OPENAI_API_KEY`)
    4. **Files**: snake_case (e.g., `openai_provider.py`)
    
    ### Code Patterns
    
    1. **Provider Implementation**:
       - Inherit from `LLMProvider`
       - Validate API key in `__init__`
       - Implement `generate_response(prompt: str) -> str`
       - Use httpx.Client with 30-second timeout
       - Wrap errors with descriptive messages
    
    2. **Error Handling**:
       - Use `try/except` blocks in provider implementations
       - Raise `ValueError` for missing API keys
       - Raise generic `Exception` with descriptive messages for API errors
       - Let FastAPI endpoint handle HTTP status code mapping
    
    3. **Environment Variables**:
       - Load with `os.getenv()`
       - Validate presence in provider `__init__`
       - Use pattern: `{PROVIDER}_API_KEY`
    
    4. **Type Hints**:
       - All methods should include type hints
       - Use Pydantic models for request/response validation
       - Return type explicitly stated
    
    ### Documentation Standards
    
    1. **Docstrings**: All classes and methods include docstrings
    2. **Comments**: Inline comments explain non-obvious logic
    3. **README**: User-facing documentation with examples
    
    ### Dependencies
    
    **Current Dependencies**:
    - `fastapi==0.109.0`: Web framework
    - `uvicorn[standard]==0.27.0`: ASGI server
    - `pydantic==2.5.3`: Data validation
    - `httpx==0.26.0`: HTTP client
    - `python-dotenv==1.0.0`: Environment variable management
    
    **Rationale**: Minimal, well-maintained dependencies that serve specific purposes.
    
    ---
    
    ## Summary
    
    This document captures the current state of the LLM Proxy application. When working with this codebase, AI agents should:
    
    1. **Follow the Factory Pattern**: All new providers must inherit from `LLMProvider` and be registered in `ProviderFactory`
    2. **Maintain Consistency**: Use the same error handling, timeout values, and code structure as existing providers
    3. **Respect Abstractions**: Keep provider-specific logic within provider classes
    4. **Update Documentation**: Any changes to architecture should be reflected in this document
    5. **Preserve Simplicity**: The design prioritizes simplicity and clarity over advanced features
    
    The architecture demonstrates clean separation of concerns through the Factory Design Pattern, making the codebase maintainable and understandable for both human developers and AI agents.