Build with OxCode

Overview

OxCode works step by step, asks before risky actions, and keeps your project history close at hand, so the editor chat becomes your main surface for real engineering work.

Use it for feature work, bug fixes, refactors, code review, test runs, build verification, and project exploration. Like GitHub Copilot or Codex it lives in your editor, but its main surface is a full editor chat with persistent sessions, context controls, command approvals, and a dedicated Memory view in the OxCode Activity Bar.

Install

Install OxCode - AI Software Engineer from the Visual Studio Code Marketplace, or search “OxCode” in the Extensions view. The Marketplace build uses the hosted Oxlo.ai gateway, so you never build the source, run a backend, or manage provider API keys.

Sign in

Open the OxCode panel from the Activity Bar and choose Continue with Google. OxCode is in invite-only alpha, so use an email that has been granted access. Your session is stored in VS Code SecretStorage, never in a file.

Open chat

Run OxCode: Open Chat from the Command Palette, use the editor-title action, or continue a saved session, then describe the task. The composer supports attached files, the active file, selected code, terminal output, slash commands, and mode selection.

# try prompts like:
Review this project and explain the main architecture.
Fix the TypeScript errors in the current file.
Add a health check endpoint and run the relevant tests.
/debug diagnose why this command is failing.
/security review this API route for risky patterns.

Sessions

Conversations are saved per workspace in the Sessions view, where you can search, rename, reopen, or delete them. Sessions are redacted before being written to disk so secrets never land in local history, and recent sessions help the next task start warm instead of cold.

Orchestrated workflow

Larger tasks run through an orchestrated lifecycle: OxCode classifies the request, gathers a working dossier, plans the work, executes focused steps, and verifies the result before calling the task done.

• Plan card: larger tasks show steps, checks, amendments, and verification status.
• Scoped execution: complex steps run as nested task cards with their own progress.
• Verification: OxCode uses diagnostics, tests, builds, and command checks when relevant.
• Session recall: recent workspace conversations help the next task start warm.

Modes

OxCode is built around three modes. Dev is live today. Vibe and Teach are coming soon. Requests are routed across the Oxlo.ai model fleet behind the scenes, so the interface focuses on what you want to do rather than raw model IDs.

Skills

A skill is a set of instructions that shapes how OxCode approaches a particular kind of work, such as reviewing code, designing an API, or teaching. It reaches every stage of a run, so the plan is written differently, not just the final answer.

OxCode often picks one for you. When your request clearly matches an installed skill, it arms that skill itself and says so on screen. You can also choose one yourself, and you can install more from our catalogue or from a third-party source.

Open OxCode: Skills and Plugins from the Command Palette to see what you have installed. One skill is active at a time.

Read the Skills guide for installing, third-party sources, and writing your own.

Command approval

Inside Dev mode, approval controls decide how much OxCode does on its own: ask before every change, auto-run safe actions, or grant full access in a trusted workspace. When a command needs review you can run it, decline it, allow it for this session, or always allow that exact command pattern for the workspace. Risky commands always pause for your confirmation.

Memory

OxCode keeps durable project knowledge in a dedicated Memory view. Project memory lives in .oxcode-memory/ inside the current project and global memory lives under ~/.oxcode/global, both as local Markdown notes you can read and edit.

Import context

Bring history from other tools into OxCode’s memory so a new project starts with what you already know.

• Import sessions from Claude Code, Codex, Cursor, or Antigravity into local memory.
• Use @file mentions when a task depends on a specific file.
• Use Send Selection to Chat for focused changes in the editor.
• Use Send to OxCode from the terminal, or ask OxCode to read recent terminal output.

Commands and settings

The Command Palette exposes Open Chat, Sign In, Sign Out, Clear Chat, Switch Mode, Send Selection, Send to OxCode, the memory commands, and context import. Default shortcuts: Ctrl/Cmd + Shift + O sends the editor selection and Ctrl/Cmd + Alt + Shift + O sends terminal output.

OxCode uses the hosted gateway by default. Advanced settings can toggle the orchestrated workflow, control anonymous telemetry counters, and tune routing for specialized setups. Most users never need to change them.

Privacy and security

To fulfil a task, OxCode can send the prompt, active-file context, selected code, diagnostics, explicitly attached terminal output, files read by tools, and tool results through the hosted gateway so the selected model can help. Anonymous orchestration telemetry contains event names and counters only, never prompts, code, or file paths.

Troubleshooting

If OxCode has no project context, open a folder in VS Code before sending a task. It operates on the current workspace folder, and file mentions only resolve inside it. If sign-in mentions invite-only access, use the Google account that was invited or request access below.