OCORVIXCODE · ACADEMY Open OrvixCode
ORVIXCODE · FULL LEARNING SYSTEM

OrvixCode Academy

Master OrvixCode from first launch to professional repository workflows. Learn by reading, practicing, testing and finishing real projects.

View full curriculum Docs
42Lessons
8Paths
14+Hours
0Completed

Academy Dashboard

0%

Progress is stored locally in your browser. No account is required. Tip: press Ctrl/⌘ + K to search.

Overview

Inside this academy

Learn by doing

0142 localized reference lessons

What you will learn + Practice lab

028 structured learning paths

Follow the full curriculum or focus on the skill area you need today.

03Practice labs for every lesson

Use the lesson in a real OrvixCode workspace instead of only reading it.

04Persistent local progress

Progress is stored locally in your browser. No account is required.

05Real project capstones

Finish the academy with larger projects that combine multiple OrvixCode skills.

06Mobile + RTL friendly

Desktop · Mobile · RTL · Search · Local progress

Skill map

Choose a learning path

Follow the full curriculum or focus on the skill area you need today.

No lessons match your search or filter.
Level · Beginner

01 · Foundations

Install OrvixCode, understand the interface and build a reliable first-project workflow.

WorkspaceProjectsChat
1 OverviewOrvixCode combines project context, an advanced code editor, AI chat, a built-in terminal, local and cloud AI models, and multi-file development workflows in one Windows desktop app. Beginner14 min⌄

OrvixCode combines project context, an advanced code editor, AI chat, a built-in terminal, local and cloud AI models, and multi-file development workflows in one Windows desktop app.

OrvixCode is a Windows desktop development environment that connects AI chat with real projects, files, editor workflows, and a built-in terminal.

You can open or create projects, analyze and edit code with AI, run multi-file project tasks, and choose between supported local or cloud models.

Core capabilities

  • Planning and continuation for long-code and large-project tasks.
  • Multi-file project generation with dependency-aware manifest validation.
  • Syntax-highlighted code editor, Problems area, AI Fix, and inline AI editing.
  • Built-in terminal with AI-assisted terminal error analysis.
  • Automatic installation and retry for missing Python packages using the same interpreter.
  • Explain, edit, and fix selected code.
  • Customizable keyboard shortcuts, response stopping, and Markdown formatting while streaming.
  • Local Ollama models, cloud providers, Combo Mode, and Visual Studio Code integration.
You stay in controlAI-prepared file changes retain preview, permission, apply, backup, and undo workflows.
What you will learn 01Workspace · Overview
What you will learn 02Projects · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “Overview” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
2 System requirementsComponent Requirement / recommendation Operating system Windows 10 or Windows 11 Architecture 64-bit Internet Required for cloud AI providers and downloading local models. Previous Beginner16 min⌄

Component Requirement / recommendation Operating system Windows 10 or Windows 11 Architecture 64-bit Internet Required for cloud AI providers and downloading local models. Previous

ComponentRequirement / recommendation
Operating systemWindows 10 or Windows 11
Architecture64-bit
InternetRequired for cloud AI providers and downloading local models. Previously downloaded Ollama models can run locally without internet access.
RAMThe desktop app has modest requirements; local AI memory use depends heavily on model size and context length.
GPU / VRAMOptional for local models, but a compatible GPU can significantly improve performance.
DiskAllow space for the app, projects, backups, and downloaded local models.
VS CodeOnly required if you use the VS Code integration.
Local AI noteModel speed and compatibility depend on RAM, VRAM, GPU support, free disk space, and context size. Very large models may not fit on lower-memory systems.
What you will learn 01Workspace · System requirements
What you will learn 02Projects · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “System requirements” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
3 InstallationDownload the current Windows installer from the official OrvixCode product page. Beginner18 min⌄

Download the current Windows installer from the official OrvixCode product page.

Download the current Windows installer from the official OrvixCode product page.

Official download
https://orvixcode.orvixgames.com/download.php?lang=en-us
  1. Download the installerOpen the OrvixCode product page and download the current Windows build.
  2. Run SetupIf Windows shows a security prompt, verify the source before continuing.
  3. Choose the install locationKeep the default path or select another supported location.
  4. Enable VS Code integrationIf Setup offers to install or update the extension, keep the option enabled if you use VS Code.
  5. Finish installationLaunch OrvixCode from the desktop shortcut or Start menu.
What you will learn 01Workspace · Installation
What you will learn 02Projects · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “Installation” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
4 First launchOn first launch, OrvixCode may show setup preferences such as application language, workspace location, and basic behavior. Beginner12 min⌄

On first launch, OrvixCode may show setup preferences such as application language, workspace location, and basic behavior.

On first launch, OrvixCode may show setup preferences such as application language, workspace location, and basic behavior.

After setup, the main workspace lets you add a project, start a new chat, or configure AI providers and local models.

What you will learn 01Workspace · First launch
What you will learn 02Projects · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “First launch” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
5 InterfaceThe left side gives quick access to projects, chats, tools, and main application areas. It can be collapsed when you need more editor space. Beginner14 min⌄

The left side gives quick access to projects, chats, tools, and main application areas. It can be collapsed when you need more editor space.

Left navigation

The left side gives quick access to projects, chats, tools, and main application areas. It can be collapsed when you need more editor space.

Tabs

Keep multiple chats or workspaces open at the same time. Closing a tab does not necessarily delete the saved chat.

AI chat area

Manage your prompt, active model, and project context here. Responses can also show affected files and the state of proposed edits.

What you will learn 01Workspace · Interface
What you will learn 02Projects · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “Interface” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
6 ProjectsProjects are the foundation of OrvixCode context. You can open existing folders, and project-generation requests can create a workspace automatically when no real project is selected. Beginner16 min⌄

Projects are the foundation of OrvixCode context. You can open existing folders, and project-generation requests can create a workspace automatically when no real project is selected.

OrvixCode projects are based on local folders. When a folder is selected as the workspace, AI can use task-relevant project context.

New or existing project

  • Create a workspace with New Project.
  • Attach an existing source-code folder directly.
  • Use + New project from the project selector below the message box.

Automatic project creation for AI tasks

If you ask OrvixCode to generate a project and no real project is selected, it can create a project folder and add it to Projects. Duplicate names receive suffixes such as Project 2 or Project 3.

File planning for large projects

Large tasks are split into subsystems and files instead of being compressed into a few oversized files. Imports and dependency contracts are checked while generation proceeds; the manifest can expand when a missing local module is discovered.

Context scopeVery large folders are not sent in full with every request. OrvixCode tries to select the files and sections relevant to the task.
What you will learn 01Workspace · Projects
What you will learn 02Projects · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “Projects” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
7 AI chatAI chat supports project questions, code generation, editing, and error analysis, including attachment context, response stopping, and Markdown formatting during streaming. Beginner18 min⌄

AI chat supports project questions, code generation, editing, and error analysis, including attachment context, response stopping, and Markdown formatting during streaming.

Use AI chat to ask project questions, analyze errors, generate code, edit files, or request architecture suggestions.

File and selected-code context

Use the + menu in the composer to attach files. Attached text/code files are explicitly exposed to the AI as available context, and selected-code explanation requests are kept separate from project-generation intent.

Stop a response

While AI is responding, the send control changes to ■ Stop. Stopping cancels continuation and large-project generation steps and prevents late output from being appended.

Streaming view

Markdown and code blocks are formatted while the response streams instead of only after completion. Long user messages preserve line breaks and code blocks.

Prompt example

Example
Review the authentication system in this project.
Find possible failures during session refresh.
If needed, edit the relevant files and explain the changes.
What you will learn 01Workspace · AI chat
What you will learn 02Projects · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “AI chat” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →

Track checkpoint · 01 · Foundations

Before moving on, complete these tasks without relying on guesswork.

  • Explain the key ideas of this path in your own words.
  • Complete one real task using the workflow from this path.
  • Verify your result with evidence such as a diff, test, build or terminal output.
Level · Intermediate

02 · AI Coding Workflow

Use Ask, Edit, Agent, the editor, terminal and undo flow without losing control of changes.

AskEditAgentTerminal
8 Ask / Edit / AgentQuestions, explanations, analysis, and edit requests when appropriate. Intermediate14 min⌄

Questions, explanations, analysis, and edit requests when appropriate.

Ask

Questions, explanations, analysis, and edit requests when appropriate.

Edit

Focused changes to the active file. Best for single-file tasks.

Agent

Multi-file work, new files, and broader project-level tasks.

Editing from Ask

Ask is not limited to explanations. When your prompt clearly requests a code change, OrvixCode can prepare an actionable edit package.

Example“Fix the error handling in this file and remove unnecessary duplication.” can trigger an analysis + edit flow.
What you will learn 01Ask · Ask / Edit / Agent
What you will learn 02Edit · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “Ask / Edit / Agent” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
9 File editingAI edits can be more than text in a chat message. OrvixCode can turn a response into a change package that can be reviewed and applied to project files. Intermediate16 min⌄

AI edits can be more than text in a chat message. OrvixCode can turn a response into a change package that can be reviewed and applied to project files.

AI edits can be more than text in a chat message. OrvixCode can turn a response into a change package that can be reviewed and applied to project files.

1. RequestYou describe the change.
2. AnalysisAI reviews relevant context.
3. PackageChanges become an applicable edit.
4. ApplyThe change is written to the editor or disk.

Creating new files

Agent tasks can create new files when the requested feature or refactor requires them.

What you will learn 01Ask · File editing
What you will learn 02Edit · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “File editing” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
10 Code editor and AI toolsThe OrvixCode editor combines syntax highlighting, the Problems area, selected-code editing, AI Fix, and undo/redo in the same workspace. Intermediate18 min⌄

The OrvixCode editor combines syntax highlighting, the Problems area, selected-code editing, AI Fix, and undo/redo in the same workspace.

The 1.2.0 code editor keeps the existing editing surface while adding syntax highlighting and error/warning layers.

Syntax and Problems

  • Syntax highlighting for common languages.
  • Parse/syntax errors can appear in red; warnings and some missing-module cases in yellow.
  • Problematic code ranges can be underlined directly in the editor.

AI editing

  • ★ Fix with AI: Fixes the open file from the Problems area without auto-saving.
  • Edit with AI…: Sends only the selected text range plus your instruction and splices the replacement back into that range.
  • Explain selected code with OrvixCode: Sends the selection as explanation context.

During inline AI editing, the selected range can temporarily blur and show ★ AI editing…. AI editor changes also participate in Ctrl+Z / Ctrl+Y history.

Save controlAI Fix and inline edits can update the editor, but they do not auto-save; writing to disk remains under your control.
What you will learn 01Ask · Code editor and AI tools
What you will learn 02Edit · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “Code editor and AI tools” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
11 Python run and dependenciesThe Python run flow prefers the project venv, can install a missing external module with the same interpreter, retry execution, and send run errors to AI Fix. Intermediate20 min⌄

The Python run flow prefers the project venv, can install a missing external module with the same interpreter, retry execution, and send run errors to AI Fix.

When running Python files, OrvixCode prefers the project .venv or venv interpreter when available.

Automatic missing-package install

If execution raises ModuleNotFoundError and the missing name is not a local project module, OrvixCode can try pip with the same interpreter and then retry the file.

Some import names map to package names, including cv2 → opencv-python, PIL → Pillow, yaml → PyYAML, and sklearn → scikit-learn.

Fix with AI

If the run fails, ★ Fix with AI can send the error, active file, and relevant context to the AI.

Package installationAutomatic installation applies to Python packages and may require network/pip access. Local project modules are not treated as pip packages.
What you will learn 01Ask · Python run and dependencies
What you will learn 02Edit · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “Python run and dependencies” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
12 Built-in terminalThe OrvixCode terminal supports normal command execution, persistent working directory, command history, and AI-assisted terminal error fixing. Intermediate14 min⌄

The OrvixCode terminal supports normal command execution, persistent working directory, command history, and AI-assisted terminal error fixing.

Use the built-in terminal like a normal command terminal.

  • cd changes persist for the terminal session.
  • clear / cls clears the output.
  • Command history is stored for the session; use Up/Down to revisit commands.

Fix terminal errors with AI

When a command fails, ★ Fix with AI can send the last command, error output, and the open file when relevant.

Command controlThe terminal does not execute unsolicited commands; only user-entered commands are run.
What you will learn 01Ask · Built-in terminal
What you will learn 02Edit · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “Built-in terminal” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
13 Diff / Apply / UndoOrvixCode tracks the state of AI edit packages. Intermediate16 min⌄

OrvixCode tracks the state of AI edit packages.

OrvixCode tracks the state of AI edit packages.

  • Diff / Preview: compare the proposed or applied change.
  • Apply: write the prepared change to the file.
  • Applied: keep a stable state for a change that was already written.
  • Undo: revert the latest supported AI change.
Auto ApplyIf automatic apply is enabled, the edit may already be on disk. In that case the UI should show the package as applied.
What you will learn 01Ask · Diff / Apply / Undo
What you will learn 02Edit · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “Diff / Apply / Undo” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →

Track checkpoint · 02 · AI Coding Workflow

Before moving on, complete these tasks without relying on guesswork.

  • Explain the key ideas of this path in your own words.
  • Complete one real task using the workflow from this path.
  • Verify your result with evidence such as a diff, test, build or terminal output.
Level · Intermediate

03 · VS Code Integration

Bring OrvixCode into VS Code and learn selection, context, Agent and synchronization workflows.

VS CodeSelectionContext
14 VS Code integrationOrvixCode provides a Visual Studio Code extension that opens an OrvixCode panel in the Activity Bar and brings the desktop app's cloud and local AI workflows into the editor. Main capabilities AI chat panel with Ask, Edit, and Agent modes Cloud and local Ollama model selection Active-file Intermediate18 min⌄

OrvixCode provides a Visual Studio Code extension that opens an OrvixCode panel in the Activity Bar and brings the desktop app's cloud and local AI workflows into the editor. Main capabilities AI chat panel with Ask, Edit, and Agent modes Cloud and local Ollama model selection Active-file

OrvixCode provides a Visual Studio Code extension that opens an OrvixCode panel in the Activity Bar and brings the desktop app's cloud and local AI workflows into the editor.

Main capabilities

  • AI chat panel with Ask, Edit, and Agent modes
  • Cloud and local Ollama model selection
  • Active-file and selected-code context
  • Context-menu actions for selected code
  • User-approved file edits, diff preview, and undo
  • Model connection and error status
  • Optional chat synchronization with the desktop app
Context isolationSimple greetings and unrelated messages do not need active-file or workspace context. Code tasks can attach the context again when required.

Quick AI actions

The extension quick actions now go beyond explanation and basic fixes:

  • Explain code
  • Fix errors
  • Refactor
  • Review project
  • Generate tests
  • Code review
  • Generate documentation
  • Suggest performance improvements
When the desktop app is missingThe extension can offer to open the download page, let you select the OrvixCode executable, or postpone setup.
What you will learn 01VS Code · VS Code integration
What you will learn 02Selection · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “VS Code integration” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
15 Install the VS Code extensionInstall OrvixCode from the Visual Studio Code Extensions view. Regular users do not need to manage VSIX packages manually. Intermediate20 min⌄

Install OrvixCode from the Visual Studio Code Extensions view. Regular users do not need to manage VSIX packages manually.

Install OrvixCode from the Visual Studio Code Extensions view. Regular users do not need to manage VSIX packages manually.

  1. Open ExtensionsUse the Extensions icon or Ctrl+Shift+X.
  2. Search for OrvixCodeUse the Marketplace search box.
  3. Install the extensionVerify the publisher shown for OrvixCode and choose Install.
  4. Open the panelSelect the OrvixCode icon from the Activity Bar.
  5. Connect the desktop appMake sure OrvixCode desktop is installed for supported AI workflows.
After installationIf the panel is missing, run Developer: Reload Window or restart VS Code.
What you will learn 01VS Code · Install the VS Code extension
What you will learn 02Selection · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “Install the VS Code extension” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
16 Context menu commandsSelect a code block in the editor and use the OrvixCode commands from the context menu. Intermediate14 min⌄

Select a code block in the editor and use the OrvixCode commands from the context menu.

Select a code block in the editor and use the OrvixCode commands from the context menu.

CommandWhat it does
Ask AI about selected codeSends the selection to the OrvixCode panel with chat context.
Explain selected codeExplains behavior, important flow, and possible issues.
Fix selected codeCan prepare an applicable correction for detected problems.
RefactorAims to simplify or reorganize code while preserving behavior.
What you will learn 01VS Code · Context menu commands
What you will learn 02Selection · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “Context menu commands” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
17 VS Code Agent modeAgent mode is designed for tasks that are not limited to one file. It can coordinate work across the open workspace. Intermediate16 min⌄

Agent mode is designed for tasks that are not limited to one file. It can coordinate work across the open workspace.

Agent mode is designed for tasks that are not limited to one file. It can coordinate work across the open workspace.

Good Agent tasks

  • Add a new feature
  • Fix a bug that spans multiple files
  • Create a module or supporting files
  • Refactor project structure
  • Coordinate HTML, CSS, and JavaScript changes
Be specificInstead of “fix the site,” describe the behavior to change, what must be preserved, and the expected result.
What you will learn 01VS Code · VS Code Agent mode
What you will learn 02Selection · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “VS Code Agent mode” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
18 Chat synchronizationSupported chat and edit activity from the VS Code extension can be synchronized into the OrvixCode desktop history. Intermediate18 min⌄

Supported chat and edit activity from the VS Code extension can be synchronized into the OrvixCode desktop history.

Supported chat and edit activity from the VS Code extension can be synchronized into the OrvixCode desktop history.

Synced sessions may appear with a VS Code · … prefix, and edit events can be associated with the corresponding chat.

Desktop app closedSynchronization events can be queued and imported later when the desktop application is available.
What you will learn 01VS Code · Chat synchronization
What you will learn 02Selection · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “Chat synchronization” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →

Track checkpoint · 03 · VS Code Integration

Before moving on, complete these tasks without relying on guesswork.

  • Explain the key ideas of this path in your own words.
  • Complete one real task using the workflow from this path.
  • Verify your result with evidence such as a diff, test, build or terminal output.
Level · Advanced

04 · Models & Context

Choose Viona, cloud providers, local models and Combo intelligently; manage context and long code.

VionaLocal AIProvidersContext
19 VionaViona can be used as the default or primary model inside OrvixCode. Available model names and options can vary by version and configuration. Advanced23 min⌄

Viona can be used as the default or primary model inside OrvixCode. Available model names and options can vary by version and configuration.

Viona can be used as the default or primary model inside OrvixCode. Available model names and options can vary by version and configuration.

The VS Code panel can display the active model together with its connection state.

What you will learn 01Viona · Viona
What you will learn 02Local AI · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “Viona” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
20 Local modelsOrvixCode can run supported models locally through Ollama . Local model requests are sent to the Ollama service on your computer and do not require a separate cloud AI API key. Advanced17 min⌄

OrvixCode can run supported models locally through Ollama . Local model requests are sent to the Ollama service on your computer and do not require a separate cloud AI API key.

OrvixCode Local Models screen and Ollama model catalog
The Local Models screen brings hardware compatibility, model size and installation options together.

OrvixCode can run supported models locally through Ollama. Local model requests are sent to the Ollama service on your computer and do not require a separate cloud AI API key.

Installed models can appear under Local / Ollama in the model selector and can be used in compatible Ask, Edit, Agent, and Combo workflows.

Third-party licensesLocal models are published by their respective providers. Review each model's current license and usage terms before deployment.

Choosing a model

Use smaller coding models for limited-memory systems and larger models when you need more reasoning capacity and your hardware can support the memory requirements.

What you will learn 01Viona · Local models
What you will learn 02Local AI · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “Local models” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
21 Ollama and local model setupThe local model center is available under Settings → Local Models . It manages the Ollama runtime, hardware checks, free disk space, installed models, and troubleshooting tools. Advanced19 min⌄

The local model center is available under Settings → Local Models . It manages the Ollama runtime, hardware checks, free disk space, installed models, and troubleshooting tools.

The local model center is available under Settings → Local Models. It manages the Ollama runtime, hardware checks, free disk space, installed models, and troubleshooting tools.

  1. Open Local ModelsCheck whether the Ollama runtime is available.
  2. Prepare OllamaIf it is not installed, use the supported setup flow and verify the local service.
  3. Check compatibilityReview RAM, VRAM, and free-disk recommendations before downloading.
  4. Download a modelUse pause, resume, or cancel controls while the model is being downloaded.
  5. Select the modelAfter installation it should appear in the main model selector.

Local model tools

  • Start the Ollama service
  • Retry GPU mode after a safe CPU fallback
  • Open runtime logs
  • Open the model storage folder
  • Run compatibility checks
What you will learn 01Viona · Ollama and local model setup
What you will learn 02Local AI · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “Ollama and local model setup” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
22 AI providersOrvixCode can centralize Viona and supported external AI providers in one provider screen. The model list can be refreshed based on the models available to your account or API acce Advanced21 min⌄

OrvixCode can centralize Viona and supported external AI providers in one provider screen. The model list can be refreshed based on the models available to your account or API acce

OrvixCode can centralize Viona and supported external AI providers in one provider screen. The model list can be refreshed based on the models available to your account or API access.

ProviderTypical use
VionaPrimary OrvixCode model workflow
OpenAI / ChatGPTGPT and coding-capable models
Google GeminiGemini models
Anthropic / ClaudeClaude models
Groq, Mistral, DeepSeek, xAI and othersAdditional cloud model options where configured
Microsoft CopilotSupported Microsoft integration when account access is available
Provider availabilityExact model names, preview status, and account requirements can change independently of the OrvixCode UI.
What you will learn 01Viona · AI providers
What you will learn 02Local AI · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “AI providers” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
23 Combo modeCombo mode lets you assign different models to different stages of a coding task. For example, one model can plan, another can write code, and a third can review the result. Advanced23 min⌄

Combo mode lets you assign different models to different stages of a coding task. For example, one model can plan, another can write code, and a third can review the result.

Combo mode lets you assign different models to different stages of a coding task. For example, one model can plan, another can write code, and a third can review the result.

1. PlanAnalyze the request and project context.
2. BuildGenerate the implementation.
3. ReviewCheck for mistakes and regressions.
4. DeliverPrepare the final answer or edit package.
Mix local and cloudCompatible local Ollama models and cloud providers can be assigned to different roles when enabled.
Default stateCombo Mode is off by default. Toggle it from the + quick menu in the message composer.
What you will learn 01Viona · Combo mode
What you will learn 02Local AI · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “Combo mode” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
24 Smart adaptive contextOrvixCode prepares context according to the task instead of sending every project file on every request. Selected code, the active file, relevant project files, and chat history ca Advanced17 min⌄

OrvixCode prepares context according to the task instead of sending every project file on every request. Selected code, the active file, relevant project files, and chat history ca

OrvixCode prepares context according to the task instead of sending every project file on every request. Selected code, the active file, relevant project files, and chat history can be prioritized differently.

Adaptive context

When a request is too large for a model or local memory budget, OrvixCode can reduce context and retry with a smaller working set.

Selected code winsFor very large files, selecting the exact region you want to discuss gives the context system a strong signal about what should be prioritized.
What you will learn 01Viona · Smart adaptive context
What you will learn 02Local AI · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “Smart adaptive context” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
25 Long code and large project generationOrvixCode plans long-code requests and large multi-file project tasks separately, continues after output limits, and validates the file manifest against local dependencies. Advanced19 min⌄

OrvixCode plans long-code requests and large multi-file project tasks separately, continues after output limits, and validates the file manifest against local dependencies.

OrvixCode detects requests that clearly require large output even when the prompt is short. This is not limited to Python; long-code tasks are supported across HTML/CSS/JavaScript/TypeScript, Go, Rust, PHP, Ruby, Java/Kotlin, C/C++/C#, Swift, Dart, Lua, Scala, Elixir, F#, Solidity, Bash, PowerShell, SQL, and more.

Long output and continuation

  • Local models can use a larger output budget when appropriate.
  • If a response is cut by a token/context limit, OrvixCode can request continuation from the missing point.
  • Repeated overlap is cleaned when continuation chunks are merged.
  • Content from an unfinished fenced code block can still be preserved as code.

Large-project planning

  1. The request is analyzed and a project structure is planned.
  2. A manifest/file plan is created.
  3. Files are generated while dependencies and contracts are tracked.
  4. If imports reveal a missing local module, the plan can be expanded.
  5. Generation continues when output limits are reached.
  6. Basic consistency checks run at the end.
Chat stays visibleGenerated code remains in chat; OrvixCode does not automatically switch to the Code page when generation finishes. Use Open in Code manually when you want to move it into the editor.
Model capacityOrvixCode manages planning and continuation, but code quality and usable context still depend on the selected model and hardware.
What you will learn 01Viona · Long code and large project generation
What you will learn 02Local AI · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “Long code and large project generation” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →

Track checkpoint · 04 · Models & Context

Before moving on, complete these tasks without relying on guesswork.

  • Explain the key ideas of this path in your own words.
  • Complete one real task using the workflow from this path.
  • Verify your result with evidence such as a diff, test, build or terminal output.
Level · Advanced

05 · Project Productivity

Work with GitHub, backups, sessions, settings and keyboard workflows on real repositories.

GitHubBackupSessionsWorkflow
26 GitHub integrationUse the GitHub import flow to bring a repository into a local OrvixCode workspace. After the clone/import completes, the project behaves like a normal local folder and can particip Advanced21 min⌄

Use the GitHub import flow to bring a repository into a local OrvixCode workspace. After the clone/import completes, the project behaves like a normal local folder and can particip

Use the GitHub import flow to bring a repository into a local OrvixCode workspace. After the clone/import completes, the project behaves like a normal local folder and can participate in AI context.

What you will learn 01GitHub · GitHub integration
What you will learn 02Backup · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “GitHub integration” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
27 BackupsOrvixCode can keep backup information around file edits to reduce the risk of data loss. Depending on the edit workflow, earlier content can be retained so changes can be reviewed Advanced23 min⌄

