Development

OpenAnalyst Development Guide

Welcome to the OpenAnalyst development guide! This document will help you set up your development environment and understand how to work with the codebase. Whether you're fixing bugs, adding features, or just exploring the code, this guide will get you started.

Prerequisites

Before you begin, make sure you have the following installed:

1. Git - For version control

2. Node.js (version [v20.19.2] recommended)

   For Windows: Using the Official Installer Go to the Node.js Downloads page https://nodejs.org/en/download Download the Windows Installer for version 20.19.2 (LTS recommended) Run the installer and follow the setup instructions After installation, open Command Prompt and verify:

   
   

    node -v
    npm -v

   
   

   For Mac:Using the Official Installer Go to the Node.js Downloads page - https://nodejs.org/en/download Download the macOS Installer for version 20.19.2 (LTS recommended) Open the downloaded file and follow the installation instructions After installation, verify:

   
   

   node -v
   npm -v

   
   

3. pnpm - Package manager (https://pnpm.io/)

   
   

    npm install -g pnpm

   
   

4. Visual Studio Code - Our recommended IDE for development https://code.visualstudio.com

Getting Started

Installation

1. Fork and Clone the Repository:

   • Fork the Repository:

     • Visit the OpenAnalyst GitHub repository

     • Click the "Fork" button in the top-right corner to create your own copy.

   • Clone Your Fork:

     git clone https://github.com/[YOUR-USERNAME]/OpenAnalyst.git
     cd OpenAnalyst

     
     

     Replace [YOUR-USERNAME] with your actual GitHub username.

2. Install dependencies:

   pnpm install

   
   

   This command will install dependencies for the main extension, webview UI, and e2e tests.

While not strictly necessary for running the extension, these extensions are recommended for development:

• ESLint - Integrates ESLint into VS Code.

• Prettier - Code formatter - Integrates Prettier into VS Code.

Project Structure

The project is organized into several key directories:

• src/ - Core extension code

  • core/ - Core functionality and tools

  • services/ - Service implementations

  • assets/ - Static assets like images and icons

• webview/ - Frontend UI code

• scripts/ - Utility scripts

Development Workflow

Running the Extension

To run the extension in development mode:

1. Press F5 (or select Run → Start Debugging) in VSCode

2. This will open a new VSCode window with OpenAnalyst loaded.

Hot Reloading

• Webview UI changes: Changes to the webview UI will appear immediately without restarting

• Core extension changes: Changes to the core extension code will automatically reload the extension host

In development mode (NODE_ENV="development"), changing the core code will trigger a workbench.action.reloadWindow command, so it is no longer necessary to manually start/stop the debugger and tasks.

Important: In production builds, when making changes to the core extension, you need to:

1. Stop the debugging process

2. Kill any npm tasks running in the background (see screenshot below)

3. Start debugging again

Building the Extension

To build a production-ready .vsix file:

pnpm build

This will:

1. Build the webview UI

2. Compile TypeScript

3. Bundle the extension

4. Create a .vsix file in the bin/ directory

Installing the Built Extension

To install your built extension:

code --install-extension "$(ls -1v bin/oa-code-*.vsix | tail -n1)"

Replace [version] with the current version number.

Testing

OpenAnalyst uses several types of tests to ensure quality:

Unit Tests

Run unit tests with:

pnpm test

This runs both extension and webview tests.

End-to-End Tests

For more details on E2E tests, see apps/vscode-e2e.

Linting and Type Checking

Ensure your code meets our quality standards:

pnpm lint          # Run ESLint
pnpm check-types   # Run TypeScript type checking

Git Hooks

This project uses Husky to manage Git hooks, which automate certain checks before commits and pushes. The hooks are located in the .husky/ directory.

Pre-commit Hook

Before a commit is finalized, the .husky/pre-commit hook runs:

1. Branch Check: Prevents committing directly to the main branch.

2. Type Generation: Runs pnpm --filter oa-code generate-types.

3. Type File Check: Ensures that any changes made to src/exports/roo-code.d.ts by the type generation are staged.

4. Linting: Runs lint-staged to lint and format staged files.

Pre-push Hook

Before changes are pushed to the remote repository, the .husky/pre-push hook runs:

1. Branch Check: Prevents pushing directly to the main branch.

2. Compilation: Runs pnpm run check-types to ensure typing is correct.

3. Changeset Check: Checks if a changeset file exists in .changeset/ and reminds you to create one using npm run changeset if necessary.

These hooks help maintain code quality and consistency. If you encounter issues with commits or pushes, check the output from these hooks for error messages.