Code0
Understand your codebase before you change it — with system-wide context for you and your coding agent.
Code0 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 Code0, AI figures things out while coding. With Code0, it figures things out first — and then codes.
Prerequisite
Claude Code
Code0 works with the Claude Code installation already available on your machine.
Before installing Code0, make sure:
- Claude Code is installed.
- The
claude command is available on your PATH.
- Claude Code is authenticated using your existing subscription or API credentials.
You can verify the installation by running:
claude
Code0 does not replace or modify your Claude credentials.
Installation
1. Install Code0
Install Code0 from the VS Code Marketplace or install the provided .vsix package.
After installation, open Code0 from the VS Code Activity Bar.
2. Open Code0
If your Frigga account is already associated with an organisation and its repositories are available to Code0, there is no additional setup required. You can start using Code0 immediately.
If Code0 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, Code0 will prepare it for use.
4. Wait for repository indexing if required
If the selected repository has not already been indexed, Code0 will index it before organisation-wide context becomes available.
Once indexing is complete, Code0 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 Code0
Open your repository and start working with Code0.
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.
Code0 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.
Code0 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.
Code0 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 Code0 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 Code0'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 Code0 workspace.
Plans & Tasks
Plan the change before execution begins.
Code0 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
Code0 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, Code0 skips unnecessary planning and tasks so the change can be handled directly.
Coffee Mode
Approve the plan once, then let Code0 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 Code0 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 Code0 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 Code0 |
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 Code0 panel.
5. Restart VS Code.
6. If the repository should already be available, contact support. |
| Code0 says my repository is still indexing |
1. Wait for indexing to complete.
2. Refresh the Code0 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. |
| Code0 cannot find Claude Code |
1. Confirm Claude Code is installed.
2. Open a terminal and run claude.
3. Confirm the claude binary is available on your PATH.
4. Restart VS Code after installing or updating Claude Code.
5. Reopen Code0 and start a new session. |
| Claude Code is installed, but Code0 still cannot detect it |
1. Run claude from the same environment used to launch VS Code.
2. Confirm there are no PATH differences between your terminal and VS Code.
3. Restart VS Code completely.
4. Re-authenticate Claude Code if required.
5. Start a new Code0 session. |
| Does Code0 include Claude Code? |
No. Code0 works with the Claude Code installation already configured on your machine. |
| Does Code0 use my Claude subscription or API key? |
Yes. Claude Code continues to use whichever credentials you have configured for it. Code0 does not replace or modify those credentials. |
| Can Code0 understand repositories that are not open locally? |
Yes. If a repository is connected and indexed by your organisation, Code0 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 Code0 without Claude Code? |
You can use Code0's repository and Git-oriented views, but agent workflows require a compatible Claude Code installation. |
| 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 Code0 panel.
4. Restart VS Code.
5. Check the code0 Output channel for errors. |
| Code0 is showing an unsupported version message |
1. Update Code0 to the latest available version.
2. Run code0: Check for Updates from the Command Palette.
3. Reload VS Code after the update.
4. If automatic updating fails, install the latest .vsix manually. |
| Code0 is not updating automatically |
1. Check the code0.autoUpdate setting.
2. Run code0: Check for Updates manually.
3. Confirm VS Code can access the Code0 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 Code0 panel.
3. Sign out of Frigga and authenticate again.
4. Restart VS Code.
5. Check the code0 Output channel for authentication errors.
6. Contact support if the issue persists. |
| Code0 is connected to the wrong organisation |
1. Sign out of Code0.
2. Sign in again with the correct Frigga account.
3. Select the intended organisation.
4. Reopen your repository.
5. Start a new Code0 session. |
| Where can I find Code0 logs? |
1. Open View → Output in VS Code.
2. Select code0 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 Code0 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. |
| Code0 is still not working |
1. Confirm you are on the latest Code0 version.
2. Restart VS Code.
3. Re-authenticate with Frigga.
4. Start a new Code0 session.
5. Check the code0 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 Code0 update behaviour: on, notify, or off. |
code0.backendUrl |
Overrides the default hosted Code0 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
Code0 checks for compatible updates automatically.
You can also run:
code0: Check for Updates
from the VS Code Command Palette.
When an update requires a reload, Code0 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 code0 output channel.
- Reproduce the problem.
- Include the relevant output when contacting support.