OrvixCode can keep backup information around file edits to reduce the risk of data loss. Depending on the edit workflow, earlier content can be retained so changes can be reviewed

OrvixCode can keep backup information around file edits to reduce the risk of data loss. Depending on the edit workflow, earlier content can be retained so changes can be reviewed or reverted.

The VS Code integration also provides an undo flow for supported recent AI changes.

What you will learn 01GitHub · Backups
What you will learn 02Backup · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “Backups” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
28 Chats and sessionsOpen tabs and saved chats are separate concepts. Closing a tab does not have to delete its conversation history. Advanced17 min⌄

Open tabs and saved chats are separate concepts. Closing a tab does not have to delete its conversation history.

Open tabs and saved chats are separate concepts. Closing a tab does not have to delete its conversation history.

  • Reopen saved chats from the navigation area.
  • Delete chats from the relevant management controls.
  • Keep multiple chat tabs open at once.
  • Synced VS Code sessions can appear under their own titles.
What you will learn 01GitHub · Chats and sessions
What you will learn 02Backup · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “Chats and sessions” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
29 SettingsThe settings area groups the main OrvixCode preferences: General: default model, creativity, writing animation, sounds, navigation, and language. Customize: theme, font family, and text appearance. AI Providers: provider connections, model refresh, and Combo configuration. Local Models: Ol Advanced19 min⌄

The settings area groups the main OrvixCode preferences: General: default model, creativity, writing animation, sounds, navigation, and language. Customize: theme, font family, and text appearance. AI Providers: provider connections, model refresh, and Combo configuration. Local Models: Ol

The settings area groups the main OrvixCode preferences:

  • General: default model, creativity, writing animation, sounds, navigation, and language.
  • Customize: theme, font family, and text appearance.
  • AI Providers: provider connections, model refresh, and Combo configuration.
  • Local Models: Ollama service, compatibility, downloads, and logs.
  • Storage & Backup: data location and automatic file backup behavior.
  • Chat Management: review and remove stored conversations.
  • Setup / VS Code: desktop and extension integration options.
  • Troubleshooter: local system and connection checks.
  • Keyboard Shortcuts: Rebind actions such as send, new chat/project, save, undo/redo, run, terminal, stop AI response, Combo, and main navigation.
What you will learn 01GitHub · Settings
What you will learn 02Backup · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “Settings” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
30 Keyboard shortcutsOrvixCode provides customizable keyboard shortcuts for major app actions and detects conflicting assignments. Advanced21 min⌄

OrvixCode provides customizable keyboard shortcuts for major app actions and detects conflicting assignments.

Open Settings → Keyboard Shortcuts to rebind major application actions. Selecting an action opens a key-capture dialog for the new combination.

Examples of configurable actions

  • Send message / new line
  • Focus the message box
  • New chat and new project
  • Attach file and save
  • Ctrl+Z undo / Ctrl+Y redo
  • Run code and open terminal
  • Stop AI response
  • Toggle Combo Mode
  • Docs, feedback, and main navigation
  • Minimize, maximize, close, or send the app to background/tray
ConflictsIf a combination is already assigned to another action, OrvixCode detects the conflict and warns you.
What you will learn 01GitHub · Keyboard shortcuts
What you will learn 02Backup · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “Keyboard shortcuts” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →

Track checkpoint · 05 · Project Productivity

Before moving on, complete these tasks without relying on guesswork.

  • Explain the key ideas of this path in your own words.
  • Complete one real task using the workflow from this path.
  • Verify your result with evidence such as a diff, test, build or terminal output.
Level · Expert

06 · Security & Control

Protect API keys, permissions and repository boundaries while keeping AI productive.

SecuritySecretsPermissions
31 Theme, font, and appearanceOpen Settings → Customize to change OrvixCode's visual appearance. Expert26 min⌄

Open Settings → Customize to change OrvixCode's visual appearance.

Open Settings → Customize to change OrvixCode's visual appearance.

SettingExamples
ThemeOrvix Dark, Light, Midnight, Graphite, Forest, and other supported themes
FontInter, Segoe UI, Arial, Georgia, Cascadia Code
Text colorCustomize interface text using the available color control
ResetRestore OrvixCode appearance defaults
Appearance onlyChanging theme or font does not change your AI providers, projects, or chat configuration.
What you will learn 01Security · Theme, font, and appearance
What you will learn 02Secrets · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “Theme, font, and appearance” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
32 File safetyOrvixCode aims to keep AI-driven file operations visible and reviewable. The edited file and change state can be shown in the chat or edit report. Expert20 min⌄

OrvixCode aims to keep AI-driven file operations visible and reviewable. The edited file and change state can be shown in the chat or edit report.

OrvixCode aims to keep AI-driven file operations visible and reviewable. The edited file and change state can be shown in the chat or edit report.

When automatic apply is disabled, a prepared edit can wait for user approval before being written.

What you will learn 01Security · File safety
What you will learn 02Secrets · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “File safety” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
33 API keysExternal AI providers require the credentials issued by the relevant service. Expert22 min⌄

External AI providers require the credentials issued by the relevant service.

External AI providers require the credentials issued by the relevant service.

Do not expose API keysNever place API keys in source code, public repositories, screenshots, or public web pages.

