Skip to content
| Marketplace
Sign in
Visual Studio Code>AI>Ebig AINew to Visual Studio Code? Get it now.
Ebig AI

Ebig AI

Ebig

|
2 installs
| (0) | Free
Ebig AI brings Ebig's AI-powered development capabilities into VS Code.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Ebig AI

Ebig AI brings Ebig's AI-powered development capabilities into VS Code.

Ask about the code in front of you, get a selection explained, and get a selection reviewed against the rules your own Ebig project holds — without leaving the editor.

Requires an Ebig account and an Ebig project. The extension is free; it is a client for the Ebig platform you already use.


What you get

Ebig AI Chat

An Ebig AI container in the Activity Bar with a Chat view. Ask a question, get an answer, keep the thread. The view shows when Ebig is working, lets you stop a running request, and shows exactly what is wrong when something fails.

The file you are in, its language and your current selection travel with the question, so you rarely have to paste code to be understood.

Explain Selection

Select code, right click → Ebig AI → Explain Selection.

You get what the code does, the role it plays, the logic step by step, the dependencies worth knowing, and any risk it carries. If something cannot be determined from the selection alone, you are told that instead of being given a guess.

Review Selection

Select code, right click → Ebig AI → Review Selection.

This is not a generic linter pass. The review is carried out against the rules and knowledge your Ebig project actually has — correctness, architecture, maintainability, security, performance, and UX where it applies. If a rule does not exist in your project, the review says so rather than inventing a standard to judge you against.

Project Context

Ebig answers inside a project. Ebig AI: Select Project sets which Ebig project this workspace belongs to, and the setting is stored per workspace — so opening a different customer's code does not carry the previous project's context with it.

Ebig AI: Select Agent lets you pin which Ebig agent answers. The list is read from your Ebig backend, and leaving it empty is the normal choice: Ebig decides which Skill applies, from your account, project and permissions.


Getting started

  1. Install the extension.
  2. Run Ebig AI: Login and sign in with your Ebig account.
  3. Set your project when asked, or run Ebig AI: Select Project.
  4. Open the Ebig AI icon in the Activity Bar and ask something.

Commands

Command What it does
Ebig AI: Open focus the Chat view
Ebig AI: Login sign in with your Ebig account
Ebig AI: Logout remove the credential from this machine
Ebig AI: Explain Selection explain the selected code
Ebig AI: Review Selection review the selected code
Ebig AI: Select Project choose the Ebig project for this workspace
Ebig AI: Select Agent choose which Ebig agent answers
Ebig AI: Settings open Ebig AI settings

Ebig authentication

Ebig AI uses your Ebig account. It does not create an account of its own and it does not hold a second set of credentials.

VS Code  →  Ebig login  →  Ebig account  →  access token  →  extension

Ebig AI: Login opens your Ebig login page and then asks for the access token, which is stored in VS Code SecretStorage — the same place VS Code keeps its own credentials. Ebig AI: Logout deletes it from this machine.

The token travels as Authorization: Bearer. Ebig verifies it; the extension never decodes, interprets or logs it.


Gateway-based architecture

Ebig AI is a client. It carries no model, no prompt, no Skill table, no review rules and no knowledge base. All of that lives in Ebig, and which Skill answers you is decided there — from your account, project and permissions.

VS Code
  └── Ebig AI extension
        ├── account · authentication
        ├── editor context
        ├── chat UI
        └── API client
               │
               ▼
        Ebig Gateway  ──►  Ebig AI  ──►  Skill · Rule · Knowledge

Every request goes through Ebig Gateway, which authenticates the caller and confirms project membership before anything reaches the AI service. There is no second route, and the extension has no way to reach around it.


Settings

Setting Default What it does
ebigAI.apiBaseUrl https://gateway.ebig.co Ebig Gateway base URL
ebigAI.loginUrl https://app.ebig.co/login where Login sends you
ebigAI.requestTimeoutMs 60000 give up on a request after this long
ebigAI.maxContextCharacters 8000 hard ceiling on editor text sent
ebigAI.projectId "" the Ebig project for this workspace
ebigAI.agent "" empty means Ebig chooses
ebigAI.sendOpenFileContext true send file name, language and selection

No setting holds a token, password or secret, and the build fails if one is ever added.


What leaves your machine

  • The file name, its language, and the text you selected. Nothing else.
  • Never your repository. No directory scanning, no file indexing, no background upload. Only what you are looking at, capped by maxContextCharacters and visibly marked when it had to be truncated.
  • File paths are relative. An absolute path names your machine and often your customer; the extension sends src/api/client.js, not /Users/you/work/customer-a/src/api/client.js.
  • Turn it off with ebigAI.sendOpenFileContext and only your typed question is sent.

Security

  • Your credential stays in SecretStorage. Not in settings, not in workspace state, not on disk, not in logs, and never inside the chat view.
  • The chat view cannot reach the network. Its content security policy declares connect-src 'none', so it physically cannot call out, and the credential is never handed to it.
  • The credential never appears in an error message, including when a failing server echoes it back.
  • AI output is inserted as text, never as HTML, behind a strict CSP with a fresh nonce for every render.

This version reads only

Ebig AI does not write to your files, does not run terminal commands, and does not execute anything the AI returns. It reads context, asks Ebig, and shows you the answer. You decide what to do with it.

This is enforced by the build, not by policy: the package fails to build if file-writing, terminal or code-execution APIs appear anywhere in the source.


Support

Questions and problems: contact@ebig.vn · ebig.co


License

See the LICENSE file included with this extension.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft