Omaya Codex
Your AI co-engineer, right inside VS Code.
Omaya Codex is an agentic AI coding assistant that lives in a chat panel in your
editor. Describe what you want in plain language — Omaya reads your code,
searches the project, edits files, and runs commands (with your approval) to get
the job done, all without leaving VS Code.
It connects to the Omaya backend, a secure gateway that handles
authentication, your subscription, and model access — so provider API keys and
billing stay on the server, never in the editor.
Why Omaya Codex
- It acts, it doesn't just answer. One request can read files, search the
project, edit code, run the test suite, and report back.
- It uses the editor's real intelligence. Omaya reads VS Code's own
type and lint diagnostics, finds references, and jumps to definitions — the
same language servers you use, not guesswork over grep output.
- It checks its own work. After editing, Omaya re-runs your verifier and
fixes what it broke before handing the task back.
- Nothing to configure. No API key, no endpoint, no model file. Sign in and
start.
- You stay in control. Destructive commands always ask first, and any turn
that edited files can be undone from the transcript.
Requirements
- VS Code 1.93.0 or newer
- An Omaya account with an active plan, created on the Omaya web app. A
free plan is available; paid plans add premium models and higher limits.
The extension cannot be used without a plan — chat requests are gated on one.
- An internet connection (the extension reaches the Omaya backend for every chat
request).
You do not need your own provider API key. Access to Anthropic, OpenAI,
Kimi and DeepSeek models comes with your Omaya plan, and the keys stay on the
server.
Getting started
1. Install
Click Install on this page, or search "Omaya Codex" in the Extensions
view (Ctrl+Shift+X) inside VS Code.
After installing, look for the Omaya Codex icon in the Activity Bar (left
edge). Click it to open the chat panel.
Tip: prefer the chat on the right? Right-click the icon →
Move to Secondary Side Bar.
2. Create an account and pick a plan
Open the Omaya web app, sign up, and pick a plan. The free plan activates
instantly — no card required.
3. Sign in from VS Code
- Open the Omaya Codex panel and click Continue with Omaya.
- Your browser opens, showing the same short verification code as VS Code.
- Confirm in the browser. VS Code detects the approval automatically and drops
you straight into chat — no copy-pasting tokens.
Sign-in uses a secure browser-based device flow. Your password is never
entered into, or stored by, the extension.
Nothing to configure. There is no server URL, API key, or endpoint setting
to fill in. The web app address is reported by the backend.
What it can do
Across a single request, Omaya Codex can chain all of these:
|
|
| Read & understand |
Open single or multiple files, inspect file info, and get a high-level view of your workspace. |
| Language intelligence |
Read live type and lint diagnostics, find every reference to a symbol, and jump to its definition — via VS Code's own language servers. |
| Search |
Fast filename globbing and full-text content search across the project. |
| Edit & create |
Write new files, make precise in-place edits, create directories, and move, rename or delete files. |
| Run commands |
Execute shell commands, launch long-running tasks in the background, stream their output, and stop them. |
| Browse the web |
Search the web and fetch a page when the answer isn't in the repository. |
| Delegate |
Spin off a focused sub-agent for a self-contained piece of research, keeping the main conversation on track. |
| Plan |
Maintain a live to-do list so you can see what's done and what's next. |
| Undo a turn |
Roll back any turn that edited files, restoring that turn and everything after it. |
| Use your own tools |
Connect MCP servers to reach external systems — see MCP servers. |
Point Omaya at a project once with Omaya Codex: Generate OMAYA.md and it
writes a project-context file that every later chat reads automatically.
Every file edit and command runs with your awareness — see
Safety & approvals.
Using the chat
- Open chat — click the Omaya Codex Activity Bar icon, or run
Omaya Codex: Open Chat from the Command Palette (
Ctrl+Shift+P).
- New chat — the + button in the panel header, or
Ctrl+Shift+L
(Cmd+Shift+L on macOS) when the chat panel is focused. A new chat clears the
conversation and resets any per-session command approvals.
- Pick a model — use the dropdown next to the input box. Which models appear
depends on your subscription plan.
- Stop a response — the send button becomes a stop button while the agent
is working.
- Watch your context — the panel shows how much of the model's context window
the conversation is using, so you know when to start fresh.
Commands
Open the Command Palette (Ctrl+Shift+P) and type "Omaya":
| Command |
Description |
| Omaya Codex: Open Chat |
Reveal and focus the chat panel. |
| Omaya Codex: New Chat |
Start a fresh conversation. |
| Omaya Codex: Generate OMAYA.md (Project Context) |
Write a project-context file the agent reads on every future chat. Needs an open folder. |
| Omaya Codex: Show Debug Log |
Open the diagnostic log — the first thing to check when something misbehaves. |
| Omaya Codex: Sign Out |
Sign out. Asks for confirmation, and revokes your session on the server. |
| Keybinding |
Action |
When |
Ctrl+Shift+L / Cmd+Shift+L |
New Chat |
Chat panel focused |
Settings
Search "Omaya" in Settings (Ctrl+,):
| Setting |
Default |
Description |
omayaCodex.sessionRating.enabled |
true |
Occasionally show a one-tap "How's this session going?" bar above the input. It appears rarely — turn it off to never see it. |
omayaCodex.mcpServers |
{} |
MCP servers to launch. See below. |
There is deliberately no backend-URL setting.
MCP servers
Model Context Protocol servers give the agent access to external systems. Add
them in settings.json using the standard mcpServers shape:
"omayaCodex.mcpServers": {
"github": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-github"],
"env": { "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_..." }
}
}
Reload the window afterwards. Their tools reach the agent as
mcp__<server>__<tool> and always require your confirmation before running.
Safety & approvals
Omaya Codex can run shell commands and modify your files, so it ships with
guardrails:
- Every command is risk-classified — safe (read-only, e.g.
git status),
moderate (build, test), high (installs, git push, permission changes), or
destructive.
- Destructive commands always ask.
rm -rf, git push --force,
DROP TABLE, disk formatting, or piping a download into a shell always
require explicit confirmation. This cannot be turned off.
- Session-scoped trust. You can allow a repetitive safe command for the rest
of the session; that trust clears the moment you start a new chat or sign out.
- Confined to your workspace. File tools resolve every path inside the
workspace root, including defences against symlinks that point outside it.
Privacy & security
- Tokens are encrypted. Access and refresh tokens live in VS Code's
SecretStorage (your OS keychain) — never in plaintext settings or files.
- No passwords in the editor. Sign-in happens in your browser via a device
flow; the extension never sees your password.
- Keys stay server-side. LLM provider API keys live on the Omaya backend, not
in the extension.
- Least-privilege sessions. Signing out revokes your refresh token on the
server. Admin privileges are always re-verified with the backend, never trusted
from a locally decoded token.
Troubleshooting
| Problem |
What to do |
| "No active subscription found." |
Your plan is missing or expired. Subscribe or renew in the Omaya web app, then try again. |
| "Failed to fetch" / can't reach the backend. |
Check your internet connection and any corporate proxy or firewall — the extension needs HTTPS access to the Omaya backend. There is nothing to reconfigure on your side. |
| Stuck on the sign-in screen. |
The verification code may have expired. Click Cancel and start again. |
| A model disappeared from the dropdown. |
Model availability follows your plan. Start a new chat to refresh the list. |
| Something else. |
Run Omaya Codex: Show Debug Log and include it when you contact support. |
Still stuck? Run Omaya Codex: Sign Out, then sign in again — that resets the
session cleanly.
Release notes
1.0.0 — first public release: agentic chat with multi-model access, file and
command tools, language intelligence, web research, sub-agents, per-turn undo,
MCP servers, and the Generate OMAYA.md project-context command.
The full history is on the Changelog tab of this listing.
License
Proprietary — © Omaya. All rights reserved. Not licensed for redistribution.