The VS Code extension is designed to use the provider configuration exposed through OrvixCode's connection layer rather than asking you to copy secrets into every editor workflow.

What you will learn 01Security · API keys
What you will learn 02Secrets · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “API keys” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
34 File permissionsMulti-file tasks can have a wider change scope than a single-file edit. Depending on your version and settings, OrvixCode can request permission for one file or for a broader propo Expert24 min⌄

Multi-file tasks can have a wider change scope than a single-file edit. Depending on your version and settings, OrvixCode can request permission for one file or for a broader propo

Multi-file tasks can have a wider change scope than a single-file edit. Depending on your version and settings, OrvixCode can request permission for one file or for a broader proposed change.

Agent permissionsBefore approving a multi-file operation, review the task scope and the files that are expected to change.
What you will learn 01Security · File permissions
What you will learn 02Secrets · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “File permissions” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →

Track checkpoint · 06 · Security & Control

Before moving on, complete these tasks without relying on guesswork.

  • Explain the key ideas of this path in your own words.
  • Complete one real task using the workflow from this path.
  • Verify your result with evidence such as a diff, test, build or terminal output.
Level · Expert

07 · Troubleshooting

Diagnose provider, VS Code, local-model and application failures using evidence instead of guesses.

DebuggingRecoveryDiagnostics
35 General troubleshootingAI is not responding Confirm that an active model is selected and available. For cloud models, verify provider credentials and internet access. For local models, confirm that the O Expert26 min⌄

AI is not responding Confirm that an active model is selected and available. For cloud models, verify provider credentials and internet access. For local models, confirm that the O

AI is not responding

  • Confirm that an active model is selected and available.
  • For cloud models, verify provider credentials and internet access.
  • For local models, confirm that the Ollama service is running.
  • In VS Code, use the connection test and review any error details.

File changes are not applying

  • Check the edit package state.
  • If Auto Apply is enabled, the change may already be applied.
  • Verify write permissions and VS Code Workspace Trust.
  • Review the diff and retry the edit if needed.
What you will learn 01Debugging · General troubleshooting
What you will learn 02Recovery · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “General troubleshooting” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
36 Viona “request size limit exceeded”This error can appear when the active file, project context, and chat history together exceed the model request limit. Expert20 min⌄

This error can appear when the active file, project context, and chat history together exceed the model request limit.

This error can appear when the active file, project context, and chat history together exceed the model request limit.

OrvixCode can reduce the context size and retry with a smaller context profile after an oversized request.

Best resultIn very large files, select the exact code region you want to change. Selected code receives higher context priority.
What you will learn 01Debugging · Viona “request size limit exceeded”
What you will learn 02Recovery · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “Viona “request size limit exceeded”” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
37 VS Code troubleshootingRefresh the Extensions view, verify internet access, and search for OrvixCode again. Newly published updates can take time to propagate. Expert22 min⌄

Refresh the Extensions view, verify internet access, and search for OrvixCode again. Newly published updates can take time to propagate.

Extension is missing from search

Refresh the Extensions view, verify internet access, and search for OrvixCode again. Newly published updates can take time to propagate.

Workspace is not trusted

File-editing features may be restricted until the workspace is trusted in VS Code.

Panel opens but AI does not respond

Run the connection test, then check cloud-provider access or the local OrvixCode/Ollama status.

Simple chat includes irrelevant project context

Update the extension and reload VS Code. Current builds are designed to isolate simple greetings from project context.

Context-menu command does not start

Confirm that code is selected, retry the command, and use a new OrvixCode chat if the issue persists.

What you will learn 01Debugging · VS Code troubleshooting
What you will learn 02Recovery · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “VS Code troubleshooting” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
38 Local model troubleshootingOpen Settings → Local Models , check the runtime state, and use the service start control. Review logs if startup continues to fail. Expert24 min⌄

Open Settings → Local Models , check the runtime state, and use the service start control. Review logs if startup continues to fail.

Ollama is not running

Open Settings → Local Models, check the runtime state, and use the service start control. Review logs if startup continues to fail.

“failed to allocate buffer / kv cache”

The selected model or context length may be too large for available RAM/VRAM. OrvixCode can retry with smaller context levels.

Example context fallback
8192 → 6144 → 4096 → 3072 → 2048

CUDA / GPU error

A safe CPU fallback can keep the model usable. You can retry GPU mode later from the local model controls.

Local model is too slow

Try a smaller model, close memory-heavy applications, and confirm that compatible GPU acceleration is active.

What you will learn 01Debugging · Local model troubleshooting
What you will learn 02Recovery · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “Local model troubleshooting” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
39 FAQCan OrvixCode work without internet? + Yes, selected features can work offline when you use a previously downloaded local Ollama model. Cloud providers and new model downloads stil Expert26 min⌄

Can OrvixCode work without internet? + Yes, selected features can work offline when you use a previously downloaded local Ollama model. Cloud providers and new model downloads stil

Yes, selected features can work offline when you use a previously downloaded local Ollama model. Cloud providers and new model downloads still need internet access.
No. OrvixCode has its own desktop interface; the VS Code extension is optional.
Yes. A clear change request can produce an applicable edit package.
Agent mode is designed for tasks that span several files.
No. Models running through local Ollama do not require a separate cloud AI API key.
Yes. Long-output requests can use larger output budgets and continuation handling when the selected model supports it.
This package was updated on September 1, 2026 for the OrvixCode 1.2.0 feature set.
What you will learn 01Debugging · FAQ
What you will learn 02Recovery · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “FAQ” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →

