Skip to main content

Beezi AI IDE Extension

The Beezi IDE Extension provides the Continue in IDE workflow for supported VS Code-based editors. It allows users to open AI-generated implementation plans and generated code directly from Beezi notifications and workflow actions.

Supported editors include:

  • VS Code
  • Cursor
  • Windsurf

This workflow is designed to give you a seamless transition from Beezi chat interactions into your local development environment.

Pricing & Availability​

Beezi AI IDE Extension workflow is available as part of the Beezi product experience and does not require a separate Beezi add-on to open plans or generated code in a supported editor.

1. Installation & Configuration​

Prerequisites​

Before using Beezi AI IDE Extension workflow, make sure:

  • You have access to Beezi platform
  • You have a supported VS Code-based editor installed
  • Git is available in your local development environment if you want to open generated code branches

Note: A desktop installation of your supported editor is required. Browser-based editors such as vscode.dev are not supported.

Basic Setup​

Install the Beezi AI extension in your preferred supported editor:

  • VS Code — search for "Beezi AI" in the Extensions panel or install from the VS Code Marketplace
  • Cursor — search for "Beezi AI" in the Extensions panel (Cursor uses the OpenVSX registry)
  • Windsurf — search for "Beezi AI" in the Extensions panel (Windsurf uses the OpenVSX registry)

Sign in to Beezi platform in the browser.

Configure your IDE preference:

Organization-Level Setup (Tenant Admin):

  • A Tenant Admin or Tenant Owner configures which IDEs are approved for use in your organization
  • This creates an allowlist of supported editors (e.g., VS Code, Cursor, Windsurf)
  • Only approved IDEs will be available for users to select

Individual User Setup:

  • Each user selects their preferred IDE from the organization's approved list in Beezi user settings
  • Even if multiple IDEs are approved (e.g., Windsurf and VS Code), each user chooses only one as their default
  • This preference determines which editor opens when you click "Continue in IDE" or "Open in IDE" buttons

Example: If your Tenant Admin has approved Windsurf and VS Code, you can choose either Windsurf or VS Code as your personal preferred IDE — not both simultaneously.

Ensure your local machine is ready to open repositories for the projects you work on.

2. Features & Workflow​

Opening Implementation Plans​

When Beezi generates an implementation plan for a task, you can open it directly in your IDE from Slack or Microsoft Teams communication channel.

How the Flow Works

  1. Beezi generates the implementation plan for the task
  2. The plan is delivered through the relevant Beezi workflow, such as Slack or Microsoft Teams
  3. You click Open or Continue in IDE (IDE part will vary depending on your preferred IDE)
  4. Your preferred IDE receives a deep-link URI and brings itself into focus
  5. The extension creates a temporary local Markdown file and opens the implementation plan in the editor

Benefits of Opening Plans in IDE

Opening the plan in your IDE allows you to:

  • Review the proposed technical approach in a development-focused environment
  • Inspect file paths, architecture changes, and implementation scope more comfortably
  • Request plan changes through Beezi chat integrations before code generation continues after the plan is reviewed

This supports a controlled review step before AI-generated code is finalized.

Opening Generated Code​

When Beezi generates code for a task and creates a Pull Request or prepares a branch for review, you can open that result directly in your IDE.

How the Flow Works

  1. Beezi generates code for the selected task
  2. Beezi creates or references the relevant Git branch
  3. You click Open in IDE (IDE part will vary depending on your preferred IDE)
  4. The extension launches your preferred editor
  5. The target branch is checked out locally
  6. The relevant repository folder, or a specific path inside it, is opened in your editor

What This Enables

This workflow lets you:

  • Review generated changes locally before merging
  • Run your normal local validation and testing steps
  • Continue development manually when iteration is required
  • Move from AI-generated output into standard engineering review without switching tools repeatedly

3. Behavior Details​

Preferred IDE Detection​

Beezi uses your configured user preference (selected from your organization's approved IDE list) to decide which supported editor should handle the handoff.

This helps standardize the experience across teams that use different VS Code-based tools while respecting organizational policies.

Temporary File Handling​

Implementation plans are opened as temporary local Markdown files.

This means:

  • The plan is available for immediate review in your editor
  • The file is intended for local inspection rather than long-term source control storage
  • If you need to preserve it permanently, save or copy it into your project documentation intentionally

Git Branch Checkout​

For generated code, the extension works with the repository and branch selected by Beezi.

At a high level, the extension can:

  • Clone the repository if it does not exist locally
  • Fetch updates if a local copy already exists
  • Check out the requested branch
  • Open the repository root or a specific target path in the editor

This makes the handoff predictable and keeps the review focused on the branch Beezi prepared for the task.

Local Environment Interaction​

Beezi AI IDE Extension is intentionally lightweight. Its role is to open the correct local context so you can continue working.

In practice, this means:

  • Opening implementation plans as local Markdown files
  • Opening repositories and branches in your editor
  • Reusing existing local repositories when possible
  • Avoiding unnecessary context switching between chat and local development

4. Workflow Benefits​

Seamless Chat-to-IDE Handoff​

The extension connects Beezi notifications and workflow actions with your local editor.

This supports a practical flow:

  1. Review the request in Slack or Microsoft Teams
  2. Open the implementation plan for the task in the IDE
  3. Approve, revise, or discuss the approach
  4. Open the generated branch locally
  5. Validate, modify, and complete the work

Iterative Development Workflow​

Beezi AI IDE Extension is designed for iterative engineering work rather than one-click blind automation.

A typical loop looks like this:

Review → Modify → Re-run → Validate → Merge

This keeps engineers in control while still benefiting from Beezi automation.

5. Permissions & Local Security​

Beezi AI IDE Extension is focused on local handoff and repository access.

Depending on the workflow, it may:

  • Open local files and folders in your editor
  • Create a temporary local file for an implementation plan
  • Use your local Git environment to clone, fetch, and check out repositories and branches

This does not replace your normal engineering controls. You should still apply your standard review, validation, and repository security practices.

The extension also makes outbound network requests to Beezi to retrieve the necessary information for the handoff.

6. Important Information​

AI-Generated Content Disclaimer​

Beezi can generate plans, code, and Pull Requests, but the IDE handoff is intended to support human review rather than bypass it.

IMPORTANT

Please keep the following in mind:

  • Implementation plan files opened by the extension may be temporary local files.
  • Always review and validate generated code before merging or deploying it.
  • Make sure your local environment is properly configured before opening generated repositories or branches.
  • Beezi AI IDE Extension opens the requested working context, but engineering correctness, testing, and final approval remain your responsibility.

Best Practices​

  • Ensure your organization's Tenant Admin has approved the IDEs you want to use before attempting to set your preference
  • Select your preferred IDE from the approved list in Beezi user settings before using the workflow
  • Keep Git available and authenticated in your local environment
  • Review implementation plans for each task before approving code generation
  • Treat generated branches like any other development branch: inspect changes, run checks, and review carefully

7. Troubleshooting​

Clicking "Continue in IDE" or "Open in IDE" Does Nothing​

Symptoms: You click the button in Slack or Microsoft Teams and nothing happens — your editor does not open or come into focus.

Possible causes and fixes:

  • The Beezi AI extension is not installed in your editor. Install the extension by searching for "Beezi AI" in your editor's Extensions panel and restarting the editor.
  • No preferred IDE is set in your Beezi user settings. Go to your Beezi user settings and select a preferred IDE from the approved list. The button cannot route to an editor if no preference is configured.
  • Your preferred IDE is not approved by your organization. Contact your Tenant Admin to confirm which editors are on the approved list, and make sure your selected IDE matches one of them.
  • You are using a browser-based editor (e.g., vscode.dev). Browser-based editors are not supported. Install a desktop version of VS Code, Cursor, or Windsurf.
  • The deep-link URI is being blocked by your operating system or browser. Make sure your OS allows the editor's custom URI scheme (e.g., vscode://, cursor://, windsurf://). On some systems, you may need to confirm a browser prompt the first time.

The Editor Opens but No File or Branch Appears​

Symptoms: Your IDE comes into focus but the implementation plan or repository does not open inside it.

Possible causes and fixes:

  • The extension is installed but not active. Check that the Beezi AI extension is enabled (not disabled) in your editor's Extensions panel. Reload the editor window if needed.
  • For implementation plans: The temporary Markdown file may have failed to be created due to a permissions issue in the target directory. Check that your editor has write access to the local temp folder it uses.
  • For generated code: The repository may not be accessible from your local machine. Verify that your local Git is authenticated and that you have access to the repository Beezi is referencing.

Git Clone or Checkout Fails When Opening Generated Code​

Symptoms: The editor opens but the branch is not checked out, or you see a Git error.

Possible causes and fixes:

  • Git is not installed or not available in your system PATH. Run git --version in your terminal to confirm Git is accessible. If not, install Git and restart your editor.
  • You are not authenticated for the repository. Make sure your local Git credentials (SSH key or HTTPS token) are configured and valid for the repository Beezi is trying to open.
  • A local repository exists but is in a conflicting state (e.g., uncommitted changes on the current branch). Stash or commit your local changes before using the "Open in IDE" action.
  • The branch no longer exists or was renamed. Confirm that the branch Beezi prepared is still available in the remote repository.

My Preferred IDE Is Not in the List in Beezi Settings​

Symptoms: When you try to set your preferred IDE in Beezi user settings, the editor you want to use is not available to select.

Possible causes and fixes:

  • Your Tenant Admin has not approved that IDE. Only editors approved at the organization level appear in the user preference list. Contact your Tenant Admin or Tenant Owner to request that the editor be added to the allowlist.

The Extension Is Installed but the Button Label Shows the Wrong IDE Name​

Symptoms: The "Continue in IDE" button shows an editor name different from the one you use (e.g., it says "Open in VS Code" but you use Cursor).

Possible causes and fixes:

  • Your preferred IDE preference is set to a different editor. Go to Beezi user settings and update your preferred IDE to match the editor you actually use.

Implementation Plan File Is Missing After Closing the Editor​

Symptoms: You opened an implementation plan in your IDE, closed the editor or the file tab, and the file is no longer there.

Expected behavior: Implementation plans are opened as temporary local Markdown files. They are not saved to your project or source control automatically.

Fix: If you need to preserve a plan, save or copy it to a location in your project documentation before closing it.

8. Getting Help​

If you encounter issues with the IDE extension:

When contacting support, include:

  • Your preferred IDE (VS Code, Cursor, or Windsurf)
  • Operating system
  • Error messages or screenshots
  • Steps to reproduce the issue