CodeZero
Understand your codebase before you change it — with system-wide context for you and your coding agent.
CodeZero is an AI engineering workspace inside VS Code that helps developers and coding agents understand existing software before making changes.
Explore architecture, repositories, features, dependencies, Git history, and implementation context across your organisation — including repositories that are not checked out on your machine.
Then plan the change, review what needs to happen, and let your coding agent execute with that context already available.
Without CodeZero, AI figures things out while coding. With CodeZero, it figures things out first — and then codes.
Prerequisite
A coding agent
CodeZero works with a coding agent CLI already installed on your machine. Any one of these is enough:
| Agent |
Command |
Verify with |
| Claude Code |
claude |
claude |
| OpenAI Codex |
codex |
codex |
| GitHub Copilot CLI |
copilot |
copilot |
| Cursor |
cursor-agent |
cursor-agent |
Before installing CodeZero, make sure that at least one of them is:
- installed, and available on your
PATH;
- signed in, using your existing subscription or API credentials.
GitHub Copilot CLI additionally requires Node.js 20.19+ or 22.12+. CodeZero hides it on older runtimes rather than offering a provider that cannot start.
CodeZero does not include, replace or modify any of these, and never proxies a prompt. Every turn runs on your machine, through your own CLI, on your own subscription.
Install more than one and you can switch between them per conversation — see Choosing your agent below.
Installation
1. Install CodeZero
Install CodeZero from the VS Code Marketplace or install the provided .vsix package.
After installation, open CodeZero from the VS Code Activity Bar.
2. Open CodeZero
If your Frigga account is already associated with an organisation and its repositories are available to CodeZero, there is no additional setup required. You can start using CodeZero immediately.
If CodeZero cannot find an associated account or organisation, it will redirect you to the Frigga account setup flow.
3. Complete account setup if required
If you are redirected:
- Create an account or sign in with your Frigga account.
- Verify your email with the OTP sent to you.
- Select your organisation.
- Select the repository you want to work with.
Once the repository is selected, CodeZero will prepare it for use.
4. Wait for repository indexing if required
If the selected repository has not already been indexed, CodeZero will index it before organisation-wide context becomes available.
Once indexing is complete, CodeZero can understand relationships and implementation context beyond the repository currently open in VS Code.
If the repository is already indexed, you can continue immediately.
5. Start using CodeZero
Open your repository and start working with CodeZero.
Explore the system → understand a feature → plan a change → execute with your coding agent.
Features
Code Graph
Understand how modules, directories, dependencies, and repositories connect across the codebase.
CodeZero gives you a wider view of how the system is wired together, so you can understand the impact of a change before touching the implementation.
Feature Mapping
Start from a product feature and trace how it is implemented through the codebase.
Follow the repositories, files, dependencies, and components involved in the feature without manually piecing the flow together across projects.
Git Workspace
Work with your repository history and everyday Git operations from one visual workspace.
CodeZero brings together:
- Commit and branch history
- Working-tree changes
- Branches, tags, and stashes
- Diff, blame, and file history
- Commit inspection and comparison
- Fetch, pull, and push
- Branch checkout and management
- Merge, rebase, and reset actions
- Stash creation, apply, pop, and drop
- Merge and conflict-resolution workflows
- Drag-and-merge directly from the graph
- One-click access to common Git actions
Work with Git visually, inspect history, move between branches, and run common Git operations without constantly dropping back to the terminal.
Multi-Repo Context & Workspaces
Work across multiple repositories from the same VS Code window.
CodeZero keeps different repository chats and workstreams separate while still giving you access to organisation-wide indexed context.
That means you can work in one repository, open another conversation for a different repository, and still let CodeZero understand relevant code elsewhere in the system without requiring every repository to be checked out locally.
Context-Aware Chat
Ask questions about your codebase with CodeZero's repository context already available.
Instead of repeatedly explaining where things live or manually attaching files, use Chat to investigate implementation details, understand relationships, and reason about code with wider system context.
Each repository can maintain its own conversation inside the same CodeZero workspace.
Choosing your agent
Every chat names the agent answering it, in the header beside the conversation title. If more than one CLI is installed, open that menu to switch.
Switching happens per conversation, at a turn boundary — not globally, and never mid-turn. The transcript stays on screen and the conversation's context is carried across, so a chat that started on one agent can continue on another without being re-explained. Each agent keeps its own native session underneath, so switching away and back does not discard its history.
The menu also shows agents CodeZero could not find, marked as such, so "installed but not detected" is visible rather than silent.
Plans & Tasks
Plan the change before execution begins.
CodeZero can turn a request into a structured implementation plan, break it into tasks and subtasks, and keep progress visible while the agent works.
Review the approach first, then follow the work from plan to execution.
Auto Mode
CodeZero adapts the workflow to the size of the change.
For larger features, Auto Mode creates a structured implementation plan first. You review and approve the plan before execution begins.
For smaller changes, CodeZero skips unnecessary planning and tasks so the change can be handled directly.
Coffee Mode
Approve the plan once, then let CodeZero continue through the work without asking for additional approvals at every step.
Coffee Mode is designed for longer, already-reviewed workflows where you want the agent to keep executing the approved plan with minimal interruption.
How CodeZero Works
Understand
Explore the system, feature implementation, dependencies, repository structure, and history.
Plan
Define what needs to change and review the implementation approach before code is written.
Build
Let your coding agent work with the relevant system context already available.
Understand → Plan → Build
FAQ & Troubleshooting
If the table below does not resolve your issue, contact hello@frigga.cloud.
| Issue |
Troubleshooting Steps |
| I signed in, but I cannot see my organisation |
1. Confirm you are signed in with the correct Frigga account.
2. Confirm your account has CodeZero access.
3. Confirm you have been added to the correct organisation.
4. Sign out and sign in again.
5. Restart VS Code.
6. If the organisation is still missing, contact hello@frigga.cloud. |
| My repository is not appearing in CodeZero |
1. Confirm you are signed in to the correct organisation.
2. Confirm the repository has been connected to your organisation.
3. Confirm repository indexing has completed.
4. Refresh the CodeZero panel.
5. Restart VS Code.
6. If the repository should already be available, contact support. |
| CodeZero says my repository is still indexing |
1. Wait for indexing to complete.
2. Refresh the CodeZero panel after indexing finishes.
3. Reopen the repository if the status does not update.
4. Restart VS Code if the repository remains stuck.
5. Contact support if indexing does not complete. |
| CodeZero cannot find my coding agent |
1. Confirm the CLI is installed — claude, codex, copilot or cursor-agent.
2. Open a terminal and run it.
3. Confirm the binary is available on your PATH.
4. Restart VS Code after installing or updating it.
5. Reopen CodeZero and open the agent menu in the chat header — it lists every agent CodeZero looked for and which ones it found. |
| The CLI is installed, but CodeZero still cannot detect it |
1. Run the command from the same environment used to launch VS Code — a VS Code started from a desktop icon can have a different PATH than your terminal.
2. Open the agent menu in the chat header; opening it forces a fresh scan.
3. Restart VS Code completely.
4. Re-authenticate the CLI if required.
5. If it is installed somewhere unusual, contact support — CodeZero checks PATH, your login shell, and the usual install locations. |
| An agent shows "sign-in required" |
The CLI was found but has no valid login. Run its own login command in a terminal — claude, codex login, copilot login or cursor-agent login — then reopen the menu. CodeZero never holds these credentials. |
| The agent menu will not open |
Update CodeZero to the latest version. Earlier versions used a system-drawn menu that could fail to appear on Linux desktops running Wayland. |
| Does CodeZero include a coding agent? |
No. CodeZero works with whichever supported CLI is already configured on your machine. |
| Does CodeZero use my subscription or API key? |
Yes. Each agent continues to use whichever credentials you have configured for it, and every turn runs on your machine. CodeZero does not proxy prompts and does not replace or modify those credentials. |
| Can I use more than one agent? |
Yes. Install more than one CLI and each conversation can choose its own, switching between turns while keeping the conversation's context. |
| Can CodeZero understand repositories that are not open locally? |
Yes. If a repository is connected and indexed by your organisation, CodeZero can use its context even if that repository is not currently checked out on your machine. |
| The agent cannot find context from another repository |
1. Confirm the repository is connected to the same organisation.
2. Confirm indexing has completed.
3. Confirm you are working in the correct organisation.
4. Start a new agent session.
5. Retry the request with the relevant feature, service, or repository named explicitly.
6. Contact support if the repository is indexed but still unavailable. |
| Can I use CodeZero without a coding agent? |
You can use CodeZero's repository and Git-oriented views, but agent workflows require at least one supported CLI to be installed. |
| Git history, diff, or blame is not displaying correctly |
1. Confirm the folder open in VS Code is a Git repository.
2. Confirm the repository has a valid Git remote and history.
3. Refresh the CodeZero panel.
4. Restart VS Code.
5. Check the CodeZero Output channel for errors. |
| CodeZero is showing an unsupported version message |
1. Update CodeZero to the latest available version.
2. Run CodeZero: Check for Updates from the Command Palette.
3. Reload VS Code after the update.
4. If automatic updating fails, install the latest .vsix manually. |
| CodeZero is not updating automatically |
1. Check the code0.autoUpdate setting.
2. Run CodeZero: Check for Updates manually.
3. Confirm VS Code can access the CodeZero update endpoint.
4. Restart VS Code.
5. Install the latest .vsix manually if required. |
| Sign-in keeps failing or returning me to the login screen |
1. Confirm your internet connection is active.
2. Retry sign-in from the CodeZero panel.
3. Sign out of Frigga and authenticate again.
4. Restart VS Code.
5. Check the CodeZero Output channel for authentication errors.
6. Contact support if the issue persists. |
| CodeZero is connected to the wrong organisation |
1. Sign out of CodeZero.
2. Sign in again with the correct Frigga account.
3. Select the intended organisation.
4. Reopen your repository.
5. Start a new CodeZero session. |
| Where can I find CodeZero logs? |
1. Open View → Output in VS Code.
2. Select CodeZero from the output channel dropdown.
3. Reproduce the issue.
4. Include the relevant output when contacting support. |
| I am using a local or self-hosted CodeZero deployment |
Confirm that code0.backendUrl, code0.identityUrl, and code0.accountsUrl point to the correct endpoints for your environment. Restart VS Code after changing these settings. |
| CodeZero is still not working |
1. Confirm you are on the latest CodeZero version.
2. Restart VS Code.
3. Re-authenticate with Frigga.
4. Start a new CodeZero session.
5. Check the CodeZero Output channel.
6. Contact hello@frigga.cloud with the issue and relevant logs. |
Advanced Configuration
Most users do not need to change these settings.
| Setting |
Description |
code0.autoUpdate |
Controls CodeZero update behaviour: on, notify, or off. |
code0.backendUrl |
Overrides the default hosted CodeZero backend for local or self-hosted environments. |
code0.identityUrl |
Overrides the default Frigga identity service. |
code0.accountsUrl |
Overrides the default Frigga sign-in page. |
Updating
CodeZero checks for compatible updates automatically.
You can also run:
CodeZero: Check for Updates
from the VS Code Command Palette.
When an update requires a reload, CodeZero will prompt you to reload VS Code.
Support
Need help?
Email hello@frigga.cloud.
If you are reporting an extension issue:
- Open View → Output.
- Select the CodeZero output channel.
- Reproduce the problem.
- Include the relevant output when contacting support.