Track checkpoint · 07 · Troubleshooting

Before moving on, complete these tasks without relying on guesswork.

  • Explain the key ideas of this path in your own words.
  • Complete one real task using the workflow from this path.
  • Verify your result with evidence such as a diff, test, build or terminal output.
Level · Advanced

08 · Platform & Release Operations

Understand Learn, service status, releases and how the OrvixCode platform communicates changes.

LearnStatusReleases
40 OrvixCode Learning CenterLearn Ask, Edit, Agent, project context, terminal workflows, local models, and safe development practices with OrvixCode Learn. Advanced17 min⌄

Learn Ask, Edit, Agent, project context, terminal workflows, local models, and safe development practices with OrvixCode Learn.

OrvixCode Learn complements the reference documentation with step-by-step, directly applicable lessons without requiring video.

What you will learn 01Learn · OrvixCode Learning Center
What you will learn 02Status · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “OrvixCode Learning Center” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
41 Announcements & Service StatusFollow live OrvixCode service status, maintenance notices, product updates, and urgent alerts. Advanced19 min⌄

Follow live OrvixCode service status, maintenance notices, product updates, and urgent alerts.

The official status page shows the website, docs, downloads, and AI services. Admin announcements appear immediately on the public page and machine-readable feeds.

OrvixCode StatusOpen status page →
JSON · RSS
What you will learn 01Learn · Announcements & Service Status
What you will learn 02Status · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “Announcements & Service Status” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →
42 Release & Latest DownloadInstall the latest stable OrvixCode release from the Microsoft Store. Advanced21 min⌄

Install the latest stable OrvixCode release from the Microsoft Store.

Download links use a centralized release setting. When an administrator publishes a new stable version, the displayed version and download target update across the platform.

Microsoft Store
https://orvixcode.orvixgames.com/download.php?lang=en-us

Download latest release →

What you will learn 01Learn · Release & Latest Download
What you will learn 02Status · Practice lab
What you will learn 03Progress · Diff · Test · Review

Practice lab

Use the lesson in a real OrvixCode workspace instead of only reading it.

1Open a small real project and identify where this lesson applies.
2Ask OrvixCode to explain the current state before making changes.
3Apply one controlled change and verify it with the project’s real checks.
Apply the “Release & Latest Download” concept to this project. Inspect and explain the current state first. Do not touch unrelated files. Make the smallest safe change, run the relevant build/test/terminal verification, and summarize the real result.
Open detailed Docs reference →

Track checkpoint · 08 · Platform & Release Operations

Before moving on, complete these tasks without relying on guesswork.

  • Explain the key ideas of this path in your own words.
  • Complete one real task using the workflow from this path.
  • Verify your result with evidence such as a diff, test, build or terminal output.
CAPSTONE

Capstone projects

Finish the academy with larger projects that combine multiple OrvixCode skills.

Project 1

Build a real product from zero

2–3 hours

Objective: Use OrvixCode Agent to build a small real web product and finish it with a verification loop.

  • Turn requirements into a plan first.
  • Implement at least three user-facing features.
  • Verify responsive behavior.
  • Run build/tests or browser-console checks.
  • Report the final diff and changed files.
Start this project →
Project 2

Bug hunt in an existing repository

2 hours

Objective: Enter an unfamiliar project, reproduce a bug, make the smallest safe fix and add regression coverage.

  • Analyze repository structure first.
  • Record a reproducible failure.
  • Explain root cause before editing.
  • Apply a minimal patch.
  • Run the same verification again.
Start this project →
Project 3

Local model and provider resilience

2–4 hours

Objective: Exercise local-model, provider fallback and Agent recovery paths with real failure scenarios.

  • Create an empty-response scenario.
  • Observe provider timeout and fallback.
  • Check tool-call compatibility.
  • Collect evidence from developer logs.
  • Do not accept silent failure.
Start this project →
Project 4

Large-repo refactor and security review

4–6 hours

Objective: Plan and execute a multi-file refactor, verify it, then run a separate security and permission review.

  • Map affected files first.
  • Write down public behavior constraints.
  • Work in small patches.
  • Run tests/build/typecheck.
  • Review secrets, permissions and unrelated file changes.
Start this project →
ORVIXCODE ACADEMY · CERTIFICATE

Academy completion certificate

Complete every lesson to unlock a printable completion certificate.

Enter the name that should appear on the certificate. Locked until 100% completion When unlocked, print or save as PDF. The certificate is formatted as one A4 landscape page.
ORVIXCODEOrvixCode Academy
ACADEMY COMPLETION
ORVIXCODE
ACADEMY
COMPLETION
ORVIXCODE ACADEMY

Certificate of Completion

This certificate is proudly presented to
—
for successfully completing the full OrvixCode Academy curriculum and demonstrating practical competence in AI-assisted software development, repository workflows, debugging, testing, model usage and safe coding practices.
42Lessons completed
8Learning paths
14+Estimated study · hours
Issued—
OrvixCode Orvix Games AI Studio Academy & Platform
Certificate ID—
Issued by OrvixCode Academy · orvixcode.orvixgames.com
LOCKED