EbivAI for Visual Studio Code

EbivAI is the Visual Studio Code companion for ebivai.com. It connects the first folder in your open workspace to the EbivAI web app so you can share selected context and apply AI-assisted changes without moving your project out of VS Code.

Features

• Sign in, save multiple EbivAI accounts and switch between them.
• Connect the active local workspace to the EbivAI web app in real time.
• Package selected repository context with Repomix include and exclude patterns.
• Create, update, delete and revert files through EbivAI workspace workflows.
• Run requested project commands in selected workspace directories and return their output.
• Create and manage template-based projects, Git branches and built previews.
• Protect supported application messages with an end-to-end encrypted channel.

Requirements

• Visual Studio Code 1.100 or later.
• An EbivAI account and an internet connection to use the web app.
• An open local folder or workspace.
• Node.js and npm when packaging repository context with Repomix or running npm-based workflows.
• Git when using template projects or Git-based discard and checkout operations.

The Marketplace extension already contains the public service configuration required to connect to EbivAI.

Optional Workflow Tools

The Marketplace extension does not require environment files or manual service configuration.

• Git is required for template repositories, project branches and Git-based workspace operations.
• Node.js, npm and npx are required for Repomix and JavaScript project setup.
• Any executable referenced by a requested build command must be installed locally.

Workspace Behavior

• EbivAI operates on the first folder when a multi-root VS Code workspace is open.
• The web app initiates context, file, project and build operations; VS Code displays progress, errors and command output.
• File inventory requests skip common generated folders and are capped for very large workspaces.

Extension Settings

The extension does not currently add user-configurable VS Code settings. Sign-in, connection status and account switching are managed from the EbivAI activity bar view.

Known Issues

• Workspace operations require the EbivAI web app to be open with the same account.
• If the sidebar remains disconnected, reload the VS Code window and refresh the web app.
• Multi-root workspaces currently use only the first workspace folder.
• Large file inventories may be truncated and omit generated directories.

Release Notes

0.9.4

This README describes the capabilities available in EbivAI 0.9.4.

• Added a dedicated transparent monochrome PNG for the VS Code activity-bar and sidebar icon.

• Reliable Realtime reconnection and queued workspace responses.

• Correlated file deployment and revert operations.

• Server-provided, tier-aware Repomix packing limits.

• Template project branches, project checkout and built preview support.

Installation

1. Open the Extensions view in Visual Studio Code.
2. Search for EbivAI.
3. Select the extension published by ebivai.
4. Choose Install.

The Marketplace extension identifier is ebivai.ebivai.

After installation, open a local folder and select the EbivAI icon in the activity bar.

Getting Started

1. Open the local folder that you want EbivAI to use.
2. Select the EbivAI icon in the VS Code activity bar.
3. Sign in with your EbivAI email address and password.
4. Open ebivai.com and sign in with the same account.
5. Wait until the extension is shown as connected and encrypted.
6. Select the connected VS Code workspace in the EbivAI web app.

Keep VS Code and the EbivAI web app open while workspace operations are running.

Working with Your Workspace

Share repository context

Use the EbivAI web app to package workspace content with Repomix include and exclude patterns. Before transfer, the extension checks the packing limit for your account; oversized packing is not sent.

Apply and revert file changes

EbivAI can create, overwrite or delete files in the connected workspace. The web workflow can also send file contents that restore an earlier deployment.

Important: File operations are applied when the web app sends them. Commit or back up important work before deploying generated changes.

Run project commands

Build requests run locally in the workspace directories selected by the web app. Logs are returned to EbivAI and are also available from the VS Code Output panel under channels that may retain the legacy “Repochat” name.

Discard tracked working-tree changes

If EbivAI requests a discard-all operation, VS Code displays a confirmation dialog before running git checkout -- .. This affects tracked working-tree content, not untracked files or staged changes.

Template Projects and Previews

EbivAI can manage local projects through a Git-backed template repository.

• Creating a template repository asks you to select a parent folder and then runs the template setup commands locally.
• Each generated project is stored on a local project/<name> branch.
• Switching projects checks out the selected branch and refreshes the workspace files.
• A project with dist/index.html can upload its built dist directory for an EbivAI preview.

Warning: Project switching uses git reset --hard and git clean -fd. Commit or copy work you want to keep before switching projects. Preview files are uploaded to EbivAI.

Security

• Account sessions are stored using VS Code Secret Storage.
• After connecting, the extension negotiates an ECDH P-256 shared key and supports AES-256-GCM encrypted application messages.
• Connection coordination, including presence and the current workspace path, is sent separately through the EbivAI Realtime channel.
• Confirm that EbivAI reports the workspace as connected and encrypted before transferring source content.

Privacy and Safety

Depending on the workflow you start, the extension may send:

• The current workspace path for connection and workspace selection.
• Relative file paths, sizes and modification times for workspace inventory.
• Source content selected for Repomix packaging.
• Build command output and error logs.
• Files from a built dist directory when you explicitly request a project preview.

Only connect devices and browser sessions that you trust. Treat generated file operations and build commands as local code execution.

The extension does not upload the entire workspace automatically. Source content is transferred when you start a context-sharing or preview workflow from EbivAI.

For account and product information, visit ebivai.com.